Installation and Configuration Supplement

2. Update the APPC Profiles on the DB2 Connect Workstation

Use the completed worksheet in Table 30 to configure DB2 Connect APPC communications for access to a remote host or AS/400 database server.

Figure 00002671 not displayed.
Go to the sections that describe how to configure APPC communications on the platforms that are present in your network:

Configuring IBM eNetwork Communications Server for OS/2

This section describes how to manually configure APPC communications between your DB2 Connect for OS/2 workstation and host or AS/400 database servers.

Before you begin, ensure that your workstation has CS/2 V5 or later for OS/2 installed. The steps in this section describe how to use IBM eNetwork Communications Server Version 5. If you have Communications Manager for OS/2 V.1.x, the steps you perform are similar, but the interface and menu names are different.

For more information on setting up your environment, refer to the online help supplied with CS/2, or to the following publications:

The following assumptions have been made:

Use the Your Value entries from the worksheet in Table 25 to complete the steps below.

Figure 00002674 not displayed.
These instructions describe how to create new profiles within a new configuration. If you are modifying an existing configuration, you may need to delete some profiles before you can verify the configuration.

To configure your system, perform the following steps:

Step  1.

Start a new configuration

  1. Double-click on the IBM eNetwork Communications Server icon.
  2. Double-click on the Communications Manager Setup icon.
  3. In the Communications Manager Setup window, click on the Setup push button.
  4. In the Open Configuration window, provide a name for a new configuration file and click on OK. The Communications Manager Configuration Definition window opens.
    The Communications Manager Configuration Definition window

Step  2.

Configure the protocol

  1. Select the Commonly used definitions radio button.
  2. In the Communications Definitions box, select the protocol that you want to use. These instructions use APPC APIs over Token-Ring.
  3. Click on the Configure push button. The APPC APIs over Token-Ring window opens.
    APPC APIs over Token-Ring
  4. Enter your Network ID ((9)) in the Network ID field.
  5. Enter your local Control Point name ((10)) in the Control point name field.
  6. Click on the End node push button that your network administrator advises you to use. You can select either the End node - to a network node server radio button or the End node - no network node server radio button. A network node server is used when many users are routed through the same connection. This example assumes no network node server is used.
  7. Click on the Advanced push button. The subsequent steps begin from this window. You will return to this window when each of the following steps are completed. The Communication Manager Profile List window opens.
    The Communication Manager Profile List Window

Step  3.

Prepare a LAN DLC profile

  1. On the Profile List window, select the DLC - Token ring or other LAN Types Adapter Parameters option and click on the Configure push button. The Token Ring or Other Lan Types Adapter Parameters window opens.
    Token Ring or Other Lan Types Adapter Parameters
  2. Enter your Network ID ((9)) in the Network ID field.
  3. Click on OK.

Step  4.

Update the SNA local node characteristics

  1. On the Profile List window, select the SNA local node characteristics option and click on the Configure push button. The Local Node Characteristic window opens.
    Local Node Characteristic window.
  2. Enter your Network ID ((9)) in the Network ID field.
  3. The Local node name was probably set when CS/2 was installed. If you are not sure, consult your local network administrator.
  4. Enter your Node ID ((13), (14)) in the Local node ID (hex) field.

    Figure 00002674 not displayed.

    The first part should be filled in for you already when you display the profile. You only need to complete the second part.

  5. Click on OK.

Step  5.

Prepare the SNA Connection Profiles

  1. On the Profile List window, select the SNA Connections option and click on the configure push button. The Connection List window opens.
    Connection List Window.
  2. From the Partner Type window, select either the To peer node radio button (normally used for OS/400 connections), or the To host radio button (normally used for OS/390, MVS, VSE, and VM connections), and click on the Create push button. The Adapter List window opens.
    Adapter List panel.
  3. Select the Token-ring, or other LAN types Adapter Type, and specify the same adapter number that you specified previously in the DLC profile.
  4. Click on the Continue push button. The Connection to a Peer Node window or the Connection to a Host window opens.
    Connection to a Host Window
    Connection to a Peer Node Window

Step  6.

Configure the connection in the Connection to a Peer Node or Connection to Host window

  1. Enter the Link name ((7)) in the Link name field.
  2. In the Connection window, click on the Additional parameters push button. The Additional Connection Parameters window opens.
  3. Enter your local Control Point name ((10)) in the Local PU name field.
  4. Clear the Backup Link check box.
  5. Enter your Node ID ((13) and (14)) in the Node ID fields.
  6. Click on OK.
  7. Enter the remote LAN address ((8)) in the LAN destination address field.
  8. Enter the Network ID ((1)) of the remote system in the Partner network ID field.
  9. Enter the Partner Node name ((4)) in the Partner node name field.
  10. Click on the Define Partner LUs push button. The Partner LU window opens.
    Partner LU window.

Step  7.

Create a partner LUs profile

  1. Enter the Network ID ((3)) of the remote system in the Network ID field.
  2. Enter the Partner LU name ((2)) in the LU name and Alias fields.
  3. Click on the Add push button to add the partner LU profile to the connection profile.
  4. Click on OK.
  5. Click on the Additional Parameters push button. The Additional Connection Parameters window opens.
    Additional Connection Parameters window
  6. Verify that the Multiple PU Parameters fields are filled in. This value is the Local Node ID in hex ((13) and (14)).
  7. Click on OK to return to the Connection window.
  8. Click on OK to return to the Connections List window.
  9. Click on the Close push button to return to the Profile List window.

Step  8.

Set SNA features

  1. On the Profile List window, select the SNA features option and click on the Configure push button. The SNA Features List window opens. Subsequent steps begin from this window.
    SNA Features List window.

Step  9.

Prepare a local LU profile

If the DB2 workstation is defined as an independent LU, prepare a Local LU Profile by performing the following steps:

  1. On the SNA Features List window, select Local LUs --> Create from the action menu bar.
  2. Enter your Local LU name ((11)) in the LU name field.
  3. Enter your Local LU alias ((13)) in the alias field.
  4. Select the Independent LU radio button in the NAU address box.
  5. Click on OK.
  6. To use this local LU when the DB2 Connect workstation starts the APPC connection, select the Use this local LU as your default local LU alias check box. By default, all APPC connections that are started from this DB2 Connect workstation will use this local LU.

Step 10.

Prepare a mode definition

  1. From the SNA Features List box, select the Modes option and click on the Create push button. The Mode Definition window opens.
    Mode Definition Window
  2. Enter your Mode name ((6), (15)) in the mode name field.
  3. For the other fields, you can either specify values that match the mode profile defined on your server systems, or tune the parameters.
  4. Click on OK to finish the creation of the mode and to return to the SNA Features List panel.

Step 11.

Create the CPIC side information

  1. From the SNA Features List box, select the CPI Communications Side Information option and click the Create push button. The CPI Communications Side Information window opens.
    CPI Communications Side Information Window
  2. Enter the Symbolic destination name ((16)) in the Symbolic destination name field.
  3. Select the Alias radio button.
  4. Click on the Alias drop down box and select your Local LU alias ((12)).
  5. Enter the remote Transaction Program (TP) name ((17)) in the Partner TP field.
  6. Select the None radio button in the Security type group. You will specify the security type later when you update the DB2 directories.
  7. Enter the mode name ((6)) in the Mode name field.
  8. Click on OK to save the CPI side information profile and return to the SNA Features List panel.
  9. Click on Close to return to the Communications Server Profile List panel.

Step 12.

