Once the CDCzLog configuration CAB file has been created, JCL similar to sample member SQDZLOGC included in the distribution is used to Mount and optionally Start the CDCzLog Publisher Agent process.
//SQDZLOGC JOB 1,MSGLEVEL=(1,1),MSGCLASS=H,NOTIFY=&SYSUID
//*
//*--------------------------------------------------------------------
//* Execute zLOGC Publisher Agent for IMS or VSAM CDC
//*--------------------------------------------------------------------
//* Required parameters (lower case):
//* config_file - Specifies the fully qualified name of the
//* predefined IMS or VSAM Publisher agent CAB file
//* (see JCL members SQDCONIP or SQDCONVP)
//*--------------------------------------------------------------------
//* Optional parameters (lower case):
//* --apply - Specifies that ALL pending changes to the config (cab)
//* file should be applied before the Publisher 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 Publisher Agent to Start processing
//* ** NOTE - This is often used in this job but can
//* ** be performed by a separate SQDCONF command
//*
//* --ziip - Instructs the Publisher to utilize zIIP engines for
//* LogStream reads and encryption (if specified in the
//* Publisher agent CAB file)
//*
//* --wait - Specifies the number of milliseconds to wait before
//* checking for more cdc data in the LogStream
//*
//*********************************************************************
//*
//JOBLIB DD DISP=SHR,DSN=SQDATA.V400.LOADLIB
//*
//SQDZLOGC EXEC PGM=SQDZLOGC,REGION=0M
//*XQDZLOGC EXEC PGM=XQDZLOGC,REGION=0M
//SQDPUBL DD DSN=SQDATA.NACL.PUBLIC,DISP=SHR
//SQDPKEY DD DSN=SQDATA.NACL.PRIVATE,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SQDLOG DD SYSOUT=*
//*SQDLOG8 DD DUMMY
//SQDPARMS DD *
--start --wait=100
/home/sqdata/vsamcdc/vsampub.cab
//*
//
--apply --start --ziip --wait=100
--high-threshold=<seconds>
--low-threshold=<seconds>
/home/sqdata/imspub1/IMSPUB1.cab
//SQDLOGL DD *
*=2
*=8
OPTIONS=NET_ACTIVITY,
MESSAGE,
PARSE,
UOW,
TIME | TS,
JOBLIB | References the Connect CDC SQData load library. |
SQDPUBL | NaCL Public key required when connecting to a SQData Controller Daemon. |
SQDPKEY | NaCL Private key required when connecting to a SQData Controller Daemon. |
SQDLOG | Will contain all diagnostic log messages. |
SQDLOG8 | Optional, used as a switch to specify Log-level 8 diagnostics, used together with the "X" named diagnostic version of the Component. |
SQDLOGL | Optional alternative to SQDLOG8 that allows the specification of additional diagnostic parameters specific to the Component. Used together with the "X" named diagnostic version of the Component will produce the most verbose version of the log. |
SQDFILE | Apply Engine only, refers to the parsed script file that will be used as input to the Engine. |
SYSPRINT | Will contain the Component runtime report. |
- Precisely recommends zIIP processors be used to enhance CPU cycle efficiency and reduce CPU cost associated with LogStream I/O and NaCL software encryption.
- The first time this Job is run you may choose to include both the --apply and --start commands. After the initial creation, --apply should not be used unless you want all changes made since the agent was last Stopped 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 SQDATACONF jobs.
- 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 CDCzLog Agent may be the same pair used by its Controller Daemon.
- --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
- The SQDLOGL parm OPTIONS=TIME | TS adds either the system Storeclock (STCK) in Miliseconds or its human readable TimeStamp to all SQDLOG messages:
OPTIONS=TIME the system Storeclock in Miliseconds 3882279447104 [ MSGS] :SQDZLOGC 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] :SQDZLOGC 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)