This group includes messages for Control-M/JCL Verify products.
Explanation: The message is issued when the Control-M/JCL Verify monitor starts executing REFRESH, REMOVE, or REMOVEF processing. For more information see Chapter 13, "Improving performance."
Corrective Action: No action is required.
Explanation: The message is issued when Control-M/JCL Verify detects that the shared tables were not initiated.
Corrective Action: Issue the Control-M/JCL Verify monitor MODIFY command with the REFRESH function.
Explanation: The message is issued when Control-M/JCL Verify detects that the shared tables were not initiated.
Corrective Action: Issue the MODIFY command 'REFRESH,SCOPE=ALL' for the Control-M/JCL Verify monitor.
Explanation: The message is issued when the application cannot allocate memory objects. The return and reason codes indicates those returned by the IARV64 system service.
Corrective Action: Check the IARV64 return and reason codes in the IBM MVS Authorized Assembler Services Reference.
Explanation: The message is issued when the application cannot locate the JES Sub-System in the sub-system table.
Corrective Action: Consult with your z/OS system administrator.
Explanation: The message is issued when the application cannot access the JES2 or JES3 data areas due to ALESERV failure.
Corrective Action: Consult with your z/OS system administrator.
Explanation: The message is issued when the JES data area does not contain the expected information.
Corrective Action: This is an internal error. Retry the process and if the problem reoccurs, call BMC Customer Support.
Explanation: The message is issued when Control-M/JCL Verify calls the JES subsystem and the JES response is not 0.
Corrective Action: Verify that the JES2 or JES3 is active. If the JES2 or JES3 is active, retry the process again. If the problem reoccurs, check the IEFSSREQ return and reason codes in the IBM MVS Authorized Assembler Services Reference.
Explanation: The message is issued because the input parameters supplied to the Control-M/JCL Verify monitor in the REFRESH, REMOVE, or REMOVEF MODIFY request are invalid.
Corrective Action: Correct the parameter and reissue the MODIFY command for the Control-M/JCL Verify monitor. The valid command is
'F CTJMON,REFRESH|REMOVE|REMOVEF,SCOPE=ALL|RULES'.
The abbreviations REF/REM/REMF can be used instead of the REFRESH/ REMOVE/REMOVEF keywords.
Explanation: The message is issued when Control-M/JCL Verify accepts a file as a LINK-LIST library, but it is not a library.
Corrective Action: Correct the JCL statement and rerun job verification.
Explanation: The message is issued when the processing of the REFERESH, REMOVE, or REMOVEF MODIFY command by the Control-M/JCL Verify monitor finishes.
Corrective Action: If RC is greater than 0, check for previous messages.
Explanation: The message is issued after the searching routine loads its table successfully.
Corrective Action: No action is required.
Explanation: The message is issued if the searching routine is unsuccessful in loading its table.
Corrective Action: Check for previous messages and make the necessary corrections.
Explanation: The message is issued while removing old data pools and one of the data pools is in use.
Corrective Action: Reissue the MODIFY command 'REMOVE' for the Control-M/JCL Verify monitor, provided that no user is currently performing a JCL verification.
Explanation: The message is issued while removing old shared pools and one of the shared pools is in use.
Corrective Action: Reissue the MODIFY command 'REMOVE' for the Control-M/JCL Verify monitor, provided that no user is currently performing a JCL verification.
Explanation: The message is issued if the MODIFY command 'REMOVE' for the Control-M/JCL Verify monitor is submitted before the MODIFY command 'REFRESH' was issued to create the shared tables, and therefore there is nothing to remove.
Corrective Action: No action is required.
Explanation: The message is issued when the CTJSHRM tries to assign a new entry in SMC, and there is no available entry.
Corrective Action: Issue the MODIFY command 'REMOVE' for the Control-M/JCL Verify monitor. If it does not help, issue the MODIFY command 'REMOVEF' and then issue the MODIFY command 'REFRESH'.
Explanation: The message is issued when the CTJSHRM tries to assign a new entry in SMC, and there is no available entry.
Corrective Action: Consult with your z/OS system administrator.
Explanation: The message is issued when supposed pointer of SMC is null.
Corrective Action: Consult with your z/OS system administrator.
Explanation: The message is issued when the CTJSHRM tries to assign a new entry in SMC, and there is no available entry.
Corrective Action: Consult with your z/OS system administrator.
Explanation: The message is issued when trying to read STEPLIB/JOBLIB/ LINKLIST library and the OPEN INPUT got S913 (Access not permitted).
Corrective Action: Grant READ permission to the mentioned PDS.
Explanation: The message is issued when a VOLSER of STEPLIB/JOBLIB/ LINKLIST library is not mounted.
Corrective Action: Check the volume existence mentioned in the message.
Explanation: The message is issued during parsing of the procedure libraries according to the rules defined in the CTJPRC member.
Corrective Action: Check syntax of CTJPRC and recode it according to the syntax rules.
Explanation: The message is issued during parsing of the procedure libraries which contain a variable that is not among the system variable names.
Corrective Action: Check the name preceded by '&'. Recode it, or remove.
Explanation: The message is issued when trying to LOCATE a procedure library in the catalog fails.
Corrective Action: Check the PROCLIBs in CTJPRC for its existence.
Explanation: The message is issued when trying to LOCATE a procedure library in the catalog fails.
Corrective Action: Create CTJPRC, according the rules.
Explanation: The message is issued when security check for reading failed.
Corrective Action: Grant READ permission to all LINK-LIST libraries.
Explanation: The message is issued when two Control-M/JCL Verify monitors are running in the same system.
Corrective Action: Wait until the other run of Control-M/JCL Verify monitor terminates.
Explanation: The message is issued when the member containing the list of rules is empty.
Corrective Action: Create the rule list.
Explanation: The message is issued when member CTJALUT contains an invalid alias definition in a certain line.
Corrective Action: Correct the CTJALUT member.
Explanation: The message is issued when the CTJJ2G member contains an invalid definition in line number line_number.
Corrective Action: Correct the CTJJ2G member.
Explanation: The message is issued when the CTJJ2G member does not contain any valid non-commented entries or does not exist.
Corrective Action: See Corrective Action for the CTJ20WW message.
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.
Explanation: The message is issued when the CTJJ2G member could not be loaded.
Where
return_code - the return code from the IOAMEM program
reason_code - the reason code from the IOAMEM program
The return and reason codes are documented in the description of the IOAMEM Assembler Macro in the INCONTROL for z/OS Administrator Guide.
Corrective Action: Correct the error.
Explanation: The message is issued when the JCL includes a JES node name or number that was not found.
Corrective Action: Contact BMC support.
Explanation: The message is issued when the JCL includes a JES DESTID that was not found.
Corrective Action: Contact BMC support.
Parent Topic |