IBM Books

Quick Beginnings for DB2 Connect Enterprise Edition

Step 2. Configure Your DB2 Connect System

Configure your DB2 Connect system as follows:

  1. Log on to the AIX machine as root.

  2. On the command line, enter 
    smit

  3. Select panels in the following order:

    1. Communications Applications and Services

    2. Communications Server for AIX

    3. Configure SNA Resources

    4. Local Node Resources

  4. Select Node Definition. Add the control point name (4) and fully qualified Control Point name ((3).(4) as follows: 
                                    Node Definition
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
 
                                                        [Entry Fields]
* Control Point alias                                [NYX]
  Description                                        []
* Fully-qualified Control Point name                 [SPIFNET.NYX]
  Node type                                           END_NODE                +
  Node identifier                                    [05d29798]                X
  Management Services support                         NORMAL                  +
 
  If BACK_LEVEL,
 
        Queue NMVTs?                                  NO                      +

  5. Return to the Local Node Resources panel and select panels in the following order:

    1. Connectivity

    2. DLCs, Ports and Link Stations

    3. Add Connectivity Resources

    4. Add Token Ring Resource

    5. Add Token Ring DLC

    Between the square brackets, enter your DLC Profile name (9): 

                                   Add Token Ring DLC
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
 
                                                        [Entry Fields]
* DLC name                                           [tok0.001]
  Description                                        []
  Negotiable link stations supported?                 YES                     +
  Initially active?                                   YES                     +
  Adapter Number                                     [0]                       #
  Maximum number of SAPs on the DLC                  [16]                      #

  6. Return to the Add Token Ring Resource panel and select Add Token Ring Port. Between the square brackets, add your DLC Profile name (9). An example screen might look like: 
                                  Add Token Ring Port
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
 
                                                        [Entry Fields]
* Port name                                          [sap04]
  Description                                        []
* DLC Name                                           [tok0.001]                       +
  Local SAP address                                  [04]                      X
  Initially active?                                   YES                     +
  Use HPR on implicit links?                          NO                      +
  Use HPR link level error recovery?                  NO                      +
  Maximum receive BTU size allowed                   [4105]                    #
  Maximum number of active links allowed             [255]                     #
  Local name                                         []
  XID retry count                                    [2]                       #
  Frame retransmit (T1) timer (1=500ms)              [8]                       #
  Frame retransmit limit                             [2]                       #
  Receive ack (T2) timer (1=500ms)                   [1]                       #

  7. Return to the Add Token Ring Resource panel and select Add Token Ring Link Station. Between the square brackets, add the adjacent note Control Point name ((4) on your worksheet). A sample screen might look like: 
                              Add Token Ring Link Station
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
 
[TOP]                                                   [Entry Fields]
* Link station name                                  [3745]
  Description                                        []
* Port name                                          [sap04]                       +
  Adjacent node Control Point name                   [NYX]
  Adjacent node type                                  LEARN_NODE              +
  Downsteam PU services supplied                      NONE                    +
 
  If SNA Gateway or DLUR,
        Downstream PU name                           []
 
  If DLUR,
        DLUS server name                             []                                                                  
  Local node id                                      [05d29798]                X
  Adjacent node id                                   [05d29801]                X
  Adjacent node MAC address                          [400011528901]                        X
  Adjacent node SAP address                          [04]                      X
  Maximum BTU size to be sent                        [4105]                    #
  Host type                                           SNA                     +
  Request CP-CP sessions?                             YES                     +
  HPR supported?                                      NO                      +
  Use HPR link-level error recovery?                  NO                      +
  Solicit SSCP sessions?                              NO                      +
  Remote node is a network node server                NO                      +
  Link station role                                   USE_PORT_DEFAULTS       +
  Activation                                          USE_INITIALLY_ACTIVE    +
  XID retry limit                                    [2]                       #
  Frame retransmit (T1) timer (1=500ms)              [8]                       #
  Frame retransmit limit                             [2]                       #
  Receive ack (T2) timer (1=500ms)                   [1]                       #

  8. Create a Mode Profile as follows. From the Local Node Resources panel, choose the following:

    1. Lu 6.2 Configuration

    2. Lu 6.2 Mode

    3. Add Mode

    Define your Mode Profile. For profile name and mode name, use the value that you wrote in item (16) of the worksheet. On the other lines, specify values that match the mode profile defined on your DRDA server systems. If you are using the mode IBMRDB, specify the following values: 

                                           
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
 
                                                   [Entry Fields]
* Name                                               [IBMRDB]
  Description                                        []
 
  Session limits
 
        Maximum number of sessions                   [256]                   #
        Initial session limit                        [128]                       #
        Min con. winner sessions                     [64]                       #
        Min con. loser sessions                      [64]                       #
        Auto-activate sessions                       [0]                       #
 
  Receive pacing window
 
        Initial                                      [4]                       #
        Maximum                                      [0]                       #
 
 
  Use default RU sizes?                               YES                     +
 
  If YES,
 
        Maximum RU size upper bound                  [32767]                    #
        Maximum RU size lower bound                  [1024]                       #

  9. If the DB2 Connect workstation is defined as an LU, update the local LU Profile as follows. In most cases, a VTAM administrator on OS/390, MVS, VSE, or VM would define an LU for DB2 Connect. For OS/400, control point routing would normally be used instead of an LU. Create a local LU profile as follows:

    1. From the Local Node Resources panel, select LU 6.2 Configuration

    2. Select LU 6.2

    3. Select Add Independent LU Type 6.2

    4. Update the LU Alias and LU name lines with the following values... 
                                Add Independent LU Type 6.2
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
 
                                                        [Entry Fields]
* LU alias                                           [NYX1GW01]
  List name                                          []                       +
  Description                                        []
* LU name                                            [NYX1GW01]
  Support Syncpoint?                                  NO                      +
  Additional LU properties                            NONE                    +
  Restrict SSCP to SSCP id                           [0]

Configuring Each Server Connection

Before using this section, be sure that you have completed the worksheet Table 19 for each OS/400, OS/390, MVS, VM, or VSE host, plus the worksheet Table 48 for each OS/400 host.

Configure each DRDA server connection that you require as follows:

  1. Update the Token Ring Link Station Profile as follows:

    1. Select the Links panel.

    2. Select the Token Ring panel.

    3. Select the Token Ring Link Station panel.

    4. Select the Add a Profile panel.

    5. Update the profile, as follows:

      • Change the profile name to the value for (7). For example: 
         *Profile name                                  [NYX1LS]     (7)
  Use Control Point's XID node ID?              yes
      • Change the SNA DLC profile name to the value for (9). For example: 
           SNA DLC Profile name          [tok0.00001]   (9)
  Stop link station on inactivity?         no
      • Change the remote link address to the value for (8). For example: 
         If link_address,
  Remote link address           [400009451902] (8)
  Remote SAP address (04-ec)    [04]
      • If you want to activate the link only when it is needed (rather than activating it when the SNA starts up), update several lines of the profile, as follows: 
          
  Adjacent Node Identification Parameters
  Verify adjacent node?                         yes           (*)
  Network ID of adjacent node                   SPIFNET       (3)
  CP name of adjacent node                      NYX           (4)
  XID node ID of adjacent node (LEN node only)  [*]
  Node type of adjacent node                    appn_end_node (*)
 
 Link Activation Parameters
  Solicit SSCP sessions?                        yes
  Initiate call when link station is activated? yes
  Activate link station at SNA start up?        no            (*)
  Activate on demand?                           yes           (*)
  CP-CP sessions supported?                     yes
  If yes,
   Adjacent network node preferred server?      no
  Partner required to support CP-CP sessions?   no
  Initial TG number (0-20)                   [1]              (*)

  2. Update the LU 6.2 Side Information Profile as follows: from the Local Node Resources panel,
    1. Select the LU 6.2 Configuration panel.
    2. Select the LU 6.2 Side Information panel.
    3. Select the Add Side Information panel.
    4. Update the profile, as follows:
      • For the profile name, use the value for (17). This value is case-sensitive; it is recommended that you use uppercase letters.
      • For the local LU or control point alias, use the value for (12).
      • For the fully qualified partner LU name, use the value for (1) followed by a period and the value for (2).
      • For the mode name, use the value for (6).
      • For the next two lines, specify the remote transaction program name. You must specify a value. There is no default value in SNA Server for AIX. On the DRDA server, the default for OS/390, MVS, or OS/400 is X'07F6C4C2'. For VM the default is the RDB_NAME and for VSE the default is the AXE transaction name.

        Use the value from (18) on the worksheet, or enter the default value. If the value is hexadecimal, specify yes for the second line; otherwise, specify no.

      For example, the file could look like this: 

                                    Add Side Information
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
  
                                                        [Entry Fields]
* Symbolic destination name                           nfcpic
  Description                                        []
  Local LU Alias                                     [NYX1GW01]               +
  Partner LU name                                    [SPIFNET.NYM2DB2]          +
  Mode                                               [IBMRDB]                 +
  TP name type                                        APPLICATION_TP          +
  TP name                                            [DB2DRDA]                +
  Conversation security                               NONE                    +
  User ID                                            []                       
  Password                                           []

    Note that if you are retrieving information about this server from the DCE Directory, then you do not need to have the Side Information Profile. More information about configuring DB2 Connect with DCE is provided in the Administration Guide, and DB2 Connect User's Guide.

  3. Update the Partner LU 6.2 Location Profile as follows:
    1. From the LU 6.2 Configuration panel, select the Partner LU 6.2 Location panel.
    2. Select the Location by Link Station panel.
    3. Update the profile, as follows:

      • For the profile name, use the value for (2).
      • For the fully qualified partner LU name, use the value for (1) followed by a period and the value for (2).
      • For the fully qualified CP name, use the value for (3) followed by a period and the value for (4).

      For example, the file could look like this: 

                                  Location By Link Station
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
 
                                                        [Entry Fields]
* Local LU name                                      [NYX1GW01]
  Fully-qualified partner LU name                    [SPIFNET.NYM2DB2]
  Partner name contains wildcards?                    NO                      +
  Description                                        []
* Link station name                                  [NYX1LS]                       +

Configuring DB2 Connect for Remote Clients

Configure your DB2 Connect server to accept inbound APPC requests from remote clients as follows.
Note:If inbound APPC requests are from remote DRDA Application Requestors, you will need to:

  • apply APAR IX77539 if you are using CS/AIX V5.

  • Update the SNA server list of Trusted group names to include the groups which will start the APPC listener to accept incoming DRDA connections. Issue the following command: 
    snaadmin define_trusted_groups, group_id=gid

  1. From the LU 6.2 Configuration panel:

  2. Select the LU 6.2 Transaction panel.

  3. Select the Add Transaction Program panel.

  4. Add the following profile, replacing NYSERVER with the TP name for your DB2 server. 
                                Add Transaction Program
 
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
  
                                                        [Entry Fields]
* Name                                               [NYSERVER]
  Description                                        []
  List name                                          []                       +
  Conversation type(s) supported                      BASIC                   +
  Conversation security is required?                  NO                      +
  Synchronization level supported?                    NONE                    +
  Program Initialization Parameters (PIP) allowed?    YES                     +

    Note:When creating new TP profiles (as opposed to migrating TP profiles from CS/AIX V4 profiles), you will need to perform the following steps:

    1. Edit the file /etc/sna/sna_tps.

    2. Search for TP profiles created for DB2 connections and modify the field STYLE=EXTENDED to STYLE=COMPATIBLE.

  5. This profile will be used for both database connections and interrupts by DB2 Universal Database Version 5 and Version 2.1 clients.

    Create any additional APPC partner LU and link profiles that may be required.

  6. Ensure the clients are also properly configured.

  7. Use Manage SNA Resources, without using DB2 Connect, in order to validate that all the APPC sessions that you need can be established.

  8. Configure the database manager. You must add the TP name that will be used by the client. to the database manager configuration file. One way to do this is to issue the following CLP command: 
    update database manager configuration using tpname NYSERVER
    The name NYSERVER is the TP name for the DB2 server.

  9. Stop the database manager, if it is running: 
       db2stop

  10. Set the value of the DB2COMM environment variable to include the string APPC.

  11. Start the database manager: 
      db2start

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

[ DB2 List of Books | Search the DB2 Books ]