Quick Beginnings

Installing the SPM

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

At the application requester
At the DB2 Connect server (the recommended location)
At a separate node.

The following rules apply throughout the remainder of this section:

Notes:

The SPM instance name must be the same as the SPM_NAME database manager configuration parameter.
For both the TM database and the SPM instance, the Database alias name must be the same as the actual database name.
Inbound DRDA 2 connections via the SPM LU to DB2 Universal Database V5.0 servers running DRDA-AS do not require a TM database, nor do they need such a database to be defined. The reason is that, for such connections, the SPM itself is the Transaction Manager (TM) for the DB2 Universal Databases, having its own logging by means of the SPM instance.
You do not need to take any actions to create the SPM instance. It is created automatically by the SPM, through emulation. This allows connections to the SPM to occur with normal CONNECT commands. Because no instance is actually created, you will not see the instance in the output from the db2ilist command.

If the SPM is on a different node to the TM database, then the SPM name must be cataloged in the database directory and the SPM node must be cataloged in the node directory on the TM node.

Summary of Steps

Perform the following steps at the workstation that has the SPM installed. This could be a DB2 Connect Enterprise Edition server, or a DB2 Universal Database Enterprise Server, or a workstation that contains both.
Note: If you expect to have only connections originating from a host system to a DB2 Universal Database server or if you use only a TP Monitor environment such as CICS for AIX, you do not require a TM Database. In order to be able to use SPM, and therefore you can omit steps 4, 5, and 6 in this section.

Install DB2 Connect Enterprise Edition in order to provide DRDA AR support, and/or DB2 Universal Database Enterprise Edition in order to provide DRDA AS support.
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 Version 5 database 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
```
The Database alias name must be the same as the actual database name.
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
```
If the TM database is remote, in order for the SPM to be able to access it during resync operations, you must catalog the TM database and node directory entries on the DB2 Connect workstation. For example:
```
   catalog tcpip node TMBNODE remote SERVERB server dbinst1c
   db2 catalog database TMB as TMB at node TMBNODE
```
The Database alias name must be the same as the actual database name.
You must also perform the following steps at the TM database node, in order that it can connect to the location of the SPM. For example:
```
   catalog tcpip node SPMNODE remote SERVERD server dbinst1c
   db2 catalog database SPMNAME as SPMNAME at node SPMNODE
```
The Database alias name must be the same as the actual database name.
Configure SNA communications as required. See "Setting up Communications for the 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.
On an AIX system, the SPM_NAME value must be same as the names of:
1. The transaction program (TP) profile used by the SPM.
2. The local side information profile used by the SPM.
3. The SPM instance name on application requesters.
Refer to Figure 21.
Catalog remote DB2 Universal Database server databases being accessed from a DRDA Application Requester (such as DB2 for OS/390 V5.1) through the SPM. For example:
```
   catalog tcpip node DB2UDSRV remote DB2UDSRV server db2inst1c
   db2 catalog database DB2UDB1 as DB2UDB1 at node DB2UDSRV
```
Determine the value to be specified for the 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. See "Database Manager Configuration Parameters for SPM" for further details.
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
```
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 start the SPM LU for the first time.

Summary of Steps for DB2 Clients Connecting to a Host

The database administrator must also perform the following steps at each system where a client will use SPM services.
Note: If you only use a TP monitor, such as CICS for AIX, you can omit steps 1 and 3 in this section.

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 application requester to connect to the SPM LU at the DB2 Connect workstation.
If the TM database is remote, catalog the database directory entry for the TM database, and catalog the node entry for the location of the TM database. For example:
catalog tcpip node TMBNODE remote SERVERB server db2inst1c db2 catalog Database TMB as TMB at node TMBNODE

The Database alias name must be the same as the actual database name.
If the SPM is remote, catalog the database directory entry for the SPM instance, and catalog the node entry for the location of the SPM. For example:
catalog tcpip node SPMNODE remote SERVERD server db1inst1c db2 catalog database SPMNAME as SPMNAME at node SPMNODE

The Database alias name must be the same as the actual database name.
Stop and restart the database manager on the application requester.

The remaining sections in this chapter review specific implementation considerations.

Summary of Steps for Remote DB2 Universal Database Servers Accessed from DRDA Hosts

This section summarizes the steps required at the DB2 Universal Database servers that contain databases accessed by host systems through the SPM. These DB2 databases are remote from the SPM workstation.

Ensure that the appropriate communication protocols are installed and enabled. To see which protocols are enabled, enter:
```
   db2set -all
```
For instructions on enabling a communication protocol, see Chapter 39. "Controlling Your DB2 Environment".
As the SPM is remote, catalog the database directory entry for the SPM instance, and catalog the node entry for the location of the SPM. For example:
```
   db2 catalog tcpip node SPMNODE remote SERVERD server db1instlc
   db2 catalog database SPMNAME as SPMNAME at node SPMNODE
```
Note: There is no need to configure the SPM_NAME database configuration parameter on this workstation.

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

[ DB2 List of Books | Search the DB2 Books ]