DB2 Universal Database primary data servers on OS/390

This section describes the primary database issues and considerations specific to the DB2 Universal Database server (on an OS/390 platform) in a Sybase replication system.

Replication Agent for DB2 UDB for OS/390

As a primary data server, DB2 interacts with the Replication Agent for DB2 UDB for OS/390 (Replication Agent for DB2 UDB).

The Replication Agent identifies and transfers information about data-changing operations (or transactions) from a DB2 primary data server to a primary Replication Server.

The Replication Agent interacts with the primary Replication Server, and with the RSSD of the primary Replication Server, if so configured.

NoteThis book describes how to use Replication Agent for DB2 UDB for OS/390 version 12.6. If you have a different version of Replication Agent for DB2 UDB, refer to the appropriate documentation for that product.

DB2 for OS/390 primary database permissions

Two user IDs must be created in DB2 to facilitate its operation as a primary data server:

Replication intrusions and impacts in DB2 for OS/390

The performance and operation of DB2 primary data servers in a Sybase replication system might be affected by the following:

Primary data server connectivity

Replication Agent for DB2 UDB requires the following to connect to a DB2 primary data server in an OS/390 environment:

Replication Server connectivity

Replication Agent for DB2 UDB requires the following to connect to the primary Replication Server:

RSSD connectivity

Replication Agent for DB2 UDB requires the following to connect to the Replication Server System Database (RSSD) of the primary Replication Server:

DB2 for OS/390 primary database configuration issues

The Replication Agent for DB2 UDB is a mainframe OS/390 application. It consist of two tasks that run simultaneously in a single OS/390 address space:

One Replication Agent for DB2 UDB started task is required for each DB2 log from which transactions will be replicated.

All Replication Agent installation and configuration issues are described in the Replication Agent for DB2 UDB Installation Guide for OS/390. The following items, however, may need further attention in a heterogeneous replication system:

Replication definitions for primary tables in DB2 for OS/390

The LTM for MVS Use_repdef configuration parameter controls whether the Replication Agent sends Log Transfer Language (LTL) that contains only the columns specified in a replication definition, or all of the columns in the DB2 primary table.

When the value of the Use_repdef parameter is set to N, the Replication Agent sends LTL with data for all of the columns in the DB2 primary table. When the value of the Use_repdef parameter is set to Y, the Replication Agent sends LTL with data for only the columns specified in the replication definition.

By sending data for only the columns needed for the replication definition, network traffic is reduced, which can improve performance.

If you set the value of Use_repdef to Y, you can use other LTM for MVS parameters, such as Minimal_cols and Suppress_col_names, to enhance Replication Agent performance. See the Replication Agent for DB2 UDB Installation Guide for OS/390 for more information.

DB2 for OS/390 primary datatype translation issues

The LTM for MVS Date_in_char configuration parameter controls whether the Replication Agent sends values in DB2 DATE columns as default CHAR(10) character strings, or converts them to the Sybase datetime format.

NoteSetting the Date_in_char parameter to convert DB2 DATE columns to Sybase datetime values will conflict with replication definition map to clauses that refer to Replication Server user-defined datatype definitions (UDDs).

In general, if the value of the Date_in_char parameter is set to N, all of the corresponding datatypes in replication definitions for DATE columns must specify the Sybase datetime datatype (that is, you cannot specify a map to clause in the replication definitions).

If you want to specify a UDD in the replication definition, you must set the value of the Date_in_char parameter to Y, and you cannot specify the Sybase datetime datatype as the source datatype for DATE columns in the replication definition.

The UDD specified in a replication definition must correspond to the default DATE format for the primary data server. The character (char or varchar) datatype specified in a replication definition for a DATE column must have sufficient length to accommodate the column’s default display length.

See the Replication Agent for DB2 UDB for OS/390 User’s and Troubleshooting Guide for a complete description of the Date_in_char parameter. See the Replication Server Administration Guide for a complete description of UDDs and their use.

NoteIf you use any date- or time-related UDDs in a replication definition, Sybase recommends that you set the Date_in_char parameter to Y to send the character representation of those values. This is a general recommendation for all Replication Agent configurations when UDDs are used.

In general, the Replication Agent for DB2 UDB should not perform datatype translations. The only condition under which you should consider having the Replication Agent perform datatype translation is when all of the replicate data servers require the same translation. In that case, from the point of view of saving processing time, it is probably better to perform the translation once at the Replication Agent, rather than at each replicate database DSI.

DB2 for OS/390 system management issues

Replication Server Manager (RSM) does not manage or monitor the Replication Agent for DB2 UDB for OS/390. RSM can, however, manage a replication system in which DB2 for OS/390 is either the primary or replicate data server.