Save the configuration

  1. Click on the Close button to return to the Communication Server Configuration Definition window.
  2. Click on the Close button to automatically verify and save the new configuration file, and leave the configuration windows.
  3. Stop and start Communications Server by selecting Stop Communications Normally --> Start Communications from the action menu bar.



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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring IBM Personal Communications for Windows

This section describes how to configure IBM Personal Communications for Windows NT, Windows 2000, Windows 98 and Windows 95 on your DB2 Connect workstation to connect to host or AS/400 database servers using APPC.

Before you begin, ensure that the IBM Personal Communications for Windows NT or Windows 9x you installed meets the following requirements:

__  1.

It is Version 4.2 or higher

__  2.

The IBM Personal Communications IEEE 802.2 LAN interface is installed (this is an installation option for IBM Personal Communications)

__  3.

The LLC2 driver is installed from the IBM Communications Server installation directory. To confirm this on Windows NT or 9x:

  1. Click on the Start push button, then select Settings --> Control Panel.
  2. Double-click on the Network icon.
  3. On the Network window, click on the Protocols tab. IBM LLC2 Protocol must be one of the protocols listed. If it is not, you need to install this protocol from your IBM Personal Communications for Windows NT or Windows 9x software. Refer to the documentation supplied with IBM Personal Communications for instructions.

For Windows 2000:

  1. Click on the Start push button and then select Settings --> System
  2. Click the Network and Dial-up Connections and select the connection you want to configure (for example, Local Area Network).
  3. From the General tab, select the Properties push button. Verify that IBM LLC2 Protocol is one of the protocols listed. If it is not, you need to install this protocol from your IBM Personal Communications software. Refer to its documentation for instructions.

The following assumptions are made:

To start IBM Personal Communications, perform the following steps:

Step  1.

Click Start and select Programs --> IBM Communications Server --> SNA Node Configuration. The IBM Personal Communications SNA Node Configuration window opens.
Configuration Window

Step  2.

Select File --> New from the menu bar. The Define the Node window opens. Subsequent steps will begin from this window.

To configure APPC communications, complete the following steps:

Step  1.

Configure the Node

  1. In the Configuration options box, select Configure Node, then click on the New push button. The Define the Node window opens.
    Configure Node
  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. Click on OK.

Step  2.

Configure the device

  1. In the Configuration options box, select Configure devices.
  2. Select the appropriate DLC from DLCs field. These instructions use the LAN DLC.
  3. Click on the New push button. The appropriate window opens with default values displayed. In this case, the Define a LAN device window opens.
  4. Click on OK to accept the default values.

Step  3.

Configure Connections

  1. In the Configuration options box, select Configure connections.
  2. Ensure that in the DLCs field, LAN is highlighted.
  3. Click on the New push button. The Define a LAN connection window opens.
    Define a LAN Device - Basic
  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 Adjacent Node tab panel:
    Define a LAN Device - Adjacent Node
    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.

Step  4.

Configure Partner LU 6.2

  1. In the Configuration options box, select Configure partner LU, then click on the New push button. The Define a partner LU 6.2 window opens.
    Define a Partner LU
  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. In the Fully-qualified CP name fields, type in the network ID (3) and the adjacent control point SSCP name (4) (SPIFNET.NYX).

    Accept the defaults in the Advanced tab panel.

  5. Click on OK.

Step  5.

Configure Modes

  1. In the Configuration options box, select Configure modes, then click on the New button. The Define a mode window opens.
    Define a Mode - Basic
  2. Enter your Mode name ((15)) in the Mode name field of the Basic tab.
  3. Select the Advanced tab.
    Define a Mode - Advanced
  4. Select #CONNECT from the Class of Service Name field.
  5. Click on OK.

Step  6.

Configure Local LU 6.2

  1. In the Configuration options box, select Configure local LU 6.2, then click on the New button. The Define a local LU 6.2 window opens.
    Define a Local LU
  2. Enter your Local LU name ((11)) in the Local LU name field.
  3. Type in a value for the LU session limit field. The default, 0, specifies the maximum allowed value.
  4. Accept the defaults for the other fields and click on OK.

Step  7.

Configure CPI-C Side Information

  1. In the Configuration options box, select Configure CPI-C side information, then click on the New push button. The Define CPI-C side information window opens.
    Define CPI-C Side Information
  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. In the Partner LU Name fields, type the Net ID (3) in the first field, and the Partner LU Name (2) (SPIFNET.NYM2DB2) in the second field.
  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.
  6. Accept the defaults for the other fields and click on OK.

Step  8.

Save the Configuration

  1. Select File --> Save As. The Save As window opens.
  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.

Step  9.

Update the environment

IBM Personal Communications uses an environment variable called appcllu to set the default Local LU used for APPC communications. You may set this variable on a per-session basis by opening a command window and typing set appcllu=local_lu_name, where local_lu_name is the name of the local LU you want to use. However, you will probably find it more convenient to permanently set the variable. To permanently set the variable in Windows NT, perform the following steps:

  1. Click on the Start push button and select Settings --> Control Panel.
  2. Double-click on the System icon. The System Properties window opens.
  3. Select the Environment tab.
  4. Type appcllu in the Variable field.
  5. Type your local LU name ((4)) in the Value field.
  6. Click on the Set push button to accept the changes.
  7. Click on OK to exit the System Properties window.

The environment variable will now remain set for future sessions.

Step 10.

Start SNA Node Operations

  1. Click on the Start push button and select Programs --> IBM Personal Communications --> Administrative and PD Aids --> SNA Node Operations. The Personal Communications SNA Node Operations window opens.
    SNA Node Operations Window
  2. From the menu bar, select Operations --> Start Node.
  3. In the window that opens, select the configuration file you saved in the previous step (for example, ny3.acg) and click on OK.



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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring IBM eNetwork Communications Server for Windows

Before you begin, ensure that the IBM eNetwork Communications Server for Windows (supported on Windows NT and Windows 2000) you installed meets the following requirements:

__  1.

It is Version 5.0 or higher if you are planning to update multiple databases within the same transaction; if you are planning to use 2-phase commit then Version 5.01 of Communications Server for Windows is required

__  2.

The IBM Communications Server IEEE 802.2 LAN interface was installed (this is an installation option for Communications Server)

__  3.

The JR11529 and JR11170 APAR fixes have been applied. These fixes are required to enable cancelling of queries in progress by using Ctrl-BREAK or issuing the SQLCancel ODBC/CLI call.

__  4.

The LLC2 driver was installed from the Communications Server for Windows installation directory. During the installation, Communications Server for Windows asks if you want to install LLC2. If you are not sure whether LLC2 was installed with your copy of Communications Server for Windows, you can find out as follows:

  1. Click Start and select Settings --> Control Panel.
  2. Double-click on the Network icon.
  3. On the Network window, click on the Protocols tab. IBM LLC2 Protocol must be one of the protocols listed. If it is not, you need to install this protocol from your IBM Communications Server for Windows software. For more information, refer to documentation supplied with Communications Server for Windows.

To start IBM eNetwork Personal Server, perform the following steps:

Step  1.

Click on Start and select Programs -->IBM Communications Server --> SNA Node Configuration. The IBM Communications Server SNA Node Configuration window opens.

Step  2.

Select File --> New --> Advanced from the menu bar. The Configuration options window opens. Subsequent steps will begin from this window.
Configuration options window

To configure IBM eNetwork Personal Server for APPC communications, complete the perform the following steps:

Step  1.

Configure Node

  1. In the Configuration options field, select Configure Node, then click on the New push button. The Define the Node window opens.
  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. Select the appropriate node type. The default is to select the End Node radio button.
  6. Click on OK.

Step  2.

Configure Devices

  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 push button. The appropriate window opens with default values displayed. For example, the Define a LAN device window.
  4. Click on OK to accept the default values.

