Defining the target CTJMON where the processing will be submitted

To specify where the processing will be submitted, use the following parameters:

Tab.JV.3.1 CTJMON routing parameters

Parameter	Description
NODE=IOAGATE node	Identifies the target SYSPLEX by specifying the NODE of the IOAGATE that runs in the target SYSPLEX. This IOAGATE must be connected to the IOAGATE in the LOCAL SYSPLEX. When the target SYSPLEX is the local SYSPLEX, this parameter can be omitted. NODE=LOCAL also specifies the local SYSPLEX. The verification request is forwarded to the CTJMON associated with the IOAGATE/CTJAS with the given NODE. The request might be forwarded to another CTJMON depending on the SYSTEM and IOA ENV parameters. Default: A blank indicates the local SYSPLEX and XCF Group. Masking is not supported.
SYSTEM=system	Identifies the target SYSTEM in the target SYSPLEX. Default: A blank indicates any SYSTEM in the target SYSPLEX. Preference is given to SYSTEM with the same name as the originating SYSTEM, when IOA ENV is not blank or . Masking: has the same meaning as blank
IOA ENV=ioa_env	Identifies the target CTJMON by the QNAME of the IOA environment in the target SYSPLEX/SYSTEM. Default: A blank specifies any IOA environment in the target SYSPLEX. Preference is given to the IOA environment that is the same as the originating CTJMON when SYSTEM is not blank or . Masking: has the same meaning as blank
AR=Y\|N\|D	Specifies whether Auto Routing will be enabled (Y) or not (N) or whether the default (D) Auto Routing will be used. Note: Auto Routing is not supported under the CTJPLAN and CTJMRFLW utilities.

The NODE name parameter can be defined in the requests that are sent to the Control-M JCL Verify monitor. This NODE name is defined in the network map member (defined by the NETWMAP= parameter in the ECAPARM<suffix> member). The NODE name identifies the target Control-M JCL Verify monitor. An undefined NODE name returns an error message without starting the JCL processing procedure.

The NODE, SYS, and IE names can be defined in the following types of JCL processing requests and user interfaces:

CTJVER procedure parameters
CTJXVER edit macro (when it is invoked with the P option)
---------------   CONTROL-M JCL VERIFY DEFINITION FACILITY  ---------------

ENTER THE PARAMETERS BELOW:

MEMBER =>           LIBRARY =>

USER=>          PROCDD=>          LINKDD =>

NODE=>          SYSTEM=>          IOA ENV=>          AUTO ROUTE=> D (Y/N/D)

Sample start of the output report of a remote verification request under CTJXVER:

  Control-M JCL Verify IS STARTING. LEVEL BJ10387

  REQUEST RECEIVED  BY MONITOR J90MON   ON SYSTEM MVS3

  REQUEST EXECUTED  BY MONITOR J90MON9  / JOB00228 ON SYSTEM MVS1

  RUNTIME PARAMETERS: FA=Y FV=Y JES=Y ME=Y ML=I CTM=N STDR=Y UT=Y

                      ENV=REXXRC   USER=M49A

Note the messages that indicate which CTJMON received the request from the user and which CTJMON executed it.
'JD' screen - JVER Definition Facility. It can be used for sending Online JVER requests (from '2', '3' or JV screens) to be handled by the Control-M JCL Verify monitor.
------------ CONTROL-M/JCL VERIFY DEFINITION FACILITY - ENTRY PANEL -------(JD)

COMMAND ===>



ENTER PARAMETERS BELOW

    PROCDD=>          LINKDD=>

    NODE=>          SYSTEM=>          IOA ENV=>          AUTO ROUTE=> D (Y/N/D)

The following Control-M JCL Verify components and requests are only handled by local monitors, they cannot be invoked in target systems nor send requests to other Control-M JCL Verify monitors:

JCL verification request on Control-M/Enterprise Manager
CTJAPI Macro (Control-M JCL Verify Application Program Interface) does not need the NODE parameter. CTJAPI is invoked in the environment and address space which handles Control-M JCL Verify verification requests. So Control-M JCL Verify monitor subtask can issue CTJAPI to perform JCL verification.

The three target parameters can be defined in the following types of JCL processing requests and user interfaces:

CTJVER, CTJENR, CTJMRFLW utility and CTJPLAN utility: procedure parameters (only the NODE can be specified)
CTJVER, CTJENR, CTJMRFLW and CTJPLAN: SYSIN DD  * parameters (all three parameters can be specified) as follows:
  CTJVER,CTJENR: //SYSIN DD *

  CTJMRFLW,CTJPLAN: //JVER.SYSIN DD *

  NODE=<node>

  IE=<IOA env> SYS=<system>

  LIB=<library>   MEM=<member>

Following is a sample of the beginning portion of the output report for a verification request in batch:

CTJU00I Control-M/JCL Verify Utility started. Date/Time 30.04.17 / 17:52. Level 9.0.03 WJ10028

CTJU01I FA=D FV=D JES=D ME=D ML=D STDR=D ENV=GENERAL CTM=D UT=D NODE=LOCAL

CTJU01I NODE=TLV1

CTJU01I SYSTEM=MVS1

CTJU01I LIB=M49.SRC MEM=M49BR144

CTJ000I Control-M/JCL Verify is starting. Level BJ10387

CTJM36I Request received by monitor J90MON on system MVS3

CTJM0DI Request executed by monitor J90MON9 / JOB00228 on System MVS1

CTJ00CI Runtime parameters: FA=Y FV=Y JES=Y ME=Y ML=I CTM=Y STDR=Y UT=Y ENV=GENERAL USER=M49A

Note the CTJM36I message, which indicates the CTJMON that received the request from the user, and the CTJM0DI message, which indicates the CTJMON that executed it.

For CTJMRFLW and CTJPLAN, the parameters are specified in the SYSIN DD * of the verification step as follows:

//CTJMRFLW JOB 0,CTJMRFLW,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID, // MSGLEVEL=(1,1)

// SET IOA=IOAA.V93J4

//*

// JCLLIB ORDER=&IOA..PROCLIB

// INCLUDE MEMBER=IOASET

//*--------------------------------------------//JVERFLW EXEC CTJMRFLW,FA=Y,FE=Y,ME=Y,

// ODATE=170418

//JOBLIST.DAJOB DD *

ORDER DSN=CTJA.CTJMRFLW.SCHEDULE MEMBER=DEPAW087

//JVER.SYSIN DD *

NODE=NODE1 SYS=MVS1 IE=V93J1

// DD DISP=(SHR,DELETE),DSN=&&PARMJV(JVERIN)

//

//CTJPLAN JOB 0,'CTJPLAN_TODAY',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID,

// USER=JUA

// SET ILPREFA=IOAA.V93J4 %%ILPREFA

// JCLLIB ORDER=&ILPREFA..PROCLIB

// INCLUDE MEMBER=IOASET

//JCLVRFY EXEC CTJPLAN,ODATE=111217,NODE=LOCAL

//SCHEDLIB DD DISP=SHR,DSN=QUEST.JVER.SCHEDULE.R

//DACAL DD DISP=SHR,DSN=QUEST.JVER.CTJPLAN.CAL

//* DD DISP=SHR,DSN=&ILPREFA..OPR.CAL

//SYSIN DD *

TABLES CURRENTD,WEEKDAYS

//JVER.SYSIN DD *

SYS=MVS1 IE=V93J1

// DD DISP=(OLD,DELETE),DSN=&RPLAN

Parent Topic

Remote verification