IBM GC09-2830-00 manual Conguring Microsoft SNA Server for Windows NT

b.Type in the IP address of the server (for example, 123.123.123.123).

c.Click on OK.

Step 5. Con®gure CPI-C Side Information

a.In the Con®guration options box, select the Con®gure CPI-C side information option and click on the New push button. The De®ne CPI-C side information window opens.

b.Enter the symbolic destination name („16…) in the Symbolic destination name ®eld.

c.Enter your Local LU alias („12…) in the Local LU alias ®eld.

d.Enter the mode name („15…) in the Mode name ®eld.

e.Enter the transaction program name („17…) in the TP name ®eld.

f.Select the For SNA API Client use check box for this transaction program.

g.Enter the network ID („3…) and partner LU name („2…) in the Partner LU name ®eld.

h.Click on OK.

Step 6. Save the Con®guration

a.Select File->Save As from the menu bar. The Save As window opens.

b.Type in a ®le name, and click on the Save push button.

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 Microsoft SNA Server for Windows NT

This section describes how to con®gure Microsoft SNA Server Version 4.0 for Windows NT on your DB2 Connect workstation to connect to host or AS/400 database servers using APPC. Although Microsoft SNA Server will run on Windows NT 4.0 Workstation, Windows NT 4.0 Server is recommended.

For instructions on how to con®gure Microsoft SNA Client for Windows NT, go to ªCon®guring Microsoft SNA Clientº on page 88.

You can de®ne the properties of your SNA connections in the Microsoft SNA Server Manager (Server Manager). The Server Manager uses an interface

Chapter 7. Con®guring APPC Communications on the DB2 Connect Workstation 79