Step  3.

Configure the Gateway

Figure 00002671 not displayed.
You need to perform this step only if you are setting up Communications Server to accept requests from Communications Server for Windows SNA Client, as described in the your DB2 Connect Quick Beginnings manual.

  1. In the Configuration options field, select Configure the Gateway, then click on the New push button. The Define Gateway window opens.
  2. Click the SNA Clients tab.
  3. Ensure that there is a check mark in the Enable SNA API Client Services check box.
  4. Click OK to accept the default values.

Step  4.

Configure Connections

  1. In the Configuration options field, select Configure connections.
  2. Ensure that LAN is highlighted in the DLCs field.
  3. Click on the New push button. The Define a LAN Connection window opens.
  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 the appropriate CP type (for example, Back-level LEN).
    3. Ensure that TG number is set to 0 (the default).
    4. Click OK.

Step  5.

Configure Partner LU 6.2

  1. In the Configuration options field, select Configure partner LU, then click on the New button. The Define a Partner LU 6.2 window opens.
  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).
  5. Leave the other fields blank. and click on OK.

Step  6.

Configure Modes

  1. In the Configuration options field, select Configure modes, then click on the New button. The Define a Mode window opens.
  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.
  4. Accept the defaults for the other fields and click on OK.

Step  7.

Configure 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 opens.
  2. In the Local LU name field, type in the name ((11)) from the worksheet (NYX1GW01).
  3. Enter a value for the LU session limit field. The default, 0, specifies the maximum allowed value.
  4. Accept the defaults for the other fields and click on OK.

Step  8.

Configure 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 opens.
  2. In the Symbolic destination name field, type in the name ((16)) from the worksheet (DB2CPIC).
  3. In the Mode name field, enter 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, enter 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, enter the name of the service TP, for example 076DB, and ensure that there is a check mark in the Service TP check box.
  6. Accept the defaults for the other fields and click on OK.

Step  9.

Save the Configuration

  1. Select File --> Save as from the menu bar. The Save As window opens.
  2. Enter a file name, for example ny3.acg
  3. Click on OK.
  4. In the window that opens you are asked if you want this configuration to be the default. Click on the Yes push button.

Step 10.

Update the Environment

IBM Personal Communications uses an environment variable called appcllu to set the default APPC Local LU. You may set this variable on a per-session basis by opening a command window and typing set appcllu=local_lu_name, however you will probably find it more convenient to permanently set the variable. In order to permanently set the variable in Windows NT, complete the following steps:

Step  a.

Click on Start and select Settings --> Control Panel. Double-click on the System icon. When the System Properties window opens, select the Environment tab.

Step  b.

Enter appcllu in the Variable field, and enter your Local LU name ((11)) in the Value field.

Step  c.

Click Set to accept the changes then click OK to exit the System Properties window.

The environment variable will now remain set for future sessions.

Step 11.

Start SNA Node Operations

To start SNA node operations on your machine, complete the following steps:

Step  a.

Click on Start and select Programs --> IBM Communications Server --> SNA Node Operations. The SNA Node Operations window opens.

Step  b.

From the menu bar, click on Operations and select Start Node. In the dialog box that opens, select the configuration file you saved at the end of Step 2 (in our example, ny3.acg). Click OK.

SNA node operations will now begin running.

Step 12.

Registering Communications Server as a Windows Service

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

To register Communications Server as a Windows service execute one of the following commands: 

   csstart -a

to register Communications Server with the default configuration, or: 

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

where c:\ibmcs\private\your.acg represents the fully qualified name of the non-default Communications Server configuration file you want to use.

Whenever your machine is booted in the future, Communications Server will be started automatically with the required configuration file.



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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring 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.0 or 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 configuration requires that you have an APPC-enabled application (such as DB2 Connect) running on the SNA API client workstation.



Figure 00002674 not displayed.
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.

To configure the Windows NT SNA API client for APPC communications, complete the following steps:

Step  1.

Create a user account for the SNA API client on the Communications Server for Windows NT Server

  1. Click Start and select Programs --> Administrative Tools (Common) --> User Manager. The User Manager window opens.
  2. Select Users --> New User from the menu bar. The New User window opens.
  3. Fill in the fields for the new SNA client user accout. For more information, refer to the Windows NT online help.
  4. Ensure that this user account is a member of the Administrators, IBMCSADMIN, and IBMCSAPI groups:
    1. Click Groups.
    2. Select a group from the Not member of box and click <- Add. Repeat this step for each group that your user account must belong to.
  5. Click OK.
  6. Click Add.

Step  2.

Start the configuration GUI for the IBM eNetwork CS/NT SNA API Client. Click Start and select Programs --> IBM Communications Server SNA Client --> Configuration. The CS/NT SNA Client Configuration window opens.
Configuration Options Screen

Step  3.

Configure Global Data

  1. In the Configuration options box, select the Configure Global Data option and click on the New push button. The Define Global Data window opens.
  2. Enter the user name for the SNA API client in the User name field. This is the user name that was defined in Step 1.
  3. Enter the password for the user account in the Password and Confirm Password fields.
  4. Click OK.

Step  4.

Configure APPC Server List

  1. In the Configuration options box, select the Configure APPC Server List option. Click on the New push button. The Define APPC Server List window opens.
  2. Type in the IP address of the server (for example, 123.123.123.123).
  3. Click OK.

Step  5.

Configure CPI-C Side Information

  1. In the Configuration options box, select the Configure CPI-C side information option and click New. The Define CPI-C side information window opens.
  2. Enter the symbolic destination name ((16)) in the Symbolic destination name field.
  3. Enter your Local LU alias ((12)) in the Local LU alias field.
  4. Enter the mode name ((15)) in the Mode name field.
  5. Enter the transaction program name ((17)) in the TP name field.
  6. Select the For SNA API Client use check box for this transaction program.
  7. Enter the network ID ((3)) and partner LU name ((2)) in the Partner LU name field.
  8. Click OK.

Step  6.

Save the Configuration

  1. Select File --> Save As from the menu bar. The Save As window opens.
  2. Enter a file name, and click Save.



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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring Microsoft SNA Server for Windows

This section describes how to configure 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.

If you wish to use DB2's Multisite Update feature with this product, your minimum requirement is Microsoft SNA Server Version 4 Service Pack 3. For more information, refer to Enabling Multisite Updates (Two-Phase Commit).

Figure 00002671 not displayed.
For instructions on how to configure Microsoft SNA Client for Windows, go to Configuring Microsoft SNA Client.

You can define the properties of your SNA connections in the Microsoft SNA Server Manager (Server Manager). The Server Manager uses an interface similar to that of the Windows NT Explorer. The following illustration shows the interface. There are two panes in the main window of the Server Manager. All the configuration options we will be using can be accessed by right-clicking on objects in the left-hand pane of the window. Every object has a context menu that you can access by right-clicking on the object.

To configure APPC communications for use by DB2 Connect using Microsoft SNA Server Manager, perform the following steps:

Step  1.

To start the Server Manager, click Start and select Programs --> Microsoft SNA Server --> Manager. The Microsoft SNA Server Manager window opens.
The Microsoft SNA Server Manager window

Step  2.

Define the control point name

  1. Click on the [+] sign beside the Servers folder.
  2. Right-click on SNA Service folder and select the Properties option. The Properties window opens.
  3. Enter the correct NETID ((9)) and Control Point Name ((10)) in the corresponding fields.
  4. Click OK.

Step  3.

Define the link service (802.2)

  1. Right-click on the SNA Service icon and select the Insert --> Link Service option. The Insert Link Service window opens.
    Insert Link Service window
  2. Select DLC 802.2 Link Service.
  3. Click Add.
  4. Click Finish.

