Installation and Configuration Supplement

Configuring the SPM

This section describes the steps required to set up the SPM on a DB2 Connect or DB2 Universal Database server, and to configure remote clients and remote servers. It also lists considerations that apply with respect to the location of the transaction manager database, which may reside on the DB2 Connect server (the recommended location), or a DB2 Universal Database server.

Applications Which Access Host or AS/400 Database Servers

Applications Which Use DB2 Universal Database to Coordinate Multisite Updates

In this situation, only SNA connectivity requires the DB2 Syncpoint Manager. TCP/IP connectivity does not require the SPM for multisite updates. To setup the DB2 Syncpoint manager, complete the following steps:

step  1.
Ensure your host or AS/400 database servers are enabled for multisite update. On DB2 for MVS and DB2 for OS/390 the VTAM APPL statement for your DB2 location must have SYNCLVL=SYNCPT. For other host or AS/400 platforms, please see the online Connectivity Supplement.
step  2.
Install the DB2 Universal Database product which provides the DB2 SPM. This could be either DB2 Connect Enterprise Edition, DB2 Universal Database Enterprise Edition, or DB2 Universal Database Enterprise Edition - Extended.

Install DB2 Connect Enterprise Edition or DB2 Universal Database Enterprise Edition or Enterprise Edition - Extended to provide multisite update support with host or AS/400 database servers.
Create a database instance on the same system. For example, you can use the default instance DB2, or use the following command to create a new instance:
db2icrt myinstance

Supply licensing information as required.
Create a TM database. Any DB2 Universal Database Version 5 or greater can be used for this purpose. The TM database should be a local database on the DB2 Connect workstation. For example, to create the TM database, enter the following command in the command line processor:
create Database TMB alias TMB

Note: If you have only DB2 Connect Enterprise Edition installed, you are licensed to create one database that can be used as the TM database.

If the TM database is local, update the TM_DATABASE Database Manager Configuration parameter with the name of the TM database. For example:
update database manager configuration using tm_database TMB

Configure SNA communications as required. See "Setting up SNA Communications for the DB2 Syncpoint Manager (SPM)".
The configuration will be easier if the SPM_NAME value is the same as the LU name.
Determine the value to be specified for the SPM_NAME database manager configuration parameter, and values for the SPM_LOG_FILE_SZ and SPM_MAX_RESYNC database manager configuration parameters if the defaults are not appropriate for your situation. The default value for the SPM_NAME is a variant of the TCP/IP hostname. See Database Manager Configuration Parameters for further details.
If the default value is not acceptable, update SPM_NAME on the DB2 Connect or DB2 Universal Database system. For example, you can use the following command:
update database manager configuration using spm_name SPMNAME

Ensure that the registry value db2comm includes the value APPC.
Stop and restart the database manager on the DB2 Connect workstation/DB2 Universal Database server to enable the SPM.

step  3.
The database administrator must also perform the following steps at each system where a DB2 client will use DB2 Syncpoint services when accessing a host or AS/400 database server.

Update the TM_DATABASE Database Manager Configuration parameter with the name of the TM database. For example:
update database manager configuration using tm_database TMB

Configure communications as required for the DB2 client to connect to the server..
Stop and restart the database manager on the application requester.

Applications Which Use an XA Compliant TP Monitor to Coordinate the Multisite Update:

Examples of XA compliant TP monitors include:

IBM TX Series CICS
IBM TX Series Encina Monitor
BEA TopEnd
Microsoft Transaction Server
BEA Tuxedo

In this situation, SNA and TCP/IP connectivity requires the DB2 Syncpoint Manager. Both SNA and TCP/IP connectivity can be simultaneously supported by the DB2 Syncpoint Manager.

On the workstation which will be used:
1. Install DB2 Connect Enterprise Edition or DB2 Universal Database Enterprise Edition or Enterprise Edition - Extended to provide multisite update support with host or AS/400 database servers.
2. Create a database instance on the same system. For example, you can use the default instance DB2, or use the following command to create a new instance:
```
   db2icrt myinstance
```
3. Supply licensing information as required.
4. If SNA connectivity
  1. Ensure that the registry value db2comm includes the value APPC.
  2. Configure SNA communications as required. See "Setting up SNA Communications for the DB2 Syncpoint Manager (SPM)".
    The configuration will be easier if the SPM_NAME value is the same as the LU name.
