Quick Beginnings

Step 2. Configure the SNA Node

To start IBM Communications Server for NT, click on the Start button, then select Programs->IBM Communications Server->SNA Node Configuration. The IBM Communications Server SNA Node Configuration screen appears.

From the File button on the menu bar, select New->Advanced. The Configuration options field appears.

To configure the DB2 Connect workstation, you need to configure the following Configuration options:

• "Configure Node"
• "Configure Devices"
• "Configure the Gateway" (used with Communications Server for Windows NT SNA Client only)
• "Configure Connections"
• "Configure Partner LU 6.2"
• "Configure Modes"
• "Configure Local LU 6.2"
• "Configure CPI-C Side Information"
• "Configure Transaction Programs". (Used when clients will connect using APPC. For example, a Communications Server for Windows NT SNA Client connecting to a Communications Server, DB2 Client Application Enablers connecting to a DB2 Connect Enterprise Edition workstation, or DRDA clients connecting to a DRDA AS DB2 Universal Database server.)

After each step, you return to the window that has the Configuration options field.

Configure Node

To configure the node:

1. In the Configuration options field, select Configure Node, then click on the New button. The Define the Node window appears.

2. In the Fully qualified CP name fields, type in the network name (9) and the local control point name (10) (SPIFNET.NYX1).

3. Optionally, in the CP alias field, type in a CP alias. If you leave this blank the local control point name (10) will be used (NYX1).

4. In the Local Node ID fields, type in the block ID (13) and the physical unit ID (14) (05D.27509).

5. Ensure that the End Node radio button is selected (this is the default).

6. Click on OK.

Configure Devices

To configure the device:

1. In the Configuration options field, select Configure devices.

2. Ensure that in the DLCs field, the appropriate DLC is highlighted. For example, LAN.

3. Click on the New button. The appropriate window appears with default values displayed. For example, the Define a LAN device window.

4. Click on OK to accept the default values.

Configure the Gateway

You need to perform this step only if you are setting up Communications Server to accept requests from Communications Server for Windows NT SNA Client, as described in Chapter 15. "Configuring IBM Communications Server for Windows NT SNA Client". To configure the gateway:

1. In the Configuration options field, select Configure the Gateway, then click on the New button. The Define Gateway window appears.

2. Click on the Select SNA Clients tab.

3. Ensure that there is a check mark in the Enable SNA API Client Services check box.

4. Click on OK to accept the default values.

Configure Connections

To configure the connections:

1. In the Configuration options field, select Configure connections.

2. Ensure that in the DLCs field, LAN is highlighted.

3. Click on the New button. The Define a LAN connection window appears.

4. On the Basic tab panel:

   1. In the Link station name field, type in the name (7) from the worksheet (LINKHOST).

   2. In the Destination address field, type in the address (8) from the worksheet (400009451902).

5. On the Security tab panel:

   1. In the Adjacent CP name fields, type in the network ID (3) and the Control Point name (4) (SPIFNET.NYX).

   2. In the Adjacent CP type field, select Back-level LEN.

   3. Ensure that TG number is set to 0 (the default).

   4. Click on OK.

Configure Partner LU 6.2

To configure the partner LU:

1. In the Configuration options field, select Configure partner LU, then click on the New button. The Define a partner LU 6.2 window appears.

2. In the Partner LU name fields, type in the network ID (3) and the partner LU name (2) (SPIFNET.NYM2DB2).

3. In the Partner LU alias field, type in the partner LU name (2) from the worksheet (NYM2DB2).

4. If you are configuring Communications Server for SNA Clients, in the Fully-qualified CP name fields, type in the network ID (3) and the adjacent control point SSCP name (4) (SPIFNET.NYX).

   Leave the other fields blank.

5. Click on OK.

Configure Modes

To configure the mode:

1. In the Configuration options field, select Configure modes, then click on the New button. The Define a mode window appears.

2. In the Mode name field (6), type in the mode name (IBMRDB).

3. Click on the Advanced tab and ensure that the Class of Service Name is set to #CONNECT.

   Accept the defaults for the other fields.

4. Click on OK.

Configure Local LU 6.2

To configure the local LU 6.2:

1. In the Configuration options field, select Configure local LU 6.2, then click on the New button. The Define a local LU 6.2 window appears.

2. In the Local LU name field, type in the name (11) from the worksheet (NYX1GW01).

3. Type in a value for the LU session limit field. The default, 0, specifies the maximum allowed value.

   Accept the defaults for the other fields.

4. Click on OK.

Configure CPI-C Side Information

To configure the CPI-C side information:

1. In the Configuration options field, select Configure CPI-C side information, then click on the New button. The Define CPI-C side information window appears.

2. In the Symbolic destination name field, type in the name (16) from the worksheet (DB2CPIC).

3. In the Mode name field, type in the name (15) from the worksheet (IBMRDB).

4. Click on the radio button beside Use Partner LU alias and select a Partner LU alias.

5. Specify the TP name. In the TP name field:

   • To specify a non-service TP, in the TP name field, type in the name of the non-service TP, for example DB2DRDA, and ensure that there is no check mark in the Service TP check box.

   • To specify a service TP, in the TP name field, type in the name of the service TP, for example 076DB, and ensure that there is a check mark in the Service TP check box.

   Accept the defaults for the other fields.

6. Click on OK.

Configure Transaction Programs

You need to configure Transaction Programs if you want Communications Server to accept APPC clients. For DB2 users, examples of this include:

• Configuring Communications Server to accept SNA Client requests as described in Chapter 15. "Configuring IBM Communications Server for Windows NT SNA Client".

• Configuring a DB2 Universal Database server to act as a DRDA AS, which accepts requests from DRDA hosts. (This does not apply to DB2 Connect users).

• Configuring a DB2 Universal Database server to accept APPC clients.

You should create a service TP and a non-service TP.

To create a service Transaction Program:

1. In the Configuration options field, select Configure Transaction Programs, then click on the New button. The Define a Transaction Program window appears.

2. On the Basic tab window:

   • To specify a non-service TP, in the TP name field, type in the name of the non-service TP, for example DB2DRDA, and ensure that there is no check mark in the Service TP check box.

   • To specify a service TP, in the TP name field, type in the name of the service TP, for example 076DB, and ensure that there is a check mark in the Service TP check box.

3. If you are configuring Communications Server for use with Communication Server SNA Client, on the Advanced tab window, ensure that there is a check mark in the For SNA API Client use check box.

   Accept the defaults for the other fields.

4. Click on OK.

To create a non-service Transaction Program:

1. In the Configuration options field, select Configure Transaction Programs, then click on the New button. The Define a Transaction Program window appears.

2. On the Basic tab window:

   • In the TP name field, type in the name (17) from the worksheet (DB2DRDA).

   • Ensure that there is no check mark in the Service TP check box.

3. If you are configuring Communications Server for use with Communication Server SNA Client, on the Advanced tab window, ensure that there is a check mark in the For SNA API Client use check box.

   Accept the defaults for the other fields.

4. Click on OK.

Save the Configuration

To save the configuration:

1. From the File button on the menu bar, select Save As. The Save As window appears.

2. Type in a file name, for example ny3.acg, then click on OK.

3. In the dialog box that appears, you are asked if you want this configuration to be the default. Click on the Yes button.

You now need to update the DB2 directories, test the connection, and bind utilities and applications to the server. The easiest way to do this is to use the CCA as described in Chapter 9. "Configuring DRDA Host Connections on OS/2 or Windows NT Workstations". However, you can also perform these steps manually as described in the sections that follow.

[ DB2 List of Books | Search the DB2 Books ]