Step  4.

Define the connection properties

  1. Right-click on SNA Service and select the Insert --> Connection --> 802.2 option. The Connection Properties window opens.
    Connection Properties Window
  2. Enter a connection name ((7)) in the Name field.
  3. Click on the Link Service drop-down box and select the SnaDlc1 option.
  4. Select the Remote End radio button from the Host System box.
  5. Select the Both Directions radio button from the Allowed Directions box.
  6. Select the On Server Startup radio button from the Activation box.
  7. Select the Address tab.
    Connection Properties - Address
  8. Fill in the Remote Network Address field ((8)). Accept the default numbers in the other fields.
  9. Select the System Identification tab.
  10. Enter the following information:
    1. For the Local Node Name, add the Network ID ((9)), the Local PU Name ((10)), and the Local Node ID ((1) plus (14)). Accept the XID Type default.
    2. For the Remote Node Name, add the NETID ((1)) and the Control Point Name ((4)).
  11. Accept the other defaults and click OK.

Step  5.

Define a local LU

  1. Right-click on the SNA Service icon and select the Insert --> APPC --> Local LU option. The Local APPC LU Properties window opens.
    Local APPC LU Properties Window
  2. Enter the following information:
    • The LU Alias ((12)).
    • The NETID ((9)).
    • The LU Name ((11)).
  3. Select the Advanced tab. If you are planning to use a DB2's multisite update support, ensure that you have:
    1. Installed Microsoft SNA Server V4 Service Pack 3
    2. De-selected the Member of Default Outgoing Local APPC LU Pool option. DB2 requires exclusive use of this LU for multisite update.
    3. From the SyncPoint Support field:
      • Select Enable.
      • Enter the SNA Server name in the Client field.

      Syncpoint support must be enabled on this server. It is not supported on SNA clients. Therefore, the Client field must contain the name of the local SNA Server. Multisite update is typically required if you use Transaction Processing (TP) Monitors such as Microsoft Transaction Server, IBM TxSeries, or BEA Tuxedo.

      An additional LU should be defined without Syncpoint support enabled, or if multisite update is not required. For this LU, you should ensure that Member of Default Outgoing Local APPC LU Pool option is selected

  4. Accept the other defaults and click OK.

Step  6.

Define a remote LU

  1. Right-click on SNA Services icon and select the Insert --> APPC --> Remote LU option. The Remote APPC LU Properties window opens.
  2. Click on the Connection drop down box and select the appropriate connection name ((7)).
  3. Enter the partner LU name ((2)) in the LU Alias field.
  4. Enter the Network ID ((1)) in the Network Name field.

    Figure 00002674 not displayed.
    		The other fields will be filled in by the program. If your LU alias is not the same as your LU Name, make sure you specify the LU Name in the appropriate field. The program will fill it in automatically, but it will be incorrect if the alias and the name are not the same.
  5. Click OK.

Step  7.

Define a mode

  1. Right-click on APPC Modes folder and select the Insert --> APPC --> Mode Definition option. The APPC Mode Properties window opens.
    The APPC Mode Properties Window
  2. Enter the Mode Name (6) in the Mode Name field.
  3. Select the Limits tab.
    The APPC Mode Properties Window - Limits
  4. Enter appropriate numbers for the Parallel Session Limit and Minimum Contention Winner Limit fields. Your Host-Side or LAN administrator should be able to supply you with the numbers if you do not know the limits you should place here.
  5. Accept the other defaults, and click OK.

Step  8.

Define the CPIC name properties

  1. Right-click on CPIC Symbolic Name folder icon and select the Insert --> APPC --> CPIC Symbolic Name option. The CPIC Name Properties window opens.
    CPIC Name Properties - General
  2. Enter the Symbolic Destination Name ((16)) in the Name field.
  3. Click on the Mode Name drop down box and select a mode name, for example, IBMRDB.
  4. Select the Partner Information tab.
    CPIC Name Properties - Partner Information
  5. In Partner TP Name box, select the SNA Service TP (in hex) radio button and enter the Service TP name ((17)), or select the Application TP radio button and enter the Application TP name ((17)).
  6. In the Partner LU Name box, select the Fully Qualified radio button.
  7. Enter the fully-qualified Partner LU Name ((1) and (2)) or alias.
  8. Click OK.
  9. Save the configuration
    1. Select File --> Save from the menu bar of the Server Manager window. The Save File window opens.
    2. Enter a unique name for your configuration into the File Name field.
    3. Click Save.


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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring Microsoft SNA Client

Read this section if you have a Windows NT workstation that has DB2 Connect installed. This section provides step-by-step instructions for setting up the communications between your DB2 Connect workstation and a Windows NT workstation that has Microsoft SNA Server V4.0 (or later) installed.

Figure 00002671 not displayed.
For instructions on how to configure Microsoft SNA Server Version 4.0 for Windows NT, go to Configuring Microsoft SNA Server for Windows.

Figure 2 illustrates the example DB2 Connect Server scenario.

Figure 2. Indirect Connection to host or AS/400 database server via SNA Communications Gateway


DB2 Connect Server Scenario with MS SNA Server and MS SNA Client

The rest of this section assumes:

  1. The Microsoft SNA Server has already been configured for APPC communications with the host, and is enabled for ODBC and DRDA. Refer to the Microsoft SNA Server documentation for further information.
  2. Microsoft SNA Client Version 2.11 is not already installed on your DB2 Connect workstation.

To configure the Microsoft SNA client, perform the following steps:

Step 1. Obtain Required Information

For your Microsoft SNA client software to function properly you must have access to a properly configured Microsoft SNA Server. Request that your SNA Server administrator:

  1. Obtain the proper license for you to use Microsoft SNA Client on your workstation.
  2. Define a user ID and password for you on the SNA Server domain.
  3. Define connections to the host and AS/400 databases that you need to access, as described in Configuring Microsoft SNA Server for Windows.
  4. Provide you with the symbolic destination name ((16)), database name ((5)), and user account to use for each database connection defined in the previous step.

    If you plan to change host passwords, the SNA administrator will also need to provide you with symbolic destination names for password management tasks on each host.

  5. Provide you with the Microsoft SNA Server domain name and the protocol used for communicating with the SNA server (TCP/IP, NetBEUI, IPX/SPX).

Step 2. Install the Microsoft SNA Client on the DB2 Connect Workstation

  1. Obtain the Microsoft SNA Client software, and follow its instructions to start the installation program.
  2. Follow the instructions on the screen to complete the installation. Choose your SNA Server domain name and communication protocol according to the instructions provided by your SNA Server administrator.
  3. When you reach the Optional Components window, deselect Install ODBC/DRDA driver so that it will not be installed.
  4. Complete the installation.

Step 3. Install DB2 Connect for Windows

  1. Install DB2 Connect.
  2. Click on Start and select Programs --> DB2 for Windows NT --> Client Configuration Assistant.
  3. You need to provide the following information:
    1. The Symbolic destination name ((16)) defined at the Microsoft SNA Server for the Partner LU ((2)) of the target host or AS/400 database server.
    2. The real database name ((5)).


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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring IBM eNetwork Communication Server for AIX

This section describes how to configure IBM eNetwork Communication Server V5.0.3 for AIX on your DB2 Connect workstation to connect to host or AS/400 database servers using APPC. IBM eNetwork Communication Server for AIX is the only SNA product supported for DB2 Connect running on RS/6000 machines.

Before you begin, ensure that your workstation has IBM eNetwork Communication Server V5.0.3 for AIX (CS/AIX) installed. If you need further information in order to configure your SNA environment, refer to the online help provided with CS/AIX.

