Messages CTJ300 through CTJ3xx

This group includes messages for Control-M/JCL Verify products.

CTJ301E ERROR: The /*PRIORITY statement must precede the JOB statement.

Explanation: The message is issued when Control-M/JCL Verify detects that a /*PRIORITY statement appears after a JOB statement.

Corrective Action: Move the /*PRIORITY statement to appear before the JOB statement.

CTJ302I CTJJ2G does not have valid entries and J2GUSEJ=Y in CTJPARM

Explanation: Auto Routing via IOAGATE can use a mapping between JES NODES and IOAGATE NODES. Such mapping is defined in member CTJJ2G. Since the member is empty or does not exit, and since J2GUSEJ=Y is defined in CTJPARM, all JES NODES will be used as IOAGATE NODES for Auto Routing purposes.

Corrective Action: No action is required.

CTJ303I CTJJ2G does not have valid entries and J2GUSEJ=N in CTJPARM

Explanation: Auto Routing via IOAGATE requires a mapping between JES NODES and IOAGATE NODES. Such a mapping is defined in the CTJJ2G member.

Corrective Action: If Auto Routing via IOAGATE is required then correct or create a CTJJ2G member with valid entries in the olprefj.PARM library.

CTJ304I CTJJ2G has valid entries and J2GUSEJ=Y in CTJPARM

Explanation: Auto Routing via IOAGATE can use a mapping between JES NODES and IOAGATE NODES. Such mapping is defined in member CTJJ2G. Since the member has some entries, and since J2GUSEJ=Y is defined in CTJPARM, only JES NODES that have no matching entry in CTJJ2G will be used as IOAGATE NODES for Auto Routing purposes.

Corrective Action: No action is required.

CTJ305I CTJJ2G has valid entries and J2GUSEJ=N in CTJPARM

Explanation: Auto Routing via IOAGATE can use a mapping between JES NODES and IOAGATE NODES. Such mapping is defined in member CTJJ2G. Since the member has some entries, and since J2GUSEJ=N is defined in CTJPARM, only JES NODES that have a matching entry in CTJJ2G will be mapped to IOAGATE NODES for Auto Routing purposes.

Corrective Action: No action is required.

CTJ306I Auto Routing will use JES NODES as IOAGATE NODES for all JES NODES

Explanation: Auto Routing via IOAGATE can use a mapping between JES NODES and IOAGATE NODES. Such mapping is defined in member CTJJ2G. Since the member is empty or does not exit, and since J2GUSEJ=Y is defined in CTJPARM, all JES NODES will be used as IOAGATE NODES for Auto Routing purposes.

Corrective Action: No action is required.

CTJ307I Auto Routing will use JES NODES as IOAGATE NODES for JES NODES not found in CTJJ2G

Explanation: Auto Routing via IOAGATE can use a mapping between JES NODES and IOAGATE NODES. Such mapping is defined in member CTJJ2G. Since the member has some entries, and since J2GUSEJ=Y is defined in CTJPARM, only JES NODES that have no matching entry in CTJJ2G will be used as IOAGATE NODES for Auto Routing purposes.

Corrective Action: No action is required.

CTJ308I Auto Routing will use only CTJJ2G to map JES NODES to IOAGATE NODES

Explanation: Auto Routing via IOAGATE can use a mapping between JES NODES and IOAGATE NODES. Such mapping is defined in member CTJJ2G. Since the member has some entries, and since J2GUSEJ=N is defined in CTJPARM, only JES NODES that have a matching entry in CTJJ2G will be mapped to IOAGATE NODES for Auto Routing purposes.

Corrective Action: No action is required.