Static section - connect_cdc_sqdata

The static section of the Master Controller PARMLIB member always appears at the top of the parameter file as in this sample:

---------------------------------------------------------------------
--  SAMPLE PARM THAT CAN BE USED FOR RUNNING PROCESSES              
--  UNDER THE MASTER CONTROLLER                                      
---------------------------------------------------------------------

QMGR =N/A
CMDQUE =SQDATA.CMDQUE
TASKDD =SQDFILE
WTOR =Y
WTORMSG =SQDATA TEST ENGINES READY
FAILJOB =N
FAILMAX =1

Note: All seven (7) parameters must be included in the static section.

QMGR

The name of MQ queue manager if using a Command Queue to issue commands to the Master for users who do not have console command privileges.

If you do not plan on using the MQ Command Queue, set QMGR=N/A.

CMDQUE

The name of the MQ queue if using a Command Queue to issue commands to the Master for users who do not have console command privileges.

If you do not plan on using the MQ Command Queue, set CMDQUE=DUMMY.

TASKDD

Specifies an internal value that is used for Apply Engines that run under the Master.

This parameter should always be set to TASKDD=SQDFILE even if no Engines will run under a Master.

WTOR

Specifies whether the master will always have an outstanding WTO on the operator's console. By replying to the outstanding WTO, you can issue any of the Master commands.

WTOR=Y - indicates that you want the Master to issue an outstanding WTO, with the text specified in parm WTOMSG .

WTOR=N - indicates that you do not want the Master to issue an outstanding WTO.

WTORMSG

Specifies the text that will be displayed for the outstanding WTO, if the WTOR parm is set to Y.

FAILJOB

Specifies whether you want to submit custom JCL for a particular agent if the agent running under the Master terminates unexpectedly (i.e. return code greater than 0).

FAILJOB=Y - indicates that you want to use the Fail JCL option.

FAILJOB=N - indicates that you do not want to use the Fail JCL option.

The Fail JCL option allows you to perform tasks such as trying to restart the agent or notifying someone of an error outside of your normal monitoring processes.

To setup Fail JCL, simply add a JCL member in the FAILJCL library, with the name matching the Agent NAME in the agent section of the Master parm.

For example, suppose that you want to try to restart DB2 Capture Agent task DB2CDCT if the Agent ends unexpectedly. You would create a member named DB2CDCT in the FAILJCL library, similar to this.

//START    EXEC PGM=SQDCONF
//SYSPRINT DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//*SQDLOG8  DD DUMMY
//SQDLOG   DD SYSOUT=*
//SQDPARMS DD *
start --apply /home/cdc/DB2CDCT.cab
//*

If the DB2 Capture Agent fails unexpectedly again, the DB2CDCT fail JCL will be submitted again, until the FAILMAX counter is exceeded. Once FAILMAX has been exceeded, a default member named $FAILMAX , if present, will be executed

FAILMAX

Limits the number of times a FAILJCL member is submitted for a particular Agent running under the Master, if parm FAILJOB=Y.

Once an Agent terminates unexpectedly more than the FAILMAX value, a default member named $FAILMAX , if present, will be executed.

You can reset the FAILMAX counter to 0 with the Reset Fail JCL command.

Static section - connect_cdc_sqdata - Latest