The following assumptions are made:

To configure CS/AIX for use by DB2 Connect, log on to the system as a user with root authority and use either the /usr/bin/snaadmin program or the /usr/bin/X11/xsnaadmin program. Information about these programs can be found in the system documentation. The following steps describe how to use the xsnaadmin program to configure CS/AIX.

Step  1.

Enter the command xsnaadmin. The Node window for the server opens.

Step  2.

Define a node.

  1. Select Services --> Configure Node Parameters. The Node Parameters window opens.
    Node Parameters Window
  2. Select End node from the APPN support drop-down menu.
  3. Enter your network ID and the local PU name ((9) and (10)) in the Control point name fields.
  4. Enter the local PU name ((10)) in the Control point alias field.
  5. Enter your Node ID ((13) and (14)) in the Node ID fields.
  6. Click OK.

Step  3.

Define a port.

  1. Select the Connectivity and Dependent LUs window.
  2. Click the Add push button. The Add to Node window opens.
  3. Select the Port using radio button.
  4. Click the Port Using drop down box and select the appropriate port type. For the purpose of our example, we will select the Token ring card option.
    Token Ring SAP window
  5. Click OK. The Port window for the chosen port type opens.
  6. Enter a name for the port in the SNA port name field.
  7. Select the Initially active check box.
  8. From the Connection network box, select Define on connection network check box.
  9. Enter your SNA Network Name ((9)) in the first part of the CN name field.
  10. Enter the Local PU Name ((10)) associated with your AIX computer in the second part of the CN name field.
  11. Click OK. The Port window closes and a new port opens in the Connectivity and Dependent LUs window.

Step  4.

Define a link station.

  1. In the Connectivity and Dependent LUs window, select the port that you defined in the previous step.
  2. Click the Add push button. The Add to Node window opens.
  3. Select the Add a link station to port radio button.
  4. Click OK. The Token ring link station window opens.
    Token Ring Link Station window
  5. Enter a name for the link in the Name field.
  6. Click the Activation drop-down box and select the On demand option.
  7. Select the Independent only option in the LU traffic box.
  8. In the Independent LU traffic box:
    1. Enter the network ID ((3)) and the partner LU name ((2)) in the Remote node fields.
    2. Click the Remote node type drop-down box and select the type of node that applies to your network.
  9. In the Contact information box, enter the SNA destination address ((8)) assigned for the host or AS/400 system in the Mac address field.
  10. Click OK. The Link Station window closes and a new link station appears in the Connectivity and Dependent LUs window.

Step  5.

Define a local LU.

  1. Select the Independent local LUs window.
  2. Click the Add push button. The Local LU window opens.
    Local LU window
  3. Enter your independent local LU Name ((11)) in the LU name field.
  4. Enter the same name in the LU alias field ((12)).
  5. Click OK. The new LU appears in the Independent Local LUs window.

Step  6.

Define a partner LU over the link station.

  1. Select Services --> APPC --> New PLUs -->Over Link Station from the menu bar. The Partner LU on link station window opens.
    Partner LU on Link Station Window
  2. Enter the name for the local LU ((11)) you defined previously in the LU name field.
  3. Enter the name for the link station you defined previously in the LS name field.
  4. Enter the name of the partner LU you want to connect to ((2)) in the Partner LU name field.
  5. Click OK. The Partner LU appears in the Independent Local LUs window of the Local LU that was created in the previous step.

Step  7.

Define an alias for the partner LU.

  1. Select the Remote Systems window.
  2. Click the Add push button. The Add to Node window opens.
  3. Select the Define partner LU alias radio button.
  4. Click OK. The Partner LU window opens.
  5. Enter an alias for the partner LU in the Alias field.
  6. Enter the same value in the Uninterpreted name field.
  7. Click OK.

Step  8.

Define a mode.

  1. Select Services --> APPC--> Modes from the menu bar. The Modes window opens.
  2. Click the New push button. The Mode window opens.
    Mode Window
  3. Enter a mode name ((15)) in the Name field.
  4. The configuration values below are suggested for the following fields:
    • Initial session limits: 20
    • Maximum session limits: 32767
    • Min con. winner sessions: 10
    • Min con. loser sessions: 10
    • Auto-activated sessions: 4
    • Initial receive pacing window: 8

    These values are suggested because they are known to work. You will need to tailor these values so that they are optimized for your particular application environment.

  5. Click OK. The new mode appears in the Modes window.
  6. Click Done.

Step  9.

Define the CPI-C destination name.

  1. Select Services --> APPC--> CPI-C from the menu bar. The CPI-C destination names window opens.
  2. Click the New push button. The CPI-C destination window opens.
    CPI-C Destination Window
  3. In the Name field, enter the Symbolic Destination Name ((16)) you want to associate with the host or AS/400 server database. This example uses db2cpic.
  4. In the Partner TP box:
    • For DB2 for MVS/ESA, DB2 for OS/390, and DB2 for AS/400, select the Service TP (hex) radio button, and enter the hexadecimal TP number ((17)). (For DB2 Universal Database for OS/390 or DB2/MVS, you can also use the default application TP DB2DRDA. For DB2 for AS/400 you can also use the default application TP QCNTEDDM.)
    • For DB2 for VM or VSE, select the Application TP radio button. For DB2 for VM, enter the DB2 for VM database name. For DB2 for VSE, enter the AXE as the application TP ((17)).
  5. In the Partner LU and mode box:
    1. Select the Use PLU alias radio button, and enter the partner LU alias ((2)) you created in a previous step.
    2. In the Mode field, enter the mode name ((15)) for the mode that you created in a previous step.
  6. In the Security box, select the radio button that corresponds to the type of security level that you want to run on your network.
  7. Click OK. The new destination name appears in the Destination Names window.
  8. Click Done.

Step 10.

Test the APPC connection.

  1. Start the SNA subsystem by entering the /usr/bin/sna start command. You can enter the /usr/bin/sna stop command to stop the SNA subsystem first, if required.
  2. Start the SNA administration program. You can enter either the /usr/bin/snaadmin command or the /usr/bin/X11/xsnaadmin command.
  3. Start the subsystem node. Select the appropriate node icon in the button bar, and click the Start push button.
  4. Start the link station. Select the link station you defined previously in the Connectivity and Dependent LUs window, and click the Start push button.
  5. Start the session. Select the LU you defined previously in the Independent Local LUs window, and click the Start push button. A session activation window opens.
  6. Select or enter a partner LU and mode.
  7. Click OK.



Figure 00002674 not displayed.
You may also need to contact your database or network administrators to have your local LU names added to the appropriate tables in order to access the host or AS/400 server database.


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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring Bull SNA for AIX

This section describes how to configure Bull DPX/20 SNA/20 Server on your DB2 Connect workstation to connect to host or AS/400 database servers using APPC. If Bull DPX/20 SNA/20 Server is installed prior to installing DB2 Connect, DB2 Connect uses Bull SNA. Otherwise, you need to configure DB2 Connect to work with IBM eNetwork Communications Server V5.0.3 for AIX. See Configuring IBM eNetwork Communication Server for AIX for more information.

To determine if Bull SNA is installed on your AIX 4.2 (or later) system, enter the following command: 

  lslpp -l express.exsrv+dsk

If Bull SNA is installed, you will see output similar to the following: 

    Fileset                      Level  State      Description
    ----------------------------------------------------------------------
  Path: /usr/lib/objrepos
    express.exsrv+dsk          2.1.3.0  COMMITTED  EXPRESS SNA Server and
                                                   Integrated Desktop

