|
|
|
|
|
When Control-M/JCL Verify detects both JES node routing commands and system identification routing keywords, Control-M/JCL Verify first routes the JCL according to the JES node commands and then the JCL is analyzed a second time to determine, according to the system identification keywords, on which monitor the JCL will be verified.
Control-M/JCL Verify monitor can Auto Route a request to a specific system within a JESPLEX, through XCF only, based on a combination of parameters in the JOB and in the JES statements. The routing logic attempts to emulate JES2/JES3 processing.
Auto Routing uses the following keywords for the target system identification:
The system chosen for verification must have an active CTJMON in the same XCFGROUP and JESPLEX. If the submission system successfully passes the selection process described below, it has priority over any other system and will be used for the verification. If there is no system that successfully passes the selection process, by default the submission system will be used for the verification.
In order to determine which system the JCL will be verified on, the Auto Routing process attempts to create three separate lists of candidate systems based on the following parameters:
If the SCHENV is invalid, Auto Routing is disabled (since the job would anyway result in a JCL error) and the verification is performed on the submission system.
The systems where the scheduling environment is active are included in the SCHENV list of candidate systems.
If the scheduling environment is not active anywhere, the SCHENV parameter is ignored and the selection process will continue with the other parameters.
The systems specified by the SYSTEM or SYSAFF parameters are used to create another list of candidate systems. These parameters will not be ignored.
If the list of these systems has no systems in common with the list of systems created by the SCHENV parameter, the SCHENV parameter will be ignored.
The third list of systems is created using the CLASS parameter. The candidate systems are selected where the specified CLASS is currently active, enabled, and supports a maximum number of jobs greater than 0. For non-WLM classes, the CLASS must have either an active or an inactive initiator on the system.
If there are no systems where the CLASS requirements are fulfilled, the CLASS parameter will be ignored.
If the list of systems that fulfill the CLASS requirements has no systems in common with the combined list of systems created by the SCHENV and SYSTEM or SYSAFF parameters, the CLASS parameter will also be ignored.
Parent Topic |