WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios

Chapter 3. Bidirectional Q replication on z/OS platforms 271

Figure 3-122 SQL script ran successfully message

The alert conditions have been changed and will take effect when the alert

monitor is re-initialized either via the Replication Center (if DAS has been

installed), or by running the USS command job asnmcmd.

3.5.9 Step 7: Set up monitoring environment using commands

WebSphere II Replication Alert Monitor configuration may be performed using

GUI, as described in 3.5.8, “Step 7: Set up monitoring environment using GUI”

on page 230, or by using ASNCLP commands to generate SQL scripts.

As mentioned earlier, ASNCLP does not run directly in a z/OS environment,

therefore the SQL scripts cannot be executed from ASNCLP as they are

generated. ASNCLP may be executed on UNIX or Windows to generate SQL

that can then be ported to z/OS and executed under SPUFI or DSNTEP2.

Note: Several options for communicating with Q replication programs running

on the z/OS platform are discussed in Appendix G, “Communicating with Q

replication programs in z/OS” on page 873.

Note: ASNCLP commands are executed in the asnclp utility. After executing a

command, the returned text should be reviewed very carefully since ASNCLP

tends to be very wordy, even for a successful execution.

Important: Before running ASNCLP on the workstation, the user environment

must be configured to provide support for Java, as shown in Example 3-37 on

page 193.

272 WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios

To ensure that the environment has been set up properly, run the asnclp

command. If the >Repl command line appears, the setup was successful. Enter

quit to exit the Repl> command line, as shown in Example 3-38.

We recommend that the commands to perform the various tasks be stored in a

file and then executed by directing the file to the asnclp utility, as shown in

Example 3-39.

The ASNCLP commands in the following sections are categorized according to

the following tasks:

The steps involved are mostly the same as with the GUI approach, as follows:

1. Create the Replication Alert Monitor control tables.

2. Create the Replication Alert Monitor contact.

3. Create the Replication Alert Monitor alert conditions.

These steps are described in detail in the following subsections.

Create the Replication Alert Monitor Control Tables in D8G1

Example 3-53 lists the ASNCLP commands for creating the Replication Alert

Monitor Control Tables on the D8G1 server. These commands should be saved

in a file that is then executed using the command described in Example 3-39 on

page 194.

Example 3-53 Create Replication Alert Monitor Control Tables on D8G1

#############################################################

##The variables in the commands are shown unbold, and

##these values are substituted from the templates described

##in Table 3-1 on page 85 and Table 3-4 on page 89

############################################################

##D8G1 from reference M.3 in Table 3-4 on page 89

##QREPADM from reference M.5c in Table 3-4 on page 89

##QREPITSO from reference B.10 in Table 3-1 on page 85

#############################################################

SET SERVER MONITOR TO DB D8G1 ID QREPADM PASSWORD "xxxxxxxx" ;

SET RUN SCRIPT LATER ;

SET PROFILE MYPROF FOR OBJECT PAGE LOCK TABLESPACE OPTIONS ZOS DB QREPITSO

BUFFERPOOL BP2;

SET PROFILE MYPROF2 FOR OBJECT ROW LOCK TABLESPACE OPTIONS ZOS DB QREPITSO

BUFFERPOOL BP2;

Chapter 3. Bidirectional Q replication on z/OS platforms 273

CREATE CONTROL TABLES FOR MONITOR CONTROL SERVER IN ZOS PAGE LOCK DB "QREPITSO"

NAMING PREFIX QM CREATE USING PROFILE MYPROF ROW LOCK DB "QREPITSO" NAMING

PREFIX QM CREATE USING PROFILE MYPROF2;

The generated SQL

3

shown in Example 3-54 can be ported to z/OS for execution

under SPUFI or DSNTEP2.

Example 3-54 Generated script for creating monitor control tables on D8G1

CONNECT TO D8G1 USER XXXX USING XXXX;

CREATE TABLESPACE TSMROW1

IN QREPITSO

SEGSIZE 4

LOCKSIZE ROW

CCSID EBCDIC;

CREATE TABLE ASN.IBMSNAP_CONTACTS(

CONTACT_NAME VARCHAR(127) NOT NULL,

EMAIL_ADDRESS VARCHAR(128) NOT NULL,

ADDRESS_TYPE CHAR(1) NOT NULL,

DELEGATE VARCHAR(127),

DELEGATE_START DATE,

DELEGATE_END DATE,

DESCRIPTION VARCHAR(1024))

IN QREPITSO.TSMROW1;

CREATE TYPE 2 UNIQUE INDEX ASN.IBMSNAP_CONTACTSX

ON ASN.IBMSNAP_CONTACTS(

CONTACT_NAME ASC);

CREATE TABLESPACE TSMROW2

IN QREPITSO

SEGSIZE 4

LOCKSIZE ROW

CCSID EBCDIC;

CREATE TABLE ASN.IBMSNAP_ALERTS(

MONITOR_QUAL CHAR(18) NOT NULL,

ALERT_TIME TIMESTAMP NOT NULL,

COMPONENT CHAR( 1) NOT NULL,

SERVER_NAME CHAR(18) NOT NULL,

SERVER_ALIAS CHAR( 8),

SCHEMA_OR_QUAL VARCHAR(128) NOT NULL,

SET_NAME CHAR(18) NOT NULL WITH DEFAULT ' ',

CONDITION_NAME CHAR(18) NOT NULL,

OCCURRED_TIME TIMESTAMP NOT NULL,

ALERT_COUNTER SMALLINT NOT NULL,

ALERT_CODE CHAR( 10) NOT NULL,

3

When ASNCLP specifies SET RUN SCRIPT LATER, the SQL that is generated by ASNCLP will be

stored in a file on the workstation, in the same directory that ASNCLP was executed from. It will have

the name of the DB from the SET SERVER Statement with an .sql extension, for example, D8G1.sql.

If the ASNCLP generates sql for two servers there will be two files generated.