If you install Bull SNA after installing DB2 Connect and you want DB2 Connect to use Bull SNA instead of IBM eNetwork Communications Server for AIX, log on to the system as a user with root authority and enter the following command: 

   /usr/lpp/db2_06_01/cfg/db2cfgos

If you want to install the Bull DPX/20 SNA/20 Server, then you must have the following software:

__  1.

AIX V4.1.4

__  2.

Express SNA Server V2.1.3

For more information on setting up your SNA environment, refer to the Bull DPX/20 SNA/20 Server Configuration Guide.

DB2 Connect, when used with the Bull SNA server, cannot have inbound APPC connections from remote clients. The only APPC connections it can have are outbound APPC connections to the host.

To configure Bull SNA for use by DB2 Connect, enter the express command to configure the following SNA parameters: 

     Config         Express           Default configuration for EXPRESS
      Node          NYX1              SPIFNET.NYX1 (HOSTNAME=NYX1)
       Indep. LUs   6.2 LUs Using All Stations
         LU         NYX1              Control Point LU
       Link         tok0.00001        Link (tok0)
        Station     MVS               To MVS from NYX1
         LU         NYX1GW01          To MVS from NYX1
          LU Pair   NYM2DB2           To MVS from NYX1
           Mode     IBMRDB            IBMRDB

Use default values for fields not listed.

The following example illustrates the sample configuration: 

   Defining hardware:
 
   System (hostname) = NYX1
   Adapter and Port  = NYX1.tok0
     MAC Address     = 400011529778
 
   Defining SNA node:
 
   Name          = NYX1
   Description   = SPIFNET.NYX1 (HOSTNAME=NYX1)
   Network ID    = SPIFNET
   Control Point = NYX1
   XID Block     = 05D
   XID ID        = 29778
 
   Defining token ring link:
 
   Name            = tok0.00001
   Description     = Link (tok0)
   Connection Network name
     Network ID    = SPIFNET
     Control Point = NYX
 
   Defining token ring station:
 
   Name               = MVS
   Description        = To MVS from NYX1
   Remote MAC address = 400009451902
   Remote Node name
     Network ID       = SPIFNET
     Control Point    = NYX
 
   Defining Local LU 6.2:
 
   Name        = NYX1GW01
   Description = To MVS from NYX1
   Network ID  = SPIFNET
   LU name     = NYX1GW01
 
   Defining Remote LU 6.2:
 
   Name                 = NYM2DB2
   Description          = To MVS from NYX1
   Network ID           = SPIFNET
   LU name              = NYM2DB2
   Remote Network ID    = SPIFNET
   Remote Control Point = NYX
   Uninterpreted Name   = NYM2DB2
 
   Defining Mode:
 
   Name             = IBMRDB
   Description      = IBMRDB
   Class of service = #CONNECT
 
   Defining Symbolic Destination Info:
 
   Name        = DB2CPIC
   Description = To MVS from NYX1
   Partner LU  = SPIFNET.NYM2DB2
   Mode        = IBMRDB
   Local LU    = NYX1GW01
   Partner TP  = DB2DRDA

After you have configured these SNA parameters, you must stop and start the SNA server. To do this, perform the following steps:

Step  1.

Log on to the system as a user with root authority.

Step  2.

Make sure your PATH contains the $express/bin (/usr/lpp/express/bin)entry.

Step  3.

Check for active users before stopping the server by entering the following command: 

   express_adm shutdown

Step  4.

Stop all EXPRESS activity by entering the following command: 

   express_adm stop

Step  5.

Start EXPRESS by entering the following command: 

   express_adm start



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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring SNAPlus2 for HP-UX

This section describes how to configure SNAplus2 for HP-UX on your DB2 Connect workstation to connect to host or AS/400 database servers using APPC. SNAplus2 for HP-UX is the only SNA product supported for DB2 Connect running on HP-UX V10 and V11 machines.

Before you begin, ensure that your workstation has HP-UX SNAplus2 installed. If you need more information in order to configure your SNA environment, refer to the online help provided with SNAplus2.

The following assumptions are made:

To configure SNAplus2 for DB2 Connect, log on to the system as a user with root authority and use either the /opt/sna/bin/snapadmin program or the /opt/sna/bin/X11/xsnapadmin program. Information about these programs can be found in the system documentation. The following steps describe how to use the xsnapadmin program to configure SNAplus2.

Step  1.

Enter the command xsnapadmin. The Node window for the server opens.

Step  2.

Define a node.

  1. Select Services --> Configure Node Parameters. The Node Parameters window opens.
    Node Parameters Window
  2. Select End node from the APPN support drop-down menu.
  3. Enter your network ID and the local PU name ((9) and (10)) in the Control point name fields.
  4. Enter the local PU name ((10)) in the Control point alias field.
  5. Enter your Node ID ((13) and (14)) in the Node ID fields.
  6. Click OK.

Step  3.

Define a port.

  1. Select the Connectivity and Dependent LUs window.
  2. Click the Add push button. The Add to Node window opens.
  3. Select the Port using radio button.
  4. Click the Port Using drop down box and select the appropriate port. For the purpose of our example, we will select the Token ring card option.
  5. Click OK. The Port window for the chosen port type opens.
    Token Ring SAP window
  6. Enter a name for the port in the SNA port name field.
  7. Select the Initially active check box.
  8. Select the Define on a connection network check box.
  9. Enter your network ID ((9)) in the first part of the CN name field.
  10. Enter your local control point name ((10)) in the second part of the CN name field.
  11. Click OK. The Port window closes and a new port appears in the Connectivity and Dependent LUs window.

Step  4.

Define a link station.

  1. In the Connectivity and Dependent LUs window, select the port that you defined in the previous step.
  2. Click the Add push button. The Add to Node window opens.
  3. Select the Add a link station to port radio button.
  4. Click OK. The Token ring link station window opens.
    Token Ring Link Station window
  5. Enter a name for the link in the Name field.
  6. Click the Activation drop-down box and select the On demand option.
  7. Select the Independent only option in the LU traffic box.
  8. In the Independent LU traffic box:
    1. Enter the network ID ((3)) and the partner LU name ((2)) in the Remote node fields.
    2. Click the Remote node type drop-down box and select the type of node that applies to your network.
  9. In the Contact information box, enter the SNA destination address ((8)) assigned for the host or AS/400 system in the Mac address field.
  10. Click OK. The Link Station window closes and a new link station appears in the Connectivity and Dependent LUs window.

Step  5.

Define a local LU.

  1. Select the Independent local LUs window.
  2. Click the Add push button. The Local LU window opens.
    Local LU window
  3. Enter your independent local LU Name ((11)) in the LU name field.
  4. Enter the same name in the LU alias field ((12)).
  5. Click OK. The new LU appears in the Independent Local LUs window.

Step  6.

Define a remote node.

  1. Select the Remote Systems window.
  2. Click the Add push button. The Add to Node window opens.
  3. Select Define remote node.
  4. Click OK. The Remote Node configuration window opens.
    Remote Node Window
  5. Enter the network ID ((3)) and the partner LU name ((2)) in the Node's SNA network name field.
  6. Click OK. The remote node appears in the Remote Systems window, and a default partner LU is defined for the node.

Step  7.

Define a partner LU.

  1. In the Remote Systems window, double-click the default partner LU that was created when you defined a remote node in the previous step. The Partner LU window opens.
    Partner LU Window
  2. Enter the same partner LU name ((2)) in the Alias and Uninterpreted name fields.
  3. Select Supports parallel sessions.
  4. Click OK.

Step  8.

