|
Prepare Db2/z Capture JCL |
Scroll |
Once the DB2 Capture configuration (.cab) file has been created, JCL similar to sample member SQDDB2C included in the distribution is used to Mount and optionally Start the DB2 Capture Agent process.
Example
//SQDDB2C JOB 1,MSGLEVEL=(1,1),MSGCLASS=H,NOTIFY=&SYSUID
//*
//*--------------------------------------------------------------------
//* Execute (Mount) DB2 CDCStore Capture Agent - SQDDB2C
//*--------------------------------------------------------------------
//* Required parameters (lower case):
//* config_file - Specifies the fully qualified name of the
//* predefined DB2 capture agent configuration
//* file (see sample JCL SQDCONDC)
//*
//* Optional parameters (lower case):
//* --apply - Specifies that ALL pending changes to the config (.cab)
//* file should be Applied before the Capture Agent is
//* Started
//* ** NOTE - This is normally NOT used in this job
//* ** REMOVE if the status of pending changes is NOT
//* ** known. Instead use SQDCONF to apply changes
//*
//* --start - Instructs the Capture Agent to Start processing
//* ** NOTE - This is often used in this job but can
//* ** be performed by a separate SQDCONF command
//*
//* --ziip - Instructs the Capture to utilize zIIP engines for
//* encryption (if specified in the Capture Agent
//* CAB file
//*
//* Note: 1) The Relational CDCStore Capture Agents include
//* a second Publisher thread that manages Engine
//* subscriptions
//*--------------------------------------------------------------------
//*
//JOBLIB DD DISP=SHR,DSN=SQDATA.V400.LOADLIB
// DD DISP=SHR,DSN=CSQ901.SCSQAUTH
// DD DISP=SHR,DSN=CSQ901.SCSQANLE
// DD DISP=SHR,DSN=DSNC10.SDSNLOAD
//*
//SQDDB2C EXEC PGM=SQDDB2C,REGION=0M
//*SQDDB2C EXEC PGM=XQDDB2C,REGION=0M
//SQDPUBL DD DSN=SQDATA.NACL.PUBLIC,DISP=SHR
//SQDPKEY DD DSN=SQDATA.NACL.PRIVATE,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//*SQDLOG8 DD DUMMY
//SQDLOG DD SYSOUT=*
//*SQDPARMS DD DISP=SHR,DSN=SQDATA.V400.PARMLIB(DB2CDC)
//SQDPARMS DD *
--apply --start
/home/sqdata/db2cdc1/DB2CDC1.cab
/*
//
--apply --start --ziip --no-ddl-tracking
--high-threshold=<seconds>
--low-threshold=<seconds>
//SQDLOGL DD *
*=2
*=8
CDCSTORE=8
DB2C=8
VFILE=8
OPTIONS=NET_ACTIVITY,
MESSAGE,
CDCSTORE,
IFI,
PARSE,
UOW,
TIME | TS,
Notes:
1.Precisely recommends zIIP processors be used to enhance CPU cycle efficiency and reduce CPU cost associated with NaCL software encryption.
2.While the SQDCONF utility is used to create the Capture Agent configuration and perform most of the other management and control tasks associated with the capture agent, on z/OS it cannot perform the function of the MOUNT command. On platforms other than z/OS, the MOUNT command brings an Agent on-line. On z/OS that function must be performed with an agent specific JOB or Started Task. Once the Capture Agent has been "mounted" on z/OS, the sqdconf utility can and should be used to perform all other functions as documented.
3.The first time this Job is run you may choose to include a special form of the sqdconf apply and start commands. After the initial creation, --apply should not be used in this JCL, unless all changes made since the agent was last Stopped are intended to take effect immediately upon the Start. The purpose of apply is to make it possible to add/modify the configuration while preparing for an implementation of changes without affecting the current configuration. Note, apply and start can and frequently will be separated into different SQDCONF jobs.
4.The Controller Daemon uses a Public / Private key mechanism to ensure component communications are valid and secure. While it is critical to use unique key pairs when communicating between platforms, it is common to use the same key pair for components running together on the same platform. Consequently, the key pair used by a Log Reader Capture agent may be the same pair used by it's Controller Daemon.
5.--high-threshold and --low-threshold Display Capture Latency alerts (in seconds), in a WTO (write to operator) message on the console and system log. These parms may be specified either at runtime using SQDPARMS DD or using sqdconf modify.
SQDZ005W Latency for capture ( 274 sec.) is high
SQDZ006I Latency for capture is back to normal
6.The SQDLOGL parm OPTIONS=TIME | TS adds either the system Storeclock (STCK) in Miliseconds or it's human readable TimeStamp to all SQDLOG messages:
OPTIONS=TIME the system Storeclock in Miliseconds
3882279447104 [ MSGS] :SQDDB2C 4.1.39-dev (zOS-370) ccsid:1047 - 0x21
3882279447104 [ MSGS] :Build-id:a93d3e38230049d11ebb7c229360042d7b098407
3882279447106 [ NET] :net_init_module
3882279447108 [ MESSAGE] :overload proc for type 0x20a0003(AGENT_MESSAGE_T_PING)
3882279447108 [ CNVFT] :cnvft_init_module <-- 0x0
3882279447109 [ MESSAGE] :overload proc for type 0x2020002(CDCCONF_MESSAGE_T_ACTION)
OPTIONS=TS
2023-01-09.14.33.14.748758 [ MSGS] :SQDDB2C 4.1.39-rel (zOS-370) ccsid:1047 - 0x21
2023-01-09.14.33.14.749565 [ MSGS] :Build-id:a93d3e38230049d11ebb7c229360042d7b098407
2023-01-09.14.33.14.751236 [ NET] :net_init_module
2023-01-09.14.33.14.753076 [ MESSAGE] :overload proc for type 0x20a0003(AGENT_MESSAGE_T_PING)
2023-01-09.14.33.14.753076 [ CNVFT] :cnvft_init_module <-- 0x0
2023-01-09.14.33.14.753202 [ MESSAGE] :overload proc for type 0x2020002(CDCCONF_MESSAGE_T_ACTION)
5.--high-threshold and --low-threshold Display Capture Latency alerts, in seconds, in a WTO (write to operator) message on the console and system log. These parms may be specified either at runtime using SQDPARMS DD or using sqdconf modify.
SQDZ005W Latency for capture ( 274 sec.) is high
SQDZ006I Latency for capture is back to normal
