IBM Books

Quick Beginnings for UNIX

Step 2. Update the APPC Profiles on the DB2 Connect Workstation

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

Figure car 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 Communication Server for AIX

This section describes how to configure IBM eNetwork Communication Server V5.0.2.5 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.2.5 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.
Node Window

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 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 on OK.

Step  3.

Define a port

  1. Select the Connectivity and Dependent LUs windows.

  2. Click on the Add push button. The Add to Node window opens.
    Add to Node Window

  3. Select the Port using radio button.

  4. Click on the Port Using drop down box and select the appropriate port type.

    Figure hint not displayed.
    		For our example, we will select the the Token ring card option.

    Token Ring SAP window

  5. Click on 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 on 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 on 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 on 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 on 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 on 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 on 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 on 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 fields.

  5. Click on 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 Sytems window.

  2. Click on the Add push button. The Add to node window opens.

  3. Select the Define partner LU alias radio button.

  4. Click on 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 on OK.

Step  8.

Define a mode

  1. Select Services->APPC->Modes from the menu bar. The Modes window opens.
    Modes window

  2. Click on 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 session: 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 on OK. The new mode appears in the Modes window.

  6. Click on 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 on the New push button. 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 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 VSE, 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. Enter the Mode name ((15)) for the mode that you created in a previous step in the Mode field.

  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 on OK. The new destination name appears in the Destination names window.

  8. Click on 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 on 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 on the Start push button.

  5. Start the session. Select the LU you defined previously in the Independent Local LUs window, and click on the Start push button. A session activation window opens.

  6. Select or enter the Partner LU and Mode desired.

  7. Click on OK.



Figure hint 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 car not displayed.
You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection.

Go to Step 3. Catalog the APPC Node.

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.2.5 for AIX. See Configuring IBM eNetwork Communication Server for AIX for more information.

