Quick Beginnings for DB2 Connect Enterprise Edition

Setting up SNA Communications for the DB2 Syncpoint Manager (SPM)

This section describes the SNA configuration requirements of the SPM, and explains the interdependencies between the SPM_NAME database manager configuration parameter and the communications configuration files.

The SPM using SNA connectivity is only supported on AIX, OS/2 and the Windows NT platform. The SPM using TCP/IP connectivity is supported on all DB2 UDB platforms.

These configuration steps are what is required for the SPM to initialise. They are not steps used for communications with remote host or AS/400 database servers or clients. Separate SNA configuration steps are required for actual communications. Please see Part 3 or Part 4 depending on your environment.

Configuring SNA Server for AIX

An LU6.2 Side Information profile and an LU6.2 Transaction Program Name profile must be defined to identify the SPM to the AIX SNA Server. The Side Information profile name and the Transaction Program Name profile name that SPM uses must match the SPM_NAME parameter of the database manager configuration. These profiles are used to allow DB2 to configure the syncpoint support. They are not used for any SNA communication.

Figure 23 shows the relationships between these entities.

Figure 23. SPM_NAME Usage with SNA Server for AIX. This diagram shows the relationships between SPM_NAME and SNA Server for AIX configuration objects.

Using SMIT

In the examples which follow:

The Database Manager configuration has SPM_NAME set to SPMNAME.
The Local LU name for the SPM is SPMLUNAM.

SPM_NAME can be set using the following command:

   update database manager configuration using spm_name SPMNAME

Side Information

Figure 24 illustrates the sample settings for defining the SPM LU in SMIT. The SPM Side Information profile identifies the local LU to be managed by the SPM. When a node directory entry is cataloged for a DRDA2 server, the Side Information profile (symbolic destination name) must use the same local LU alias as the local LU alias specified in the SPM Side Information profile.

This example uses SPMALIAS as the name of the SPM LU alias and SPMNAME as the profile name.

Figure 24. Side Information Profile for the SPM Local LU

+--------------------------------------------------------------------------------+
|                      Add LU 6.2 Side Information Profile                       |
|Type or select values in entry fields.                                          |
|After making all desired changes, press Enter.                                  |
|                                                                                |
|                                                        [Entry Fields]          |
|* Profile name                                       [SPMNAME]                  |
|  Local LU or Control Point alias                    [SPMALIAS]               + |
|  Provide only one of the following:                                            |
|     Partner LU alias                                []                       + |
|     Fully qualified partner LU name                 []                         |
|  Mode name                                          [IBMRDB]                 + |
|  Remote transaction program name (RTPN)             []                         |
|  RTPN in hexadecimal?                                no                      + |
|                                                                                |
|  Comments                                           [DB2 SyncPoint Profile]    |
+--------------------------------------------------------------------------------+

The SPM local LU cannot be the Control Point LU.

Transaction Program Name

Figure 25 illustrates the sample settings for defining the SPM Transaction Program Name profile using SMIT. The SPM Transaction Program Name profile identifies that the SPM supports all sync level conversations. Also, multiple instances supported must be set to no. Each DB2 instance is required to have a unique SPM_NAME.

Figure 25. Transaction Program Name Profile Required for SPM (for AIX)

+--------------------------------------------------------------------------------+
|                             Add LU 6.2 TPN Profile                             |
|Type or select values in entry fields.                                          |
|After making all desired changes, press Enter.                                  |
|                                                                                |
|[TOP]                                                   [Entry Fields]          |
|                                                                                |
|* Profile name                                       [SPMNAME]                  |
|  Transaction program name (TPN)                     []                         |
|  Transaction program name (TPN) is in hexadecimal?   no                      + |
|  PIP data?                                           no                      + |
|     If yes, Subfields (0-99)                        [0]                       #|
|  Use Command Line Parameters?                        no                      + |
|  Command Line Parameters                            []                         |
|  Conversation type                                   either                  + |
|  Sync level                                          all                     + |
|  Resource security level                             none                    + |
|     If access, Resource Security Access List Prof.  []                         |
|  Full path to TP executable                         [/dev/sna]                 |
|  Multiple instances supported?                       no    +                   |
|  User ID                                            [100]                     #|
|  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]             |
|                                                                                |
|  Comment                                             [DB2 SyncPoint TP]        |
|                                                                                |
| [BOTTOM]                                                                       |
+--------------------------------------------------------------------------------+

