IBM GC09-2830-00 manual Catalog the APPC or APPN Node

__ a. The Symbolic destination name („16…) de®ned at the Microsoft SNA Server for the Partner LU („2…) of the target host or AS/400 database server.

__ b. The real database name („5…).

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º and the sections that follow.

Step 3. Catalog the APPC or APPN Node

You must add an entry to the DB2 Connect workstations's node directory to describe the remote node. In most cases, you will add an APPC node entry to the node directory. For OS/2, Windows 9x, and Windows NT, you can alternatively add an APPN node entry if your local SNA node has been set up as an APPN node.

To catalog the node, perform the following steps:

Step 1. Log on to the system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority.

Step 2. To catalog an APPC node, specify the chosen alias (node_name), Symbolic destination name (sym_dest_name), and the APPC security type (security_type) that the client will use for the APPC connection. Enter the following commands:

catalog "appc node node_name remote sym_dest_name security security_type"

terminate

The sym_dest_name parameter is case-sensitive and must exactly must match the case of the Symbolic destination name you de®ned previously.

For example, to catalog a remote database server with the Symbolic destination name DB2CPIC on the node called db2node, using APPC Security type program, enter the following commands:

catalog appc node db2node remote DB2CPIC security program terminate

Step 3. To catalog an APPN node, specify the chosen alias (node_name), the network ID („9…), the remote partner LU („4…), the transaction

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