To determine if Bull SNA is installed on your AIX 4.1.4 (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.

Figure hint not displayed.
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 car not displayed.
You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection.

Go to Step 3. Catalog the APPC Node.

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.
Node Window

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 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 on OK.

Step  3.

Define a port

  1. Select the Connectivity and Dependent LUs window.

  2. Click on the Add push button. The Add to Node window opens.
    Add to Node Window

  3. Select the Port using radio button.

  4. Click on the Port Using drop down box and select the appropriate port.

    Figure hint not displayed.
    		For our example, we will select the Token ring card option.

  5. Click on 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 on 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 on 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 on 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 on 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 on 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 on 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 on 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 on the Add push button. The Add to Node window opens.

  3. Select Define remote node.

  4. Click on OK. The Remote Node configuration window appears.
    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 on 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 on OK.

Step  8.

Define a mode

  1. Select Services->APPC->Modes from the menu bar. The Modes window opens.
    Modes window

  2. Click on 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 session: 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 on OK. The new mode appears in the Modes window.

  6. Click on 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 on the New push button. 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 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 VSE, 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. Enter the Mode name ((15)) for the mode that you created in a previous step in the Mode field.

  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 on OK. The new destination name appears in the Destination names window.

  8. Click on Done.

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 command, the /opt/sna/bin/X11/xsnaadmin command.

  3. Start the subsystem node. Select the appropriate the 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 on the Start push button.

  5. Start the session. Select the LU you defined previously in the Independent Local LUs pane, then click on the Start button. A session activation window opens. Select or enter the Partner LU and Mode desired.

  6. Click on OK.


Figure hint 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 car not displayed.
You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection.

Go to Step 3. Catalog the APPC Node.

Configuring SunLink SNA for Solaris

This section describes how to configure SunLink SNA PU 2.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 installed. If you need further information in order to configure your SNA environment, refer to the SunLink PU 2.1 Server Configuration and Administrator's Manual.

The following assumptions are 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.

Create the CPIC Side File

Step  2.

Create the SNA Server Configuration File

Step  3.

Define the Environment Variables Required by SunLink SNA

Step  4.

Start the SunLink SNA Subsystem

Note: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.

Create the CPIC Side File

You can use any plain text editor to create the CPIC side file. The file must be placed in the application's path for a standalone DB2 Connect for Solaris system. However, for remote DB2 clients to be able to access it on the DB2 Connect for Solaris system, the file should be in one of the following directories:

Note:The name of the CPIC side file must be the same as the symbolic destination name specified in the DB2 node directory on the DB2 Connect for Solaris system.

The example below shows the CPIC side file sections required for configuring the SunLink SNA to connect to host or AS/400 database servers. 

# CPIC Side File information
#
PTNR_LU_NAME=NYM2DB2
MODE_NAME=IBMRDB
TP_NAME=X'07F6C4C2'
SECURITY=PROGRAM

Create the SNA Server Configuration File

You can use any plain text editor to create the SNA server configuration file. This file is called sunpu2.config, and it must be placed in /opt/SUNWpu21, or the directory where SunLink SNA PU 2.1 Server is installed.

The following example shows the configuration file sections required for configuring the SunLink SNA to connect to host or AS/400 database servers. Other sections that are not shown are required for accepting inbound APPC connections. 

// SunLink SunLU6.2/SunPU2.1 SNA Server Sample Configuration
// Token Ring Peer-to-Peer System A @(#)sunlu62.a.tr
//
// The physical connection is a Token Ring interface adapter.
 
CP      NAME=NYX1                       // Local name (8 char max)
        NQ_CP_NAME=SPIFNET.NYX1         // Network Qualified Name
        window opens
 
TRLINE  NAME=MAC1                       // SunLink specific name
        SOURCE_ADDRESS=x'400011527509'  // sysA_mac_addr for Sun machine
        window opens
 
DLC     NAME=HOSTLINK                   // User defined name (8 char max)
        LINK_NAME=MAC1                  // Line name this station is on
        LCLLSAP=x'04'                   // Local Link Service Access Point
        RMTLSAP=x'04'                   // Remove Link Service Access Point
        RMTMACADDR=x'400009451902       // sysB_mac_addr
        TERMID=x'07127509'              // XID negotiation
        window opens
 
LU      NAME=NYX1GW0A                   // Local name (8 char max)
        NQ_LU_NAME=SPIFNET.NYX1GW0A     // Network Qualified Name
        SESS_LMT=50                     // Max LU sessions
        LUTYPE=6.2
        window opens
 
PTNR_LU NAME=NYM2DB2                    // Partner LU name(8 char max)
        LOC_LU_NAME=NYX1GW0A            // Associated Local LU
        NQ_LU_NAME=SPIFNET.NYM2DB2      // Network Qualified Name
        window opens
 
MODE    NAME=IBMRDB                     // Mode Name (8 char max)
        DLC_NAME=HOSTLINK               // Associated DLC
        PTNR_LU_NAME=NYM2DB2            // Associated Partner LU
        LCL_MAX_SESS_LMT=30             // Max Session Limit
        MIN_CW_SESS=15                  // Min Conwinners
        MIN_CL_SESS=15                  // Min Conlosers
        window opens

Define the Environment Variables Required by SunLink SNA

In order to run any application, you must set the following environment variables:

APPC_GATEWAY
Name of the DB2 for Solaris server (usually the TCP/IP hostname).

APPC_LOCAL_LU
Name of the local LU name provided in the SNA configuration file.

For a DB2 Connect for Solaris server, export these on the DB2 Connect machine before proceeding with the next step.

Start the SunLink SNA Subsystem

To start the SunLink SNA subsystem, perform the following steps:

Step  1.

Change to the SunLink installation directory, usually: 

   cd /opt/SUNWpu21

Step  2.

Set up environment variables for FlexLM licensing. For example: 

   export LD_LIBRARY_PATH=/usr/openwin/lib:/usr/lib
   export LM_LICENSE_FILE=/etc/opt/licenses/licenses_combined

Refer to the SunLink documentation for full details.

Step  3.

Ensure you have created the CPIC side file.

Step  4.

Ensure you have created the SNA server configuration file.

Step  5.

Use the sunop utility to check the status of SunLink SNA if it is already started.

Check to see if the PU and/or DLC status is connected. You can also use sunop to check the status of links.

Refer to the SunLink documentation for details of the sunop utility.

Step  6.

Stop SunLink if it is active. For example, enter: 

   kill -9 sunpu2.pid
   kill -9 sunlu2.pid

Step  7.

Start SunLink using the following command: 

   sunpu2.1



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

Go to Step 3. Catalog the APPC Node.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]