SNA System Defaults

On AIX, the SNA Server list of Trusted Group Names should be updated to include the groups which will be able to start SPM. To list the trusted group name, use SNA Defaults.
For AIX SNA Version 2 enable the recovery resource support.
For AIX SNA V3 enable the recovery resource support in the LU 6.2 profile representing the SPM_NAME value.

AIX/SNA Server Operational Considerations

Terminating SNA Server for AIX while the SPM is active causes the SPM to stop. Once SNA Server for AIX is restarted, you must issue db2stop and db2start on the DB2 Connect workstation in order to allow the SPM to reinitialize.

AIX SNA Server Coexistence Considerations

If a DB2 Connect workstation has Syncpoint Manager started and you want to use it as a DRDA1 AS or as a database server for clients accessing via APPC, you must do the following:

On the DB2 Connect for AIX Syncpoint Manager (SPM) Server Node:
1. You must install DB2 UDB Enterprise Edition or Extended Enterprise Edition for AIX.
2. Ensure that there are no SNA Server/UDB EE, EEE for AIX LU 6.2 Transaction Program Name (TPN) definitions defined for the following transaction programs:
  - X'07F6C4C2'
  - X'07F6E2D5'
  - X'06F2'
  - X'06F2F0F1'
  - DB2INTERRUPT (alphanumeric)
  - DB2DRDA (alphanumeric)
  - TP name defined in the database manager configuration parameter TPNAME.
  You can validate this by setting the SPM_NAME to the correct LU name and setting the DIAGLEVEL = 4 in the Database Manager Configuration. When you issue db2start to initiate the SPM you should NOT see the following message in the db2diag.log:
```
SPM0445 The Transaction Program TPname will not be listened for
by DB2. This is not a severe error, but if you require this Transaction
Program, you must ensure that it is not defined in the Transaction
Profile of the AIX SNA configuration.
```
On the Database Client Node:
Ensure all clients use the LU specified on the SPM node in the Database Manager Configuration parameter SPM_NAME as their partner LU.

Configuring Communications Server for OS/2 and Windows NT

The following example assumes:

Either IBM Communications Server for OS/2 V4.1 or IBM Communications Server for Windows NT V5.01 is installed
SPMNAME is the local LU name
SPM_NAME is set to SPMNAME.

These requirements must be met:

The SPM_NAME Database Manager Configuration parameter must specify the local LU to be used by SPM. The SPM_NAME cannot represent the Control Point LU. There is no need to configure any Communication Server profiles. DB2 will dynamically create or modify the necessary profiles. Ensure the LU represented by the SPM_NAME parameter is only used by DB2.

SPM_NAME can be set using the following command:
```
   update database manager configuration using spm_name SPMNAME
```
If your DB2 Universal Database SPM workstation will be used as a server accepting DB2 Universal Database client connections through APPC, you will need to ensure that you configure the database manager configuration parameter tpname with an appropriate value. For example:
```
db2 update dbm cfg using tpname NYSERVER
```

Note:

If all of the following apply to your environment:

You are using the SPM workstation to connect to host or AS/400 database servers.
You are using the SPM workstation to accept connections from host or AS/400 database clients.
You have DB2 Universal Database clients accessing the SPM workstation through APPC.

then the DB2 Universal Database clients and the host or AS/400 database clients must:

Use the same transaction program name to connect to the SPM workstation.
Use the SPM_NAME LU as their partner logical unit.

Communications Server Operational Considerations

Communications Server for OS/2 requires that syncpoint LUs be registered by the SPM before they can be used for DRDA2 calls. Thus DB2 must be started explicitly beforehand, in order that the SPM can register the syncpoint LU. Otherwise you may encounter the following message on DRDA2 calls:

 SQL0859N Access to the Transaction Manager Database failed with
 SQLCODE "-1032".  SQLSTATE=08502.

In order to execute DRDA1 calls successfully when DB2 is not started, the default LU should specify a non-SPM LU. You can use the APPCLLU environment variable to specify an LU name that is not the same as the value in SPM_NAME. Otherwise you may encounter the following message:

SQL30081N  A communication error has been detected. Communication protocol
being used: "APPC". Communication API being used: "CPI-C". Location where
the error was detected: "". Communication function detecting the error:
"xcstp". Protocol specific error codes: "20", "*", "*".  SQLSTATE=08001

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

[ DB2 List of Books | Search the DB2 Books ]