Chapter 3. Bidirectional Q replication on z/OS platforms 89
Table 3-4 Replication Alert Monitor configuration information
3.5.4 Step 4: Set up user IDs, privileges, and database servers
The user IDs that run the Q replication and event publishing programs need
authority to connect to servers, access or update tables, put and get from
WebSphere MQ queues, and perform other operations such as write to
directories. In addition, appropriate databases to be used in replication need to
be created and cataloged for access by the Replication Center. The steps
involved are described here.
Q Subscriptions list (A.29)
23 ITSO-xxxx tables
(B.29)
23 ITSO-xxxx tables
Description Server A Server B
Description Designated server
Host name (M.1) WTSC53
Host IP address (M.2) 9.12.6.77
DB2 subsystem name or instance owner (M.3) D8G1
DB2 tcp port (M.4) 38060
Monitor database server/alias information
򐂰 Database server/alias
򐂰 db2instance
򐂰 User ID/password
򐂰 Contact name
򐂰 Contact email address
򐂰 Monitor qualifier
򐂰 Schema name
򐂰 (M.5a) DB8G
򐂰 (M.5b) D8G1
򐂰 (M.5c) QREPADM/xxx
򐂰 (M.5d) QMONITOR
򐂰 (M.5e) QREPADM@us.ibm.com®
򐂰 (M.5f) ITSO_QMON
򐂰 ASN
Monitor log path (not for z/OS) (M.6)
DB2 group name (z/OS only) (M.7) D8GG
DB2 location name (z/OS only) (M.8) DB8G
Note: These tables and our configuration use a single subsystem member of
the DB2 share group as the database alias for connecting replication
programs to the database. If one is running in a share group, for greater
flexibility consider using the DB2 group name as the alias, and placing the MQ
objects in a WebSphere MQ cluster. That will allow replication programs to run
on any member of the sysplex.
90 WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios
User IDs and privileges
User IDs need to be defined for executing Q Capture (reference A.7b in Table 3-1
on page 85) and Q Apply (reference A.7c in Table 3-1 on page 85).
򐂰 Q Capture
User IDs that run a Q Capture program must:
Be registered with access to UNIX System Services (USS).
The Q Capture program must be APF authorized, which means that the
program must reside in an APF authorized library, and the user must have
execution access to it.
Be defined to use z/OS UNIX or OS/390® UNIX (must have an OMVS
segment).
An OMVS segment is the portion of a RACF® profile that contains OMVS
logon information.
Have read and write access permission to either the /tmp directory or the
directory that is specified by the TMPDIR environment variable.
Have SYSADM authority, or the following specific privileges:
SELECT, UPDATE, INSERT, and DELETE for all control tables on the
Q Capture server
SELECT for the DB2 catalog (SYSIBM.SYSTABLES,
SYSIBM.SYSCOLUMNS, SYSIBM.SYSTABCONST,
SYSIBM.SYSKEYCOLUSE, SYSIBM.SYSINDEXES, and
SYSIBM.SYSKEYS)
TRACE
MONITOR1 and MONITOR2
EXECUTE for the Q Capture program packages
򐂰 Q Apply
User IDs that run a Q Apply program must:
Be registered with access to UNIX System Services (USS).
The Q Apply program must be APF authorized, which means that the
program must reside in an APF authorized library, and the user must have
execution access to it. The program must be APF-authorized in order for
the Q Apply program to use the Automatic Restart Manager (ARM) or
produce SVCDUMPs.
Be defined to use z/OS UNIX or OS/390® UNIX (must have an OMVS
segment).
An OMVS segment is the portion of a RACF® profile that contains OMVS
logon information.

Get WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.