Quick Beginnings

Step 2. Configure Your DB2 Connect System

Configure your DB2 Connect for AIX system as follows:

Log on to the AIX machine as root.
On the command line, enter:
```
   smit
```
Select panels in the following order:
1. Communications Applications and Services
2. SNA Server/6000
3. Configure SNA Profiles
4. Advanced Configuration.
The next several steps begin from the Advanced Configuration panel.

Update the Control Point Profile as follows:

Select the Control Point panel.
Select the Change/Show a Profile panel.

Between the square brackets [ ], enter the value of the XID node ID (combine the values for (14) (ID NUM plus IDBLK) plus (15) (Network name), or specify [*].

The control point name was probably set when the SNA Server for AIX was installed. For OS/390, MVS, VSE, and VM, check that this value matches (11).

To minimize confusion, use the same value for the control point alias as for the control point name.

For example, the panel could look like this:

              Change / Show Control Point Profile
 
 *Profile name                                node_cp
  XID node ID                                [07127509]       (14)+(15)
  Network name                               [SPIFNET]        (10)
  Control Point (CP) name                    [NYX1]           (11) 
  Control Point alias                        [NYX1]           (12)
  Control Point type                          appn_end_node
  Maximum number of cached routing trees     [500]
  Maximum number of nodes in the TRS database[500]
  Route addition resistance                  [128]

Check the Token Ring SNA DLC Profile as follows:
1. Select the Links panel.
2. Select the Token Ring panel.
3. Select the Token Ring SNA DLC panel.
4. Select the Change/Show a Profile panel.
5. The profile name and data link device name were probably set when SNA Server for AIX was installed. If you have a reason to change these values, you can do so. If no values appear in the profile, talk to your LAN administrator.
  Write down the profile name (9).
  For example, the profile might look like this:
```
               Add Token Ring SNA DLC Profile
 
 *Profile name                                 [tok0.00001]   (9)
  Data link device name                        [tok0]
  Force disconnect time-out (1-600 seconds)    [120]
  User-defined maximum I-Field size?           no
     If yes, Max. I-Field size (265-30729)     [30729]
```
6. If you will use APPC for connections from remote clients, make sure that the profile has the following value:
```
  Dynamic link stations supported?                    yes
```

Create a Mode Profile as follows:

Select the Sessions panel.
Select the LU 6.2 panel.
Select the LU 6.2 Mode panel.
Select the Add a Profile panel.

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:

 *Profile name                                      [IBMRDB] (16)
  Mode name                                         [IBMRDB] (16)
  Maximum number of sessions (1-5000)               [30]     (*)
  Minimum contention winners (0-5000)               [15]     (*)
  Minimum contention losers (0-5000)                [15]     (*)
  Auto activate limit (0-500)                       [0]
  Upper bound for adaptive receive pacing window    [16]
  Receive pacing window (0-63)                      [8]      (*)
  Maximum RU size (128,...,32768: multiples of 32)  [4096]   (*)
  Minimum RU size (128,...,32768: multiples of 32)  [1024]   (*)
  Class of Service (COS) name                       [#CONNECT]

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 AIX. For OS/400, control point routing would normally be used instead of an LU.Create a Local LU profile as follow:

Select the Sessions panel.
Select the LU 6.2 panel.
Select the LU 6.2 Local LU panel.
Select the Add a Profile panel.

Update the three lines with the following values: Use (12) for the first two lines, and (13) for the third line. For example, the file could look like this:

               Add LU 6.2 Local LU Profile
 
 *Profile name                                   [NYX1GW01]   (12)
  Local LU name                                  [NYX1GW01]   (12)
  Local LU alias                                 [NYX1GW01]   (13)
  Local LU is dependent?                          no
     If yes,
        Local LU address (1-255)                 []
        System services control point
            (SSCP) ID (*, 0-65535)               [*]
        Link Station Profile name                []
  Conversation Security Access List Profile name []

Configuring Each Server Connection

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

Configure each DRDA server connection that you require as follows:

Update the Token Ring Link Station Profile as follows:

Select the Links panel.
Select the Token Ring panel.
Select the Token Ring Link Station panel.
Select the Add a Profile panel.

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]              (*)

Update the LU 6.2 Side Information Profile as follows:
1. Select the Sessions panel.
2. Select the LU 6.2 panel.
3. Select the LU 6.2 Side Information panel.
4. Select the Add a Profile panel.
5. 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 or VSE the default is the RDB_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 LU 6.2 Side Information Profile
 
 *Profile name                              [DB2CPIC]         (17)
  Local LU or Control Point alias           [NYX1GW01]        (12)
  Provide only one of the following:
     Partner LU alias
     Fully qualified partner LU name        [SPIFNET.NYM2DB2] (1.2)
  Mode name                                 [IBMRDB]          (6)
  Remote transaction program name (RTPN)    [07F6C4C2]        (18)
  RTPN in hexadecimal?                       yes
```
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.
Update the Partner LU 6.2 Location Profile as follows:
1. Select the Sessions panel.
2. Select the LU 6.2 panel.
3. Select the Partner LU 6.2 Location panel.
4. Select the Add a Profile panel.
5. 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:
```
             Add Partner LU 6.2 Location Profile
 
*Profile name                                       [NYM2DB2] (2)
 Fully qualified partner LU name            [SPIFNET.NYM2DB2] (1.2)
 Partner LU location method                             owning_cp
 If owning_cp,
  Fully qualified owning Control Point (CP) name[SPIFNET.NYX] (3.4)
  Local node is network server for LEN node?                   no
```

Configuring DB2 Connect for Remote Clients

Configure your DB2 Connect server to accept inbound APPC requests from remote clients as follows:

Select the Sessions panel.
Select the LU 6.2 panel.
Select the LU 6.2 Transaction Program Name (TPN) panel.
Select the Add a Profile panel.

Add the following profile, replacing NYSERVER with the TP name for your DB2 server.

*Profile name                                      [db2v5]   (*)
 Transaction program name (TPN)                    [NYSERVER](27)
 Transaction program name (TPN) is in hexadecimal? no
 PIP data?                                         no
   If yes, Subfields (0-99)                        [0]
 Conversation type                                 basic     (*)
 Sync level                                        none/confirm
 Resource security level                           none
      If access, Resource Security Access List Prof. []
 Full path to TP executable    [INSTHOME/sqllib/bin/db2acntp](*)
 Multiple instances supported?                     yes        (*)
 User ID                                           [1918]     (*)
 Server synonym name                               []
 Restart action                                     once
 Communication type                                 signals
    If IPC, Communication IPC queue key            [0]
 Standard input file/device                        [/dev/console]
 Standard output file/device                       [/dev/console]
 Standard error file/device                        [/dev/console]
 
 Comments                                          []

Notes:

This profile will be used for both database connections and interrupts by DB2 Universal Database Version 5 and Version 2.1 clients.
If you are migrating from a previous release of DB2 Connect, you should be aware that the db2acntp, db2aittp and db2cnsm executables have been consolidated into the db2acntp executable.

Create any additional APPC partner LU and link profiles that may be required.
Ensure the clients are also properly configured.
Use SNA Server functions, without using DB2 Connect, in order to validate that all the APPC sessions that you need to establish can be.
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.
Stop the database manager, if it is running:
```
   db2stop
```
Set the value of the DB2COMM environment variable to include the string APPC.
Start the database manager:
```
  db2start
```

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

[ DB2 List of Books | Search the DB2 Books ]