5. If TCP/IP connectivity
  You must ensure the DB2 TCP/IP Listener is activated. Do the following
  1. Ensure that the registry value db2comm includes the value TCPIP.
  2. Ensure the Database Manager Configuration parameter SVCENAME is set to the proper TCP/IP port.
6. Determine the value to be specified for the SPM_NAME database manager configuration parameter, and optionally values for the SPM_LOG_FILE_SZ and SPM_MAX_RESYNC database manager configuration parameters if the defaults are not appropriate for your situation. Ensure that the SPM_NAME value is unique within your network. The SPM_NAME value will be set to a variant of the TCP/IP hostname when the instance is created.
  If only SNA connectivity is being used, the SPM_NAME value must be the local LU alias used for communications with the host system. If only TCP/IP connectivity is being used, then the suggested value for SPM_NAME is the TCP/IP hostname of the machine on which the DB2 instance is installed. If both SNA and TCP/IP are used, the SPM_NAME value must be the local LU alias of the local LU used for communications with the host system.
  See Database Manager Configuration Parametersfor further details.
7. If the default value is not acceptable, update SPM_NAME on the DB2 Connect workstation/DB2 Universal Database server. For example, you can use the following command:
```
   update database manager configuration using spm_name SPMNAME
```
8. Stop and restart the database manager on the DB2 Connect workstation/DB2 Universal Database server to activate the SPM.

Host or AS/400 Applications Which Access a DB2 Universal Database Server in a Multisite Update

In this situation, SNA connectivity is the only type supported. The DB2 Syncpoint Manager is required to permit multisite update. DB2 Universal Database does not support multisite update from host or AS/400 database clients using TCP/IP connectivity.

The database server which is being accessed from the host or AS/400 database client does not have to be local to the workstation which has the DB2 Syncpoint Manager. The host or AS/400 database client could connect to a DB2 UDB server using the DB2 Syncpoint Manager workstation as an interim server. This allows you to isolate the DB2 Syncpoint Manager workstation in a secure environment while the actual DB2 UDB Servers are remote in your organisation. This also permits UDB servers which do not have SNA Syncpoint Support to participate in a multisite update originating from a host or AS/400 database client.

The steps are as follwos:

On the workstation which has the DB2 Syncpoint Manager
1. Install DB2 Universal Database Enterprise Edition or Enterprise Edition - Extended to provide multisite update support with host or AS/400 database clients.
2. Create a database instance on the same system. For example, you can use the default instance DB2, or use the following command to create a new instance:
```
   db2icrt myinstance
```
3. Supply licensing information as required.
4. Ensure that the registry value db2comm includes the value APPC.
5. Configure SNA communications as required. See "Setting up SNA Communications for the DB2 Syncpoint Manager (SPM)".
  The configuration will be easier if the SPM_NAME value is the same as the LU name, and the SPM uses the same LU as the DB2 Connect workstation.
6. Determine the value to be specified for the SPM_NAME database manager configuration parameter, and values for the SPM_LOG_FILE_SZ and SPM_MAX_RESYNC database manager configuration parameters if the defaults are not appropriate for your situation. The default for SPM_NAME will be a variant of the TCP/IP hostname. See Database Manager Configuration Parameters for further details.
7. If the default value is not acceptable, update SPM_NAME on the DB2 Universal Database server. For example, you can use the following command:
```
   update database manager configuration using spm_name SPMNAME
```
8. Configure communications as required for this DB2 workstation to connect to remote DB2 UDB servers, if any.
9. Configure communications as required for remote DB2 UDB Servers to connect to this DB2 Syncpoint Manager workstation.
10. Stop and restart the database manager on the DB2 Universal Database server to start the SPM for the first time.
  You should be able to connect to the remote DB2 UDB servers from this DB2 Syncpoint Manager workstation.

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

Multisite updates using SNA connectivity is provided on OS/2, AIX, and Windows NT only.

The supported SNA stacks are:

IBM eNetwork Communications Server for OS/2 Version 5
IBM eNetwork Communications Server for AIX Version 5.0.2.4
IBM eNetwork Communications Server for Windows NT Version 5.01.

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

[ DB2 List of Books | Search the DB2 Books ]