Define a mode.

  1. Select Services --> APPC--> Modes from the menu bar. The Modes window opens.
  2. Click the New push button. The Mode window opens.
    Mode Window
  3. Enter a mode name ((15)) in the Name field.
  4. The configuration values below are suggested for the following fields:
    • Initial session limits: 20
    • Maximum session limits: 32767
    • Min con. winner sessions: 10
    • Min con. loser sessions: 10
    • Auto-activated sessions: 4
    • Initial receive pacing window: 8

    These values are suggested because they are known to work. You will need to tailor these values so that they are optimized for your particular application environment.

  5. Click OK. The new mode appears in the Modes window.
  6. Click Done.

Step  9.

Define the CPI-C destination name.

  1. Select Services --> APPC--> CPI-C from the menu bar. The CPI-C destination names window opens.
  2. Click the New push button. The CPI-C destination window opens.
    CPI-C Destination Window
  3. In the Name field, enter the Symbolic Destination Name ((16)) you want to associate with the host or AS/400 server database. This example uses db2cpic.
  4. In the Partner TP box:
    • For DB2 for MVS/ESA, DB2 for OS/390, and DB2 for AS/400, select the Service TP (hex) radio button, and enter the hexadecimal TP number ((17)). (For DB2 Universal Database for OS/390 or DB2/MVS, you can also use the default application TP DB2DRDA. For DB2 for AS/400 you can also use the default application TP QCNTEDDM.)
    • For DB2 for VM or VSE, select the Application TP radio button. For DB2 for VM, enter the DB2 for VM database name. For DB2 for VSE, enter the AXE as the application TP ((17)).
  5. In the Partner LU and mode box:
    1. Select the Use PLU alias radio button, and enter the partner LU alias ((2)) you created in a previous step.
    2. In the Mode field, enter the mode name ((15)) for the mode that you created in a previous step.
  6. In the Security box, select the radio button that corresponds to the type of security level that you want to run on your network.
  7. Click OK. The new destination name appears in the Destination Names window.
  8. Click Done.

Step 10.

Test the APPC connection.

  1. Start the SNA subsystem by entering the /opt/sna/bin/sna start command. You may need to enter the /opt/sna/bin/sna stop command to stop the SNA subsystem first.
  2. Start the SNA administration program. You can use either the /opt/sna/bin/snaadmin command or the /opt/sna/bin/X11/xsnaadmin command.
  3. Start the subsystem node. Select the appropriate node icon in the button bar, and click the Start push button.
  4. Start the link station. Select the link station you defined previously in the Connectivity and Dependent LUs window, and click the Start push button.
  5. Start the session. Select the LU you defined previously in the Independent Local LUs pane, then click the Start button. A session activation window opens. Select or enter a partner LU and mode.
  6. Click OK.


Figure 00002674 not displayed.
You may also need to contact your database or network administrators to have your Local LU names added to the appropriate tables in order to access the host or AS/400 server database.



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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Configuring SNAP-IX Version 6.0.1 for SPARC Solaris

This section describes how to configure DCL SNAP-IX V6.0.6 for SPARC Solaris on your DB2 Connect workstation to connect to host or AS/400 database servers using APPC.

Before you begin, ensure that your workstation has DCL SNAP-IX V6.1.0 for SPARC Solaris installed. For more information on configuring your SNA environment, refer to the online help provided with DCL SNAP-IX V6.1.0 for SPARC Solaris.

The following assumptions have been made:

To configure DCL SNAP-IX V6.1.0 for SPARC Solaris for DB2 Connect, log on to the system as a user with root authority and use either the /opt/sna/bin/snaadmin or the /opt/sna/bin/X11/xsnaadmin program. For more information about these programs, refer to the system documentation.

To configure DCL SNAP-IX V6.1.0 for SPARC Solaris using the xsnaadmin program, perform the following steps:

Step  1.

Enter the xsnaadmin command. The Node window for the server opens.

Step  2.

Define a node.

  1. Select Services --> Configure Node Parameters. The Node Parameters window opens.
    Node Parameters Window
  2. Select End node from the APPN support drop-down menu.
  3. Enter your network ID and the local PU name ((9) and (10)) in the Control point name fields.
  4. Enter the local PU name ((10)) in the Control point alias field.
  5. Enter your Node ID ((13) and (14)) in the Node ID fields.
  6. Click OK.

Step  3.

Define a port.

  1. Select the Connectivity and Dependent LUs window.
  2. Click Add. The Add to Node window opens.
  3. Select the Port using radio button.
  4. Click on the Port Using drop down box and select the appropriate port. For the purpose of our example, we will select the SunTRI/P Adapter option.
  5. Click OK. The Port window for the chosen port type opens.
  6. Enter a name for the port in the SNA port name field.
  7. Select the Initially active check box.
  8. Click OK. The Port window closes, and a new port appears in the Connectivity and Dependent LUs window.

Step  4.

Define a link station.

  1. In the Connectivity and Dependent LUs window, select the port that you defined in the previous step.
  2. Click Add. The Add to Node window opens.
  3. Select the Add a Link Station to Port radio button.
  4. Click OK. The Token Ring Link Station window opens.
  5. Enter a name for the link in the Name field.
  6. Select the Independent Only option in the LU traffic box.
  7. In the Independent LU traffic box:
    1. Enter the Network ID ((3)) and the Partner PU Name ((2)) in the Remote Node fields.
    2. Click on the Remote node type drop down box and select the type of node that applies to your network.
  8. In the Contact information box, enter the SNA Destination Address ((8)) assigned for the host or AS/400 system in the Mac address field.
  9. Click OK. The Link Station window closes, and a new link station appears in the Connectivity and Dependent LUs pane.

Step  5.

Define a local LU.

  1. Select the Independent local LUs window.
  2. Click the Add push button. The Local LU window opens.
    Local LU window
  3. Enter your independent local LU Name ((11)) in the LU name field.
  4. Enter the same name in the LU alias field ((12)).
  5. Click OK. The new LU appears in the Independent Local LUs window.

Step  6.

Define a remote node.

  1. Select the Remote Systems window.
  2. Click the Add push button. The Add to Node window opens.
  3. Select Define remote node.
  4. Click OK. The Remote Node configuration window opens.
    Remote Node Window
  5. Enter the network ID ((3)) and the partner LU name ((2)) in the Node's SNA network name field.
  6. Click OK. The remote node appears in the Remote Systems window, and a default partner LU is defined for the node.

Step  7.

Define a partner LU.

  1. Select Services --> APPC --> New partner LUs --> Partner LU on Remote Node from the menu bar. The Partner LU window opens.
  2. Enter the Partner LU name in the Partner LU Name fields.
  3. Enter the same Partner LU name ((2)) in the Alias and Uninterpreted Name fields.
  4. Select Supports Parallel Sessions.
  5. Enter the Partner PU name in the Location fields.
  6. Click OK.

Step  8.

Define a mode.

  1. Select Services --> APPC--> Modes from the menu bar. The Modes window opens.
  2. Click the New push button. The Mode window opens.
    Mode Window
  3. Enter a mode name ((15)) in the Name field.
  4. The configuration values below are suggested for the following fields:
    • Initial session limits: 20
    • Maximum session limits: 32767
    • Min con. winner sessions: 10
    • Min con. loser sessions: 10
    • Auto-activated sessions: 4
    • Initial receive pacing window: 8

    These values are suggested because they are known to work. You will need to tailor these values so that they are optimized for your particular application environment.

  5. Click OK. The new mode appears in the Modes window.
  6. Click Done.

Step  9.

