Chapter 3. Bidirectional Q replication on z/OS platforms 77
Figure 3-2 Overview of setup steps
3.5.1 Step 1: Install WebSphere MQ, WebSphere II with Q replication
The following documentation provides details on installing WebSphere MQ and
WebSphere II Replication.
IBM Program Directory for WebSphere MQ for z/OS Version 5 Release 3,
Modification Level 1, GI10-2548-03, for details on prerequisites and
installation; and IBM WebSphere MQ for z/OS System Setup Guide V5.3.1,
SC34-6052-02, to customize WebSphere MQ after it is installed.
IBM DB2 Information Integrator Replication Installation and Customization
Guide for z/OS Version 8.2, SC18-9127-01, for details on prerequisites and
steps for installing WebSphere II with Q replication.
We implemented the following configuration for our scenario:
1. Authorize WebSphere II programs to run as UNIX System Services (USS) as
a. Define RACF® group to contain any user IDs that will run WebSphere II
for z/OS, as shown in Example 3-1.
Collect topology & configuration information for WebSphere MQ & Q replication
STEP 2: Determine toplogy (unidirectional, bidirectional or peer-to-peer)
Install WebSphere MQ, WebSphere II with Q replication & verify successful install
STEP 4: Setup userids, privileges, and database servers
STEP 7: Set up WebSphere MQ and Q replication monitoring environment (GUI or commands)
STEP 5: Configure WebSphere MQ & verify successful configuration
STEP 6: Configure & activate Q replication (GUI or commands)
78 WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios
Example 3-1 RACF group
ADDUSER DB2PROD DFLTGRP(SYS1) OMVS(UID(3214) HOME(/u/db2prod) PROGRAM(/bin/sh))
+ NAME('QREP STARTED TASKS') NOPASSWORD NOOIDCARD SETROPTS CLASSACT(STARTED)
SETROPTS RACLIST(STARTED) GENERIC(STARTED)
RDEFINE STARTED QREP*.* STDATA(USER(DB2PROD) GROUP(SYS1) TRACE(YES))
RDEFINE STARTED QCAP*.* STDATA(USER(DB2PROD) GROUP(SYS1) TRACE(YES))
SETROPTS RACLIST(STARTED) GENERIC(STARTED) REFRESH
b. Grant any user ID that runs Q replication programs read-access to the
HFS install directory and its subdirectories.
c. Grant any user ID that runs Q replication programs write-access to the
/tmp directory or the directory that the TMPDIR environment variable
chmod -R a+r .....................
2. Define the WebSphere Information Integration environment to Unix System
Services (USS). Although we do not plan to execute the capture or apply
programs from USS or the Replication Center, this definition is required to run
the command programs to modify parameters via the BPXBATCH job.
a. A USS profile must be defined for any user ID running BPXBATCH.
b. The time zone specified for an East Coast environment is TZ=EST5EDT.
c. The language for messages is LANG=EN_US.
d. The temporary directory for output information is TMPDIR=/tmp.
e. The PATH environment variable points to a list of directories that the
system searches to find executable programs:
f. The STEPLIB environment variable points to the data set that contains
executable load modules:
g. The TMPDIR variable must be the same for user IDs that start a program
and issue commands to that program:
Since we intend to start the capture and apply programs via MVS Started
Task procedures, the HFS message catalog path must be specified in the
JCL, including the language to be used for messages and the USS path to
locate the messages.
If SMPE is used to install the product, the MSGS HFS file will be placed into
the following path. This will become the MSGS DD statement for capture and
apply, as follows:
//MSGS DD PATH='/usr/lpp//db2repl_08_02/msg/En_US/db2asn.cat'