Auto Routing based on JES nodes

To enable Control-M JCL Verify to support JES node commands, the CTJJ2G member must be defined as described in CTJJ2G - JES nodes to CTM/JCL Verify gateway nodes association.

The following JES2 commands are supported for Auto Routing:

• /*XMIT
• /*ROUTE XEQ
• /*XEQ

The following JES3 command is supported for Auto Routing:

• //*ROUTE XEQ

The following JCL command is supported for Auto Routing based on JES nodes:

• //   XMIT  DEST=<node>

Each JES command is processed as follows:

1. The JES node name, JES node number, or JES DESTID is extracted.
2. The JES node number or JES DESTID is translated to a JES node name.
   1. If there is a Control-M JCL Verify monitor with the given JES node in the local XCF group, send the request to the JES node via XCF.
   2. Lookup the JES node name entry in the CTJJ2G member to obtain the IOAGATE node name.
   3. If the JES node name is not found in the CTJJ2G member, and the CTJPARM parameter J2GUSEJ is set to Y, use the JES node name as the IOAGATE node name.
3. Send the JCL to the correct monitor through the IOAGATE and XCF as described in Inter-monitor communication for remote verification.