Define the CPI-C destination name.

  1. Select Services --> APPC -->CPI-C from the menu bar. The CPI-C Destination Names window opens.
    CPI-C Destination Names window
  2. Click New. The CPI-C Destination window opens.
    CPI-C Destination Window
  3. Enter the Symbolic Destination Name ((16)) you want to associate with the host or AS/400 server database in the Name field. This example uses DB2CPIC.
  4. In the Local LU box:
    • Select the specific Local LU alias radio button and enter the Local LU alias you created previously.
  5. In the Partner LU and mode box:
    1. Select the Use PLU Alias radio button, and enter the Partner LU Alias ((2)) you created in a previous step.
    2. Enter the Mode name ((15)) for the mode that you created in a previous step in the Mode field.
  6. In the Partner TP Box:
    1. For DB2 for MVS/ESA, DB2 for OS/390, and DB2 for AS/400, select the Service TP (hex) radio button.
    2. Enter the hexadecimal TP number ((17)). (For DB2 Universal Database for OS/390 or DB2/MVS, you can also use the default application TP DB2DRDA. For DB2 for AS/400 you can also use the default application TP QCNTEDDM.)
    3. For DB2 for VM or VSE, select the Application TP radio button. For DB2 for VM, enter the DB2 for VM database name. For DB2 for VSE, enter the AXE as the application TP. ((17))
  7. In the Security box, select the radio button that corresponds to the type of security level that you want to run on your network.
  8. Click OK. The new destination name appears in the Destination Names window.
  9. Click Done.
  10. Test the APPC connection.
    1. Start the SNA subsystem by entering the /opt/sna/bin/sna start command. You can enter the /opt/sna/bin/sna stop command to stop the SNA subsystem first, if required.
    2. Start the SNA administration program. You can use either the /opt/sna/bin/snaadmin or the /opt/sna/bin/X11/xsnaadmin command.
    3. Start the subsystem node. Select the node icon in the button bar, and click the Start push button.
    4. Start the link station. Select the link station that you previously defined in the Connectivity and Dependent LUs window. Click Start.
    5. Start the session. Select the LU you defined previously in the Independent Local LUs window, then click Start. A session activation window opens. Select or enter the Partner LU and Mode desired.
    6. Click OK.


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

For OS/2 and Windows platforms, the easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, see Configuring Client-to-Server Communications Using the Client Configuration Assistant. For manual configuration instructions, and for UNIX platforms, see 3. Catalog the APPC or APPN Node and the sections that follow.

Step 10.

Test the APPC connection.

  1. Start the SNA subsystem by entering the /opt/sna/bin/sna start command. You can enter the /opt/sna/bin/sna stop command to stop the SNA subsystem first, if required.
  2. Start the SNA administration program. You can use either the /opt/sna/bin/snaadmin or the /opt/sna/bin/X11/xsnaadmin command.
  3. Start the subsystem node. Select the node icon in the button bar, and click the Start push button.
  4. Start the link station. Select the link station that you previously defined in the Connectivity and Dependent LUs window. Click Start.
  5. Start the session. Select the LU you defined previously in the Independent Local LUs window, then click Start. A session activation window opens. Select or enter the Partner LU and Mode desired.
  6. Click OK.


Figure 00002674 not displayed.
You may also need to contact your database or network administrators to have your Local LU names added to the appropriate tables in order to access the host or AS/400 server database.

Configuring SunLink 9.1 for Solaris

This section describes how to configure SunLink 9.1 (SunLink SNA) for Solaris on your DB2 Connect workstation to connect to host or AS/400 database servers using APPC. SunLink SNA for Solaris is the only SNA product supported for DB2 Connect running on Solaris.

Before you begin, ensure that your workstation has SunLink SNA 9.1 installed. The following assumptions have been made:

To configure the SunLink SNA Server for use by DB2 Connect, log on to the system as a user with root authority and perform the following steps:

Step  1.

Start the Configuration Program

Step  2.

Configuring for a Link Station

Step  3.

Configuring for a Session



Figure 00002674 not displayed.
You may also need to contact your database or network administrators to have your local LU names added to the appropriate tables in order to access the host or AS/400 server database.

Start the Configuration Program

The Sunlink Version 9.1 configuration tool uses a graphical user interface accessible through X Windows. To begin the configuration, do the following:

  1. Log on as root.
  2. To initialize the daemons:
    1. Start the sunsetup program by entering: 
           /opt/SUNWgman/sunsetup
    2. Select option 4, and then 5 (Start GMAN/PU21 Software).
  3. To start the graphical interface for configuring Sunlink:
    1. Export your display (for example, export DISPLAY=hostname:0)
    2. Start the sungmi program by entering: 
           /opt/SUNWgmi/sungmi

Configuring for a Link Station

In SNA networking you must have a working link station before you can establish a session. To establish a link station with Sunlink 9.1, complete the following steps:

  1. Double click on the config1 folder in the left-hand pane of the configuration window. A hierarchical tree of icons representing resources will open. Each of the configuration actions you will perform can be launched by right-clicking on the appropriate icon in this window.
  2. Begin by configuring Systems. Select the Systems icon, and right-click.
    1. From the menu that appears, select New --> System
    2. Set HOST = Solaris3. All other information can be left to defaults.
  3. Next, you will need to configure PU2.1 Servers. Select the PU2.1 Servers icon, and right-click.
    1. From the menu that appears, select New PU2.1 Servers> PU2.1 Server.
    2. If you are using Solaris3, enter the following: 
           Name: OMXUF5
     CP Name: CAIBMOML.OMXUF5
     Command Options: -t -1
     sunop service:  brxadmin_pu2 
     lu6.2 service:  brxlu62_serv

      All other options can be left as default values.

  4. The next step is to configure your LAN connections. Select the LAN Connections icon, and right-click.
    1. From the menu that appears, select New 'Lan Connections' LAN Connection.
    2. If you are using Solaris3, enter the following: 
           Line Name:  MAC	
     Local Mac:  08002082611F
    3. Click on Advanced. Ensure that the following is set: 
           Lan Speed: 16Mbs
  5. The last item is your DLC settings. Select MAC icon, and right-click.
    1. From the menu that appears, select New --> DLC (PU2).
    2. For example, If you are using Solaris3, enter the following: 
           DLC Name:  Jetsons
     Remote Mac:  400011529798
     Remote CP: CAIBMOML.OMXR88

Stop the SNA daemons and start them again. You should now see an active Link Station connection. Ensure that this works before continuing.

Configuring for a Session

To configure an SNA session for database communications, double click on the config1 folder in the left-hand pane of the configuration window. A hierarchical tree of icons representing resources will open. Each of the configuration actions you will perform can be launched by right-clicking on the appropriate icon in this window.

To configure for a session:

  1. Start by configuring the independent LU. Select the Independent LU icon, and right-click.
    1. From the menu that appears, select New --> Independent LU.
    2. If you are using Solaris3, enter the following: 
           Name:  OMXUF50A
    3. Click on Advanced. Set the session limit as follows: 
           Session Limit:  16
     Sync level : No
      Note:Two-Phase commit is currently not supported by DB2 with SUNLINK.
  2. Next, set the partner LU. Select the Partner LU's icon, and right-click.
    1. From the menu that appears, select New --> Partner LU.
    2. If you are using Solaris3, enter the following: 
           Name:  OMXR880A
     Local LU: OMXUF50A
  3. Finally, set the mode. Select the OMXR880A icon found under the Partner LU icon, and right-click.
    1. From the menu that appears, select New --> Mode.
    2. For example, If you are using Solaris3, enter the following: 
           Mode Name:  IBMRDB  
     DLC Name: Jetsons

To activate the session, you must stop and then restart the SNA daemons.

[ Top of Page | Previous Page | Next Page ]