IBM GC09-2830-00 manual to register Communications Server with the default conguration, or

To automatically start Communications Server when the machine is booted, you can register it as a Windows NT Service.

To register Communications Server as an NT service execute one of the following commands:

csstart -a

to register Communications Server with the default con®guration, or:

csstart -a c:\ibmcs\private\your.acg

where c:\ibmcs\private\your.acg represents the fully quali®ed name of the non-default Communications Server con®guration ®le you want to use.

Whenever your machine is booted in the future, Communications Server will be started automatically with the required con®guration ®le.

You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection.

The easiest way to do this is to use the Client Con®guration Assistant (CCA). For more information on using the CCA, go to ªChapter 6. Con®guring DB2 Connect to Host or AS/400 Communications Using the CCAº on page 57. However, you can also perform these steps manually, as described in ªStep 3. Catalog the APPC or APPN Nodeº on page 91 and the sections that follow.

Con®guring IBM eNetwork Communications Server for Windows NT SNA API Client

Read this section if you have a Windows NT workstation that has IBM eNetwork Communications Server for Windows NT SNA API Client Version

5.0or higher installed and you want to connect to an IBM eNetwork Communications Server for Windows NT server.

The Communications Server for Windows NT server and its SNA API client act as a split client. This con®guration requires that you have an APPC-enabled application (such as DB2 Connect) running on the SNA API client workstation.

The instructions in this section use a Windows NT client. The instructions for other supported operating systems are similar; refer to your Communications Server for Windows NT documentation for more information.

76Quick Beginnings