CTI–CTM

This group includes messages for the Control-O, Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart on Demand products.

CTI Messages

This group includes messages for Control-O products.

Messages CTI600 through CTI6xx

This group includes messages for the Control-O product.

CTI650E STORAGE OBTAIN FAILED WITH RETURN CODE `rc`

Explanation: An attempt to acquire storage for an internal table failed with return code rc. The CTOCTI utility requested working storage for an internal table.

The CTOCTI utility terminates.

Corrective Action: Increase the region size specified in the JOB or EXEC JCL statement and rerun the job.

CTI651E OPEN FAILED FOR DDNAME OBJFILE

Explanation: The CTOCTI utility attempted to open the data set referenced by the DD statement OBJFILE but failed.

Possible causes are:

the OBJFILE DD statement is misspelled.
the data set (member) referenced by the OBJFILE DD statement does not exist.

The CTOCTI utility terminates.

Corrective Action: Verify that the data set exists and is spelled correctly. Rerun the job.

CTI652S INTERNAL OBJECT TABLE MUST BE ENLARGED

Explanation: The amount of storage allocated for an internal table is insufficient. The system has more started tasks than the CTOCTI utility anticipated. The storage allocated for one of the internal tables is insufficient.

The CTOCTI utility terminates.

Corrective Action: Contact your INCONTROL administrator.

CTI653E ALESERV ADD FAILED FOR `addr-spc` WITH RETURN CODE `rc`

Explanation: The ALESERV function was invoked to analyze address space addr-spc, but failed with return code rc.

Control-O continues its analysis with the next address space.

Corrective Action: No action is required.

CTI654I ADDRESS SPACE `addr-spc` IS SWAPPED OUT AND WILL BE SKIPPED

Explanation: This information message indicates that Control-O failed to get information from the address space addr-spc. The ALESERV function was invoked to analyze the address space but failed because the specified address space is swapped out.

Control-O continues its analysis with the next address space.

Corrective Action: No action is required.

CTI655E ALESERV DELETE FAILED FOR `addr-spc` WITH RETURN CODE `rc`

Explanation: Control-O acquired information from the address space addr-spc but the attempt to disconnect from the address space failed.

After analyzing the address space, the ALESERV function DELETE tried to disconnect from the address space but failed with return code rc.

Control-O continues its analysis with the next address space.

Corrective Action: No action is required.

CTI656I STARTED TASK `taskName` WILL BE ADDED TO THE DATABASE

Explanation: This information message indicates that started task taskName was not specified in the Object file but was active in the system.

The started task is added to the COSMOS database.

Corrective Action: No action is required.

CTI657I OBJECT_NAME/DESC CLASS_NAME/DESCR ADDRSPAC STATUS _J

Explanation: This information message is the header for data displayed by the CTO659I message. It is generated when invoking the CTOCTI utility.

The J field at the end of this message is usually blank. When J is displayed, it means JOINed, and indicates that the address space is part of a composite address space. For example, CICS monitors use three address spaces: AOR, TOR and FOR.

Corrective Action: No action is required.

CTI658I `text`

Explanation: This information message is an internal message issued by the CTOCTI utility. When running the CTOCTI utility to define started tasks for the Control-O/COSMOS database, a Control-O rule traps these internal messages and creates the required definitions for Control-O/COSMOS.

Corrective Action: No action is required.

CTI659I `objectName className addrSpace status j`

Explanation: This information message displays the object name (16 characters), class name (16 characters), address space name (8 characters), status (ACTIVE, INACTIVE, EXCLUDED) and j (1 character)

The J field at the end of this message is usually blank. When J is displayed, it means JOINed and indicates that the address space is part of a composite address space. For example, CICS monitors are use three address spaces: AOR, TOR, and FOR.

Corrective Action: No action is required.

CTJ messages

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

Messages CTJ000 through CTJ0xx

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

CTJ000I Control-M JCL Verify is starting. Level`apar_id`

Explanation:The message is issued when Control-M JCL Verify starts the first time.

Corrective Action:No action is required.

CTJ001I Control-M JCL Verify is ended RC=`return_code`

Explanation:The message is issued when Control-M JCL Verify completes the validation processing. RC is the highest return code that occurs during the validation processing.

Corrective Action:If RC is not zero, it means that at least one validation has failed. Review the warning and error messages and handle them appropriately.

CTJ002I Start processing MEMBER `member_name`DSNAME=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify starts processing the JCL of the member_name member from the dataset_name dataset.

Corrective Action:No action is required.

CTJ003I Processing ended RC=`return_code`REASON`reason_code` MEMBER`member_name`SNAME `dataset_name`

Explanation:The message is issued when Control-M JCL Verify finished processing the JCL of the member_name member from the dataset_name dataset. RC is the highest return code that occurs during the validation processing. REASON is the reason code of the highest return code.

Corrective Action:If RC is not zero, it means that at least one validation has failed. Review the warning and error messages and handle them appropriately.

CTJ004I Processed`number`members from `lib_name`

Explanation:The message is issued when Control-M JCL Verify finished verifying the lib_name library, which contains number members.

Corrective Action:No action is required.

CTJ005E MEMBER`member_name`not found in `lib_name`

Explanation:The JCL verification failed because the member_name member does not exist in the lib_name library. Return code is 12. Reason code is 00080014.

Corrective Action:Correct the member or library name and re-submit the Control-M JCL Verify job.

CTJ006ECould not find LIBRARY=`lib_name`

Explanation:The JCL verification failed because the lib_name library cannot be found. Return code is 12. Reason code is 00010014.

Corrective Action:Check the library name. If necessary, change or correct the library name.

CTJ007W Empty MEMBER `member_name` in library `lib_name`

Explanation:The JCL verification failed because the member_name member, in the lib_name library, is empty. Return code is 04. Reason code is 0.

Corrective Action:Check the member and library names. If necessary, change or correct the appropriate name.

CTJ008I Start verifying JOB`job_name` MEMBER `member_name`

Explanation:The message is issued when Control-M JCL Verify starts processing a JCL JOB from the member_name member.

Corrective Action:No action is required.

CTJ009I Processing ended RC=`return_code` for JOB `job_name` MEMBER `member_name`

Explanation:The message is issued when Control-M JCL Verify completed processing a JCL JOB from the member_name member. RC is the highest return code occurring during the validation process.

Corrective Action:If RC is not zero, it means that at least one validation failed. Review the warning and error messages and handle them appropriately.

CTJ00AE Control-M JCL Verify is not APF-authorized

Explanation:Control-M JCL Verify must be executed in an APF-authorized environment. The Control-M JCL Verify initialization process found that the environment is not APF-authorized.

Corrective Action:Verify that the JOBLIB or STEPLIB are all defined as APF- authorized. Under TSO, validate that the ISPF Edit Macro is defined as an Authorized command.

CTJ00BE Reading library's directory using mask`mask`failed DSNAME=`dataset_name`

Explanation:The Control-M JCL Verify initialization process failed to retrieve any member from the specified library.

Corrective Action:Check that the mask masking name is valid and results in at least one member name.

CTJ00CI Runtime parameters: FA=`fa` FV=fv JES=`jes` ME=`me` ML=`ml` CTM=`ctm` STDR=`stdr` UT=`ut` ENV=`env`USER=`user`

Explanation:Control-M JCL Verify displays the values of the control parameters before scanning is performed. The message is issued whenever one of the parameters is changed.

Corrective Action:No action is required.

CTJ00DS CAN NOT DISPLAY HUGE REPORT WITH`number_of _records` OF RECORDS

Explanation:Control-M JCL Verify cannot display huge report, which contains number_of_ records of records.

Corrective Action:No action is required.

CTJ00FI Jobs Dependency Flow is Active

Explanation:This Message will be display when jobs dependency flag is on.

Corrective Action:No action is required.

CTJ00II Job ID `jobid` in Jobs Dependency Flow.

Explanation:The message is issued when Control-M JCL Verify recognizes the job ID of each of the jobs in the flow. To recognizes the job IDs, the Jobs Dependency flag must be set to "On."

Corrective Action:No action is required.

CTJ00JI Start processing MEMBER`mem_name`DSNAME=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify starts processing the JCL of the mem_name member from the dataset_name dataset.

Corrective Action:No action is required.

CTJ00MI Start processing MEMBER `mem_name`DSNAME=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify starts processing the JCL of the mem_name member from the dataset_name dataset.

Corrective Action:No action is required.

CTJ00NI Start verifying JOB`job_name`MEMBER`mem_name`

Explanation:The message is issued when Control-M JCL Verify starts processing a JCL job from the mem_name member.

Corrective Action:No action is required.

CTJ00PW PACKED MEMBER`member_name`in library `lib_name`

Explanation:The JCL verification failed because the member_name member, in the lib_name library, is ISPF-PACKed and will be skipped. Return code is 04. Reason code is 0.

Corrective Action:Check the member and library names. If necessary, change or correct the appropriate name.

CTJ00QE File/Member referenced in DDNAME ddname could not be opened

Explanation: The JCL verification failed because the member cannot be found. Return code is 12. Reason code is 00010014.

Corrective Action: Check the member name.

CTJ00RE Internal error while opening file/member referenced in DDNAME ddname

Explanation: The JCL verification failed because of an internal error while opening the member. Reason code is 00010014.

Corrective Action: Contact BMC Customer Support.

CTJ00SE `jcl_statement_number` RULE-ERR: `text`

Explanation:The user specified the DO MSG action parameter in the DO section of the Control-M JCL Verify Rule definition. As part of the DO MSG definition, the user specified "E" (for an error type message) and typed in text for the actual message.

Corrective Action:No action is required.

CTJ00SI `jcl_statement_number` RULE-INFO: `text`

Explanation:The user specified the DO MSG action parameter in the DO section of the Control-M JCL Verify Rule definition. As part of the DO MSG definition, the user specified "I" (for an information type message) and typed in text for the actual message.

Corrective Action:No action is required.

CTJ00SW `jcl_statement_number` RULE-WARN: `text`

Explanation:The user specified the DO MSG action parameter in the DO section of the Control-M JCL Verify Rule definition. As part of the DO MSG definition, the user specified "W" (for a warning type message) and typed in text for the actual message.

Corrective Action:No action is required.

CTJ00TI`jcl_statement_number` REXX-INFO:`message text`

Explanation:The message text is an information message issued by a DOMSG from an EXEC.

Corrective Action:No action is required.

CTJ00TW `jcl_statement_number` REXX-WARN:`message text`

Explanation:The message text is a warning message issued by a DOMSG from an EXEC.

Corrective Action:No action is required.

CTJ00TE`jcl_statement_number` REXX-ERR:`message text`

Explanation:The message text is an error message issued by a DOMSG from an EXEC.

Corrective Action:No action is required.

CTJ00UI Processing ended RC=return_code REASON=reason_code file/member referenced in DD ddname

Explanation: Control-M JCL Verify finished processing the JCL of the member from the DDNAME dataset. RC is the highest return code that occurs during validation processing. REASON is the reason code of the highest return code.

Corrective Action: If the member was not found in the library allocated by the DDNAME, correct the member name. If an internal error occurred, contact BMC Customer Support.

CTJ00VE Empty file/member referenced in DDNAME ddname

Explanation: JCL verification failed because the member/file that was referred by DDNAME is empty. Return code is 4. Reason code is 0.

Corrective Action: Check the member and library names, and correct them as necessary.

CTJ00WW Packed file/member referenced in DDNAME ddname

Explanation: JCL verification failed because the member/file that was referred by DDNAME is packed and is skipped. Return code is 4. Reason code is 0.

Corrective Action: Check the member and library names, and correct them as necessary.

CTJ00XI Start verifying file/member referenced in DDNAME=ddname

Explanation: Control-M JCL Verify has started JCL verification of the member/file that is referred by DDNAME.

Corrective Action: No action is required.

CTJ00YI Processing ended RC=rc for JOB job_name referenced in DDNAME ddname

Explanation: Control-M JCL Verify completed the processing of a JCL JOB referred by DDNAME. RC is the highest return code that occurred during the validation process.

Corrective Action: If the RC is not zero, at least one validation failed. Review the warning and error messages and handle them appropriately.

Messages CTJ100 through CTJ1xx

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

CTJ105I //SYSIN DD * GENERATED BY CTJVER

Explanation:The message is issued if Control-M JCL Verify finds instream data (a.k.a. SYSIN), which is not preceded by a "DD *" statement. Control-M JCL Verify simulates the JES2 and JES3 behaviors and generates the //SYSIN DD statement.

Corrective Action:No action is required.

Messages CTJ200 through CTJ2xx

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

CTJ200I Function `function_name`is Starting Level `level_id`APAR:`apar_id`

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.

CTJ201E ERROR `string` tables were not initiated

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.

CTJ202I Shared INFO does not exist. Issue Modify command 'REFRESH,SCOPE=ALL' for CTJ monitor.

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.

CTJ203E ERROR: Storage not available Return Code:`return_code`, Reason:`reason_code`

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.

CTJ204E ERROR: JES sub-system is not available

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.

CTJ205E ERROR: string tables cannot be accessed. Return Code: return_code

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.

CTJ206E ERROR: Sub-System internal error

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.

CTJ207E ERROR: Sub-System failure. Return Codes:return_code - reason_code

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.

CTJ208E ERROR: Function function_name input parameters invalid. RC=return_code

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

Copy

'F CTJMON,REFRESH|REMOVE|REMOVEF,SCOPE=ALL|RULES'.

The abbreviations REF/REM/REMF can be used instead of the REFRESH/ REMOVE/REMOVEF keywords.

CTJ209E ERROR: STEPLIB dataset is not a library, DSN=dataset_name

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.

CTJ20AI CTJ monitor Function `function_name` Scope `string` ended - RC=`return_code`

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.

CTJ20BI Control-M JCL Verify Data Pool was created successfully

Explanation:The message is issued after the searching routine loads its table successfully.

Corrective Action:No action is required.

CTJ20CE Data Pools were not created

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.

CTJ20DW Data Pool is in use and was not removed. SCOPE=string

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.

CTJ20EW JES search table string not recognized

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.

CTJ20FE Control-M JCL Verify system anchor was not created. RC=return_code

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.

CTJ20GE ERROR: string library info cannot be obtained for library_name

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'.

CTJ20HE Number of tasks exceeds

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.

CTJ20IE internal error: Shared Memory Object was not found

Explanation:The message is issued when supposed pointer of SMC is null.

Corrective Action:Consult with your z/OS system administrator.

CTJ20JE CTJSHRM - Not Enough Memory. STORAGE RC=return_code

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.

CTJ20KE PDS `pds_name` cannot be accessed due to authorization issue

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.

CTJ20LW WARNING: Library volume`volume_id`cannot be accessed DSN=`dataset_name`

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.

CTJ20ME Syntax error during CTJPRC parsing. Line:line_number

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.

CTJ20NE Unrecognized System Variable Name:variable _name

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.

CTJ20OI Procedure Library was not Found. Library:library

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.

CTJ20PE No JES Procedure libraries provided with `string` DD name

Explanation:The message is issued when trying to LOCATE a procedure library in the catalog fails.

Corrective Action:Create CTJPRC, according the rules.

CTJ20QI INFORMATION: LLA Library is not authorized for reading

Explanation:The message is issued when security check for reading failed.

Corrective Action:Grant READ permission to all LINK-LIST libraries.

CTJ20RE CTJ monitor utility is already running. Execution aborted.

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.

CTJ20SE Rule List member member_name is empty

Explanation:The message is issued when the member containing the list of rules is empty.

Corrective Action:Create the rule list.

CTJ20TW Member member_name: Line number will be ignored due to invalid syntax.

Explanation: The message is issued when member CTJALUT contains an invalid alias definition in a certain line.

Corrective Action: Correct the CTJALUT member.

CTJ20UW Member CTJJ2G: Line line_number will be ignored due to invalid syntax.

Explanation:The message is issued when the CTJJ2G member contains an invalid definition in line number line_number.

Corrective Action:Correct the CTJJ2G member.

CTJ20VW Member CTJJ2G does not contain any valid uncommented entries or does not exist

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.

CTJ20WW Auto Routing of JCL with JES NODES via IOAGATE will not be performed

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.

CTJ20XW Error loading member CTJJ2G. RC=return_code RSN=reason_code

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.

CTJ20YE JES NODE NAME OR NUMBER node NOT FOUND

Explanation:The message is issued when the JCL includes a JES node name or number that was not found.

Corrective Action: Contact BMC support.

CTJ20ZE JES DESTID`destid`NOT FOUND

Explanation:The message is issued when the JCL includes a JES DESTID that was not found.

Corrective Action: Contact BMC support.

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

Corrective Action: No action is required.

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

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.

Messages CTJ400 through CTJ4xx

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

CTJ401E Rule Error: Type 1 invalid

Explanation:During scanning of the rule member, type 1 is detected, which is not one of the valid types.

Corrective Action:Change the rule using the online interface.

CTJ402E Rule Error: Type 2 invalid when type 1 is R

Explanation:During scanning of the rule member, type 1 is detected, which is not one of the valid types.

Corrective Action:Change the rule using the online interface.

CTJ403E Rule Error: ON_RULE cards not in order

Explanation:During scanning of the rule member, an ON_RULE statement with an invalid type was detected.

Corrective Action:Changethe rule using the online interface.

CTJ404E Rule Error: ON criteria type is invalid

Explanation:During scanning of the rule member, an ON critera statement with an invalid type was detected.

Corrective Action:Change the rule using the online interface.

CTJ405E Rule Error: ON criteria Type 3 invalid

Explanation:During scanning of the rule member, an ON criteria Type 3 statement with an invalid type was detected.

Corrective Action:Change the rule using the online interface.

CTJ406E Rule Error: ON criteria DDNAME card is missing

Explanation:During scanning of the rule member, missing card with DD not provided.

Corrective Action:Change the rule using the online interface.

CTJ407E Rule Error: DO_BLOCK type 2 is invalid

Explanation:During scanning of the rule member, type 2 of DO_BLOCK is not among valid types.

Corrective Action:Change the rule using the online interface.

CTJ408E Rule Error: DO_IF_BLOCK type 3 is invalid

Explanation:During scanning of the rule member, type 3 of DO IF is not among valid types.

Corrective Action:Change the rule using the online interface.

CTJ409E Rule Error: RETURN/REASON code not numeric/hexadecimal

Explanation:During scanning of the rule member a DO RETURN or EXIT return or reason code that is not numeric/hexadecimal respectively was detected.

Corrective Action:Change the RETURN/REASON code using the online interface.

CTJ40AE Rule Error: DO ELSE/END without previous DO IF

Explanation:During scanning of the rule member, a DO ELSE or DO END without a preceding DO IF was detected.

Corrective Action:Change the DO-IF logic in the rule using the online interface.

CTJ40BI Rule Error: string

Explanation:This message follows a rule error message and indicates the erroneous card.

Corrective Action:No action is required.

CTJ40CI Rule Loading. Member:`member_name`, Rule:`rule_name`

Explanation:Indicates loading of rule member.

Corrective Action:No action is required.

CTJ40DE Insufficient Storage

Explanation:Indicates that the rule buffer is not large enough.

Corrective Action:Consult with your z/OS system administrator.

CTJ40EE Abend S0`abend_code` at offset:`offset` in `program` code. Run `string`

Explanation:The CTJx11x program captured an abend S0Cxx.

Corrective Action:Report this message to your system administrator.

CTJ40FE RULES segments exceeds maximum

Explanation:The RULES segment exceeds maximum abend S0Cxx.

Corrective Action:Consult with your z/OS system administrator.

CTJ40GI string data pools has been successfuly released

Explanation:At least one segment of RULES/Shared Memory data pool has been released.

Corrective Action:No action is required.

Messages CTJ500 through CTJ5xx

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

CTJ505I TOTAL ISSUED

Explanation:Total number of messages issued.

Corrective Action:No action is required.

CTJ506I INFORMATION MESSAGES

Explanation:Total number of information messages issued.

Corrective Action:No action is required.

CTJ507I WARNING MESSAGES

Explanation:Total number of warning messages issued.

Corrective Action:No action is required.

CTJ508I ERRORS MESSAGES

Explanation:Total number of error messages issued.

Corrective Action:No action is required.

CTJ509I THE HIGHEST SEVERITY CODE ENCOUNTERD WAS max_rc

Explanation:Indicates the highest severity code encountered.

Corrective Action:No action is required.

CTJ50AI Statistics

Explanation:Title for the statistics section.

Corrective Action:No action is required.

CTJ50BI JOBS PROCESSED

Explanation:Number of verified jobs.

Corrective Action:No action is required.

CTJ50CI JOBS ENDED WITH ERRORS

Explanation:Number of jobs that ended with errors.

Corrective Action:No action is required.

CTJ50DI JOBS ENDED WITH WARNING

Explanation:Number of jobs that ended with warning.

Corrective Action:No action is required.

CTJ50EI JOBS ENDED OK

Explanation:Number of jobs that ended ok.

Corrective Action:No action is required.

CTJ50HI DD STATEMENTS PROCESSED

Explanation:Number of DD statements (cards) processed.

Corrective Action:No action is required.

CTJ50JI PROCEDURES PROCESSED

Explanation:Number of procedures processed.

Corrective Action:No action is required.

CTJ50KI STEPS PROCESSED

Explanation:Number of steps processed.

Corrective Action:No action is required.

CTJ50LE Internal error encountered in procedure verification process

Explanation:CTJAPI encountered an internal problem while verifying the procedure.

Corrective Action:Contact BMC Customer Support.

CTJ50MW EOJ mark found within a procedure

Explanation:While processing a procedure, an EOJ mark was found within the procedure. All following statements will be ignored.

Corrective Action:No action is required.

CTJ50NI EOJ mark found within a JOB

Explanation:While processing a JOB, an EOJ mark (//) was found within the JOB, followed by additional statements.

Corrective Action:No action is required.

CTJ50OW EOJ mark found within procedure proc_name

Explanation:While processing an external procedure, an EOJ mark (//) was found within the procedure, followed by additional statements.

Corrective Action:Review the procedure to ensure that the EOJ mark is needed.

CTJ50PWSYMBOL `symbol` WAS NOT RESOLVED

Explanation:An unresolved symbol was found between apostrophes. In a real submission, no JCL error will occur.

Corrective Action: Check whether the string that follows the ampersand is a symbol that should be resolved. If it is not, no action is required. Also, ensure that the symbol is not split between lines. If the symbol needs to be resolved, set its value in the PROC definition or invocation, or using a SET statement.

Messages CTJA00 through CTJAxx

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

CTJA01E Control-M JCL Verify is not installed

Explanation:The message is issued if Control-M JCL Verify is not installed.

Corrective Action:Verify that CTJ=Y is specified in the IOAPARM member and rerun Control-M JCL Verify.

CTJA02W Control-M JCL Verify ended with a WARNING

Explanation:The message is issued when a warning message is issued by Control-M JCL Verify for the job.

Corrective Action:If required, modify the JCL of the job.

CTJA03E Control-M JCL Verify ended with an ERROR

Explanation:The message is issued when an error message is issued by Control-M JCL Verify for the job.

Corrective Action:Modify the JCL of the job.

CTJA04S Control-M JCL Verify ended with an ERROR. RC=return_code

Explanation:The message is issued when a severe error is encountered by Control-M JCL Verify.

Corrective Action:Refer to the Control-M JCL Verify messages for a detailed explanation of the problem.

CTJA05W Control-M is not installed. Statement ignored.

Explanation:The message is issued when Control-M JCL Verify detects that Control-M is not installed.

Corrective Action:Verify that CTM=Y is specified in the IOAPARM member and rerun the utility.

CTJA06W ADJUST MESSAGE - SYNTAX ERROR IN MEMBER CTJEMSG,ROW NUMBER: row_number

Explanation:The message is issued when Control-M JCL Verify utility recognizes that there is a syntax error in the CTJEMSG member.

Corrective Action:Verify that the syntax of CTJEMSG is correct. For example: "MSGID=messages_id,SEV=I\W\E,SUPPRESS=N\Y" .

CTJA07W UNABLE TO READ THE MEMBER CTJEMSG.

Explanation:The message is issued when Control-M JCL Verify is unable to read the CTJEMSG member from the CTJPARM library

Corrective Action:Check the CTJEMSG member.

Messages CTJD00 through CTJDxx

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

CTJD01W `jcl_statement_number` WARNING: VOLUMES list and VOLUMES in catalog are not matched. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the list of the volumes in the catalog is not match the list of volumes specified in the JCL. Wrong volumes list in the JCL that override the catalog list, might corrupt the data in the file.

Corrective Action:Verify that the list of volumes specified in the JCL is correct.

CTJD02W `jcl_statement_number` WARNING: DSN with DISP=NEW, already exists. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset, specified by DISP=NEW in the JCL, already exists.

Corrective Action:Verify that the DISP and the DSN are correct.

CTJD03S `jcl_statement_number` ERROR: CTJDSC GETMAIN `error`

Explanation:The message is issued when Control-M JCL Verify starts validating the dataset, but fails to allocate workarea. The validation is aborted. This is an internal error.

Corrective Action:Try again. If the problem reoccurs, call BMC Customer Support.

CTJD04S `jcl_statement_number` ERROR: The DSN block was not found

Explanation:The message is issued when Control-M JCL Verify starts validating the dataset, but fails to access the DSN block. The validation is aborted. This is an internal error.

Corrective Action:Try again. If the problem reoccurs, call BMC Customer Support.

CTJD05W `jcl_statement_number` WARNING: DSN with DISP=`disp` not found. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset specified by DISP=OLD or DISP=SHR does not exist, is not cataloged, or has been deleted during the job processing.

Corrective Action:Verify that the DISP and the DSN are correct.

CTJD06W `jcl_statement_number` WARNING: DSN with DISP=DELETE not found. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset specified by DISP=DELETE does not exist, or has been previously deleted during the job processing.

Corrective Action:Verify that the DISP and the DSN are correct.

CTJD07W `jcl_statement_number` WARNING: invalid DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset name is invalid because it does not comply with the syntax rules.

The validation continues without validating this dataset.

Corrective Action:Provide a valid dataset name.

CTJD08W jcl_statement_number WARNING: file was already cataloged. DSN=dataset_name

Explanation:The message is issued when Control-M JCL Verify starts the dataset validation and detects DISP CATLG. However, the file has already been cataloged so when the job is executed a "NOT CATLGD 2" message might be issued by the system.

Corrective Action:Validate that the DSN and DISP=(status,CATLG) are correct.

CTJD09W `jcl_statement_number` WARNING: file was already cataloged on a previous statement. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify starts the dataset validation and detects DISP CATLG. However, the file has already been cataloged in a previous step so when the job is executed a "NOT CATLGD 2" message might be issued by the system.

Corrective Action:Remove the CATLG from the DISP=(status,CATLG).

CTJD0AS `jcl_statement_number` The DSN TREE is empty

Explanation:The message is issued when Control-M JCL Verify starts the dataset validation process, but detects that the list of datasets is empty.

The validation is aborted. This is an internal error.

Corrective Action:Try again. If the problem reoccurs, call BMC Customer Support.

CTJD0BW `jcl_statement_number` WARNING: DATA CLASS `data_class`does not exist. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify checks the data SMS class, but detects that the SMS class does not exist.

Corrective Action:Verify that the DATA CLASS is correct.

CTJD0CW jcl_statement_number WARNING: STORAGE CLASS storage_class does not exist. DSN=dataset_name

Explanation:The message is issued when Control-M JCL Verify checks the storage SMS class, but detects that the SMS class does not exist.

Corrective Action:Verify that the STORAGE CLASS is correct.

CTJD0DW `jcl_statement_number` WARNING: MANAGEMENT CLASS`management_class`does not exist. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify checks the management SMS class, but detects that the SMS class does not exist.

Corrective Action:Verify that the MANAGEMENT CLASS is correct.

CTJD0EW `jcl_statement_number` WARNING: VOLSER `volser` is not in use by CATALOG DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify checks the VOLSER of a dataset, but detects that the VOLSER is different from the CATALOG information.

Corrective Action:Verify that the VOLSER and DSN are correct.

CTJD0FW `jcl_statement_number` WARNING: CATALOGED DSN, IS NOT FOUND. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify checks if the dataset is cataloged, but it does not exist.

Corrective Action:Verify that the DSN is correct.

CTJD0GW `jcl_statement_number` WARNING: VOLSER`volser` is not mounted

Explanation:The message is issued when Control-M JCL Verify checks the VOLSER of a dataset, but detects that the VOLSER is not mounted.

Corrective Action:Verify that the VOLSER is correct.

CTJD0HS `jcl_statement_number` WARNING: SMS CLASSES are used but SMS is not active. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects the SMS CLASSES, while SMS is not active.

Corrective Action:Check if DFSMS is active and rerun the job after DFSMS has been started.

CTJD0IW `jcl_statement_number` WARNING: The specified SMS CLASS does not exist. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that either the SMS CLASS does not exist or it is invalid.

Corrective Action:Verify that the SMS CLASS is correct.

CTJD0JS `jcl_statement_number` DFSMS interface function ended not OK. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify is retrieving information from the DFSMS interface and the process ends with an error.

Corrective Action:Check the previous messages from the SMS that might appear in the JOB LOG.

CTJD0KW `jcl_statement_number` WARNING: The specified UNIT=`unit`oes not exist.

Explanation:The message is issued when Control-M JCL Verify detects that the specified UNIT does not exist.

Corrective Action:Verify that the UNIT name is correct.

CTJD0LW `jcl_statement_number` WARNING: The specified UNIT=`unit` is OFFLINE.

Explanation:The message is issued when Control-M JCL Verify detects that the specified UNIT is offline.

Corrective Action:Verify that the UNIT name is correct.

CTJD0MW `jcl_statement_number` WARNING: The specified VOLSER=`volser` does not match UNIT=`unit`

Explanation:The message is issued when Control-M JCL Verify detects that the specified VOLSER does not match the provided UNIT.

Corrective Action:Verify that the VOLSER and the UNIT are correct.

CTJD0NI `jcl_statement_number` INFORMATION: DATASET is migrated. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is migrated.

Corrective Action:Verify that the dataset is correct.

CTJD0OW `jcl_statement_number` WARNING: MEMBER= `member_name` is not found in DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the specified member does not exist in the specified dataset.

Corrective Action:Verify that the member and the dataset are correct.

CTJD0PW `jcl_statement_number` WARNING: Direct access to VSAM `vsam`of DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a VSAM (index or data) component rather than a cluster.

Corrective Action:Verify that the dataset is using the correct DSNAME.

CTJD0QW `jcl_statement_number` WARNING: Using DISP=NEW but space was not provided. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that DISP=NEW, but SPACE was not set in the JCL statement.

Corrective Action:Verify if the SPACE setting is required or the space can be set by SMS ACS routines.

CTJD0RE `jcl_statement_number` ERROR: DISP=NEW is not allowed in files' CONCATENATION. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects DISP=NEW, but the DD statement is part of the CONCATENATION files. Since this is not valid, the job might abend due to an OPEN error.

Corrective Action:Change the DISP=NEW to SHR or OLD, or remove the DD statement from the CONCATENATION group.

CTJD0SS `jcl_statement_number` ERROR:CTJDSC parameter error.

Explanation:The message is issued when Control-M JCL Verify detects that the CTJDSC module either did not receive any parameter list or it received an incorrect one. The validation is aborted. This is an internal error.

Corrective Action:Verify that the parameter list is correct.

CTJD0TE `jcl_statement_number` ERROR: DISP=OLD or SHR and VOL=SER was specified. UNIT is required for DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects the above DD statement and the UNIT keyword is missing. When DISP=OLD or SHR and VOL is specified, the dataset is accessed directly without checking the catalog and therefore the UNIT is required.

Corrective Action:Correct the statement and rerun job verification.

CTJD0UE `jcl_statement_number` ERROR: DISP=NEW and DISP=OLD for same file in the same step. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects the above DD statement and it detects that the dataset is referred to twice; once with DISP=NEW and once with DISP=SHR/OLD. The dataset will not be found because the dataset does not exist when the system tries to allocate the dataset as an existing dataset.

Corrective Action:Correct the statement and rerun job verification.

CTJD0VE `jcl_statement_number` ERROR: DISP=(NEW,PASS) and twice DISP=(OLD,CATLG). DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects the above DD statement and that the dataset is created with DISP=(NEW,PASS). In addition, it detects that the dataset is referred to twice in the same step with either DISP=(OLD,CATLG) or DISP=(SHR,CATLG). The second statement fails because the system removes the pass flag when handling the first DD statement. Refer to the MVS JCL Reference and MVS JCL Guide.

Corrective Action:Correct the statement and rerun job verification.

CTJD0WE `jcl_statement_number` WARNING: USING DISP=NEW but space was not provided. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the DISP=NEW, but SPACE was not set in the JCL statement.

Corrective Action:Add the missing SPACE keyword.

CTJD0XW `jcl_statement_number` WARNING: DSN with DISP=NEW previously allocated in the job. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset, specified by DISP=NEW in the JCL, was already allocated in a previous step.

Corrective Action:Verify that the DISP and the DSN are correct.

CTJD0YW `jcl_statement_number` WARNING: DSN with DISP=`disp_type` was deleted in previous step. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the specified dataset has been deleted (or renamed by a IDCAMS ALTER NEWNAME command) during the job processing.

Corrective Action:Verify that the DISP and the DSN are correct.

CTJD0ZW `jcl_statement_number` WARNING: DSN with SYMBOLICRELATE can not resolved. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset specified by ALIAS with SYMBOLICRELATE, but the symbol is not found in the system symbolic variables.

Corrective Action:Verify that the SYMBOL can be resolved in the system.

CTJD10W `jcl_statement_number` WARNING: DSN with DISP=`disp_type`was CREATED | DELETED in job`jobname` ID `jobid` statement `statement_number` [and may not exist | and may exist]

Explanation:The message is issued when Control-M JCL Verify detects that the specified dataset was CREATED or DELETED in a previous job. When the current job and the previous job are not on the same level, the last section of the message, "and may not exist | and may exist," is not relevant and therefore it is not displayed.

When the jobs are at the same level, the message changes according to the case as follows:

The specified dataset was CREATED by a job at the same level, but since it might still be possible that the dataset does not yet exist, the warning message ends with the "and may not exist" phrase.
The specified dataset was DELETED by a job at the same level, but since it might be possible that the dataset still exists, the warning message ends with the "and may exist" phrase.

Corrective Action:Verify that the DISP and the dataset are correct.

CTJD11I`jcl_statement_number` INFORMATION: DSN with DISP=PASS (`attribute_number`) is deleted. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the file was created in the job with the PASS attribute, but was not cataloged or kept. The z/OS operation system deletes a file with the PASS attribute either during the last step of the job that references the file, or at the termination of the job.

Control-M JCL Verify does not issue this message for temporary datasets.

Corrective Action:No action is required.

CTJD12I `jcl_statement_number` INFORMATION: DSN with DISP=UNCATLG will be removed from the catalog but will not be deleted.

Explanation:The message is issued when Control-M JCL Verify detects that the file was created in the job with the UNCATLG attribute and was not cataloged or kept. The z/OS operation system deletes a file with the UNCATLG attribute either during the last step of the job that references the file, or at the termination of the job.

Note: Control-M JCL Verify does not issue this message for temporary datasets.

Corrective Action:No action is required.

CTJD13I `jcl_statement_number` INFORMATION: DSN withDISP=`disp_type`was uncatalog (`parameter`). DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the file was created in the job with the disp_type attribute and was not cataloged or kept. The z/OS operation system deletes a file with the disp_type attribute either during the last step of the job that references the file, or at the termination of the job.

Note: Control-M JCL Verify does not issue this message for temporary datasets.

Corrective Action:No action is required.

CTJD14E `jcl_statement_number` ERROR: DSN with DISP=`disp_type`was uncatalog (`parameter`). DSN=`dataset_name`

Control-M JCL Verify does not issue this message for temporary datasets.

Corrective Action:No action is required.

CTJD15I jcl_statement_number INFORMATION: JOB IDjob_id is part of another Control-M flow.

Explanation:The message is issued when Control-M JCL Verify detects that the dataset specified was CREATED or DELETED in a previous job.

Corrective Action:Verify that the DISP and the DSN are correct.

CTJD16W jcl_statement_numberWARNING: DSN is deleted will be used by job at the same level DISP=dispositionjobjobname IDjob_idstatementjcl_number

Explanation:The message is issued when Control-M JCL Verify, using the job dependency awareness feature for Control-M jobs (VD=Y), detects that the dataset specified in jcl_number with DISP2=DELETE was used with DISP=SHR/OLD in a previous job job_id at the same job hierarchy level. The JOB might fail because the file might have been deleted.

Corrective Action:Verify that the DISP and the DSN are correct.

CTJD17W jcl_statement_numberWARNING: SYSTEM SYMBOL CANNOT BE RESOLVED, SYMBOL=symbol

Explanation:The message is issued when Control-M JCL Verify detects that the system symbol is used, but symbol is not found in the system symbolic variables.

Corrective Action:Verify that the symbol can be resolved in the system.

CTJD18E jcl_statement_numberERROR: DD statement with DIS=disposition, is without DSN keyword, or VOLSER

Explanation:The message is issued when Control-M JCL Verify detects a DD statement without a DSN keyword or VOLSER.

Corrective Action:Provide the DSN keyword or VOLSER with the required value.

CTJD19E IGGCSI00 fails with RC=`rc`MODID=`mod`RSN=`rsn`

. For more information refer to message IDC3009I.

Explanation:The message is issued when the catalog search interface fails during processing of a catalog query request. For more information refer to IBM message IDC3009I.

Corrective Action:Re-invoke the JCL Verify validation process for accurate results.

CTJDC0W WARNING: DSN WITH DISP=NEW MAY ALREADY EXIST. DSN=<`dsn name`>

Explanation:The message is issued when Control-M JCL Verify detects that the dataset, specified by DISP=NEW in the JCL, was already allocated in the preceding conditional step.

Corrective Action:Make sure that the current step and the preceding conditional step are mutually exclusive.

CTJDC1W WARNING: DSN WITH DISP=<`disp`> MAY NOT EXIST. DSN=<`dsn name`>

Explanation:The message is issued when Control-M JCL Verify detects that the dataset, specified by DISP=OLD or DISP=SHR has been created or deleted by a conditional step earlier in the job.

Corrective Action:Make sure that the current step and the preceding conditional step are mutually exclusive.

CTJDC3W WARNING: NEW GDS MAY HAVE BEEN PREVIOUSLY ALLOCATED IN THIS JOB. DSN=<`dsn name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset GDS with a relative positive number that is greater than zero specified by DISP=NEW in the JCL, that was already allocated in a preceding conditional step.

Corrective Action:Make sure that the current step and the preceding conditional step are mutually exclusive.

CTJDC5W WARNING: DSN MAY ALREADY BE CATALOGED. DSN=<`dsn name`

Explanation:The message is issued when Control-M JCL Verify detects DISP CATLG but the file was cataloged in a preceding conditional step.

When the job is executed a "NOT CATLGD 2" message might be issued.

Corrective Action:Make sure that the current step and the preceding conditional step are mutually exclusive.

CTJDG0I `jcl_statement_number` INFORMATION: Allocating and concatenating all files in GDG=`gdg_base_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset, specified by DISP=SHR or OLD, is GDG and therefore all GDS in the GDG will be allocated.

Corrective Action:If this situation is not what is required, correct the DSNAME or add the GDS relative number.

CTJDG1E `jcl_statement_number` ERROR: Requested generation is above the limit of `gdg_limit`. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the relative GDS number is higher than the GDG LIMIT in the GDG catalog entry. The job will fail with a JCL error.

Corrective Action:Correct the relative GDS number so that it is within the limit set in the GDG catalog entry.

CTJDG2E `jcl_statement_number` ERROR: Relative generation number specified for GDG is larger than 255. DSN=`dataset_name`

Explanation:The message is issued when the Control-M JCL Verify relative GDS number is higher than 255. The job will fail with a JCL error.

Corrective Action:1) For DISP=SHR or OLD, correct the relative GDS number to be within the limit set in the GDG catalog entry. 2) For DISP=NEW, set the relative GDS number to a value lower than 255.

CTJDG3E `jcl_statement_number` ERROR: Relative generation number is not numeric. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDS with a relative number, but the string number is not numeric. The job will fail with a JCL error.

Corrective Action:Correct the relative number.

CTJDG4E `jcl_statement_number` ERROR: Relative generation number longer than three characters. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDS with a relative number, but the string contains more than three characters. Since the maximum number of characters is three, the relative number is invalid. The job will fail with a JCL error.

Corrective Action:Correct the relative string number so that it is no more than three characters.

CTJDG5W `jcl_statement_number` WARNING: GDG is empty. No file will be allocated. GDG=`gdg_base_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDG but does not contain any GDS. The job will fail with a JCL error.

Corrective Action:Correct the name of the file or add a GDS to the GDG.

CTJDG6E `jcl_statement_number` ERROR: GDS relative sign is not valid. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the GDS relative sign is not valid. (The valid values are: "+', "-" or "0".) The job will fail with a JCL error.

Corrective Action:Correct the relative GDS number.

CTJDG7E `jcl_statement_number` ERROR: Using existing GDS as a new file. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDS with a relative number of zero or negative, but the DISP=NEW. The job will fail with a JCL error.

Corrective Action:Correct the relative GDS number so that it is a positive number, or change the DISP=NEW to DISP=SHR/OLD/MOD.

CTJDG8E `jcl_statement_number` ERROR: Using new GDS as an existing file. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDS with a relative positive number (greater than zero), but the DISP=SHR or OLD. The job will fail with a JCL error.

Corrective Action:Correct the relative GDS number so that it is zero or negative, or change the DISP=SHR/OLD/MOD to DISP=NEW.

CTJDG9E `jcl_statement_number` ERROR: New GDS was previously allocated in this job. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDS with DISP=NEW and with the same relative positive number that was already used in a previous step.

The job will fail with a JCL error.

Corrective Action:Correct the GDS relative number to be a different positive number (greater than zero).

CTJDGAI `jcl_statement_number` INFORMATION: DISP is `disp`. GDS will not ROLL INTO GDG. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a new GDS, but the termination DISP value is not CATLG and therefore, the GDS will be part of the GDG. In a SMS environment the file will be cataloged and the GDG will be marked as pending ROLE IN. A None-SMS file will not be cataloged and can exist on the volume.

Corrective Action:Correct the DISP= to be DISP=(NEW,CATLG).

CTJDGBW `jcl_statement_number` WARNING: DISP is UNCATLG. GDS will be removed from GDG. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDS, but the termination DISP=(status,UNCATLG) will cause the file to be uncataloged, removed from GDG, and deleted from the volume it is allocated on.

Corrective Action:Correct the DISP= with the correct termination value.

CTJDGCE `jcl_statement_number` ERROR: Using existing GDG as a new file. GDG=`gdg_base_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDG name with DISP=NEW in the JCL. A GDG cannot be a new file. A GDG with a relative positive number that is larger than zero can exist and it is called a GDS. The job will fail with a JCL error.

Corrective Action:If the DSNAME is correct, add a GDS positive relative number that is greater than 0. Otherwise, change the DSNAME.

CTJDGDW `jcl_statement_number` WARNING: Request GDS file but file is not a GDS type. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is in a GDS format but it is not part of a GDG. The job will fail with a JCL error.

Corrective Action:Provide a valid GDS or add the file to the GDG using the IDCAMS ALTER ROLLIN command.

CTJDGES `jcl_statement_number` ERROR: GDS catalog search error. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify starts the dataset validation and the internal validation failed. The validation is aborted.

Corrective Action:Try again. If the problem reoccurs, call BMC Customer Support.

CTJDGFE `jcl_statement_number` ERROR: GDS name is too long. max length is 35. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a GDS with a relative number, but the name is longer than 35 characters. When the GDG name, together with the relative number, is transformed to the full DSNAME, it cannot be longer than 44 characters. The relative number format ID ".GxxxxVyy". The job will fail with a JCL error.

Corrective Action:Correct the dataset name.

CTJDGGW `jcl_statement_number` WARNING: Request GDS file but GDG does not exist. GDG=`gdg_base_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is in a GDS format, but the GDG does not exist in the MVS Catalog. The job will fail with a JCL error.

Corrective Action:Check whether the GDS name must be corrected.

CTJDGHI INFORMATION:`action`GDS:`gdg_base_name`

Explanation:The message is issued when Control-M JCL Verify detects that a GDS file was allocated or deleted. Note that the "V%%" suffix added to the GDS name indicates that it is a psuedo GDS DSNAME, not a real and cataloged GDS name.

Corrective Action:No action is required.

CTJDS0I INFORMATION:file is SMS Managed. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a SMS-MANAGED file.

Corrective Action:No action is required.

CTJDS1I INFORMATION: file is not SMS Managed. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is not a SMS-MANAGED file.

Corrective Action:No action is required.

CTJDS2W WARNING: Not a SMS file but DSNTYPE=`dataset_type`requires SMS-MANAGE file.

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is not a SMS-MANAGED file.

Corrective Action:No action is required.

CTJDS3W WARNING:PATH= `parameter` is required when DSNTYPE=PIPE.

Explanation:The message is issued when Control-M JCL Verify detects that the DSNTYPE=PIPE was specified without specifying PATH=parameter.

Corrective Action:No action is required.

CTJDS7S ERROR: DFSMS`subsystem` RC`return_code`SSSA`sssa_reason_code`ACS`acs_return_code/acs_reason_code`SAF`saf_return_code/saf_reason_code`. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify received an unidentified return code or reason code from the DFSMS subsystem.

Corrective Action:Review the return and reason codes.

In most cases the problem is because of ACS routines or exit violations.

If RC is not 0, review the return codes as described in the IBM z/OS DFSMSdfp Diagnosis Reference, in the Storage Management Subsystem interface return codes section.
If SSSA is not 0, review the reason codes as described in the IBM DFSMSdfp Diagnosis Reference, in the Subsystem interface reason codes and ACS services reason codes sections.
If the ACS return and reason codes are not 0, review the reason codes as described in IBM DFSMSdfp Diagnosis Reference, in the ACS executor reason codes section.
If the SAF (security) return and reason codes are not 0, it is only relevant if the ACS or the DFSMS exits perform security validations. Control-M JCL Verify skips the security validations done by the DFSMS.

CTJDS8S ERROR: Internal error CTJSMS Return code `return_code`

Explanation:The message is issued when Control-M JCL Verify detects an error return from the Storage Management Subsystem.

Corrective Action:Verfy that the DFSMS subsystem has not stopped during the Control-M JCL Verify process. Review the return codes as described in the IBM DFSMSdfp Diagnosis Reference, in the Storage Management Subsystem interface return codes section.

CTJDS9I INFORMATION: using DATA class `data_class` STORAGE class `storage_class` MANAGEMENT class `management_class`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a SMS-MANAGED file and the above classes were selected by the ACS routine or exits.

Corrective Action:No action is required.

CTJDSAI INFORMATION: using STORAGE group `storage_group`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a SMS-MANAGED file and the above storage group was selected by the ACS routine or exits.

Corrective Action:No action is required.

CTJDSBW WARNING: Dataset is not SMS-MANAGED but SMS-MANAGED VOLUME was specified. VOL:`volume`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is not an SMS-MANAGED file, but an SMS-MANAGED VOLUME was specified.

Corrective Action:No action is required.

CTJDSCI INFORMATION: File is SMS-MANAGED but the VOLUME serial was specified is not SMS-MANAGED. VOL:`volume`

Explanation:The message is issued when Control-M JCL Verify detects that the dataset is a SMS-MANAGED file but the volume in the DD statement is not SMS-MANAGED volume.

Corrective Action:Correct the VOLUME and change it to an SMS MANAGED volume serial number.

CTJDSDI INFORMATION:`sms_class` is ignored by ACS routine. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the SMS DATA/STORAGE/MANAGEMENT class selected by the ACS routine is not the same as specified in the previous DD statement.

Corrective Action:Verify that the selected class is correct.

CTJDSEW WARNING: Request SMS-Managed file but DFSMS ignored the request. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that a file should be an SMS managed file, but the ACS rejects the file as not being an SMS-MANAGED file and therefore ignored the SMS DATA/STORAGE/MANAGEMENT class settings in the DD statement.

Corrective Action:Verify that the file should not be an SMS MANAGED file.

CTJDSFE ERROR: ACS `reason_code`return `return_code`which does not exist. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify received reason code 1011 from the DFSMS SUBSYSTEM, which means that the ACS routine assigned a DATA/STORAGE/MANAGEMENT class that does not exit.

Corrective Action:For more information, refer to the description of the IBM message IGD01011I.

CTJDSHE ERROR: The ACS STORAGE GROUP ROUTINE did not assign a STORAGE GROUP. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify received an error reason code from the DFSMS SUBSYSTEM, which means that the ACS routine did not assign a storage group, as it was supposed to.

Corrective Action:For more information, refer to the description of the IBM message IGD01013I.

CTJDSIW WARNING: SPECIFIED `sms_class`does not exist. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the SMS CLASS specified by DATACLAS/STORCLAS/MGMCLAS does not exist.

Corrective Action:For more information, refer to the description of the IBM message IGD01014I.

CTJDSJE ERROR: file is VSAM or temporary but ASSIGNED STORAGE GROUP: `storage_group`

Explanation:The message is issued when Control-M JCL Verify detects that the ACS STORAGE GROUP ROUTINE ASSIGNED an incorrect storage group.

Corrective Action:For more information, refer to the description of the IBM message IGD01012I.

CTJDSKE ERROR: ACS Error code `return_code`reason`reason_code`. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the SMS CLASS specified by DATACLAS/STORCLAS/MGMCLAS does not exist.

Corrective Action:For more information, refer to the description of the IBM message IGD01001I.

CTJDSLE ERROR: ALLOCATION REQUEST FAILED BY ACS DUE TO AUTHORITY ERROR

Explanation:The message is issued when Control-M JCL Verify received an AUTHORITY error from the DFSMS SUBSYSTEM, which means that the ACS routine or the SMS EXIT failed to fulfill the allocation request.

Corrective Action:Refer to the previous message(s).

CTJDSLW WARNING: Allocation request failed by ACS exit or ACS routine.DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify received reason code 1001 from a DFSMS subsystem, meaning that the ACS or SMS exit failed to fulfill the allocation request.

Corrective Action:Refer to previous message(s).

CTJDSMW WARNING: SPACE REQUESTED MAY NOT BE AVAILABLE

Explanation:The message is issued when Control-M JCL Verify detects that the space requested for a new allocation might not be available in the volume or storage group.

Corrective Action:Refer to previous message(s).

CTJDSNW WARNING: SPACE NOT SPECIFIED FOR ALLOCATION OF DATA SET

Explanation:The message is issued when Control-M JCL Verify detects that the user tried to allocate a new dataset without specifying the space parameter.

Corrective Action:Refer to previous message(s).

CTJDSOW WARNING: DIRECTORY SPACE BEING REQUESTED IS GREATER THAN PRIMARY

Explanation:The message is issued when Control-M JCL Verify detects that the user tried to allocate a new partitioned dataset (PDS/PDSE), but the space requested for the directory exceeds the available primary space.

Corrective Action:Refer to previous message(s).

CTJDSPW WARNING: ALLOCATION FAILED, REQUESTED SPACE EXCEEDS 65535 TRACKS

Explanation:The message is issued when Control-M JCL Verify detects that the user tried to allocate a new dataset with a space request exceeding 65535 tracks for a data set type that is limited to 65535 tracks per volume.

Corrective Action:Refer to previous message(s).

CTJDSQE `jcl_statement_number` ERROR: : PARTITIONED DATA SET IS NOT ELIGIBLE TO BE A MULTI- VOLUME. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the user tried to allocate a new dataset with a partitioned and multi-volume structure. However, partitioned datasets cannot be multi-volume datasets.

Corrective Action:Correct the dataset allocation parameters.

CTJDSRW WARNING: INCOMPATIBLE STORAGE CLASS AND VOLUME

Explanation: This warning message is specified when Control-M JCL Verify detects that the user is trying to allocate a new data set with GUARANTEE SPACE=YES in the SMS defenition but the volume that is specified is not compatible with the storage class.

Messages CTJE00 through CTJExx

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

CTJE00E `alloc`: `dynalloc error message`

Explanation:Dynamic allocation or deallocation of the DSNAME specified in DO REXX failed with the given error message, where

alloc is either ALLOC or DEALLOC.
dynalloc error message is the IBM error message which starts with a message code of IKJ*.

This message is followed by message CTJE06I.

System Action: For ALLOC: the DO REXX is not performed. For DEALLOC: the DO REXX has been performed.

Corrective Action:For ALLOC, correct the DSNAME in the DO REXX. For DEALLOC, contact BMC support.

CTJE01E DO REXX failed with IRXEXEC RC=`return_code`

Explanation:The call to IRXEXEC to execute REXX EXEC failed with RC=return_code.

Corrective Action:To understand the reason for the failure, note the following:

Return codes of IRXEXEC are described in the z/OS V1R13.0 TSO/E REXX Reference.
RC=20 usually means that the specified EXEC (member) was not found in the specified DSN.
Review additional IRX* error messages in JESMSGLG.
RC > 20000 means that there was a syntax error in the EXEC.
See SYSTSPRT for additional IRX* error messages.

This message is followed by message CTJE06I.

If the reason for the failure is still not clear, contact BMC support.

CTJE02E DOMSG from EXEC: No message provided

Explanation:DOMSG did not provide the message text.

Corrective Action:Correct the error described above.

CTJE03E DORC from EXEC: No RC and no RS provided

Explanation:DORC did not provide the return code (RC) and the reason code (RS). This message is followed by message CTJE06I.

Corrective Action:Correct the error described above.

CTJE04E DORC from EXEC: Invalid decimal characters in RC=`return_code`

Explanation:The return code (RC) in DORC must contain only decimal characters.

Corrective Action:Correct the error described above.

CTJE05E DORC from EXEC: Invalid hex characters in RS=`reason_code`

Explanation:The reason code (RS) in DORC must contain only hex characters. This message is followed by message CTJE06I.

Corrective Action:Correct the error described above.

CTJE06I RULE=`rule name`TABLE=`table name` EXEC=`exec`DSN=`dataset_name`

Explanation:This message identifies which rule and EXEC caused the error described in the preceding message.

Corrective Action:Correct the error described above.

CTJE07E CTJRXX SETVAR or RESOLVE was called with incorrect number of arguments.

Explanation:A REXX EXEC invoked by a DO REXX includes a call to CTJRXX SETVAR or RESOLVE with more or less than 2 arguments.

CTJRXX SETVAR and RESOLVE must be called with 2 arguments. This message is followed by message CTJE06I.

The SETVAR or RESOLVE function is not performed.

Corrective Action:Correct the CTJRXX call in the REXX EXEC.

CTJE08E DO REXX failed in IRXEXCOM with RC=`return_code`

Explanation:The call to IRXEXCOM to set stem variables with the results of SYSINREAD failed with RC=return_code. Some or all of the REXX stem variables were not set.

Corrective Action:Review the descriptions of the IRXEXCOM return codes in the z/OS V1R13.0 TSO/E REXX Reference. Review additional IRX* error messages in JESMSGLG and in SYSTSPRT. This message is followed by message CTJE06I. If the reason for the failure is still not clear, contact BMC customer support.

CTJE09I The command appears in REXX EXEC=REXX Name DSN=REXX dataset

Explanation: This message identifies the REXX EXEC that caused the error described in the preceding message.

Corrective Action: See the following message for an explanation of the error, and correct the issue accordingly.

CTJE0AE CTJRXX/ADDRESS JVER called with an invalid function=`function_name`

Explanation:CTJRXX or ADDRESS JVER was called from a REXX EXEC with an invalid function function_name. This message is followed by message CTJE06I. The CTJRXX or ADDRESS JVER is not executed.

Corrective Action:Fix the syntax error and call CTJRXX or ADDRESS JVER with a valid function.

CTJE0BE CTJRXX ICMNTB/ICMNTA/REPCMNT must be called with 3 arguments

Explanation: This message is followed by message CTJE06I.

CTJE0CE CTJRXX ADJMSG must be called with at least 3 arguments

Explanation: This message is followed by message CTJE06I.

CTJE10I Loading STDR | ENFORCE | REFORMAT rules

Explanation:Information message indicating that the CTJMON monitor is loading the site standard rules (indicated by STDR), enforcement rules (indicated by ENFORCE), or reformatting rules (indicated by REFORMAT).

Corrective Action:No action is required.

CTJE11I Updated JCL saved to member`member_name`in library `lib_name`

Explanation:Information message indicating that the JCL member was saved to the library after the reformat or enforcement process was completed.

Corrective Action:No action is required.

CTJE12W Updated JCL not saved. Requested member `member_name` already exists in library `lib_name`

Explanation:Warning message indicating that the JCL member was not saved to the library after the reformat or enforcement process was completed. Probably the OVR parameter is set to N.

Corrective Action:Set OVR=Y to overwrite the existing member.

CTJE13I Control-M JCL Verify processing REFORMAT or ENFORCEMENT

Explanation:Informational message indicating that Control-M JCL Verify is processing the JCL for reformatting or enforcement.

Corrective Action:No action is required.

CTJE14I `original_jcl_record`

Explanation:Informational message containing the original JCL record before reformatting or enforcement. This message is issued if SHOW ORIGINAL Y is specified in the rule definition.

Corrective Action:No action is required.

CTJE15E ENFORCEMENT RULES ARE NOT LOADED, ENFORCEMENT CAN NOT BE PERFORMED

Explanation:Since the enforcement rules are not loaded, the enforcement process cannot be performed.

Corrective Action:Load the enforcement rules.

CTJE16E REFORMAT RULES ARE NOT LOADED, REFORMATTING CAN NOT BE PERFORMED

Explanation:Since the reformatting rules are not loaded, the reformatting process cannot be performed.

Corrective Action:Load the reformatting rules.

CTJE17E AT LEAST ONE OF PARAMETERS "ENF" AND "REF" MUST BE "Y"

Explanation:The CTJENR batch utility detects that both the REF and ENF parameters are set to "N". The utility ended with RC=16.

Corrective Action:Set at least one of these parameters to "Y".

CTJE18E ERROR WHILE TRYING TO SAVE THE MEMBER `member_name`(RSN=`reason_code`)

Explanation:The CTJENR batch utility failed to save the member. The utility ended with RC=16.

Corrective Action:Check the reason with support.

CTJE19I Runtime parameters: SAV=N OVR=N CTM=Y ENV=GENERAL

Explanation:Informational message indicating runtime parameters.

Corrective Action:No action is required.

CTJE1AW Updated JCL not saved. Requested member`mem_name` is in use in library `lib_name`

Explanation:Warning message indicating that the JCL member was not saved to the library after the reformat or enforcement process was completed, because the member was in use.

Corrective Action:Check who is using or holding the member.

CTJER0S Invalid or redundant parentheses encountered

Explanation: The message is issued when Control-M JCL Verify attempts to perform ENFORCEMENT or REFORMAT and encounters invalid or redundant parentheses in the JCL. The CTJER3S message follows with the erroneous record and the processing of the statement is terminated.

Corrective Action: Remove the redundant parentheses. If the problem re-occurs, contact BMC support and provide them with the output of the ENORCEMENT or REFORMAT request.

CTJER1S module (apar) return code`return_code`reason code`reason_code`

Explanation:The message is issued when Control-M JCL Verify attempts to perform either the enforcement or reformatting function, but the process module ended with an error. The message displays the module's name and APAR ID, and the return and reason codes at the time of the error. Additional messages might follow CTJER1S and the enforcement or reformatting function is terminated.

Corrective Action:Perform the enforcement or reformatting function again. If the problem re-occurs, contact BMC customer support. Please add the enforcement or reformatting function outputs to your call.

CTJER2SJOB `jobname`MEMBER `member`DSN`dsn`

Explanation:The message is issued when Control-M JCL Verify attempts to perform either the enforcement or reformatting function, but the process module ended with an error. The message displays the jobname, the member, and the library that were handled at the time of the error. Message CTJER1S preceeds this message and the enforcement or reformatting function is terminated.

CTJER3SRECORD:`string`

Explanation:The message is issued when Control-M JCL Verify attempts to perform either the enforcement or reformatting function, but the process module ended with an error. The message displays the record was handled at the time of the error. Message CTJER1S preceeds this message and the enforcement or reformatting function is terminated.

CTJERAS Unknown keyword encountered

Explanation: The message is issued when Control-M JCL Verify attempts to perform ENFORCEMENT or REFORMAT and encounters an unknown keyword in the JCL.

System Action: The CTJER3S message follows with the erroneous record, and the processing of the statement terminates.

Corrective Action: Contact BMC support and provide them with the output of the ENFORCEMENT or REFORMAT request with your call.

Messages CTJG00 through CTJGxx

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

CTJGATI EP=`entry_point`RELEASE `release`LEVEL`apar`COMPILE`timestamp`

Explanation:This is an information message giving details about the CTJGATI module, where

entry_point is the entry point of the module
release is the release of the module
apar is the last APAR applied to the module
timestamp is the time stamp when the module was compiled

Corrective Action:No action is required.

Messages CTJJ00 through CTJJxx

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

CTJJ00I SITE STANDARD'S RULES WERE NOT LOADED, SITE STANDARDS VER. DEACTIVATED

Explanation:The site standards rules were not loaded, therefore, this kind of verification is deactivated for this run.

Corrective Action:Load the rules using the Control-M JCL Verify monitor.

CTJJ01E ERROR: Missing statement `begin_statement` before `block_type`

Explanation:While verifying a JES ENDPROCESS or ENDDATASE statement, Control-M JCL Verify detected that a PROCESS or a DATASET statement is missing before the beginning of the PROCESS or DATASET block.

Corrective Action:Either add the missing statement or remove the above statement and then rerun job verification.

CTJJ02E ERROR: SIGNON ERROR - NEW PASSWORD is incorrect, must be in position 35 to 42

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that the new password is incorrect.

Corrective Action:Correct the password and rerun job verification.

CTJJ03E ERROR: SIGNON ERROR - NEW PASSWORD2 is incorrect, must be in position 73 to 80

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that the new password2 is incorrect.

Corrective Action:Correct the password and rerun job verification.

CTJJ04E ERROR: Invalid JES statement - placement in JCL is not correct

Explanation:This message is issued when Control-M JCL Verify detects that a JES2 XMIT or JES3 ROUTE statement is incorrectly placed in the JCL.

Corrective Action:Ensure that the JES2 XMIT or JES3 ROUTE statement is placed correctly after the JOB statement.

CTJJ05E ERROR: SIGNON ERROR - blanks are required after WORKSTATION name until position 21

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that blanks are missing after the workstation name.

Corrective Action:Add the required blanks after the workstation name, until position 21, and rerun job verification.

CTJJ06E ERROR: SIGNON ERROR - BLANK is required in position 24

Explanation:While verifying the SIGNON JES3 statement, Control-M JCL Verify detected that position 24 is not blank.

Corrective Action:Correct the statement and rerun job verification.

CTJJ07E ERROR: SIGNON ERROR - 'A' or BLANK is required in position 22

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that neither a "A" nor a blank is in position 22.

Corrective Action:Correct the statement and rerun job verification.

CTJJ08E ERROR: SIGNON ERROR - 'R' or BLANK is required in position 23

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that neither a "R" nor a blank is in position 23.

Corrective Action:Correct the statement and rerun job verification.

CTJJ09E INTERNAL ERROR CODE=100

Explanation:While verifying a JES statement, Control-M JCL Verify detected an internal error.

Corrective Action:Rerun job verification. If the problem reoccurs, call BMC Customer Support.

CTJJ09W WARNING: The above /*SETUP statement has no volume to request

Explanation:While verifying the SETUP JES2 statement, Control-M JCL Verify detected that the statement does not contain any VOLUME for making a mounting request to the OPERATOR. JES2 does not issue a $HASP103 null, but the JES2 sets the JOB to hold state.

Corrective Action:Correct the statement and rerun job verification.

CTJJ0AE ERROR: Above JES statement has a keyword error

Explanation:While verifying a JES statement, Control-M JCL Verify detected invalid data in the keyword statement.

Corrective Action:Correct the keyword data and rerun job verification.

CTJJ0BE ERROR: JES statement node is unknown to JES. NODE:`node_string`

Explanation:While verifying a JES statement, Control-M JCL Verify detected a node that is not known to JES.

Corrective Action:Correct the node and rerun job verification.

CTJJ0CI INFORMATION: Keyword was ignored by Control-M JCL Verify

Explanation:While verifying a JES statement, Control-M JCL Verify ignored the keyword.

Corrective Action:No action is required.

CTJJ0DE ERROR: Missing mandatory keyword

Explanation:While verifying a JES statement, Control-M JCL Verify detected that a mandatory keyword is missing for the above type of JES statement. For more information, see the IBM MVS JCL Reference.

Corrective Action:Add the missing keyword and rerun job verification.

CTJJ0EI INFORMATION: KEYWORD `keyword`contains an unknown value: `string`

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword statement contains an unknown value.

Corrective Action:No action is required.

CTJJ0EW WARNING: KEYWORD `keyword` has invalid value:`string`

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword statement contains an invalid value.

Corrective Action:Correct the keyword data and rerun job verification.

CTJJ0FE ERROR: Invalid JES statement type

Explanation:While verifying a JES statement, Control-M JCL Verify detected detected an invalid statement type.

Corrective Action:Correct the statement type and rerun job verification.

CTJJ0GE ERROR: Invalid keyword:`keyword`

Explanation:While verifying a JES statement, Control-M JCL Verify detected an invalid keyword.

Corrective Action:Correct the keyword and rerun job verification.

CTJJ0HE ERROR: Invalid delimiter:`delimiter`

Explanation:While verifying a JES statement, Control-M JCL Verify detected an invalid delimiter between two keywords or values.

Corrective Action:Correct the delimiter and rerun job verification.

CTJJ0IE ERROR: Multiply-defined keyword:`keyword`

Explanation:While verifying a JES statement, Control-M JCL Verify detected a keyword used more than one time in the statement.

Corrective Action:Correct the statement and rerun job verification.

CTJJ0II INFORMATION: Multiply-defined keyword:`keyword`

Explanation:While verifying a JES statement, Control-M JCL Verify detected a keyword used more than one time in the statement.

Corrective Action:No action is required.

CTJJ0JE ERROR: Keyword `keyword` data is not numeric. DATA:`data`

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword data is not numeric, as required by JES.

Corrective Action:Correct the keyword and rerun job verification.

CTJJ0KE ERROR: Keyword `keyword` VALUE `value` is out of range

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword data is not in the allowed range.

Corrective Action:Correct the keyword data and rerun job verification.

CTJJ0LE ERROR: Total number of groups is higher than 255

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the total number of groups is greater than 255.

Corrective Action:Correct the groups and rerun job verification.

CTJJ0ME ERROR: Too many groups in list. Maximum allowed is 8 groups.

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the number of groups is greater than the maximum allowed by JES.

Corrective Action:Correct the groups and rerun job verification.

CTJJ0NI INFORMATION: Invalid PRIORITY statement - ignored by JES2

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the PRIORITY statement is invalid. JES2 will ignore the PRIORITY statement when the job is submitted.

Corrective Action:If you want to use the PRIORITY statement, correct the PRIORITY statement and rerun job verification.

CTJJ0OE ERROR: SIGNON Invalid REMOTE WORKSTATION:`string`

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the remote workstation name in the SIGNON statement is invalid.

Corrective Action:Correct the statement and rerun job verification.

CTJJ0PI INFORMATION: Multiple //*NET statements encountered in input stream

Explanation:While verifying a JES statement, Control-M JCL Verify detected multiple //*NET statements.

Corrective Action:Correct the JCL and rerun job verification.

CTJJ0QI INFORMATION: JES statement above may have an invalid TSO or z/VM USERID:`userid`

Explanation:While verifying a JES statement, Control-M JCL Verify detected an invalid TSO or VM user ID.

Corrective Action:If the remote destination is a z/OS or a z/VM you might have to correct the user ID.

CTJJ0RE ERROR: Unbalanced parentheses on keyword data

Explanation:While verifying a JES statement, Control-M JCL Verify detected unbalanced parentheses on keyword data.

Corrective Action:Correct the parentheses on the keyword data and rerun job verification.

CTJJ0SE ERROR: SIGNON ERROR - Must have BLANKS in position 9 to 15

Explanation:While verifying a SIGNON statement, Control-M JCL Verify detected that the data between position 9 and 15 is not BLANK, as required.

Corrective Action:Correct the SIGNON statement and rerun job verification.

CTJJ0TE INTERNAL ERROR

Explanation:While verifying a JES statement, Control-M JCL Verify detected an internal error.

Corrective Action:Rerun job verification. If the problem reoccurs, call BMC Customer Support.

CTJJ0UE ERROR: SIGNON ERROR - Must be a REMOTE name group position 16 to 24

Explanation:While verifying a SIGNON statement, Control-M JCL Verify detected that the data of the REMOTE name field is blank.

Corrective Action:Correct the SIGNON statement and rerun job verification.

CTJJ0VE ERROR: Keyword `keyword` invalid destination name.

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the destination name is not valid.

Corrective Action:Correct the keyword and rerun job verification.

CTJJ0WE ERROR: SIGNON ERROR - PASSWORD1 invalid, must be in position 25 to 32

Explanation:While verifying a SIGNON statement, Control-M JCL Verify detected that the password1 is invalid.

Corrective Action:Correct the password and rerun job verification.

CTJJ0XE ERROR: `keyword/statement_string` has invalid value:`value`

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword has an invalid value.

Corrective Action:Correct the keyword and rerun job verification.

CTJJ0XI INFORMATION: `keyword/statement_string` has unknown value:`value`

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword has an unknown value.

Corrective Action:No action is required.

CTJJ0YE ERROR: Missing or invalid DDNAME

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the mandatory keyword DDNAME is missing or has an invalid value.

Corrective Action:Correct the keyword and rerun job verification.

CTJJ0ZE ERROR: Keyword `keyword/statement_string` data length error

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword's data length is not valid.

Corrective Action:Correct the keyword and rerun job verification.

CTJJ11E ERROR: SIGNON ERROR - NEW PASSWORD2 is incorrect, must be in position 35 to 42

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that the new password2 is incorrect.

Corrective Action:Correct the password and rerun job verification.

CTJJ12E ERROR: SIGNON ERROR - NEW PASSWORD is incorrect, must be in position 44 to 51

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that the new password2 is incorrect.

Corrective Action:Correct the password and rerun job verification.

CTJJ13W WARNING: KEYWORD `keyword` member for value `string` does not exist in SYS1.IMAGELIB

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the keyword statement contains an invalid value.

Corrective Action:Correct the keyword data and rerun job verification.

CTJJ14I INFORMATION: PRIORITY value `priority_string`is not numeric. Statement will be ignored by JES2

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the PRIORITY value is not numeric, as required. JES2 will ignore the PRIORITY statement when the job is submitted.

Corrective Action:If you want to use the PRIORITY statement, correct the PRIORITY statement and rerun job verification.

CTJJ15I INFORMATION: PRIORITY value `priority_number`is out of range. Statement will be ignored by JES2

Explanation:While verifying a JES statement, Control-M JCL Verify detected that the PRIORITY value is not between 0 to 15. JES2 will ignore the PRIORITY statement when the job is submitted.

Corrective Action:If you want to use the PRIORITY statement, correct the PRIORITY statement and rerun job verification.

CTJJ16E ERROR: the statement above has missing separator character

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected that the separtor character is missing.

Corrective Action:Correct the statement and rerun job verification.

CTJJ17E ERROR: //PROCESS is not allowed after //ENDPROCESS

Explanation:While verifying the SIGNON JES statement, Control-M JCL Verify detected //*PROCESS after //*ENDPROCESS, which is not allowed.

Corrective Action:Correct the statements and rerun job verification.

CTJJ18E ERROR: unknown `NODE/REMOTE/DEST` name

Explanation:While verifying a JES statement, Control-M JCL Verify detected that a NODE/REMOTE/DEST name is unknown to JES.

Corrective Action:Correct the statements and rerun job verification.

CTJJ19E ERROR: In the above JES3 statement`keyword1`and`keyword2`are mutually exclusive keywords

Explanation:While verifying the JES statement, Control-M JCL Verify detected that the above statement contains keywords that cannot be in the same statement.

Corrective Action:Correct the statement and rerun job verification.

CTJJ1AE ERROR: Label of XMIT statement is invalid

Explanation: During statement verification, Control-M JCL Verify detected an invalid label.

CTJJ1BE ERROR: Duplicate keyword: `keyword`

Explanation: While verifying a JES statement, Control-M JCL Verify detected a duplicate keyword.

Corrective Action: Correct the duplication and rerun job verification.

CTJJ1HE ERROR: Invalid SUBCHARS: `subchars`

Explanation: While verifying a JES statement, Control-M JCL Verify detected an invalid delimiter between two keywords or values.

Corrective Action: Correct the delimiter and rerun job verification.

Messages CTJL00 through CTJLxx

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

CTJL00E `ID`GOING DOWN DUE TO INTERNAL ERROR CODE `error_code`

Explanation:Control-M JCL Verify Application Server subtask ID is shutting down because of internal error error_code.

Corrective Action:Contact BMC Customer Support.

CTJL01W `ID`NO CONNECTION WITH NODE=`node`

Explanation:Control-M JCL Verify Application Server subtask ID received a remote Control-M JCL Verify verification request for node, but there is no connection with node.

Corrective Action:Contact the Control-M JCL Verify administrator.

CTJL02W `ID`NO RESPONSE RECEIVED WITHIN EXPECTED TIME INTERVAL

Explanation:Control-M JCL Verify Application Server subtask ID received a remote Control-M JCL Verify verification request for node and sent it to the remote node, however no reply has been received within the defined timeout.

Corrective Action:Contact the Control-M JCL Verify administrator.

CTJL03W `ID`COMMUNICATION SLOWDOWN ENCOUNTERED

Explanation:Control-M JCL Verify Application Server subtask ID attempted to send a Control-M JCL Verify verification request to a remote node, but has been notified by IOAGATE that IOAGATE experiences a SLOWDOWN condition, with almost all available SIB type control blocks depleted.

Corrective Action:Contact the Control-M JCL Verify administrator.

CTJL04E `ID`MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: `func` RC=`rc`

Explanation:Control-M JCL Verify Application Server subtask ID experienced an internal error when trying to communicate via IOAGATE, where

func is the attempted function via IOAGATE
rc is the return code with which the function failed

Corrective Action:Contact the Control-M JCL Verify administrator.

CTJL05I `ID`TERMINATING

Explanation:Control-M JCL Verify Application Server subtask ID is terminating.

Corrective Action:No action is required.

CTJL0CE Control-M JCL Verify MONITOR IS NOT ACTIVE ON NODE=`node`

Explanation:A remote Control-M JCL Verify verification request has been sent to node, but could not be carried out because the Control-M JCL Verify Monitor is not active on that node.

Corrective Action:Contact the Control-M JCL Verify administrator.

Messages CTJM00 through CTJMxx

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

CTJM01I Control-M JCL Verify `monitor_type` IS READY TO HANDLE REQUESTS

Explanation:Control-M JCL Verify Monitor or Application Server successfully initialized the queue of Control-M JCL Verify requests and the Cross Memory environment to access the queue.

Corrective Action:No action is required.

CTJM02E INITIALIZATION ERROR. REASON: '`error_type'-reason_code`

Explanation:Control-M JCL Verify Monitor or Application Server failed to initialize the queue of Control-M JCL Verify requests and the Cross Memory environment to access the queue.

Corrective Action:Depending on the reason code, contact IOA/System administration or IOA technical support.

CTJM03E Control-M JCL Verify `monitor_type`ALREADY ACTIVE ON SYSTEM`system_id`

Explanation:Control-M JCL Verify Monitor or Application Server is already running on the system. Only one Control-M JCL Verify Monitor or Application Server may be activated on every system.

Corrective Action:No action is required.

CTJM04I Control-M JCL Verify `monitor_type` FINISHED PROCESSING REQUESTS

Explanation:Control-M JCL Verify Monitor or Application Server finished processing Control-M JCL Verify requests and removed the Cross Memory environment to access the queue of these requests. Usually issued before the monitor shuts down.

Corrective Action:No action is required.

CTJM05E INTERNAL ERROR IN MANAGING VERIFY REQUESTS. FUNCTION: `'function_name'-return_code`

Explanation:Control-M JCL Verify Monitor or Application Server failed in processing the queue of Control-M JCL Verify requests.

Corrective Action:Contact IOA technical support.

CTJM06I MODIFY COMMAND RECEIVED:`command`

Explanation:Control-M JCL Verify Monitor received Modify operator command.

Corrective Action:No action is required.

CTJM07E INVALID MODIFY COMMAND RECEIVED

Explanation:Control-M JCL Verify Monitor received invalid Modify operator command.

Corrective Action:Recheck the Modify command requested and issue the correct one.

CTJM08I SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation:Control-M JCL Verify Monitor received STOP operator command.

Corrective Action:No action is required.

CTJM09I `request_number` Control-M JCL Verify MONITOR REQUESTS STILL IN PROGRESS. RE-ISSUE STOP LATER.

Explanation:Control-M JCL Verify Monitor received STOP operator. But the monitor cannot shut down immediately because it currently handles JCL verification requests.

Corrective Action:Issue STOP command later, after the monitor finishes handling the JCL verification requests.

CTJM0AE INTERNAL ERROR IN EXECUTING Control-M JCL Verify REQUESTS. FUNCTION:`'function_name"-return_code`

Explanation:Control-M JCL Verify Monitor failed in processing of a Control-M JCL Verify request.

Corrective Action:Contact IOA technical support.

CTJM0BE INTERNAL ERROR IN PROCESSING REMOTE Control-M JCL Verify REQUEST. FUNCTION:`'function_name"-return_code`

Explanation:Control-M JCL Verify Monitor failed to pass the remote
Control-M JCL Verify request to the Control-M JCL Verify Application Server.

Corrective Action:Contact IOA technical support.

CTJM0CE Control-M JCL Verify APPLICATION SERVER NOT ACTIVE. REMOTE VERIFYING DISABLED

Explanation:Control-M JCL Verify Monitor is not able to process the request for remote verification because the Control-M JCL Verify Application Server is not active.

Corrective Action:Start the Control-M JCL Verify Application Server.

CTJM0DI Control-M JCL Verify processing performed by Monitor `monitor_jobname / monitor_jobid` on System`system_id`

Explanation:Informational message added to the top of the verification report when the verification was handled by the Control-M JCL Verify Monitor.

Corrective Action:No action is required.

CTJM0EE Control-M JCL Verify Local Monitor is not active. Re-start the monitor

Explanation:Error message indicating that the Control-M JCL Verify cannot perform verification because the local Control-M JCL Verify monitor has not been started.

Corrective Action:Re-start the monitor.

CTJM0FE Control-M JCL Verify Local Monitor internal error: `error`

Explanation:Error message indicating that the Control-M JCL Verify cannot perform verification because the local Control-M JCL Verify monitor has failed to respond.

Corrective Action:No action is required.

CTJM0GW REMOTE JCL VERIFICATION ENVIRONMENT IS NOT AVAILABLE

Explanation:Control-M JCL Verify Application Server was not installed or activated on this system. Remote JCL Verification is not possible.

Corrective Action:If Remote JCL Verification is required, install and activate Control-M JCL Verify Application Server. Check that message CTJM0HI is issued by Control-M JCL Verify Monitor.

CTJM0HI THE NODE NAME IS`node_id`

Explanation:Informational message indicating the NODE name of the IOAGATE associated with this Control-M JCL Verify monitor.

Corrective Action:No action is required. Remote verification requests can be processed even if no IOAGATE is associated with the local monitor.

CTJM0IE ERROR IN CREATING CTMSUB SUBTASK, RC=`return_code`

Explanation:Internal error in Control-M JCL Verify monitor when it attempted to create a CTMSUB subtask. Control-M JCL Verify monitor terminates.

Corrective Action:Contact IOA technical support.

CTJM0JE CTMSUB SUBTASK FAILED

Explanation:CTMSUB subtask of Control-M JCL Verify monitor failed. Control-M JCL Verify monitor terminates.

Corrective Action:Contact IOA technical support.

CTJM0KE ERROR IN THE IOA SECURITY ENVIRONMENT INITIALIZATION. RC=`return_code`

Explanation:Control-M JCL Verify Monitor failed to initialize the security environment. Control-M JCL Verify monitor terminates.

Corrective Action:Contact IOA technical support.

CTJM0LI SECURITY DEFINITIONS REFRESH POSTPONED DUE TO `request_number` CURRENTLY ACTIVE REQUESTS

Explanation:The MODIFY operator command NEWSECDEF (to refresh the security definitions) was received by Control-M JCL Verify Monitor. However, it cannot be processed immediately because there are active verification request sessions currently in process. Security Refresh is postponed until there are no active verification sessions running.

Corrective Action:Later, check the IOA or Control-M JCL Verify Monitor Log to verify whether the Security Refresh was performed.

CTJM0MI SECURITY DEFINITIONS REFRESHED SUCCESSFULLY

Explanation:The security definitions were successfully refreshed by the Control-M JCL Verify Monitor as a result of the MODIFY Operator command NEWSECDEF.

Corrective Action:No action is required.

CTJM0NE SECURITY DEFINITIONS REFRESH FAILED. RC=`return_code`

Explanation:The Control-M JCL Verify Monitor failed to refresh the security definitions (requested by the MODIFY operator command NEWSECDEF). Control-M JCL Verify Monitor terminates.

Corrective Action:Contact IOA technical support.

CTJM0OE Access Environment not created for user`user_name`. RC=`return_code`

Explanation:Control-M JCL Verify Monitor failed to create the security access environment for the verification request owner. JCL verification is not possible.

Corrective Action:Contact the system security administrator.

CTJM0PE User `user_name`not defined

Explanation:Control-M JCL Verify Monitor failed to create the security access environment for the verification request owner because the owner is not defined in the security. JCL verification is not possible.

Corrective Action:Contact the system security administrator. For remote verification, specifying a default user for remote verification (RMTUSER=Control-M JCL Verify installation parameter) can be used.

CTJM0QW User `user_name` not defined. Default User`default_user_name`used for Remote Verification

Explanation:The owner of the remote verification request is not defined in the target system (where the verification is to be performed). Control-M JCL Verify used the default user for the remote verification (RMTUSER=Control-M JCL Verify installation parameter) instead of the request owner.

Corrective Action:Contact the system security administrator.

CTJM0RW IOA security is disabled. Processing is performed using CTJMON's user id

Explanation:IOA security is not installed or is disabled. Processing is performed using CTJMON's user ID and not the requester's user ID. This may result in inaccurate verification results (for example, incorrect "user is not allowed to" messages) or might be used to bypass system security policies (for example, the user may view data that he is not allowed to view).

Corrective Action:Ensure that the IOA Security interface is properly installed. For more information, refer to the INCONTROL for z/OS Installation Guide.

CTJM11E Verification processing failed with `reason_code ABEND|COMPLETION_code`

Explanation:Control-M JCL Verify processing failed with ABEND or COMPLETION code. No verification report available.

Corrective Action:Contact IOA technical support.

CTJM12E Remote Verification environment not available. Request rejected.

Explanation:XCF communications are not available, and Control-M JCL Verify Monitor cannot locate its associated IOAGATE. Remote verification requests cannot be processed.

Message CTJM0HI is issued by Control-M JCL Verify Monitor after it detects that the Control-M JCL Verify Application Server has been activated, and the monitor successfully extracts its own NODE name, so that it can process remote verification requests.

Corrective Action:Activate IOAGATE, which controls the Control-M JCL Verify Application Server. Check that message CTJM0HI is issued by Control-M JCL Verify Monitor. Alternatively, activate XCF communications (if available, by specifying XCF=Y in the CTJPARM member), so that Control-M JCL Verify can communicate with remote monitors using XCF, or use a remote IOAGATE to communicate with monitors in remote sysplexes.

CTJM13E Verification session not found in Control-M JCL Verify Monitor

Explanation:An internal error occurred during processing of a Control-M JCL Verify request.

Corrective Action:Contact IOA technical support.

CTJM14E No report produced by Control-M/JCL Verification

Explanation:Control-M/JCL Verification failed and did not create a report.

Corrective Action:Contact IOA technical support.

CTJM15E `name` Unable to connect to target Node`node_id`

Explanation:.

name - the name of the system that reported the error, or an IOAGATE node name.
node_id - the value of the NODE parameter specified in the verification request.

The NODE parameter was specified in the verification request, indicating that the verification will be performed on a remote sysplex. One of the following errors occurred:

There is no active IOAGATE associated with any Control-M JCL Verify monitor in the local sysplex. In this case, the local system name will appear in the name field.
There is an active IOAGATE, but it is not connected to another IOAGATE identified by the node name. In this case, name is the IOAGATE node name.

Corrective Action:

In case 1: Ensure that IOAGATE is started and connected to one of the Control-M JCL Verify Monitors in the local SYSPLEX.

In case 2: Check the node name specified in the verification request. If it specifies a valid IOAGATE node name then start the corresponding IOAGATE and JCL Verify monitor on the remote SYSPLEX.

IOAGATE node names are specified in the ECAPARM member. In order to be able to communicate, the nodes must also be defined in the network map. The network map name is defined by the NETWMAP parameter in ECAPARM. For more information, refer to the INCONTROL for z/OS Installation Guide: Installing.

If you need to perform the verification in the local SYSPLEX then you do not need to specify a node name, since XCF can be used.
A node name of ‘*’ is invalid.

CTJM16E Timeout occurred waiting for reply from Node`node_id`

Explanation:No response received from the remote Node within a timeout interval.

Corrective Action:Contact IOA technical support.

CTJM17E Session ABENDED in local Control-M JCL Verify Application Server

Explanation:The processing of a Remote JCL verification request failed with ABEND in the local Control-M JCL Verify Application Server.

Corrective Action:Contact IOA technical support.

CTJM18E Control-M JCL Verify Monitor is not active on Node`node_id`

Explanation:Remote JCL verification cannot be performed on the Node displayed because Control-M JCL Verify Monitor is not active on that Node.

Corrective Action:Start Control-M JCL Verify Monitor on the required Node.

CTJM19E Communication with target Control-M JCL Verify Monitor failed: FUNCTION:`'function_name"-return_code`

Explanation:An internal error occurred while trying to perform a remote JCL verification. The error occurred in the communication between the Control-M JCL Verify Application Server and the Control-M JCL Verify Monitor on the target Node.

Corrective Action:Contact IOA technical support.

CTJM1AE Application Server not active. Remote verifying disabled

Explanation:Control-M JCL Verify Monitor is not able to process the request for remote verification because the Control-M JCL Verify Application Server is not active.

Corrective Action:Change NODE to make the local verification or start the Control-M JCL Verify Application Server.

CTJM1BE `system_id`: IOA Environment `ioa_env` not found on SYSTEM `system_parm`

Explanation:A Control-M JCL Verify monitor was not found on the system identified by the message.

system_id – The name of the system that reported the error.

ioa_env - The IOA environment name specified in the verification request.

system_parm – The name specified in the SYSTEM parameter.

Corrective Action:Ensure that a Control-M JCL Verify monitor is running on system system_parm, and that the QNAME parameter in the IOAPARM member matches the "IOA Env" parameter. If NODE was specified, then ensure that it refers to the correct SYSPLEX.

"IOA env" is optional, and that you can specify ‘*” as the system name so that Control-M JCL Verify will search the IOA environment in all the systems in the SYSPLEX.
The named IOA environment refers only to Control-M JCL Verify monitors. Other monitors such as Control-M monitors might share the same QNAME.

CTJM1CE `system_id`: SYSTEM `system_parm` not found

Explanation:A Control-M JCL Verify Monitor was not found in the system specified by the SYSTEM parameter.

system_id – The name of the system that reported the error.

system_parm – The name specified in the SYSTEM parameter.

Corrective Action:

Ensure that a Control-M JCL Verify Monitor is running on the system specified by the SYSTEM parameter, and that the NODE parameter identifies the correct SYSPLEX.
If the system is located in the local SYSPLEX then remove the NODE parameter.
If the verification can be performed on any monitor in the SYSPLEX then do not specify the SYSTEM parameter, or use ‘*’.

CTJM1DE `system_id`: Auto routing - JES node `node_name` not found in sysplex

Explanation:Control-M JCL Verify could not verify the member on the system identified by the JES node name, node number, or DESTID specified in a JES control statement.

system_id – The name of the system that reported the error.

node_name – The JES node name as specified directly by the user, or as translated from the JES node number or DESTID.

Corrective Action:

Ensure that a Control-M JCL Verify Monitor is running on the system identified by the JES node.
If the system is not located in the local SYSPLEX, ensure that it is defined in the CTJJ2G member and points to the node name of IOAGATE on the remote SYSPLEX.

CTJM1EE `system_id`: SYSTEM `system_parm` and/or IOA Env `ioa_env` not found

Explanation:The verification was requested to be performed in a specific system and IOA environment. No matching JCL Verify monitor was found.

system_id – The name of the system that reported the error.

system_parm – The name specified in the SYSTEM parameter.

ioa_env – The IOA environment name specified in the request.

Corrective Action:

1. Ensure that a Control-M JCL Verify monitor is running on the system specified by the SYSTEM parameter, and that the NODE parameter identifies the correct SYSPLEX.

2. If the system is located in the local SYSPLEX then remove the NODE parameter.

3. See messages CTJM1BE and CTJM1CE for errors in the SYSTEM and IOA Env parameters.

CTJM1FI XCF GROUP: `xcf_group_name` STATUS: `xcf_status`

Explanation:In response to the ‘F CTJMON,DXCF command’, the following information is shown:

xcf_group_name – XCF group name, as specified in the CTJPRM member.

xcf_status

ENABLED: XCF communication is active
DISABLED: XCF=N was specified in CTJPARM
ERROR: XCF=Y XCF communications was disabled due to an error

Corrective Action:Check that the XCF group name and status match the intended configuration.

If status is ERROR:

Review the monitor’s console message log for previous XCF related error messages.
Issue D XCF,GRP,xcf_group_name,ALL to obtain more information.
If still unresolved, restart the monitor.

CTJM1GI SYSTEM IOA ENV IOAGATE JES NODE

Explanation:This information message provides header information about Control-M JCL Verify monitors which joined the XCF group. CTJM1HE messages that follow provide details for each monitor. This message is issued once, in response to a ‘F CTJMON,DXCF’ command.

Corrective Action:No action is required.

CTJM1HI `system qname ioagate jes node`

Explanation:This information message provides detailed information about a single Control-M JCL Verify Monitor. It is issued for each communication channel in response to a ‘F CTJMON,DXCF’ command.

system: The system name where the monitor is active.

qname: The IOA environment name specified in the IOAPARM member.

ioagate: The node name (as specified in the ECAPARM) of the IOAGATE that is associated with this monitor.

jes node: The node name of the JES running in the system identified in this message.

Corrective Action:If there is more than one monitor with a IOAGATE node name, it is recommended to move the monitor to another XCF group.

CTJM1II END

Explanation:This information message indicates the end of the output from the ‘F CTJMON,DXCF’ command.

Corrective Action:No action is required.

CTJM1JE `system_id`: Auto routing - SYSTEM/SYSAFF `parm` not found in sysplex

Explanation:Control-M JCL Verify could not verify the member on the system identified by the JES node name, node number, or DESTID specified in a JES control statement.

system_id – The name of the system that reported the error.

parm – The SYSTEM or SYSAFF parameter as specified in the JCL.

Corrective Action:Ensure that a Control-M JCL Verify monitor is running on the system identified by the SYSTEM or SYSAFF parameter, and in the same XCF group as the monitor to which the request was submitted.

CTJM1KI THE LOCAL IOAGATE IS DOWN

Explanation:Control-M JCL Verify monitor has detected that the IOAGATE with which it was associated is no longer active. The IOAGATE was previously identified by message CTJM0HI.

Corrective Action:No action is required. The monitor might still be able to perform remote verifications using XCF communications and remote IOAGATEs.

CTJM1LE `system_id`:AutoRouting - SYSTEM/SYSAFF `parm` not found in jesplex

Explanation: Control-M JCL Verify could not verify the member on the system identified in a JES control statement.

system_id – The name of the system that reported the error.

parm – The SYSTEM or SYSAFF parameter as specified in the JCL.

Corrective Action: Ensure that a Control-M JCL Verify monitor is running on the system identified by the SYSTEM or SYSAFF parameter, and in the same XCF group as the monitor to which the request was submitted.

CTJM1ME `system_id`:AutoRouting - IOAGATE NODE `node` can't be reached

Explanation: Control-M JCL Verify monitor failed to communicate with the IOAGATE node.

Corrective Action: No action is required. The monitor might still be able to perform remote verifications.

CTJM1NE `system_id`: AutoRouting - no eligible system found

Explanation:Control-M JCL Verify could not find a system where the request could be processed.

system_id – The name of the system that reported the error.

Corrective Action:Review the system affinity related parameters (JOB SYSTEM, SYSAFF, SCHENV, JOBPARM S,SYSAFF, MAIN SYSTEM). For example, you specified SYSTEM=(-SYS1,SYS2) but currently the JESPLEX does not have any other active members.

If you still would like to verify the job remotely, specify AR=N (no Auto Routing) and a system name in the Edit macro or batch verification parameters.

CTJM1OE `system_id`: AutoRouting failed due to XCF error

Explanation:Auto Routing cannot be performed because of XCF related problems. Possible reasons are communication errors between monitors and internal processing errors.

system_id – The name of the system that reported the error.

Corrective Action:Do the following:

Verify that the monitor on the remote system is active – it might have come down while processing the request. Look for XCF related errors in the monitor job log.
Internal error in the monitor. Forward the monitor’s job log and DATRACE file to BMC support.

CTJM1PE `system_id`: AutoRouting - SYSAFF `member_name` not active in JESPLEX

Explanation:The JESPLEX member name specified in JOB SYSAFF parameter or JOBPARM S/SYSAFF is defined in the JESPLEX, but is not currently active on any system. Auto Routing cannot be performed. system_id is the name of the system that reported the error.

Corrective Action:Verify that the parameter specifies an active member in the JESPLEX. If the member is currently down and you still would like to verify the job remotely then specify AR=N and a system name in the Edit Macro screen or batch verification parameters.

CTJM1QE CPU TIME LIMIT EXCEEDED IN `statement_type` STT# `statement_numberstatement_text`

Explanation:The CPU time limit set by the STMAXCPU parameter was exceeded for the JCL statement. The error message provides the type of statement, the statement number, and the text of the JCL statement (truncated). The type of statement in which the error occurred can be one of the following:

DO WHILE — a DO WHILE action in a rule, or a REXX exec within a DO WHILE loop
DO REXX EXEC NAME member_name — a REXX exec triggered by a rule, identified by member name

Corrective Action:Review the logic to determine the reason for the high CPU usage (for example, an infinite loop).

CTJM1RE INTERNAL ERROR WHILE PROCESSING STT# `statement_numberstatement_text`

Explanation:An internal error occurred during the processing of the JCL statement. The error message provides the statement number and the text of the JCL statement (truncated).

Corrective Action:Contact BMC Support.

CTJM31I Control-M JCL Verify MONITOR ASSOCIATED WITH XCF GROUP:`xcf_group_name`

Explanation:Control-M JCL Verify Monitor is successfully associated with other such monitors in the specified Cross-System Coupling Facility (XCF) Group in the SYSPLEX. Monitors within the XCF group can communicate without using IOAGATE.

xcf_group_name – XCF group name, as specified in the CTJPRM member.

Corrective Action:No action is required.

CTJM32W ASSOCIATING WITH XCF GROUP FAILED. RETURN CODE: `return_code`

Explanation:Control-M JCL Verify Monitor failed to associate with other monitors in the specified Cross-System Coupling Facility (XCF) Group in the SYSPLEX. This monitor can still communicate with other Control-M JCL Verify Monitors (for performing remote verification) via IOAGATE.

return_code: the XCF error and reason codes.

Corrective Action:The error and reason codes are listed in the IBM manual, MVS Programming: Sysplex Services Reference. If the problem persists, contact BMC technical support.

CTJM33E ERROR IN CROSS SYSTEMS COMMUNICATION: `function_name-return_codediagnostic_data`

Explanation:Control-M JCL Verify Monitor failed to to pass a request via Cross-System Coupling Facility (XCF) communication between monitors running on the same SYSPLEX.

function_name – internal function name

return_code – return code from the function

diagnostic_data – additional diagnostic data

Corrective Action:Contact BMC technical support.

CTJM34I `number_of_requests` JCL Verify SESSIONS TERMINATED

Explanation:Control-M JCL Verify Monitor terminated all the active sessions as a result of the TERM operator Modify command (F CTJMON,TERM)

number_of_requests – The number of requests that were terminated.

Corrective Action:No action is required.

CTJM35I THE MONITOR RUNS ON '`system_id`' AND BELONGS TO IOA ENVIRONMENT '`ioa_env`'

Explanation:This informational message follows CTJM31I and contains the System and IOA Environment identification for the Control-M/JCL monitor. These values are used by the monitors to communicate with each other using XCF.

Corrective Action:No action is required. You can use these values in the verification request to specify where the verification request will be processed.

CTJM36I The request was received by monitor `monitor_id` on system `system_id`

Explanation:This informational message contains the system and the started task name of the first monitor which received the Control-M JCL Verify request (the originating system).

Corrective Action:No action is required.

CTJM37I The request was submitted by monitor `monitor_id` on system `system_id`

Explanation:This informational message follows CTJM36I and contains the system and the started task name of the monitor to which the Control-M JCL Verify request was submitted, if it is not the same as the originating system. If Auto Routing is used, then the request might eventually be processed by another monitor, which will be identified by the CTJM0DI message.

Corrective Action:No action is required.

CTJM38I ROUTING PARAMETERS: NODE=`node` SYS=`system_name` IE=`environment` AR=`value`

Explanation: This message is issued when a routing parameter is set.

Corrective Action: No action is required.

Messages CTJP00 through CTJPxx

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

CTJP0CW `jcl_statement_number` WARNING: PGM `pgm_module` not found

Explanation:The message is issued when Control-M JCL Verify detects that the specified PGM module does not exist.

Corrective Action:Check if the module name is correct. If necessary, add a STEPLIB or JOBLIB.

CTJP0EI `jcl_statement_number` INFORMATION: PGM `pgm_module` found in the STEPLIB library

Explanation:The message is issued when Control-M JCL Verify detects that the specified PGM module exists in the given STEPLIB library.

Corrective Action:No action is required.

CTJP0FI `jcl_statement_number` INFORMATION: PGM `pgm_module` found in the JOBLIB library

Explanation:The message is issued when Control-M JCL Verify detects that the specified PGM module exists in the given JOBLIB library.

Corrective Action:No action is required.

CTJP0GI `jcl_statement_number` INFORMATION: PGM `pgm_module` found in LINKLIST library

Explanation:The message is issued when Control-M JCL Verify detects that the specified PGM module exists in one of the given LINKLIST libraries.

Corrective Action:No action is required.

CTJP0HI `jcl_statement_number` INFORMATION: PGM `pgm_module` found in LPA/PLPA library

Explanation:The message is issued when Control-M JCL Verify detects that the specified PGM module exists in one of the given LPA or PLPA libraries.

Corrective Action:No action is required.

CTJP0II `jcl_statement_number` INFORMATION: PGM `pgm_module` found in library `library`

Explanation:The message is issued when Control-M JCL Verify detects that the specified PGM module exists in the given library.

Corrective Action:No action is required.

CTJP0JI `jcl_statement_number` INFORMATION: PGM `pgm_module` found in LINKDD library

Explanation:The message is issued when Control-M JCL Verify detects that the specified PGM module exists in one of the libraries listed in the CTJLINK member with the ddname specified in the LINKDD edit macro, JD or batch SYSIN parameter.

Corrective Action:No action is required.

Messages CTJR00 through CTJRxx

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

CTJR01I Control-M JCL Verify started resolving Control-M AutoEdit variables

Explanation:The message is issued when Control-M JCL Verify begins resolving Control-M AutoEdit variables.

Corrective Action:No action is required.

CTJR02I `AutoEdit variable list`

Explanation:The message is issued when Control-M JCL Verify is resolving Control-M AutoEdit variables. The text contains a list of the Control-M AutoEdit variables being resolved.

Corrective Action:No action is required.

CTJR03I Control-M JCL Verify completed resolving Control-M AutoEdit variables

Explanation:The message is issued when Control-M JCL Verify finishes resolving Control-M AutoEdit variables.

Corrective Action:No action is required.

CTJR04I Control-M JCL Verify resolving JOB=`jobname` in LIB=`library`

Explanation:The message is issued when Control-M JCL Verify is resolving the Control-M AutoEdit variables in the jobname job located in the library library.

Corrective Action:No action is required.

CTJR05I `text`

Explanation:The message is issued when Control-M JCL Verify is resolving Control-M AutoEdit variables and replaces the original JCL statement with a resolved JCL statement. The text contains the original JCL statement.

Corrective Action:No action is required.

CTJR06E Job definition(s) not supported by JCL verification

Explanation:The message is issued when Control-M JCL Verify finds a schedule definition without one of the following Task Types: Regular job, Emergency job, or Cyclic job.

Corrective Action:No action is required.

CTJR07E Empty JOB `jobname` in MEMBER `member_name` in LIBRARY `lib_name`

Explanation:The message is issued when Control-M JCL Verify attempts to verify a JCL member, which is specified in the lib_name library, but the member_name member is empty.

Corrective Action:Check the member and library names, and correct the incorrect name.

CTJR08I Verify JCL in JOB `jobname` from TABLE `table` in LIBRARY `library`

Explanation:The message is issued when Control-M JCL Verify is verifying the jobname job from the table table, located in the library library.

Corrective Action:No action is required.

CTJR09I Verify JCL for JOB `jobname` will not be verified since it is `reason`.

Explanation:The jobname job will not be verified by Control-M JCL Verify because of the reason indicated by reason.

Corrective Action:No action is required.

CTJR0AW NO JOB `jobname` WAS FOUND IN TABLE `table`

Explanation:The message is issued when Control-M JCL Verify attempts to verify a job, but fails to locate the jobname job in the table table. This an internal error.

Corrective Action:No action is required.

CTJR0BI INTERNAL MESSAGE

Explanation:As CTJ101I message used when CTM=Y for REXX used.

Corrective Action:No action is required.

CTJR0CI Verify JCL in JOB`jobname`from TABLE `member`in LIBRARY`library`

Explanation:The message is issued when Control-M JCL Verify is verifying the jobname job from the member member, located in the library library.

Corrective Action:No action is required.

CTJR0DI SCHEDLIB=`schedule_library`

Explanation:The message is issued when Control-M JCL Verify is verifying the schedule_library schedule library.

Corrective Action:No action is required.

Messages CTJS00 through CTJSxx

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

CTJS00I INFORMATION: JCL contains no errors

Explanation:The message is issued when Control-M JCL Verify does not detect any errors in the JCL.

Corrective Action:No action is required.

CTJS01E ERROR: JCL errors found

Explanation:The message is issued when Control-M JCL Verify detects errors in the JCL.

Corrective Action:Read the error messages to determine the problem.

CTJS02E Unable to open PROCLIB DDNAME

Explanation:The message is issued when Control-M JCL Verify is unable to open the JES2 or JES3 PROCLIB library, indicated by the ddname DD statement, to access the JCL procedure.

Corrective Action:Check previous messages and additional messages in the JOBLOG.

CTJS03E ERROR: Invalid or missing JOB statement

Explanation:The message is issued when Control-M JCL Verify detects that the JCL contains an invalid or missing JOB statement.

Corrective Action:Correct the JOB statement or add one in the JCL member.

CTJS04E Invalid parameter list

Explanation:The message is issued when Control-M JCL Verify receives an invalid parameter list.

Corrective Action:Contact BMC Customer Support.

CTJS05E ERROR: Converter/Interpreter failure

Explanation:The message is issued when Control-M JCL Verify had an internal failure.

Corrective Action:Contact BMC Customer Support.

CTJS06E `jcl_statement_number` ERROR: Invalid REFERBACK in the DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects an error with the BACK REFERENCE in the DSN keyword.

Corrective Action:Check the BACK REFERENCE DD statement to determine the problem.

CTJS07E `jcl_statement_number` ERROR: Invalid REFERBACK in the VOL=REF=`string`

Explanation:The message is issued when Control-M JCL Verify detects an error with the BACK REFERENCE in the VOL=REF keyword.

Corrective Action:Check the BACK REFERENCE DD statement to determine the problem.

CTJS08E `jcl_statement_number` ERROR: Invalid REFERBACK in the UNIT=AFF=`string`

Explanation:The message is issued when Control-M JCL Verify detects an error with the BACK REFERENCE in the UNIT=AFF keyword.

Corrective Action:Check the BACK REFERENCE DD statement to determine the problem.

CTJS09E `jcl_statement_number` ERROR: Invalid REFERBACK in the PGM=`string`

Explanation:The message is issued when Control-M JCL Verify detects an error with the BACK REFERENCE in the PGM= keyword.

Corrective Action:Check the BACK REFERENCE DD statement to determine the problem.

CTJS0AI `jcl_statement_number` INFORMATION: DDNAME `ddname` previously allocated in this step

Explanation:The message is issued when Control-M JCL Verify detects that the specified DDNAME was previously allocated in the STEP.

Corrective Action:No action is required.

CTJS0BE `jcl_statement_number` ERROR: Invalid REFERBACK in the DCB=`string`

Explanation:The message is issued when Control-M JCL Verify detects an error with the BACK REFERENCE in the DCB= keyword.

Corrective Action:Check the BACK REFERENCE DD statement to determine the problem.

CTJS0CW `jcl_statement_number` WARNING: Inconsistent dataset type and directory block specification

Explanation:The message is issued when Control-M JCL Verify detects that the user specified DSORG=PO without the directory block parameter.

Corrective Action:No action is required.

CTJS0DW `jcl_statement_number` WARNING: Record length of zero is only valid if RECFM=U

Explanation:The message is issued when Control-M JCL Verify detects that the user specified LRECL=0 with RECFM=U.

Corrective Action:No action is required.

CTJS0EW `jcl_statement_number` WARNING: Block size must be a multiple of record length for RECFM=FB

Explanation:The message is issued when Control-M JCL Verify detects that the user specified LRECL=0 with RECFM set to a value other than U.

Corrective Action:Change the LRECL setting, or set RECFM=U, and rerun job verification.

CTJS0FW `jcl_statement_number` WARNING: Record length must equal blocksize for RECFM=F

Explanation:The message is issued when Control-M JCL Verify detects that the user specified LRECL=BLKSIZE with RECFM=F.

Corrective Action:No action is required.

CTJS0GW `jcl_statement_number` WARNING: Record length must be less than block size for RECFM=F

Explanation:The message is issued when Control-M JCL Verify detects that the user specified LRECL with a value greater than BLKSIZE for RECFM=F.

Corrective Action:No action is required.

CTJS0HW `jcl_statement_number` WARNING: Block size inconsistent with record size for RECFM=V

Explanation:The message is issued when Control-M JCL Verify detects that the user specified LRECL with a value greater than (BLKSIZE-4) for RECFM=F.

Corrective Action:No action is required.

CTJS0II `jcl_statement_number` INFORMATION: Block size zero or missing, will be set by the system

Explanation:The message is issued when Control-M JCL Verify detects that the block size setting is missing or the block size is set to zero.

Corrective Action:No action is required.

CTJS0JI `jcl_statement_number` INFORMATION: Unable to open PROCLIB DD statement

Explanation:The message is issued when Control-M JCL Verify is unable to open the JES2 or JES3 PROCLIB library, indicated by the ddname DD statement, to access the JCL procedure.

Corrective Action:Check previous messages and additional messages in the JOBLOG.

CTJS0KW `jcl_statement_number` WARNING: DIRECTORY BLOCK WAS SPECIFIED WITH DSORG=PS

Explanation:The message is issued when Control-M JCL Verify detects that the user specified DSORG=PS for the directory block.

Corrective Action:Correct the statement.

CTJS0LE ERROR: DD CAN'T BE DUMMY OR NULLFILE

Explanation: Control-M JCL Verify detected that the user specified DUMMY or NULLFILE within the SYSCHK DD card.

Corrective Action: Fix the problematic statement.

CTJS0ME ERROR: DD WAS SPECIFIED WITH DISP=NEW

Explanation: Control-M JCL Verify detected that the user specified DISP=NEW within the SYSCHECK DD card.

Corrective Action: Fix the problematic statement.

CTJS0NE ERROR: DATASET TYPE IS `type` DSN=`dsn`

Explanation: Control-M JCL Verify detected that the user specified VSAM or PDSE DATASET within the SYSCHK DD card.

Corrective Action: Fix the problematic statement.

CTJS0OW WARNING: INVALID DATA SET SPECIFIED IN DCB KEYWORD. DSN=`dsn`

Explanation: Control-M JCL Verify detected that the user specified an invalid data set name within the DCB keyword.

Corrective Action: Fix the problematic statement.

CTJSA0S IOA security is disabled. Access validation is disabled.

Explanation:The message is issued when Control-M JCL Verify detects during initialization that the IOA security is either disabled or not installed. Therefore, the Control-M JCL Verify file access validation feature is disabled.

Corrective Action:Contact your IOA administrator to ensure that IOA security is installed and enabled.

CTJSA1E ERROR: Permission to access was not granted for DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the user that performs the verification does not have READ access to the JCL library that contains the jobs being verified. The verification request is aborted.

Corrective Action:Verify that the provided user has READ access to the JCL library.

CTJSA2W `jcl_statement_number` WARNING: Permission to READ was not granted for DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that read access was not granted to the provided user for the indicated dataset.

Corrective Action:Verify that the correct user is being used and that the user is allowed to read the dataset.

CTJSA3W `jcl_statement_number` WARNING: Permission to UPDATE was not granted for DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that update access was not granted to the provided user for the indicated dataset.

Corrective Action:Verify that the correct user is being used and that the user is allowed to update the dataset.

CTJSA4S `jcl_statement_number` WARNING: No authorization to commit a security query. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that authority for committing a security query was not granted to the provided user for the indicated dataset.

Corrective Action:Check if the STEPLIB or JOBLIB library are APF authorized. Retry, and if the problem is not solved, call BMC Customer Support.

CTJSA5W `jcl_statement_number` WARNING: Permission to delete was not granted for DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that ALTER access was not granted to the provided user for the indicated dataset and therefore the user cannot delete the dataset.

Corrective Action:Verify that the correct user is being used and that the user has ALTER authority for the dataset.

CTJSA6W `jcl_statement_number` WARNING: Permission to UNCATLG was not granted for DSN=`dataset_name`

Corrective Action:Verify that the correct user is being used and that the user is allowed to uncatalog the dataset.

CTJSA7W WARNING: The provided user is not defined. USERID=`user_ID`

Explanation:The message is issued when Control-M JCL Verify detects that the provided user is not defined in the SECURITY package (CA-ACF2, CA/Top Secrete or IBM RACF).

Corrective Action:Verify that the correct user is being used.

CTJSA8W Access validation check cannot be performed by Control-M JCL Verify

Explanation:The message is issued when Control-M JCL Verify detects that the provided user does not have a valid user ID and therefore the access validation check cannot be performed.

Corrective Action:Check for previous messages in the SYSPRINT or JOBLOG.

CTJSA9I Access Verification USERID is changed from `string_1` to `string_2`

Explanation:Control-M JCL Verify displays this message when the access verification user ID has been changed to the user ID that appears in the scanned job statement.

Corrective Action:No action is required.

CTJSAAW WARNING: SCHEDULING ENVIRONMENT EXISTS BUT IS NOT AVAILABLE

Explanation:Control-M JCL Verify displays this message when the scheduling environment, defined in the JOB statement parameter SCHENV=xxx, exists in the WLM definition, but it is not available for this system.

Corrective Action:Check and correct the SCHENV parameter in the JOB statement.

CTJSABE ERROR: SCHEDULING ENVIRONMENT DOES NOT EXIST IN WLM SERVICE

Explanation:Control-M JCL Verify displays this message when the scheduling environment, defined in the JOB statement parameter SCHENV=xxx, does not exist in the WLM service definition.

Corrective Action:Check and correct the SCHENV parameter in the JOB statement.

CTJSACE Missing required DD `DDname` for PARMDD PARAMETER

Explanation:The message is issued when Control-M JCL Verify detects that the PARMDD PARAMETER in the EXEC statement points to a missing DD statement.

Corrective Action:Check and correct the PARMDD parameter in the EXEC statement.

CTJSADE Job might fail to open PARMDD dataset

Explanation:The message is issued when Control-M JCL Verify detects that the dataset associated with the PARMDD=DDname cannot be opened. It might be because the specified dataset has an incompatible dataset organization or record format.

Corrective Action:Check and correct the PARMDD parameter in the EXEC statement.

CTJSAEE EXCESSIVE USER PARAMETER STRING LENGTH

Explanation:The message is issued when Control-M JCL Verify detects that the dataset associated with the DDname specified in the PARMDD=keyword EXEC statement contains a parameter string that exceeds 32760 bytes in length.

Corrective Action:Check and correct the PARMDD parameter in the EXEC statement.

CTJSAGE ERROR: ILLEGAL JOB CARD - MULTIPLE JOB/JOBGROUP CARDS DETECTED

CTJSAGW `jcl_statement_number` WARNING: Access was not granted for DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that access was not granted to the provided user for the indicated dataset.

Corrective Action:Verify that the provided user has sufficient authority for the dataset.

CTJSAHE ERROR: SYSTEM/SYSAFF invalid, begins with "-" on second or later value

CTJSAOEERROR: User not authorized for JCLLIB `dataset_name`

Explanation:The user does not have read access to a dataset specified in the JCLLIB statement. Procedures or include members from this dataset cannot be accessed. If the job is submitted, it will result in an abend S913.

Corrective Action:Verify that the user who performs the verification has read access to all the datasets specified in the JCLLIB statement.

CTJSR0E %%$SYSINREAD ended with RC=08

Explanation:The message is issued when a Control-M JCL Verify rule invokes the %%$SYSINREAD function on the dsn dataset, but the data is not read.

Corrective Action:Refer to previous messages for more details why the data was not read.

CTJSR4I INFORMATION: DCB dsorg `dsorg` not supported by %%$SYSINREAD. DSN=`dsn`

Explanation:The message is issued when a Control-M JCL Verify rule invokes the %%$SYSINREAD function on the dsn dataset, but the dsorg of the file is not supported by %%$SYSINREAD. Only DSORG PS or PO (PDS or PDSE) are supported.

Corrective Action:Correct the verification rule to skip invoking %%$SYSINREAD for such cases.

CTJSR6I INFORMATION: New GDS file is not supported by %%$SYSINREAD. DSN=`dsn`

Explanation:The message is issued when a Control-M JCL Verify rule invokes the %%$SYSINREAD function on the dsn dataset, which is a GDS file created in a previous step. Since the contents of a new GDG file created by a previous step is not available until after the actual JOB execution, %%$SYSINREAD cannot read it.

Corrective Action:Correct the verification rule so it skips the %%$SYSINREAD function for a new GDS file, which is created in a previous step in the verified job.

Messages CTJT00 through CTJTxx

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

CTJT001I Valid values are Y, N, S, U, or D

Invalid parm value

If you press PF1, ISPF displays the full CTJT001I message.

Corrective Action: Set the parameter value, by entering one of the valid values (Y, N, S, U, or D) in the appropriate field.

CTJT002I Valid values are I, W, E or D

Invalid msg level value

If you press PF1, ISPF displays the full CTJT002I message.

Corrective Action: Set the message level, by entering one of the valid values (I, W, E or D) in the MESSAGE LEVEL field.

CTJT003I Valid values are Y, N, or D

Explanation: When Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an invalid value for one or more of the following fields: JES SYNTAX, DATASET AUTHORIZED, PROGRAM EXISTENCE, RESOLVE CONTROL-M AUTO-EDIT VARIABLE, SITE STANDARDS RULES or UTILITIES VALIDATION, first ISPF displays the following short message:

Invalid parm value

If you press PF1, ISPF displays the full CTJT003I message.

Corrective Action: Set the parameter value, by entering one of the valid values (Y, N, or D) in the appropriate field.

CTJT004I USERID field cannot be empty

Explanation: When Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an empty value for the USERID field, first ISPF displays the following short message:

USERID field empty

If you press PF1, ISPF displays the full CTJT004I message.

Corrective Action: Enter a valid user ID in the USERID field.

CTJT005I USERID should be a valid user name

Invalid USERID field

If you press PF1, ISPF displays the full CTJT005I message.

Corrective Action: Enter a valid user ID in the USERID field.

CTJT006I ENVIRONMENT field can't be empty

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an empty value for the ENV field, first ISPF displays the following short message:

ENVIRONMENT field empty

If you press PF1, ISPF displays the full CTJT006I message.

Corrective Action: Enter a valid user ID in the ENVIRONMENT field.

CTJT007I ENVIRONMENT field should be a valid environment name

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowingyou to change parameter values. If you enter an invalid value for the ENV field, first ISPF displays the following short message:

Invalid ENV field

If you press PF1, ISPF displays the full CTJT007I message.

Corrective Action: Enter a valid user ID in the ENVIRONMENT field.

CTJT008I ODAT field should be a valid date (`YYMMDD`)

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an invalid value for the ODAT field, first ISPF displays the following short message:

Invalid ODAT field

If you press PF1, ISPF displays the full CTJT008I message.

Corrective Action: Enter a valid user ODAT in YYMMDD format.

CTJT009I ODAT must be blank when RESOLVE CONTROL-M AUTO-EDIT="N"

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an invalid value for the ODAT field and RESOLVE CONTROL-M AUTO-EDIT="N", first ISPF displays the following short message:

Parameters conflict

If you press PF1, ISPF displays the full CTJT009I message.

Corrective Action: Enter RESOLVE CONTROL-M AUTO-EDIT="Y" or clear the ODAT value.

CTJT010I NODE field should be a valid node name

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an invalid value for the NODE NAME field, first ISPF displays the following short message:

Invalid NODE field

If you press PF1, ISPF displays the full CTJT010I message.

Corrective Action: Enter a valid NODE name in the NODE NAME field.

CTJT016I JREPPREF field should contain a valid DSN prefix

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an invalid value for the JREPPREF field (not a valid DSN prefix), first ISPF displays the following short message:

Invalid JREPPREF value

If you press PF1, ISPF displays the full CTJT016I message.

Corrective Action: Enter a valid DSN prefix in the JREPPREF field.

CTJT017I JREPVOL field should contain a valid VOLUME name

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you enter an invalid value for the JREPVOL field (not a valid VOLSER name), first ISPF displays the following short message:

Invalid JREPVOL value

If you press PF1, ISPF displays the full CTJT017I message.

Corrective Action: Enter a valid VOLSER name in the JREPVOL field.

CTJT018I Field should be blank when SAVE REPORTS set to "D"

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you choose to use the default values for the ‘Save Report’ feature (values from CTJPARM), you cannot enter values in JREPPREF, JREPVOL, and JREPUNIT from this screen. ISPF first displays the following short message:

Field should be blank

If you press PF1, ISPF displays the full CTJT018I message.

Corrective Action: Delete the values from JREPPREF, JREPVOL, and JREPUNIT, or change SAVE REPORTS to Y.

CTJT019I JREPUNIT field should not be blank when JREPVOL exists

Explanation: When the Control-M JCL Verify Edit Macro is executed with the "P" parameter, a prompt window opens, allowing you to change parameter values. If you choose to enter a value for JREPVOL (name of VOLSER), then you cannot leave JREPUNIT blank, and you must define a UNIT. ISPF first displays the following short message:

Invalid JREPUNIT value

If you press PF1, ISPF displays the full CTJT019I message.

Corrective Action: Enter a valid UNIT in the JREPUNIT field, or delete the value from the JREPVOL field.

CTJT01AW DATASET ALLOCATION FAILED

Explanation: This warning appears when Control-M JCL Verify fails to allocate a file for saving reports.

Corrective Action: Enter valid values in JREPPREF, JREPVOL, and JREPUNIT. Ensure that these values meet the requirements of your system.

CTJT0RI RULE: <ruleID>, TABLE: <tableName> (ENVIRONMENT <envName>)

Explanation: When RULE TRACE is set to Y, Control-M JCL Verify shows an information message regarding each rule being executed.

Corrective Action: No action is required.

Messages CTJU00 through CTJUxx

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

CTJU00I Control-M JCL Verify Utility started. LEVEL `apar_id`

Explanation:The message is issued when Control-M JCL Verify starts the first time. Level indicates the module APAR ID.

Corrective Action:No action is required.

CTJU01I `echo-sysin`

Explanation:The message echoes the input from PARM or *SYSIN statements to Control-M JCL Verify.

Corrective Action:No action is required.

CTJU02I Control-M JCL Verify Utility ended. RC=`return_code`.

Explanation:The message is issued when Control-M JCL Verify ends. RC is the highest return code that occurs during the validation processing.

Corrective Action:If RC is not zero, it means that at least one validation has failed. Review the warning and error messages and handle them appropriately.

CTJU03S Input not read from SYSIN. RC=12

Explanation:The message is issued when Control-M JCL Verify attempts to read the SYSIN file, but it is either an empty or a DUMMY file.

Corrective Action:Add at least one valid statement or a comment and rerun job verification.

CTJU04I ORDER ID=`order_id`MEMBER=`member_name` DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify processes an ORDERID or AJF request.

Corrective Action:No action is required.

CTJU05I ORDER ID=`order_id`INSTREAM JOB

Explanation:The message is issued when Control-M JCL Verify processes an ORDERID or AJF request for an instream job.

Corrective Action:No action is required.

CTJU06E Continuation card is missing. RC=12

Explanation:There is a non-blank character in the 72nd position of the SYSIN statement, but the continuation card is missing.

Corrective Action:Either remove the non-blank character or add the continuation card.

CTJU0CE Keyword `keyword` is not a valid keyword

Explanation:The message is issued when Control-M JCL Verify detects an unrecognized keyword, and continues to the next input statement. Control-M JCL Verify terminates with RC=12.

Corrective Action:Correct the keyword and re-submit the Control-M JCL Verify job.

CTJU0EE Input library not found.

Explanation:The message is issued after Control-M JCL Verify scans all statements, but detects that a SCAN or ORDER statement does not have a DSN or LIBRARY keyword or the value is null. Control-M JCL Verify terminates with RC=12.

Corrective Action:Add a DSN or LIBRARY keyword with a file name to the SCAN or ORDER statement and re-submit the Control-M JCL Verify job.

CTJU0FE Function `function_name` Is not a valid function

Explanation:The message is issued after Control-M JCL Verify detects a statement containing an invalid function. Control-M JCL Verify terminates with RC=12.

Corrective Action:Correct the statement and re-submit the Control-M JCL Verify job.

CTJU0GE Keyword `keyword` contains invalid data `data`

Explanation:The message is issued after Control-M JCL Verify detects that a keyword in one of the statements contains invalid data. Control-M JCL Verify terminates with RC=12.

Corrective Action:Correct the keyword data and re-submit the Control-M JCL Verify job.

CTJU0HW The requested ORDERID `text`

Explanation:A job, which is requested by either the ORDERID or the AJF function, is not processed because of one of the following reasons: it does not have embedded JCL statements, it is a TABLE Entity, it is a Started Task, it is not found in the AJF, or it is already deleted.

Corrective Action:Verify that the requested job is correct.

CTJU0IE SAVMEM PARAMETER INVALID - ONLY SUPPORTED WHEN SPECIFIC (NON GENERIC) MEM=VALUE PROVIDED

Explanation:The message is issued after Control-M JCL Verify detects that a SAVMEM parameter was specified, but the MEM parameter did not provide the specified member name. Control-M JCL Verify stops execution.

Corrective Action:Correct the keyword and re-submit the Control-M JCL Verify job.

CTJUA0I IDCAMS user input record

Explanation:This message displays the user's input.

Corrective Action:No action is required.

CTJUA1E Object type is `object_type_1` but IDCAMS command specified `object_type_2`

Explanation:The type of pre-existing object, as defined in the catalog, is different from the type specified in the IDCAMS command, or a PATH is being defined but the object that was specified in the PATHENTRY parameter is not a cluster or alternate index.

and object_type_2 are object types, such as: ALIAS, GDG, CLUSTER, PATH, AIX.

Corrective Action: Correct the IDCAMS command.

CTJUA2I `object_name` will be deleted

Explanation:The object named in the message will be deleted by a generic delete command.

Corrective Action:Ensure that the object will not be deleted unintentionally.

CTJUA3E MARGINS subparameters are missing, not numeric or out of range

Explanation:The MARGINS parameter of the PARM command is invalid.

Corrective Action:Ensure that the left and right margin sub-parameters are specified and that they are numeric and in the range between 1 and 80.

CTJUA4E Right margin not greater than left margin

Explanation:The MARGINS parameter of the PARM command is invalid.

Corrective Action:Ensure that the right margin specifies a column number that is greater than the left margin.

CTJUA6E ALLOCATE command - invalid use of ')', keyword = `keyword`

Explanation:One of the parameters contains a closing parenthesis ')', but is followed by text or another parenthesis. The variable term, keyword, refers to the keyword or syntax unit that contains the ')'.

Corrective Action:Ensure that the parameters are separated by spaces.

CTJUA7E `idcams_command` command - syntax error type `z`, keyword = `keyword`

Explanation:A syntax error was found in the IDCAMS command. The variables are defined as follows:

idcams_command - first 8 characters of the IDCAMS command name
keyword - first 8 characters of the parameter in error
z - Error type - approximate type of error, which can be one of the following:
- 1 - incomplete parameter. End of statement reached.
- 2 - Missing ')'
- 3 - ')' present but '(' missing
- 4 - A keyword without a value or an unknown keyword
- 5 - Missing '('
- 6 - ')' precedes '('
- E - incorrect expiration date ('TO' or 'FOR' parameter)

Corrective Action:Correct your input.

CTJUA8E "ELSE" command appears improperly

Explanation:An ELSE command appears without a previous IF-THEN sequence.

Corrective Action:Ensure that the ELSE command has a matching IF-THEN sequence.

CTJUA9E "SET" command has invalid assignment expression

Explanation:The required assignment expression in the SET command is invalid.

Corrective Action:Correct the SET command so that the expression is in the following form: SET condition = value. For example: SET MAXCC = 8.

CTJUAAE "IF" command has invalid relational expression or missing/incomplete "THEN" keyword

Explanation:The relational expression in the command is invalid or the THEN keyword is missing.

Corrective Action:Correct the IF command and retry the verification.

CTJUABE Verb name too long - `first_word`

Explanation:The first word in an input statement is too long to be a valid IDCAMS command. Up to 20 characters are displayed.

Corrective Action:Correct your input and retry the verification.

CTJUACE ALLOCATE - DATASET parameter missing

Explanation:The ALLOCATE command requires a DATASET/DA parameter.

Corrective Action:Correct your input and retry the verification.

CTJUADE `parameter` - Value is too long

Explanation:The specified parameter value is too long, where parameter can be a parameter such as: DDNAME, DATASET, LIKE.

Corrective Action:Correct your input and retry the verification. The maximum length for the DDNAME parameter is 8 characters, and 44 characters for all DSNAME related parameters.

CTJUAEE Required verb or parameter(s) missing - `command`

Explanation:A non-modal IDCAMS command was entered without any parameters. command is the assumed command name.

Corrective Action:Review your input, searching especially for missing continuation marks (such as '-' or '+'). Correct your input and retry the verification.

CTJUAFW Unbalanced parentheses, verification continues

Explanation:The IDCAMS command (other than ALLOCATE) contains an unequal number of '(' and ')', but might be valid.

Corrective Action:Subsequent messages will indicate if the command is valid. Even if verification succeeds, it is recommended that you add or remove parentheses as needed, because it might cause Control-M JCL Verify to misinterpret the input for file (FV) or file access (FA) verification.

CTJUAGE End of comment is missing

Explanation:The beginning of comment symbol '/*' was found without the matching end of comment symbol '*/'.

Corrective Action:Correct your input and retry the verification.

CTJUAHI DELETE with MASK specified, no FV/FA checks will be performed.

Explanation:Control-M JCL Verify does not support file (FV) or file access (FA) verification checks for generic DELETE, where the MASK parameter is used.

Corrective Action:No action is required.

CTJUAII `object_name` will be altered

Explanation:The object named in the message will be altered by a specific or generic ALTER command.

Corrective Action:Ensure that the object will not be altered unintentionally. If the object is being renamed, the new name will be displayed by message CTJUAJI.

CTJUAJI `object_name` is the new name

Explanation:The object named in the message is the new name of an object that was affected by a specific or generic ALTER command.

Corrective Action:Ensure that the object has not been renamed unintentionally. The CTJUAII message displays the original object name.

CTJUAKE 'IF' nesting level was exceeded

Explanation:More than 10 levels of 'IF' were detected. For example: IF MAXCC>2 THEN IF MAXCC>3 THEN IF MAXCC>4 THEN IF MAXCC>5 THEN IF MAXCC>6 THEN IF MAXCC>7 THEN IF MAXCC>8 THEN IF MAXCC>9 THEN IF MAXCC>10 THEN IF MAXCC>11

Corrective Action:Simplify your logic and retry the verification.

CTJUALE Input stream end-of-file detected before command end

Explanation:The end-of-file on IDCAMS input stream occurred while expecting more parameters.

Corrective Action:Add the missing data and retry the verification.

CTJUAME IDC`xxxxx` message

Explanation:IDCAMS detected a syntax error in the user's input.

Corrective Action:Refer to the IBM messages manual.

CTJUANE ALLOCATE - Duplicate parameter `parameter`

Explanation:An ALLOCATE command parameter was specified more than once.

Corrective Action:Correct your input and retry the verification.

CTJUAOE CATALOG parameter requires RECATALOG on DEFINE PAGESPACE

Explanation:If CATALOG is specified on DEFINE PAGESPACE, then the RECATALOG parameter is required.

Corrective Action:See the explanation of IBM message IDC3171I for possible responses.

CTJUAPE Error occurred while processing an in-stream SYSIN file

Explanation:The message is issued when Control-M JCL Verify fails to read an in-stream IDCAMS input file (//SYSIN DD *).

Corrective Action:Do the following:

Activate traces 88, 89, 370 on the Control-M JCL Verify monitor.
Retry verification.
Inactivate the traces.
Collect the SYSTSPRT and DATRACE SYSOUT files and the Control-M JCL Verify monitor system messages file.
Contact BMC Customer Support.

CTJUAQE Error: Cannot process SYSIN file

Explanation:The file specified in the SYSIN DD statement cannot be read and therefore the IDCAMS step cannot be verified.

Corrective Action:Verify that the file specified by SYSIN is a readable sequential file or library member and that the record format is not UNDEFINED.

CTJUARW No objects were found for generic operation

Explanation:The generic DELETE or ALTER command will not affect any object, because no object was found that matches the specified entry name.

Corrective Action:Ensure that the entry name (which includes a '*') will match some existing object names at job execution time.

CTJUASW Improperly placed comma has been found and ignored

Explanation:IDCAMS detected an unneeded comma and ignored it. Verification continues.

Corrective Action:Remove the extra comma.

CTJUATE ALLOCATE command - invalid DSNAME

Explanation:The dataset name specified in the ALLOCATE command contains commas or unbalanced quotes.

Corrective Action:Correct the parameter containing the DSNAME.

CTJUAUE `specified_name` DD statement missing

Explanation:An IDCAMS parameter such as INFILE named a DD statement, but the statement was not found in the user's job step JCL.

Corrective Action:Ensure that the JCL includes a DD statement that matches the name specified in the IDCAMS parameter.

CTJUAVW DELETE entryname format may require the MASK parameter

Explanation:A generic entryname was specified, but it might require the MASK parameter, and might fail during execution. Neither dataset verification nor file access verification will be performed.

Corrective Action:Correct the entryname or add the MASK parameter.

CTJUAWE DELETE VVR requires the FILE parameter

Explanation:The command passed IDCAMS syntax checking, but it might fail during execution because the FILE parameter is needed to identify the volume on which the VVDS resides.

Corrective Action:Add the required parameter and DD statement.

CTJUAXE FILE `filename` in use, ALLOCATE will fail

Explanation:The FILE parameter in the ALLOCATE command specified a name that is already in use by the job step.

Corrective Action:Review the need for using the FILE parameter. If it is needed, ensure that all the FILE parameters in ALLOCATE commands are unique and also differ from any DD names in the job step JCL.

CTJUAYE ALLOCATE command - invalid FILE parameter

Explanation:The FILE parameter must adhere to the rules of DD names in DD statements.

Corrective Action:Correct the parameter and retry verification.

CTJUAZE IDCAMS will ignore remainder of input if MAXCC >= 16

Explanation:A SET command changed the condition code to a value greater or equal to 16. If this command is reached during execution, IDCAMS ignores the rest of the input stream.

Corrective Action:No action is required.

CTJUB0E Object not found or is not a catalog - `user_catalog`

Explanation:The user catalog specified in the CATALOG parameter could not be found, or the name specified is not a user catalog.

Corrective Action:Specify a pre-existing user catalog name and ensure that the catalog is accessible on the local system.

CTJUB1W ALLOCATE command - 'NEW' not specified, data set status unpredictable

Explanation:The IDCAMS ALLOCATE command can only be used for allocating new data sets.

Corrective Action:If you intend to allocate a new data set, add the NEW parameter.

CTJUB2E ALLOCATE command - invalid use of '(', keyword = `keyword`

Explanation:The IDCAMS ALLOCATE command contains multiple opening parentheses. The variable term, keyword, refers to the keyword or syntax unit that contains the '('.

Corrective Action:Ensure that the parameters are separated by spaces and that multiple parentheses are not used inappropriately.

CTJUB3E Invalid utility input file - `error_type`

Explanation:A SYSIN input file for IDCAMS, or a SYSTSIN file for TSO batch is invalid. The variable term, error-type, refers to one of the following error types:

DYNAMIC ALLOCATION ERROR - the file could not be allocated
TAPE DATA SET - the data set resides on tape
NEW FILE - the data set is not available for verification
TEMPORARY FILE - the data set is not available for verification
PDS BUT NO MEMBER - the data set is a library, but no member name was specified

Corrective Action:Ensure that the utility input file is valid.

CTJUB4E Required volumes and/or devicetypes have been omitted

Explanation:The DEFINE NONVSAM command must include the VOLUMES and DEVICETYPES parameters.

Corrective Action: Ensure that both parameters are specified for the command.

CTJUB5I IDCAMS Allocated DSNAME will be name

CTJUH0I `user input record`

Explanation: This message displays a record from the utility's SYSIN files.

Corrective Action:No action is required.

CTJUH1E Invalid command

Explanation: The input statement does not contain a valid command recognized by the utility.

Note that commands must not start in column 1.

Corrective Action:Correct your input.

CTJUH2E Required parameter or value missing – `parameter`

Explanation: A required parameter is missing, or a keyword was specified without a value.

Corrective Action: Add the required parameter. If it is a keyword, add a value.

CTJUH3E Parameter not valid for operation - `parameter`

Explanation: The parameter cannot be specified for the requested operation. For example, 'SYS' cannot be specified with SCRATCH DSNAME.

Corrective Action: Remove the parameter.

CTJUH4E Error in parameter - `parameter`

Explanation: The specified parameter is unrecognized, inappropriate for the command, is incomplete or is syntactically incorrect. For example, a keyword is not followed by the '=' sign.

Corrective Action: Correct your input and retry verification.

CTJUH5E Duplicate parameter - `parameter`

Explanation: The parameter was already specified in the statement.

Corrective Action: Ensure that each parameter or keyword appears only once.

CTJUH6E Mutually exclusive parameters – `parameter1`+`parameter2`

Explanation: The two parameters (parameter1,parameter2) cannot be both specified in the same statement.

Corrective Action: Remove one of the parameters and retry.

CTJUH7W Invalid EXEC PARM field, verification continues

Explanation: The PARM field on the EXEC card contains errors.

The errors are ignored by the utility.

Corrective Action:Correct or remove the PARM field.

CTJUH8W Duplicate parameters in EXEC PARM, verification continues

Explanation: The PARM field on the EXEC card contains multiple occurrences of the same parameter. The utility will ignore the error.

Corrective Action:Correct or remove the PARM field.

CTJUH9E Error in parameter - `parameter`

Explanation: The parameter value is invalid. The message identifies the parameter and error. For example, the device type is unknown, unbalanced parentheses or unbalanced apostrophes.

Corrective Action: Correct the parameter and retry.

CTJUHAE Too many DSNAMEs - maximum of 10 allowed

Explanation: The list of DSNAMES is too long.

Corrective Action: First check if the command allows multiple DSNAMEs. If it does, add another command and divide the DSNAMEs between the two commands.

CTJUHBE Too many volume serial numbers

Explanation: The list of volumes in the VOL parameter is too long.

Corrective Action: First check if the command allows multiple volsers. If it does, add another command and divide the volsers between the two commands.

CTJUHCE Parameter length error - `value`

Explanation: The parameter value is either too long or too short. For example, the maximum for volser is 6 and for DSN is 44.

Corrective Action: Correct the parameter and retry.

CTJUHDE Invalid control card - `x`

Explanation:One of the following errors were detected:

DELIMITER x - the character x is not allowed or in wrong position
NO COMMAND OR PARAMETER FOUND
DATA IN COLS 1-15 - illegal on a continuation card
DELIM/SPACE IN WRONG POSITION – a space or a special character appears in an unexpected position. For example, a space appears after a '=' sign, or a '*' appears where only alphanumeric or national symbols are allowed.
CONTINUATION ERROR – column 72 is space
UNBALANCED PARENTHESES
EXPECTED CONTINUATION - but encountered end of file
Keyword without a value.
COLUMN 16 SHOULD NOT BE SPACE – on a continuation card

Corrective Action: Correct the parameter and retry.

CTJUHEE DD statement missing or invalid device type for volume `volume`

Explanation: The specified volume is not allocated to the job step, or the device type is invalid for the requested operation.

Corrective Action: Add a DD statement which refers to the volume needed for the operation. The volume must be online and of the same device type as specified in the utility control statement. If no VOL=keyword was specified, add a DD for the system residence volume.

CTJUHFE Tape device type not allowed for command

Explanation: The command (such as LISTVTOC) is not supported for tape device types.

Corrective Action: Ensure that VOL=devtype=volser refers to a DASDI device type

CTJUHGE Error: Cannot process `ddname`file

Explanation: The file specified on the SYSIN or SYMNAMES DD statement cannot be read. The utility step cannot be verified.

Corrective Action: Verify that the file specified by SYSIN or SYMNAMES is a readable sequential file or library member that contains utility control statements, and that the logical record length is 80.

CTJUHHI SCRATCH VTOC - individual file verification bypassed

Explanation: File verification and access checks will not be performed because the command may apply to a large number of data sets.

Corrective Action:Display the contents of the volume to ensure that no unintended deletions will occur and that deletions will not fail due to insufficient authorization.

CTJUHIE ACTION CANNOT BE PERFORMED ON VSAM COMPONENTS OR ALIASES

Explanation: IEHPROGM operations are not supported for VSAM data sets, aliases or any entity other than a non-VSAM data ser.

Corrective Action:Use IDCAMS utility for VSAM and other catalog entry types not supported by IEHPROGM.

CTJUHJE Columns 1-15 on continuation card are not empty

Explanation: Data on continuation cards must start on column 16 data sets.

Corrective Action:Correct the continuation card and retry.

CTJUHKW Attempt to scratch a VTOC index data set

Explanation: IEHPROGM will not scratch the data set containing the index for a indexed VTOC.

Corrective Action:Do not use IEHPROGM do delete SYS1.VTOCIX data sets.

CTJUHLE Attempt to scratch the VTOC of the SYSRES volume

Explanation: Caution should be exercised when attempting to delete the files of the system residence volume.

Corrective Action:Review utility input to ensure that it will not damage the system.

CTJUHME Invalid tape file sequence number

Explanation: You are cataloging a dataset on tape, and one of the file sequence numbers is not numric or exceeds 99999.

Corrective Action:Correct the sequence number or change it to 1.

CTJUHNI Generic DSNAME not verified

Explanation:The DSNAME parameter of an IEHLIST command contains *a '*' or '%'. The data set names in the command will not be verified.

Corrective Action:Ensure that your intention was to list multiple generic data sets.

CTJUHOI ADRDSSU message

Explanation: Message issued by the utility during syntax checking.

Corrective Action: Review message. If it indicates an error then correct your input.

CTJUHPE (`task_id`) Verification of `keyword` bypassed - `ddname` DD missing

Explanation: The DD statement specified in the FILTERDD, PASSWORD(dsn) or EXCLUDE(DDNAME(ddname)) keyword cannot be found in the job step's JCL, where task_id is the Task ID (see message CTJUJTI).

Corrective Action: Correct the JCL.

CTJUHPW (`task_id`) Verification of `keyword` bypassed - `reason_code`

Explanation: The file specified by the FILTERDD, PASSWORD(dsn), or EXCLUDE(DDNAME(ddname)) keyword is not verified, but it might still be correct, where task_id is the Task ID (see message CTJUJTI).

The reason_code can be one of the following:

SPLIT VALUE – Keyword or value split between multiple records. Corrective Action: Input might be correct but needs to be simplified for verification.
ALLOCATION ERROR – Error allocated the FILTERDD file.
ALLOCATED IN JOB – File was allocated previously in the job. Input might be correct but cannot be verified
MAX 10 EXCEEDED – More than 10 FILTERDD's verified concurrently.
GDG + – File is a GDG +1 generation, cannot be verified.
ERROR CREATING TEMP – Error creating temporary file needed for verification.
ERROR WRITING TEMP – Error writing temporary file.
DISP=NEW OR MOD – File has DISP=NEW or MOD, cannot be verified.
DELETED IN PREV STEP – File deleted in a previous job step.
FILE IS DUMMY
CONCATENATION – File is part of concatenation. May be correct but cannot be verified.
TAPE – Cannot be verified.
NOT CATALOGED – VOL=SER specified. Verification not supported.
DSORG / NOT AVAIL – one of the following errors:
- Invalid DSORG
- VOL=REF specified or DDNAME= specified
- File not found or not available for verification
LRECL NOT 80 – Invalid LRECL – must be 80
INVALID RECFM – must be FB or F
USER NOT AUTHORIZED - User not authorized to access file
MEMBER NOT FOUND – PDS but member not specified or not found

CTJUHQE UNCATLG OF AN SMS MANAGED DATA SET IS NOT ALLOWED

Explanation: The DSNAME in an IEHPROGM UNCATLG command refers to a SMS-managed data set. IEHPROGM cannot uncatalog it.

Corrective Action: To uncatalog the data set, see the following IBM manuals: z/OS DFSMS Managing Catalogs and z/OS DFSMS Access Method Services Commands.

CTJUHRE Volume `volume` appears as non-first on a DD VOL=SER list

Explanation: For IEHLIST and IEHPROGM, the volser specified in the command must not appear as the non-first volser in the VOL=SER list on a DD statement.

Corrective Action: Ensure that the volser has its own DD card and remove it if it appears as non-first in a VOL=SER list.

CTJUHSE Volume `volume` is not first in a DD concatenation

Explanation: For IEHLIST and IEHPROGM, the volser specified in the command appears on a DD concatenation but is not the first DD.

Corrective Action: Either add specific DD pointing to the volser or ensure that the DD is the first in a concatenation.

CTJUHTE SYSPRINT BLKSIZE/LRECL NOT MULTIPLE OF 121

Explanation: For IEHLIST and IEHPROGM, The block size of the SYSPRINT data set must be a multiple of 121. LRECL should be set correspondingly.

Corrective Action: Remove DCB=BLKSIZE from SYSPRINT statement.

CTJUHUI Required parameter or value missing - DUMP OR FORMAT

Explanation: A LISTVTOC INDEXDSN statement requires either DUMP or FORMAT.

Corrective Action: Review input. Processing continues.

CTJUHVE Step contains DD statements with identical names

Explanation:The job step includes DD statements that have identical names. This might cause IEHLIST to fail.

Corrective Action:Ensure that all the DD's have different names.

CTJUHWE Data set is not a PDS: `dsname`

Explanation: The DSNAME specified on a LISTPDS command does not refer to a partitioned data set.

Corrective Action: Check the dsname and ensure that it is a PDS.

CTJUHXE SYSIN LRECL not 80 or BLKSIZE not multiple of 80

Explanation: For IEHLIST and IEHPROGM, The block size of the SYSIN data set must be a multiple of 80. LRECL should be 80.

Corrective Action: Remove DCB=BLKSIZE from the SYSIN statement.

CTJUHYE DD statement missing for system residence volume `volume`

Explanation: The command did not include the VOL=devtype=volser parameter.

The system residence volume volume is used as default.

Corrective Action: ensure that a DD statement for the system residence volume is added to the job step, or add an appropriate VOL parameter on the utility command.

CTJUHZE INDEXDSN must be specified as SYS1.VTOCIX.`value`,`value`=`third_level_qualifier`

Explanation: Examine message.

Corrective Action: Correct your input and retry.

CTJUJ0I Using system residence volume `volume`

Explanation: A IEHLIST command did not specify a volser. The system residence volume volume is used as default.

Corrective Action:No action is required.

CTJUJ1W Syntax error in name field. Verification continues.

Explanation: The name field of a IEHPROGM command is invalid. Utility processing will continue.

Corrective Action: Ensure the name field is 1-8 characters, starts with a letter and contains only alphanumeric or national characters.

CTJUJ2W Data set was created on a different volume – `volume`

Explanation: A data set was created in a job step prior to IEHPROGM. In the IEHPROGM step, a CATLG command is issued but specified a volume different from the one on which the data set was created.

Corrective Action: Correct the VOL= parameter on the CATLG command so it matches the VOL= parameter on the DD that created the data set.

CTJUJ3W WARNING: file was already uncataloged. DSN=`dataset_name`

Explanation: A IEHPROGM UNCATLG command refers to a data set that was not cataloged, or was uncataloged in a previous job step.

Corrective Action: Check if the UNCATLG command is needed.

CTJUJ4W Volume count mismatch between allocation and CATLG – `dataset_name`

Explanation: A data set dataset_name was allocated in one step and then cataloged using IEHPROGM is another step. The number of volume serial numbers specified in the two steps is not the same.

Corrective Action: Correct either the allocation JCL or the IEHPROGM CATLG command.

CTJUJ5E Invalid DSN=`dataset_name`

Explanation: The data set name dataset_name that appears in a IEHPROGM or IEHLIST command is invalid. For example, it starts with a numeral.

Corrective Action: Correct the DSNAME in the utility input.

CTJUJ6I DDNAME name - DISP=OLD recommended

CTJUJ7W ADR`xxx`W warning message

Explanation: A warning message issued by the ADRDSSU utility.

Corrective Action: Look up the explanation of the ADRxxxW message in the following IBM manual: DFSMSdss Storage Administration Guide.

CTJUJ8E ADR`xxx`E error message

Explanation: A error message issued by the ADRDSSU utility.

Corrective Action: Look up the explanation of the ADRxxxE message in the following IBM manual: DFSMSdss Storage Administration Guide.

CTJUJ9E Invalid `parameter` value specified in EXEC PARM

Explanation: The ABEND or SDUMP parameters for the ADRDSSU program contain an invalid value.

Corrective Action: The parameters must specify 1 – 3 numerals. For more information, see the following IBM manual: DFSMSdss Storage Administration Guide.

CTJUJAE ADRDSSU Utility cannot be loaded due to memory shortage

Explanation: Verification of ADRDSSU input cannot be performed because there is not enough storage to load the utility in the private area below the line.

Corrective Action:

Retry the verification. Memory shortage might occur due to a large number of concurrent verifications.
If error persists then the problem is due to fragmentation of free storage. Restart the JVER monitor and retry verification.

CTJUJTI ADR101I TASKID (`task_id`) HAS BEEN ASSIGNED TO COMMAND `command`

Explanation:ADRDSSU assigned task ID task_id to command command. All future ADR and CTJUHPE/W messages related to this command will contain the task ID indicated in parentheses.

Corrective Action:No action is required.

CTJUT1I Plan `plan_name`is valid and operative.

Explanation:Plan verification was successful.

Corrective Action:No action is required.

CTJUT2E Plan `plan_name`is `status_1`(`z`) and`status_2`.

Explanation:Plan verification failed because it is either invalid, inoperative, or both.

The variables are defined as follows:

plan_name - Plan name
status_1 - Valid or Invalid
(z) - Value of the VALID column in the DB2 catalog.
status_2 - Operative or Inoperative

Corrective Action:Re-BIND the plan and retry verification. For more details, refer to the IBM DB2 for z/OS SQL Reference manual for descriptions of the VALID and OPERATIVE columns in the SYSIBM.SYSPLAN table.

CTJUT3E Plan `plan_name`cannot be found.

Explanation:The plan row was not found in the DB2 catalog.

Corrective Action:Verify that the plan name is correct and that the BIND process for the plan was completed successfully.

CTJUT4E Subsystem`subsystem_id`not found

Explanation:The named DB2 subsystem is not defined on the system.

Corrective Action:Check your input and ensure that the verification is performed for the system where the DB2 subsystem is active.

CTJUT5E Subsystem `subsystem_id`is INACTIVE

Explanation:The named DB2 subsystem is defined, but not active.

Corrective Action:Activate the subsystem.

CTJUT6I Using DB2 subsystem `subsystem_id`from`source`

Explanation:The message identifies the name of the DB2 subsystem being used to verify the user's DSN commands, and the source of the name.

The variables are defined as follows:

source - one of the following:
- DSN COMMAND: the name specified in the SYSTEM parameter of the DSN command.
- CTJPARM DB2SYS: the name specified in the DB2SYS parameter in CTJPARM.
- SYSTEM DEFAULT: the default DB2 subsystem, which is obtained from the DSNHDECP module. The module is first searched for in the user's JCL STEPLIB or JOBLIB libraries. If it is not found, it is loaded from the Control-M JCL Verify STEPLIB or the system's link libraries (LNKLST).
subsystem_id - DB2 subsystem name.

Corrective Action:No action is required.

CTJUT7E Missing, invalid or duplicate command/parameter

Explanation:An invalid SYSTEM, PLAN, or PROGRAM parameter has been detected in the user's input or a duplicate DSN or RUN command has been detected on the same line.

Corrective Action:Ensure that the above parameters are coded correctly.

Possible errors:

Parameter has no value.
Parameter was specified multiple times and one of the occurrences has no value (if all have a value then the last one will be used).
There are unbalanced parentheses to the left of the parameter.
Parameter value is too long. The maximum number of characters for the parameters are as follows: PLAN - 8, SYSTEM - 4, PROGRAM - 8

CTJUT8E RUN subcommand requires either PROGRAM or PLAN+CP parms

Explanation:RUN PLAN(..) was detected, but no PROGRAM or CP parameters were specified.

Corrective Action:Specify parameters for both PLAN and PROGRAM, or PLAN and CP, or just PROGRAM.

CTJUT9E RUN subcommand cannot have both PROGRAM and CP parameters

Explanation:PROGRAM and CP parameters are mutually exclusive.

Corrective Action:If a TSO command follows the RUN command, then remove PROGRAM. Otherwise remove the CP parameter.

CTJUTAW A RUN command was found without a preceding valid DSN command

Explanation:If the intention was to run a DB2 application, then the RUN subcommand must be preceded by a valid DSN command. Alternatively, this could be a call to the RUN TSO command (unrelated to DB2).

Corrective Action:If your intention was to run a DB2 application, then make sure the RUN subcommand is preceded by a DSN command, and that no errors were reported on the DSN command.

CTJUTBE Incomplete command detected at end of input

Explanation:The last utility input record ended with a continuation sign ('-' or '+').

Corrective Action:Ensure that the utility input commands are complete.

CTJUTCE Failure to open JVER plan `plan_name`, RC=`return_code`, RS=`reason_code`

Explanation:An error occurred opening the Control-M JCL Verify (JVER) DB2 plan used to verify the user's plans.

return_code, reason_code - DB2 return code and reason code. See "CAF error codes and reason codes" in the IBM DB2 Application Programming and SQL Guide.

Corrective Action:Do the following:

If reason code is 00F30034 then the Control-M JCL Verify monitor is not authorized to use the Control-M JCL Verify plan. Ensure that Control-M JCL Verify was granted the appropriate DB2 authorizations on the subsystem identified in the preceding CTJUT6I message. See "Enabling DB2 support" in INCONTROL for z/OS Installation Guide: Installing.
Ensure that the Control-M JCL Verify DB2 plan was bound successfully during installation. If the plan name was changed in the BIND job from the default (CTJDB2) then specify the new name by using the DB2PLAN parameter in CTJPARM.

CTJUTDE Timestamp mismatch between the JVER DB2 plan and its DBRM.

Explanation:The Control-M JCL Verify plan (normally CTJDB2) is out of synchronization with its DBRM, and cannot be used.

Corrective Action:Ensure that the BIND job for the Control-M JCL Verify plan was successfully run, either during Control-M JCL Verify installation or after installing a PTF for the CTJDB2 module. See also message CTJUTCE above.

CTJUTEE Connect to DB2 subsystem `subsystem_id`failed, RC=`return_code`, RS=`reason_code`

Explanation:An error occurred connecting to the specified DB2 subsystem.

Corrective Action:Ensure that the specified DB2 subsystem is active on the system where the verification is performed. Review the accompanying messages: CTJUT4E, CTJUT5E, and/or CTJUTLE. If the error still cannot be determined, find the return and reason codes in "CAF error codes (RC) and reason codes (RS)" in the IBM DB2 Application Programming and SQL Guide.

CTJUTFE DB2 verification failed - error loading DB2 modules, RS=`reason_code`

Explanation:An error occurred while Control-M JCL Verify was attempting to load DB2 default modules from one of the user's STEPLIB or JOBLIB libraries, which seemed to contain the DSNHDECP member. However, the library or member are not valid.

RS=reason_code is one of the following:

ERNOALI - failed to load the DSNALI or DSNHLI2 modules
ERRALLO - failed to dynamically allocate a user's STEPLIB or JOBLIB library
ERROPEN - failed to open a user's STEPLIB or JOBLIB library
ERRFREE - failed to dynamically free a user's STEPLIB or JOBLIB library
ERRBLDL - failed to retrieve directory information from a user's STEPLIB or JOBLIB library
ERRECFM - a user's STEPLIB or JOBLIB library appears not to be a load module library
ERRSIZE - the DSNHDECP module from the user's STEPLIB or JOBLIB appears to be too large
ERRLOAD - failed to load the DSNHDECP module from the user's STEPLIB or JOBLIB library

Corrective Action:Ensure that the Control-M JCL Verify monitor STEPLIB includes the following DB2 libraries: SDSNLOAD and SDSNEXIT, or that these libraries are in LNKLST. If you intend to load the DB2 modules from your STEPLIB or JOBLIB libraries, then review your JCL and ensure that the SDSNEXIT library is included. Alternatively, specify the DB2 subsystem, to be used in the TSO DSN command or in the DB2SYS parameter, in the CTJPARM member.

CTJUTGE DB2 verification failed - insufficient storage

Explanation:DB2 verification failed because Control-M JCL Verify failed to obtain storage.

Corrective Action:Review Control-M JCL Verify monitor storage requirements. Retry the verification with an increased region size. If it fails again, contact BMC Customer Support.

CTJUTHE Verification failed for plan `plan_name`

Explanation:An error occurred while accessing the DB2 catalog for verifying the user's plan.

Corrective Action:Do the following:

See the accompanying message CTJUTKE for the specific SQL error code.
Verify that the DB2 subsystem is functioning properly.
Ensure that DB2 support was properly enabled in Control-M JCL Verify. For more information, see INCONTROL for z/OS Installation Guide: Installing.

CTJUTIE Error: Cannot process SYSTSIN file

Explanation:The file specified in the SYSTSIN DD statement cannot be read. The TSO batch step cannot be verified.

Corrective Action:Verify that the file specified by SYSTSIN is a readable sequential file or library member and that the record format is not UNDEFINED.

CTJUTJE Error occurred while processing an in-stream SYSTSIN file

Explanation:The message is issued when Control-M JCL Verify fails to read an in-stream TSO batch input file (//SYSTSIN DD *).

Corrective Action:Activate traces 88, 89, 370 on the Control-M JCL Verify monitor and retry verification. Then inactivate the traces, collect the SYSOUT files SYSTSPRT and DATRACE and the Control-M JCL Verify monitor system messages file and contact BMC Customer Support.

CTJUTKE SQL error code is `sql_error_code`

Explanation:This message details the error that occurred while trying to verify a DB2 plan.

Corrective Action:See message CTJUTHE.

CTJUTLE Subsystem `subsystem_id`is DEFINED

Explanation:This message might be issued for a DB2 connection failure. The specified DB2 subsystem is defined but cannot be contacted.

Corrective Action:Verify that the DB2 subsystem is operational on the system where Control-M JCL Verify monitor is executing.

CTJUTMI `echo`

Explanation:This message echoes the user's TSO batch input.

Corrective Action:No action is required.

CTJUTNE Verification failed - error loading SYSEXEC modules

Explanation:An error occurred while loading the processing modules from the SYSEXEC DDNAME.

Corrective Action:Ensure that the SYSEXEC DD card is included in the Control-M JCL Verify monitor procedure. For more information, see INCONTROL for z/OS Installation Guide: Installing.

CTJUTRE Invalid default DB2 subsystem name

Explanation:The default subsystem name does not adhere to DB2 specifications, such as not starting with a letter. The error is most likely to occur if the user's STEPLIB or JOBLIB libraries contain a member named DSNHDECP, which is not valid.

Corrective Action:Ensure that the member is valid, or remove it and use the DB2 link libraries (LNKLST), or specify a subsystem name in the TSO DSN command or in the DB2SYS parameter in CTJPARM.

CTJUTSE NOT ABLE TO LOCATE `program_name`IN DSNAME`library_name`

Explanation:The DB2 application program specified in the DSN command could not be found in the library specified in the RUN subcommand, where

program_name - program name as specified in the PROGRAM parameter
library_name - library name as specified in the LIBRARY parameter of the RUN subcommand.

Corrective Action:Ensure that the LIBRARY parameter of the RUN subcommand points to the correct library.

CTJUTTE NOT ABLE TO LOCATE `program_name`IN THE STANDARD SEARCH ORDER

Explanation:The DB2 application program specified in the DSN command could not be found in the job's STEPLIB, JOBLIB, or the system link libraries.

Corrective Action:Ensure that the program name is correct. If necessary, add the LIBRARY parameter to point to the library where the module resides.

CTJUV0I INFORMATION: verifying utility `autoimmune`

Explanation:The message is issued when Control-M JCL Verify starts verifying a utility program.

Corrective Action:No action is required.

CTJUV1I INFORMATION:verifying utility `util_name`ended RC=`return_code`.

Explanation:The message is issued when Control-M JCL Verify ended the utility program verification with a return code.

Corrective Action:If the return code is not 0, correct the error as specified in the previous messages.

CTJUV2I `jcl_statement_number`INFORMATION:`dd_name`is DUMMY.`util_name`messages will not be available.

Explanation:The message is issued when Control-M JCL Verify detects the utility DD messages' DD statement is DUMMY or NULLFILE and during the utility runtime the messages will not be listed.

Corrective Action:If this is correct, no change is needed. Otherwise, set the DD name to a SYSOUT or to a dataset.

CTJUV3I `jcl_statement_number`INFORMATION: `dd_name`is DUMMY.`util_name`will use defaults.

Explanation:The message is issued when Control-M JCL Verify detects the utility control statement input data set is DUMMY or NULLFILE. Therefore the utility will use the default input statements and parameters.

Corrective Action:If this is correct, no change is needed. Otherwise, set the DD name to a SYSIN or to a dataset with the required control statements.

CTJUV4S `util_name` ERROR: LOAD error `pgm_name`. Verifying is terminated.

Explanation:The message is issued when Control-M JCL Verify fails to load the utility program. The verification is terminated.

Control-M JCL Verify uses standard LOAD or LINK services to invoke the utility.

Corrective Action:Verify that the pgm_name exists in the verification JOBLIB, STEPLIB or one of the system LINKLIST libraries.

CTJUV5E `util_name` ERROR: Label error.

Explanation:The message is issued when Control-M JCL Verify detects that the previous statement contains an invalid label.

Corrective Action:Correct the label.

CTJUV6I `jcl_statement_number` INFORMATION:`dd_name - util_name`is empty. MEMBER=`member_name`DSN`dataset_name`

Explanation:The message is issued when Control-M JCL Verify read that the util_name and the dataset_name or member_name is empty.

Corrective Action:No action is required.

CTJUV7I `jcl_statement_number`INFORMATION:`dd_name` concatenation contains DUMMY DD. All the following concatenated data sets will be ignored.

Explanation:The message is issued when Control-M JCL Verify detects the utility control statement input datasets' concatenation contains a DUMMY statement or DSN=NULLFILE statement. Therefore the utility will ignore all the datasets following this statement.

Corrective Action:If this is correct, no change is needed. Otherwise, set the DD name to a SYSIN or to a dataset with the required control statements.

CTJUV8E `util_name` ERROR: Label error.

Explanation:The message is issued when Control-M JCL Verify detects that the previous statement contains a label that is too long.

Corrective Action:Correct the label.

CTJUV9E `util_name` ERROR: Null statement.

Explanation:The message is issued when Control-M JCL Verify detects that the previous statement does not contain any text besides the label.

Corrective Action:Delete the statement.

CTJUVAE `util_name` ERROR: Missing mandatory DD statement`dd_name`

Explanation:The message is issued when Control-M JCL Verify detects that a mandatory DD statement is missing in the STEP that calls the utility program util_name.

Corrective Action:Add the missing DD statement.

CTJUVBE `jcl_statement_number` ERROR:`string`is not allowed for DD statement`dd_name` by`util_name`

Explanation:The message is issued when Control-M JCL Verify detects that DD statement jcl_statement_number is a DUMMY, DYNAM, SYSOUT=, SUBSYS=, or DSN=NULLFILE, which are not allowed by the utility program.

Corrective Action:Correct the DD statement.

CTJUVCE `jcl_statement_number` ERROR: DISP=`disp`is not allowed for DD statement`dd_name`by`util_name`

Explanation:The message is issued when Control-M JCL Verify detects that DD statement jcl_statement_number has DISP=NEW or DISP=MOD, which are not allowed by the utility program.

Corrective Action:Correct the DD statement.

CTJUVDI INFORMATION: `util_name`found `number1`error and `number2`warning messages

Explanation:The message is issued when Control-M JCL Verify summarizes the number of error and warning messages found by the utility program.

Corrective Action:Correct the errors.

CTJUVEE `util_name` ERROR: Utility validation for current member is interrupted: time-out is reached

Explanation:The message is issued when Control-M JCL Verify, running in the IOA Online Monitor, detects that another user of the utility validation, such as SORT, is holding the resource for more than 10 seconds.

Corrective Action:Try to run again.

CTJUVFE `util_name` ERROR: DD `dd_name_1`and `dd_name_2`are missing or DUMMY. One of them is required for utility

Explanation:The message is issued when Control-M JCL Verify detects that the DD statements are missing, DUMMY, or NULLFILE.

Corrective Action:Add or correct the DD statements.

CTJUVGW `jcl_statement_number` WARNING: Data set cannot be accessed by`userid`- Utility `util_name`cannot be validated

Explanation:The message is issued when Control-M JCL Verify detects that the user performing the validation cannot access the file in the DD statement jcl_statement_number.

Corrective Action:Contact the security administrator to get the required authorization for accessing the file.

CTJUVHE `jcl_statement_number` ERROR: member`member_name`does not exist. Utility`util_name`cannot be validated

Explanation:The message is issued when Control-M JCL Verify detects that the member in the DD statement jcl_statement_number does not exist.

Corrective Action:Correct the DD statement.

CTJUVIEFile does not exist or is invalid. Utility`utility_name`cannot be validated DSN=`dataset_name`

Explanation:The variable term, utility_name, refers to the name of the utility being verified. For utility SYSIN or SYSTSIN, one of the following errors occurred:

The file cannot be found
The file is not sequential or not a member in a library

Corrective Action:Correct the DD statement.

CTJUVJE `util_name` ERROR: Invalid keyword `string`

Explanation:The message is issued when Control-M JCL Verify detects that the keyword keyword is not valid.

Corrective Action:Correct the keyword.

CTJUVKI `util_name` INFORMATION: duplicated keyword `keyword` - keyword is ignored

Explanation:The message is issued when Control-M JCL Verify detects that keyword keyword appears more than once in the statement or parameter list of the utility. The utility uses the first keyword and ignores all its duplications.

Corrective Action:Remove all the unnecessary keywords.

CTJUVLE `util_name` ERROR: Invalid data in keyword `string`

Explanation:The message is issued when Control-M JCL Verify detects that keyword keyword has invalid data.

Corrective Action:Correct the data in the keyword.

CTJUVNE `util_name` ERROR: The above`string`statement is not valid.

Explanation:The message is issued when Control-M JCL Verify detects that the statement above contains an invalid keyword.

Corrective Action:Correct the statement using a valid keyword.

CTJUVOE `util_name` ERROR: A control statement COPY, COPYGRP, COPYMOD or ALTERMOD must be before the above statement

Explanation:The message is issued when Control-M JCL Verify detects that statement above (INDD, SELECT or EXCLUDE) requires a copy or ALTERMOD statement before it.

Corrective Action:Add the missing control statement or remove the existing statement above.

CTJUVPI `util_name` INFORMATION: Using PARM= with a copy option. SYSIN is ignored.

Explanation:The message is issued when Control-M JCL Verify detects that PARM= in the EXEC JCL statement contains the copy option; therefore the SYSIN statement is ignored.

Corrective Action:No action is required.

CTJUVQI `util_name` INFORMATION: DD statement in the SYSIN concatenation or one of the SYSIN files is a DUMMY DD statement or DSN=NULLFILE. All the following DD statements are ignored.

Explanation:The message is issued when Control-M JCL Verify detects that one of the DD statements in the SYSIN concatenation or in one the of SYSIN files is a DUMMY or DSN=NULLFILE. All the following DD statements are ignored.

Corrective Action:No action is required.

CTJUVRE `util_name` ERROR: Unknown Control statement`statement` - Statement is ignored

Explanation:The message is issued when Control-M JCL Verify detects an unknown control statement.

Corrective Action:Correct the DD statement.

CTJUVSE `util_name` ERROR: Missing required DD`DD`for`command_type`

Explanation:The message is issued when Control-M JCL Verify detects a command_type or operand that needs a DD statement.

Corrective Action:Add the missing DD statement.

CTJUVTE `util_name` ERROR: After standalone `command`command, the next COPY command is ignored

Explanation:The message is issued when Control-M JCL Verify detects a standalone command, therefore the next COPY command is ignored.

Corrective Action:No action is required.

CTJUVUE `util_name` ERROR: After the previous statement, all standalone COPY type commands are ignored

Explanation:The message is issued when Control-M JCL Verify detects that all the standalone COPY commands will be rejected, as a result of the previous control statement.

Corrective Action:Remove the standalone commands.

CTJUVVE `util_name` ERROR: Unknown Operand`Opr` - Statement is ignored

Explanation:The message is issued when Control-M JCL Verify detects an unknown Opr.

Corrective Action:Correct the operand statement.

CTJUVWE `util_name` ERROR: Null Operand `Opr` - Statement is ignored

Explanation:The message is issued when Control-M JCL Verify detects a NULL operand.

Corrective Action:Correct the operand statement.

CTJUVXE `util_name` ERROR: The above statement has an invalid continuation. Statement is ignored.

Explanation:The message is issued when Control-M JCL Verify detects an invalid continuation, and therefore the statement is ignored.

Corrective Action:Correct the continuation statement.

CTJUVYI `util_name` Validate SYSIN`type/num`contains `num` records from `src`

Explanation:The message is issued as a heading summary of the SYSIN type, with the number of records, and the source of the records that Control-M JCL Verify has checked.

Corrective Action:No action is required.

CTJUVZ`s util_name echo`

Explanation:The message is issued as an echo of the statement checked by Control-M JCL Verify. The suffix (s) of the message, E, I, or W, describes the its severity.

Note: the suffixes of the message are:

E - Error
I - Information
W - Warning.

Corrective Action:If the message is CTJUVZI, no action is required. Otherwise perform the required process to correct the error or ignore the warning message.

CTJUW0I `util_name` INFORMATION: IEBCOPY will use minimum block size of`minblk`and maximum block size of `maxblk`.

Explanation:The message is issued when Control-M JCL Verify verifies a COPYMOD command that has MINBLK and MAXBLK. The message indicates the minimum and maximum block sizes that the COPYMOD will use during run time.

Corrective Action:No action is required.

CTJUW1W `util_name` WARNING: MAXBLK value is too small`maxblk`. IEBCOPY will use the default of 1024

Explanation:The message is issued when Control-M JCL Verify detects that the COPYMOD command has a MAXBLK value that is less than 1024.

Corrective Action:Correct the MAXBLK value.

CTJUW2W `util_name` WARNING: MAXBLK value (`maxblk`) is above the limit. IEBCOPY will use the optimum maximum block size for the device.

Explanation:The message is issued when Control-M JCL Verify detects that the COPYMOD command has a MAXBLK value that is higher than the maximum block size for the device.

Corrective Action:Correct the MAXBLK value.

CTJUW3E `util_name` ERROR: Operand`Opr`is not valid in `statement`statement.

Explanation:The message is issued when Control-M JCL Verify detects that the operand in the command statement is not valid.

Corrective Action:Remove the operand.

CTJUW4E `util_name` ERROR: Statement EXCLUDE is not supported by COPYGRP

Explanation:The message is issued when Control-M JCL Verify detects an EXCLUDE statement together with COPYGRP.

Corrective Action:Remove the EXCLUDE statement.

CTJUW5I `util_name` IEBCOPY will use minimum block size of`minblk`and the optimum maximum block size for the device.

Explanation:The message is issued when Control-M JCL Verify verifies a COPYMOD command that has MINBLK. The message indicates the minimum and maximum block sizes that the COPYMOD will use during run time.

Corrective Action:No action is required.

CTJUW6W `util_name` WARNING: MAXBLK `maxblk`is lower than MINBLK `minblk`. MINBLK will be use as MAXBLK.

Explanation:The message is issued when Control-M JCL Verify verifies a COPYMOD command that has a MAXBLK value that is smaller than the MINBLK value.

Corrective Action:Correct the MAXBLK value.

CTJUW7W `util_name` WARNING: Dataset DD`DD`does not exist. DSN=`dataset_name`.

Explanation:The message is issued when Control-M JCL Verify detects that a required file, specified in a DD statement for the COPY or ALTERMOD command, does not exist.

Corrective Action:Correct the file name.

CTJUW8E `jcl_statement_number` ERROR: RECFM 'U' required with`command`for ddname`ddname`

Explanation:The message is issued when Control-M JCL Verify detects the use of DD with RECFM, different from 'U' with control statement ALTERMOD or COPYMOD.

Corrective Action:Correct the DD statement.

CTJUW9E `util_name` ERROR: Concatenation is not allowed DD `ddname`.

Explanation:The message is issued when Control-M JCL Verify detects concatenation while it is not allowed.

Corrective Action:Delete the concatenation.

CTJUWAE `util_name` ERROR: DSORG 'PO' required with ALTERMOD for ddname `ddname`.

Explanation:The message is issued when Control-M JCL Verify detects that the DD is not a PDS.

Corrective Action:Correct the DD name.

CTJUWBE `util_name` ERROR: The above `statement` has unequal parentheses.

Explanation:The message is issued when Control-M JCL Verify detects that statement has unequal parentheses.

Corrective Action:Correct the statement.

CTJUWCE `util_name` ERROR: No mixing of SELECT and EXCLUDE in same copy step

Explanation:The message is issued when Control-M JCL Verify detects that SELECT and EXCLUDE are mixed in same copy command.

Corrective Action:Correct the statement.

CTJUWDW `util_name` WARNING: Compress is ignored when copy step with SELECT

Explanation:The message is issued when Control-M JCL Verify detects a compress command in a copy step, which contains SELECT.

Corrective Action:Correct the statement.

CTJUWEE `util_name` ERROR: RENAME and REPLACE are not allowed in EXCLUDE command

Explanation:The message is issued when Control-M JCL Verify detects RENAME and REPLACE in an EXCLUDE command.

Corrective Action:Correct the statement.

CTJUWFW `util_name` WARNING: Found duplicate member name`member_name` - member will not be copied.

Explanation:The message is issued when Control-M JCL Verify detects a duplicated member name member_name.

Corrective Action:Remove the duplicated members.

CTJUWGW `util_name` WARNING: Found old member name `member_name`and new member name are the same. Member will not be copied.

Explanation:The message is issued when Control-M JCL Verify detects that the old member name and the new member name in the SELECT statement are the same. Therefore the member will not be copied.

Corrective Action:Change the old or the new member name.

CTJUWHE `util_name` ERROR: Invalid member name `member_name`

Explanation:The message is issued when Control-M JCL Verify detects invalid member_name name.

Corrective Action:Correct the member name.

CTJUWIE `util_name` ERROR: Statement `statement`has no operand.

Explanation:The message is issued when Control-M JCL Verify detects a statement without an operand.

Corrective Action:Correct the statement.

CTJUWJE `util_name` Duplicate keyword `keyword`

Explanation:The message is issued when Control-M JCL Verify detects a duplicated keyword.

Corrective Action:Remove the duplicated keyword.

CTJUWKE `util_name` ERROR: Missing mandatory keyword`keyword` in the above statement

Explanation:The message is issued when Control-M JCL Verify detects that a mandatory keyword is missing in the above statement.

Corrective Action:Correct the statement.

CTJUWLE `util_name` ERROR: INVALID REPLACE SPECIFIED - Statement is ignored

Explanation:The message is issued when Control-M JCL Verify detects that a member contains an invalid REPLACE (R) operator.

Corrective Action:Change the REPLACE operator to "R".

CTJUWME `util_name` ERROR: REPLACE is not allowed in`command`

Explanation:The message is issued when Control-M JCL Verify detects that a member contains a REPLACE (R) operator as part of ALTERGRP or COPYGRP.

Corrective Action:Remove the REPLACE operator.

CTJUWNE `util_name` ERROR: COPYMOD - INDD can not equal OUTDD. DDNAMEs are `dd_name`

Explanation:The message is issued when Control-M JCL Verify detects that that in the COPYMOD statement, the INDD and OUTDD are the same DD name.

Corrective Action:Change the INDD or OUTDD.

CTJUWOE `util_name` ERROR: COPYMOD - INDD`in_dd_name`and OUTDD`out_dd_name` have the same DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that in the COPYMOD statement, the INDD and OUTDD use the same dataset.

Corrective Action:Change the DSN (dataset name) INDD or OUTDD.

CTJUWPE `util_name` ERROR: `return_code` - `reason_code`DSORG is not valid. File must have DSORG=`dsorg_type`

Explanation:The message is issued when Control-M JCL Verify detects that the DDNAME's DSORG is not valid for the command performed by the utility.

Corrective Action:Correct the data set with the required DSORG specification.

CTJUWQE `jcl_statement_number`ERROR:`util_name` - `dd_name`file is PDS or PDSE but member is missing. DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the file is a PDS or PDSE but no member name was specified in the DSN=dataset_name or the member related statement or keyword is missing in the util_name.

Corrective Action:Add the member name in the dataset_name or the util_name statement

CTJUWRE `jcl_statement_number`ERROR: `command - ddname`RECFM `recfm`is not valid or missing.

Explanation:The message is issued when Control-M JCL Verify either detects that the ddname's RECFM is not valid for this utility, or that the file is a DUMMY file and the RECFM is missing.

Corrective Action:Either correct the DSN so that it has a valid RECFM, or for a DUMMY file, ensure that it has a valid RECFM.

CTJUWSE `util_name` ERROR: RECFM INCOMPATIBLE - INDD `in_dd_name` RECFM `recfm` OUTDD `out_dd_name` RECFM `recfm`

Explanation:The message is issued when Control-M JCL Verify detects that the INDD and OUTDD attributes are incompatible.

Corrective Action:Correct the files attributes.

CTJUWTE `jcl_statement_number`ERROR: RECORD length `value` inconsistent with BLOCK size `value` for RECFM=`record_format`

Explanation:The message is issued when Control-M JCL Verify detects that the file jcl_statement_number LRECL value and the BLKSIZE value are incompatible with the record format's rule. This can be lead to I/O errors (ABEND) when the utility writes to the file.

The values for LRECL, BLKSIZE, or RECFM can be specified in the JCL statement or copied from the INDD file.

Corrective Action:Correct the files attributes.

CTJUWUE `util_name` ERROR: Multiple INDD invalid for `command`

Explanation:The message is issued when Control-M JCL Verify detects that there are multiple INDDs, which are invalid for the same command.

Corrective Action:Remove the multiple INDDs, or change them so each INDD is part of a different COPYGRP or COPYGROUP statement.

CTJUWVI `util_name` INFORMATION: `operand`is not a PDS. DD=`ddname`DSN`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the file is not a PDS or PDSE. If the file is an INDD, IEBCOPY performs a restore. Otherwise IEBCOPY performs a backup.

Note: IEBCOPY might ignore the DCB parameters in the JCL or file, and instead determine the attributes using the process and file contents.

Corrective Action:No action is required.

CTJUWWI `util_name`INFORMATION: OUTPUT DATASET RECFM/LRECL/BLKSIZE COPIED FROM INPUT DATASET

Explanation:The message is issued when Control-M JCL Verify detects that the DCB attributes of the OUTPUT file are not all set, and IEBCOPY will complete the attributes from the first input file.

Corrective Action:If the DCB attributes are not specified as required, set the RECFM, LRECL, or BLKSIZE values in the JCL definition of the OUTPUT file.

CTJUWXI `jcl_statement_number`INFORMATION: `command`for file type`type` is not relevant

Explanation:The message is issued when Control-M JCL Verify detects that command is for a file type that is not relevant.

Corrective Action:No action is required.

CTJUWYE `util_name`ERROR: Invalid new member name `string`

Explanation:Explanation: The message is issued when Control-M JCL Verify detects that the new member name string in the MEMBER operand is invalid.

Corrective Action:Correct the member name.

CTJUWZI `jcl_statement_number`INFORMATION: File Access(FA), File Verification(FV) or Module Existence(ME) disabled. Utility cannot be verified.

Explanation:The message is issued when Control-M JCL Verify detects that one one or more of the following functions, File Access (FA), File Verification (FV), and Module Existence (FE), which are required for the utility validation, are not active. Therefore, the utility cannot be validated.

Corrective Action:Ensure that the IOA Security is installed and active, and then set the parameters as follows: FA=Y, FV=Y, and ME=Y.

CTJUX0E `jcl_statement_number`ERROR: Member masking is not supported by `statement`

statement

Explanation:The message is issued when Control-M JCL Verify detects that MEMBER contains a masking pattern. MEMBER masking is supported only by COPYGROUP, which was introduced in IEBCOPY in z/OS V2.1.

Corrective Action:Correct the member.

CTJUX1E `jcl_statement_number`ERROR: COPYGROUP supports EXCLUDE only after SELECT statement

Explanation:The message is issued when Control-M JCL Verify detects that an EXCLUDE statement occurs before a SELECT statement.

Corrective Action:Correct the statement.

CTJUX2E `jcl_statement_number`ERROR: NEW NAME is not allowed with member masking. MEMBER=`member_name`

Explanation:The message is issued when Control-M JCL Verify detects that MEMBER contains a masking patttern. MEMBER masking is supported only by COPYGROUP, which was introduced in IEBCOPY in z/OS V2.1.

Corrective Action:Correct the member name.

CTJUX3W `util_name` WARNING:`operand`request `number-1`using `number-2`

Explanation:The message is issued when Control-M JCL Verify verifies a COPYMOD command that has a MAXBLK or MINBLK, which is not set according to the assignment in the statement.

The reasons might be:

MAXBLK is lower than the MINBLK. The MINBLK set as the MAXBLK.
The file BLOCK SIZE is lower than the MAXBLK. MAXBLK is set to the file block size.
The OUTDD library BLOCK SIZE is zero. IEBCOPY uses the INDD BLOCK SIZE.

Note: If Control-M JCL Verify cannot determine the OUTDD BLOCK SIZE, the maximum value allowed is 32760.

Corrective Action:Adjust the MAXBLK or MINBLK values.

CTJUX4I `util_name`INFORMATION:`operand`value `number1`is above the limit. IEBCOPY will use`number2`

Explanation:The message is issued when Control-M JCL Verify detects COPYMOD command has operand (MAXBLK or MINBLK) that is higher than maximum block allowed (32760).

Corrective Action:Correct the MAXBLK value.

CTJUX5I `util_name`INFORMATION: `operand`value `number1`is below the limit. IEBCOPY will use`number2`

Explanation:The message is issued when Control-M JCL Verify detects COPYMOD command has operand (MAXBLK or MINBLK) that is lower than minimum block size allowed (1024).

Corrective Action:Correct the MINBLK value.

CTJUX6E `util_name` ERROR: DD `ddname`DSN is a PDS with`member`, but this member does not exist.

Explanation:The message is issued when Control-M JCL Verify detects that the utility refers to a DD with a DSN referencing a PDS or PDS/E with the member member. However, the member member does not exist, and as result, the utility might fail because of an OPEN error.

Corrective Action:Correct JCL if necessary.

CTJUX7W `util_name`WARNING: The following FILE cannot be read. Member`member`DSN=`dataset_name`

Explanation:The message is issued when Control-M JCL Verify detects that the file cannot be read. This problem might occur if the file validation is not completed.

Corrective Action:Turn on the dataset verification or check why the file cannot be read and correct it. Then perform the verification again.

CTJUX8I `util_nameddname` is not available. Utility cannot be validated.

Explanation:A utility control statement file (SYSIN, SYSTSIN or DFSPARM DD) specifies DISP=SHR, but the file was created in a previous step. Since it does not yet exist it cannot be verified.

Corrective Action:No action is required.

Messages CTJV00 through CTJVxx

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

CTJV00E Rule=`rule` Table=`table` Command=`cmd` RC=`return_code` RS=`reason_code`

Explanation:DO cmd in the given rule failed due to a syntax error.

Corrective Action:See following message CTJV03I which explains the error and correct the DO command accordingly.

CTJV01I Text= `text`

Explanation:The message shows the text of the command that failed.

Corrective Action:No action is required.

CTJV02S Rule=`rule` Table=`table` Command=`cmd` RC=`return_code` RS=`reason_code`

Explanation:Command cmd in Rule rule Table table failed with RC return_code RS reason_code.

Corrective Action:Contact BMC support.

CTJV03E `explanation`

Explanation:The message shows the text of the command that failed.

Corrective Action:Use this explanation to troubleshoot the command.

CTJV03I `explanation`

Explanation:The message shows the text of the command that failed.

Corrective Action:No action is required.

CTJV04E INVALID SYNTAX - VARIABLE NAME IS TOO SHORT

CTM messages

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages CTM0 through CTM0xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM001I CTMSLC STARTED

Explanation: This information message indicates that the CTMSLC utility, which enables you to remove old job scheduling definitions from the schedule library, has started.

Corrective Action: No action is required.

CTM005S OPEN OF DDNAME `ddName` FAILED

Explanation: The automatic zap application program failed to open the specified DD name. Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement does not exist.

The program stops execution with a condition code of 08.

Corrective Action: The JCL was probably modified incorrectly. Restore the original JCL job stream, as follows:

Using the documentation provided as part of the IOA Monthly Maintenance Upgrade system, transfer the JCL job stream from the diskette to the mainframe.
Modify the JCL as specified in the documentation.
Submit the job.

You may run the JCL job stream as often as necessary. If a zap is already applied, it is bypassed.

CTM008S SORT FAILED RC = `rc`

Explanation: Internal sort failed in the CTMRFLW or CTMRAFL utility. The CTMRFLW or CTMRAFL utility activates the regular sort program of the installation.

In this message, rc is a return code specific to the sort program.

The program stops executing with a condition code of 08.

Corrective Action: Check the sort program literature for the meaning of the sort return code (rc), and correct the JCL for the job accordingly.

CTM00AI NO JOBS WERE DELETED BY LIBRARY CLEANUP PROCESS

Explanation: The CTMSLC utility completed successfully without deleting any job scheduling definitions from the scheduling library.

The utility terminates with a return code of 4.

Corrective Action: No action is necessary.

CTM011E ONLINE MONITOR NOT ACTIVE, IOA SESSION NOT ESTABLISHED RC= `rc`

Explanation: An error was detected while attempting to start an IOA session. The IOA Online interface uses the services of an online monitor that supplies all IOA online services. If no IOA Online monitor is active, the session cannot be established.

Corrective Action: The user response depends on the value of the return code (rc). The following table displays possible values for rc, together with their explanations and the appropriate user action.

Return Code	Explanation	User Action
1	A valid subsystem name (the SSNAME parameter) was not specified in the IOAXPRM member.	Either correct the value specified for the SSNAME parameter in the IOAXPRM member, or define an entry in the IEASSN00 member of the SYS1.PARMLIB library that corresponds to the SSNAME parameter.
2	No IOA Online monitor was started since the last IPL.	Activate an IOA Online monitor.
3	No IOA Online monitor was started since the last IPL.	Activate an IOA Online monitor.
4	The IOA Online monitor specified for the current transaction in the IOAXPRM member is not active.	Activate the IOA Online monitor defined for this transaction.
5	No IOA Online monitor was defined for the current transaction in the IOAXPRM member.	Define an IOA Online monitor for the current transaction in the IOAXPRM member (the SSNAME parameter).

CTM012E MAXIMUM IOA SESSIONS EXCEEDED, PLEASE TRY AGAIN LATER

Explanation: The number of active online sessions permitted reached the maximum. The MAXSESS parameter in IOAXPRM defines the maximum number of sessions that can be active at a certain moment. The CICS interface determined that this maximum was reached for all the active Online monitors.

The session is not established.

Corrective Action: Do one of the following:

Wait until other users terminate their sessions.
Open one more Online monitor and enter the transaction name again.
Increase the value of the MAXSESS parameter in IOAXPRM, and increase the region size of the Online monitor correspondingly.

CTM013I IOA SESSION ENDED RC=`rc`

Explanation: This information message indicates that the IOA Online monitor ended the session normally due to a user request, or abnormally due to a problem in the IOA Online monitor. The session is terminated.

Return Code	Explanation	User Action
0	The session was terminated in response to a user request.	No action is required.
1	The IOA Online monitor serving the current transaction was terminated.	Reactivate the IOA Online monitor if required.
2	The user did not press Enter within the time specified in the TIMEOUT parameter in the IOAXPRM member. No action was performed in this session during the specified amount of time.	Log on again if required. The IOA Online monitor does not need to be reactivated.
4	The session was terminated by pressing an attention key (PA1/PA2).	Log on again if required. The IOA Online monitor does not need to be reactivated.

CTM014E IOA SESSION INITIALIZATION FAILED RC= `rc`

Explanation: Initialization of an IOA online session failed. The reason for session termination is indicated by the return code included in the message.

Possible return code values, with their explanations, are displayed in the following table.

Return Code	Explanation
01	Internal process communication failed.
02	An internal error occurred.
04	Load of the CTMSUSIE module failed.
05	An IPL occurred since initialization.

The connection between the TP monitor and IOAOMON is terminated.

Corrective Action: If the problem persists, or the return code is 02, contact BMC Customer Support.

CTM015E INTERNAL ERROR, IOA SESSION TERMINATED, RC= `abCode`

Explanation: The IOA CICS interface transaction abended due to either an internal error or storage violations caused by other transactions.

In this message, abCode is the CICS abend code.

The session is terminated.

Corrective Action: Use standard CICS problem determination techniques to determine the cause of the abend. If no storage violations produced by other transactions are found, contact BMC Customer Support.

CTM016E ONLINE MONITOR NOT ACTIVE, IOA SESSION TERMINATED. RC= `rc`

Explanation: The user sent a command to the IOA online monitor when the monitor was not active. The connection between the TP monitor and IOAOMON is terminated.

Return Code	Explanation	User Action
01	The IOA Online Monitor terminated during user action.	Restart the IOA Online Monitor, and log on again.
02	The IOA Online Monitor bounced: was terminated and restarted.	Log on again, if required.
03	The IOA Online Monitor terminated	Restart the IOA Online Monitor, and log on again.
04	The IOA Online Monitor terminated	Restart the IOA Online Monitor, and log on again.
05	The IOA Online Monitor terminated	Restart the IOA Online Monitor, and log on again.

CTM017E LOAD OF IOAX037 FAILED. IOA SESSION TERMINATED

Explanation: Loading of IOA User Exit 37 failed.

Possible causes are:

The IOA Load library is not in the load modules search list.
There is insufficient memory to load the exit.
The IOAX037 module does not exist in the Load library.
The IOA Load library has been updated while you were working and the position of the IOAX037 module has changed.

The function requested is terminated.

Corrective Action: Check the system log for additional messages that clarify the situation. Try one of the following:

If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
If the loading failed because of lack of memory: for batch jobs, increase the REGION size; for TSO, try to logon again using a larger SIZE parameter. If you are using many IOA screens concurrently, try to exit a few using the END command. This can release memory which is used by the screens.
Add the IOAX037 module to the Load library.
If the Load library has been modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again.

CTM018E INSTALLATION ERROR. DFSLI000 IS NOT LINKED TO IOAIMS. IOA SESSION TERMINATED.

Explanation: The IMS routine is not linked to the IOAIMS program of the IOA-IMS online interface.

IOA session terminates.

Corrective Action: For more information, see the description of the Link IMS routine in the IOA chapter of the INCONTROL for z/OS Installation Guide.

CTM01AE PROBLEM WITH USER `userId` IN ASID `asId`, ALESERV R.C. IS `rc`

Explanation: The Online monitor failed to invoke the ALESERV MVS service, and returned a return code of rc. The specified user in the asId address space may not be responding.

Corrective Action: Use the DUMP command to cancel the Online monitor, and send the dump to BMC Customer Support for investigation.

CTM01BE PROBLEM WITH USER `userId` IN ASID `asId`, ECB IS NOT MODIFIABLE

Explanation: The Online monitor failed to post the ECB in the CICS address space for the specified user in the asId address space, because the ECB resides in a non-modifiable area.

Corrective Action: Use the DUMP command to cancel the Online monitor, and send the dump to BMC Customer Support for investigation.

CTM01CE PROBLEM WITH USER `userId` IN ASID `asId` A.S. SWAPPED OUT MORE THAN 1 MIN

Explanation: The Online monitor failed to post the ECB in the CICS address space for the specified user in the asId address space, because the CICS address space was swapped out for more than 1 minute.

Corrective Action: Check why the CICS address space was swapped out. BMC highly recommends defining the CICS address space as non-swappable.

CTM01DE PROBLEM WITH USER `userId` IN ASID `asId`, ASCB DO NOT MATCH

Explanation: The Online monitor failed to post the ECB in the CICS address space for the specified user in the asId address space, because the CICS address space was brought down.

Corrective Action: No action is necessary.

CTM025I CTMSLC ENDED

Explanation: This information message indicates that the CTMSLC utility ended normally. The CTMSLC utility enables you to remove old job scheduling definitions from the schedule library.

Corrective Action: No action is required.

CTM027S UNABLE TO LOAD MODULE `modName`

Explanation: Loading of the modName module failed.

Possible causes are:

The IOA Load library is not in the load modules search list.
There is not enough memory to load the module.
The modName module does not exist in the Load library.
The IOA Load library has been updated while you were working and the position of the modName module has changed.

The function requested is terminated.

Corrective Action: Look on the system log for additional messages related to the problem.

Try one of the following:

If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
If the loading failed because of lack of memory do one of the following:
- For batch jobs, increase the REGION size.
- For TSO, try to logon again using a larger SIZE parameter.
- If you are using many IOA screens concurrently, try to exit a few using the END command. This can release memory which is used by the screens.
If the Load library has been modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again. If the IOA Load library is in the Linklist, a refresh to the LLA is needed.

CTM030I TAPE PULL UTILITY IS SUBMITTING JOBS WITH TYPRUN=SCAN

Explanation:Highlighted, unrollable message.

The Tape Pull List is currently submitting jobs with TYPRUN set to SCAN. To perform JCL checking, the Tape Pull utility submits jobs through the internal reader with the TYPRUN parameter set to SCAN. It then reads the sysout of the jobs that are submitted, and deletes the sysout from the spool.

Corrective Action: No action is required.

CTM038I TAPE PULL LIST UTILITY STARTED

Explanation: The Tape Pull List utility has started.

Corrective Action: No action is required.

CTM039I TAPE PULL LIST UTILITY ENDED

Explanation: The Tape Pull List utility has ended.

Corrective Action: No action is required.

CTM041I NEW ACTIVE JOBS FILE SUCCESSFULLY CREATED

Explanation: This information message indicates that the CTMCAJF utility has successfully copied the Active Jobs file.

Corrective Action: No action is required.

CTM041S SMFWTM RETURNED RC= 4 - SMF RECORD TOO LONG

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but the record could not fit completely in an SMF data set.

The CTDX006 Control-D Exit has been modified, but an incorrect value was moved to the SMFLEN field (DSECT CTDUSMF). This field contains the length of the SMF record.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Correct the problem in CTDX006, assemble and link-edit this exit, and bring down Control-D. When Control-D is brought up again, SMF recording will resume.

CTM042S SMFWTM RETURNED RC= 8 - SMF RECORD TOO SHORT

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record which is less than 18 characters long.

The CTDX006 Control-D Exit has been modified, but an incorrect value has been moved to the SMFLEN field (DSECT CTDUSMF). This field contains the length of the SMF record.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the Control-D log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Correct the problem in CTDX006, assemble and link-edit this exit, and bring down Control-D. When Control-D is brought up again, SMF recording will resume.

CTM043S REQUIRED OPERATION CANNOT BE PERFORMED BECAUSE THE Control-M MONITOR IS ACTIVE

Explanation: An attempt has been made to run the CTMCAJF utility while the Control-M monitor is active. Maintenance of the Control-M Active Jobs file can be performed only when the Control-M monitor is not active.

The CTMCAJF utility determines whether a Control-M monitor is active by using the enqueue management mechanism to enquire whether the QNAME of the monitor is in use. If the QNAME is not in use, the monitor is down.

The utility terminates with a condition code of 08.

Corrective Action: Shut down the Control-M monitor. If you are using the COPY function, read the instructions for the utility in the Control-M for z/OS User Guide.

CTM044S SMFWTM RETURNED RC= 20 - SMF EXIT IEFU83 SUPPRESSED THE RECORD

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but the IEFU83 SMF exit suppressed the record.

Corrective Action: Correct the IEFU83 SMF exit to allow Control-D to write SMF records. When Control-D is brought up again, SMF records will resume.

CTM045S SMFWTM RETURNED RC= 24 - THE SMF FILES ARE FULL

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but the SMF files are full.

The SMF record is not written, but Control-D continues processing. Control-D will write the SMF049I message to the IOA Log file. This log message is a replacement for SMF recording, and can be entered into SMF later.

Control-D will keep attempting to write to the SMF file. If the SMF file is still full, the SMF049I message will be written to the log.

Please note that Control-D does not have to be taken down. As soon as room is found on an SMF file, SMF recording will take place automatically.

Corrective Action: The operator should clear SMF files according to the conventions of the site. As soon as this is done, Control-D will automatically continue with SMF recording.

CTM046S BLDL/LOAD FAILED FOR THE MODULE " `modName` "

Explanation:This is one of two messages with the same ID, but different text.

Loading of the modName module failed.

Possible causes are:

The IOA Load library is not in the load modules search list (STEPLIB + Linklist).
There is insufficient memory.
There is some other system-oriented reason which may be found in the syslog.

Execution might stop.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTM046S INTERNAL PROBLEM IN MVS. SMF RECORD NOT WRITTEN

Explanation:This is one of two messages with the same ID, but different text.

Highlighted, unrollable message.

Control-D attempted to write an SMF record, but there is an internal problem in MVS.

This is due to one of the following return codes from MVS:

Return Code	Explanation
26	Record is not currently being recorded.
40	Buffer storage caused data to be lost.
44	SVC 83 unable to establish recovery.

For information about the return code, see message SMF047S.

Corrective Action: Call the system programmer. After the problem is fixed by the system programmer, bring down Control-D. When Control-D is brought up again, SMF recording will resume.

CTM047S RC= `rc` RECEIVED FROM MACRO SMFWTM

Explanation:Highlighted, unrollable message.

Control-D is unable to write SMF records.

Possible causes are:

The SMF046S message was issued. This message specifies the RC returned by SMF.
An unknown return code was issued by SMF. This message specifies the RC returned by SMF.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the SMF049I message is written to the Control-D log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Call your INCONTROL administrator.

CTM049I NEW HISTORY JOBS FILE SUCCESSFULLY CREATED

Explanation: This information message indicates that the CTMHCOP utility successfully created a new History Jobs file from the old one.

Corrective Action: No action is required.

CTM050I NEW TIME ZONE DEFINITIONS SUCCESSFULY LOADED

Explanation: This information message indicates that when the Control-M monitor was started, newly specified Time Zone definitions were successfully loaded.

Corrective Action: No action is required.

CTM053S OPEN OF MANUAL CONDS SYNC FILE FAILED. DDNAME "DANSINC"

Explanation: An attempt to open the Manual Conditions Synchronization file failed (the DANSINC DD statement).

Possible causes are:

The DANSINC DD statement is missing.
The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is a different version or for a different IOA installation.

Corrective Action: Correct the JCL for the job or the allocations for the CLIST.

CTM054I LOADING OF IOA MANUAL CONDITIONS FILE STARTED

Explanation: This information message indicates that loading of the IOA Manual Conditions file has started.

The IOALDNRS utility will start collecting the Manual Conditions from the job orders on the Active Jobs file. These are all the prerequisite conditions which are suspected of requiring manual confirmation.

Corrective Action: No action is required.

CTM055I LOADING OF IOA MANUAL CONDITIONS FILE ENDED

Explanation: This information message indicates that the IOA Manual Conditions file has finished loading.

The Manual Conditions file currently contains all the missing conditions for the job orders on the Active Jobs file.

Corrective Action: No action is required.

CTM056S IOA MANUAL CONDITIONS FILE WAS NOT LOADED

Explanation: The IOA Manual Conditions file was not loaded (the IOALDNRS utility). The utility output should contain a prior message that describes the cause of the problem, or whether the AJF (if Control-M is in use) and the AMF (if Control-D is in use) files are empty.

Corrective Action: Correct the problem and rerun the utility.

CTM057S OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED - DDNAME "DACKPT"

Explanation: Open of Control-M Active Jobs file failed (the DACKPT DD statement).

The error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List and is due to one of the following:

The DACKPT DD statement is missing.
The data set described by the DACKPT DD statement is not the Control-M Active Jobs file.
The data set described by the DACKPT DD statement is the Control-M Active Jobs file, but of another Control-M monitor, or of a different version of Control-M.

The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

CTM058E FILE ALLOCATED TO DDNAME "DACKPT" IS NOT CONTROL-M ACTIVE JOBS FILE

Explanation: The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.

This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List.

Possible causes include:

The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.
The file allocated to the DACKPT DD statement is the Control-M Active Jobs file, but it is of a different version or of a different Control-M monitor.

The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file will not be loaded.

Corrective Action: Correct the JCL for the job.

CTM059E ACTIVE JOBS FILE IS BEING FORMATTED. PLEASE TRY AGAIN LATER

Explanation: The Active Jobs file is currently being formatted, which indicates that the New Day procedure is running.

This error message is issued by the IOALDNRS utility (used to load or create the Manual Conditions List), which terminates with a condition code of 08. The IOA Manual Conditions file is not be loaded.

Corrective Action: Try again later.

If the Control-D and Control-M New Day procedures start at the same time, you need to ensure that both procedures finish before running the IOALDNRS utility or the CTDLDNRS step. Use one of the following options:

Set Control-D New Day time (DAYTIMED) long enough after Control-M New Day time (DAYTIME) to ensure that Control-M New Day is ended.
Remove the CTDLDNRS step from the CTDNDAY procedure. Run the IOALDNRS utility after both Control-M and Control-D New Day procedures have finished.

CTM060W ACTIVE JOBS FILE IS EMPTY

Explanation: The IOA Manual Conditions file is not built. The Active Jobs file is empty.

This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. No manual conditions are found because there are no job orders.

The IOA Manual Conditions file will not be loaded.

Corrective Action: No action is required.

CTM061E FILE ALLOCATED TO DDNAME "DASINC" IS NOT THE IOA SYNCHRONIZATION FILE

Explanation: The data set described by the DASINC DD statement is not the IOA Conditions Synchronization file.

This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. Possible causes are:

The file allocated to the DASINC DD statement is not the IOA Conditions Synchronization file.
The file allocated to the DASINC DD statement is the IOA Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

CTM062E FILE ALLOCATED TO DDNAME "DANSINC" IS NOT THE IOA MANUAL CONDS SYNC FILE

Explanation: The data set described by the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.

This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. Possible causes are:

The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

CTM064E INVALID PARAMETER:- `parm`

Explanation: Invalid parameter for the IOALDNRS utility.

This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List. For more details, please see the IOALNDRS utility in the INCONTROL for z/OS Utilities Guide.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

CTM065E MISSING PARAMETER AFTER:- `parm`

Explanation: Missing subparameter after the parm parameter.

This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List. For more details, please see the IOALDNRS utility in the INCONTROL for z/OS Utilities Guide.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

CTM066E REDUNDANT PARAMETER: - `parm`

Explanation: Redundant parameter for the IOALDNRS utility.

This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. For more details, please see the IOALDNRS utility in the INCONTROL for z/OS Utilities Guide.

The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

CTM069E OPEN OF ACTIVE MISSIONS FILE FAILED - DDNAME "DAAMF"

Explanation: Open of Control-D Active Missions file failed (the DAAMF DD statement).

This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List, and is due to one of the following:

The DAAMF DD statement is missing.
The data set described by the DAAMF DD statement is not the Control-D Active Missions file.
The data set described by the DAAMF DD statement is the Control-D Active Missions file, but of another Control-D monitor, or of a different version of Control-D.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

CTM070E FILE ALLOCATED TO DDNAME "DAAMF" IS NOT THE EXPECTED ACTIVE MISSIONS FILE

Explanation: The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.

This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List, and may be due to one of the following:

The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.
The file allocated to the DAAMF DD statement is the Control-D Active Missions file, but of another Control-D monitor, or of a different version of Control-D.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

CTM071E ACTIVE MISSIONS FILE IS FORMATTING NOW

Explanation: The Control-M Active Missions file is currently formatting, meaning, the Control-D New Day procedure is running.

This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file will not be loaded.

Corrective Action: Try again later.

CTM072E ACTIVE MISSIONS FILE IS DAMAGED - NOTIFY THE IOA ADMINISTRATOR

Explanation: The Active Missions file is probably damaged.

The program stops executing with a condition code of 08.

Corrective Action: Check whether the file allocated to the DAAMF DD statement is the Control-D Active Missions file. If it is, it has been damaged; in that event, consult your INCONTROL administrator or BMC Customer Support.

CTM075S OPEN OF DDNAME "DASIMOUT" FAILED. SIMULATION STOPPED

Explanation: Open of simulation printout file failed (the DASIMOUT DD statement - the CTMSIM utility).

This is due to one of the following:

The DASIMOUT DD statement is missing.
The data set described by the DASIMOUT DD statement cannot be opened for sequential write.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

CTM076I SIMULATION STARTED

Explanation: This information message indicates that simulation started (the CTMSIM Control-M utility).

This message is issued by the CTMSIM Control-M utility, which activates the Simulation and Forecasting Facility.

Corrective Action: No action is required.

CTM077S OPEN OF DDNAME "DASIMPRM" FAILED. SIMULATION STOPPED

Explanation: Open of simulation parameters file failed (the DASIMPRM DD statement - the CTMSIM utility)

This could be due to one of the following:

The DASIMPRM DD statement is missing.
The data set described by the DASIMPRM DD statement cannot be opened for sequential read.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

CTM078I SIMULATION ENDED

Explanation: This information message indicates that simulation has ended (the CTMSIM Control-M utility).

Corrective Action: No action is required.

CTM085S LOADING OF SIMULATION CONTROL TABLE FAILED. SIMULATION STOPPED

Explanation: Loading of simulation control table failed. The CTMSMT module is not in the IOA SIML library, or there is insufficient memory.

Simulation stops.

Corrective Action: Check the IOA SIML library or increase the REGION size.

CTM090E INSUFFICIENT MEMORY. UNABLE TO CONVERT TABLE

Explanation: There is not enough memory available for the CTMBGRP utility.

The utility ends with a return code of 20 without converting any jobs.

Corrective Action: Increase the REGION size and resubmit the utility.

CTM091E TABLE `tableName` IS IN USE. TRY AGAIN LATER.

Explanation: The tableName table is being used by another user or by the Control-M monitor.

The table is not converted. The utility continues processing with the next table, and ends with a return code of 8.

Corrective Action: Try to convert the table later.

CTM092E TABLE `tableName` IS NOT A VALID SCHEDULING TABLE

Explanation: The tableName table specified by the user is not a valid scheduling table. As a result, the table cannot be converted into a group format.

The table is not converted. The utility continues with the next table, and ends with a return code of 8.

Corrective Action: No action is required.

CTM093E CTMMEM FAILED. TABLE= `tableName`, FUNCTION= `func`, RC= `rc`

Explanation: The CTMGRB utility issued function func for table tableName. The function failed. The CTMMEM service routine ended with a return code of rc.

The table is not converted. The utility continues with the next table, and ends with a return code of 8.

Corrective Action: Check the function and return code of CTMMEM and correct the problem. For details about CTMMEM functions and return codes, see DOCIMEM in the IOA DOC library.

CTM094S CTMGRB INITIALIZATION FAILED: `shortDesc`

Explanation: The initialization phase of the CTMGRB utility failed. A short description (shortDesc) at the end of the message specifies the cause of the failure. For example:

LOAD FAILED FOR MODULE modName
OPEN fileName FAILED
DD ddName MISSING

The utility terminates with a return code of 16, and no jobs are converted.

Corrective Action: Check the short description specified in the message, and proceed accordingly.

CTM095I CTMGRB ENDED. MAX RC: `rc`

Explanation: This information message

indicates that the CTMGRB utility has finished running
displays the highest return code (rc) from the utility conversions

Corrective Action: No action is required.

CTM096I CTMGRB `msg` - TABLE `tableName` FROM `dsn`, GROUP `grpname`

Explanation: This information message is issued at the beginning and end of each table conversion.

The variables in this message are:

msg - information about the table conversionValid values are:

tableName - the name of the table
- CONVERT STARTED - The conversion has begun.
- ENDED “OK” - The conversion ended and was successful,
- ENDED “NOT OK” - The conversion ended and was unsuccessful.
grpname - the group name that was added to the new table by the conversion process

Corrective Action: If the value of msg was ENDED "NOT OK", check for a previous error message specifying the cause of the error and proceed accordingly.

CTM097I JOB `jobName` CONVERTED USING RBC `rbcName`

Explanation: This information message is issued for each job converted.

As part of the conversion process, basic scheduling criteria for each job are replaced by a schedule RBC. The message indicates the job name and the new schedule RBC that was added to it.

Corrective Action: No action is required.

CTM098W TABLE `tableName` CONTAINS ONLY COMPRESS JOBS. NOT CONVERTED TO GROUP FORMAT

Explanation: The tableName table that was selected for conversion contains only COMPRESS jobs. COMPRESS jobs are job scheduling definitions utilizing MINIMUM and PDS. If an entire table contains only COMPRESS jobs, the entire table is not converted and this message is issued.

The utility continues with the next table and ends with a return code of 4.

Corrective Action: No action is required.

CTM099E TABLE `tableName` IS ALREADY A GROUP TABLE

Explanation: The tableName table, which was selected for conversion, is already in group format.

The table is not converted. The utility continues with the next table and ends with a return code of 8.

Corrective Action: No action is required.

CTM09AE INVALID SYSIN CARD ENCOUNTERED: `text`

Explanation: For one table, an invalid keyword was specified, or a valid keyword was omitted from the file referenced to by the SYSIN DD statement.

The variable text specifies the SYSIN statement and the error. Examples are:

MISSING KEYWORD keyword
MISSING CARD ddstmt

The utility continues with the next table and ends with a return code of 8.

Corrective Action: Proceed according to the variable text specified in the message.

CTM09BW TABLE `XXXXXXXX`, JOB `YYYYYYYY` CONTAINS AN RBC - NOT CONVERTED TO SMART TABLE FORMAT

Explanation: During the execution of the CTMBTBL utility, an attempt was made to convert a regular scheduling table to a SMART table format. However, the utility encountered a job in the table which contains a CTM-Level RBC. The utility does not support such tables and the table is not converted.

The utility bypasses the affected table and continues processing other table conversion request. The utility ends with a return code of 4.

Corrective Action: No action is required.

Messages CTM100 through CTM1xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM100I CONTROL-M MONITOR STARTED

Explanation: This information message is a general message issued when the Control-M monitor is started.

Corrective Action: No action is required.

CTM101I NEWCONLIST COMMAND ACCEPTED. SUB SYSTEM(S) WILL BE NOTIFIED

Explanation: This information message appears after the operator issued a NEWCONLIST modify command to Control-M.

The Control-M monitor will notify all the console subsystems on all the computers of the required change.

Corrective Action: No action is required.

CTM101S LCT EXCEEDED MAXIMUM NUMBER OF ENTRIES (10000)

Explanation: An attempt was made to add an entry to the Local Command Table (LCT), an internal program table, but it already contains the maximum number of allowable entries.

Control-M Extended MCS tracking is stopped.

Corrective Action: Check the SPY289E message, which always accompanies this message, and proceed accordingly.

CTM102E CONTROL-M MONITOR NOT APF-AUTHORIZED

Explanation: The Control-M monitor is not APF-authorized. The CTMRUN module is not in an APF-authorized library, or does not have the AC attribute set to 1.

The Control-M monitor terminates with a return code of 8.

Corrective Action: Add the library name in which CTMRUN resides to the IEAAPF00 member in SYS1.PARMLIB.

CTM102S JNF EXCEEDED MAXIMUM NUMBER OF ENTRIES (10000)

Explanation: An attempt was made to add an entry to the Job Not Found Table (JNF), an internal program table, but it already contains the maximum number of allowable entries.

Control-M Extended MCS tracking is stopped.

Corrective Action: Check the SPY289E message, which always accompanies this message, and proceed accordingly.

CTM103E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

Explanation: An erroneous parameter was passed to the Control-M monitor by an operator modify command (F). A list of valid modify parameters is displayed on the console after this message.

The modify command is rejected.

Corrective Action: Enter a correct modify parameter.

CTM104S BLDL/ATTACH CTMMRUN FAILED FOR TASK `taskName`

Explanation: Initialization of the taskName Control-M monitor internal task failed.

Possible causes are:

The task was not found in the IOA Load library.
There is insufficient memory for the Control-M monitor.

The exact reason (system code) can be found on the computer log.

Control-M monitor shuts down.

Corrective Action: Call your system programmer for assistance. If necessary, increase the Control-M monitor REGION size.

CTM105S UNRECOVERABLE ERROR ENCOUNTERED

Explanation: An unrecoverable error occurred in the operation of the Control-M monitor.

The IOA Log contains a previous message concerning the error.

The Control-M monitor may:

abend on U0006
terminate with a non-zero return code
hang. See the IOA Administrators Guide, Chapter 3, section ‘Shutting Down the Control-M Monitor’ to perform a manual shutdown.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM106S SUBTASK `subtaskName` HAS ABENDED

Explanation: The subtaskName Control-M monitor internal subtask has abended.

Control-M monitor shuts down with the 0006 user abend. A dump of the abending task will be included in the output.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM107I SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message is issued when the Control-M monitor is shut down upon request from the operator.

Control-M monitor shuts down.

Corrective Action: No action is required.

CTM108S INITIALIZATION ROUTINE FAILED. RC= `rc`

Explanation:Highlighted, unrollable message.

Error encountered when initializing the Control-M monitor.

The exact cause of the error is indicated by the return code (rc).

The Control-M monitor shuts down.

Corrective Action: If the return code (rc) is 4, verify that the JES subsystem name as defined in IEFSSNxx is either JES2 or JES3, and that the JESTYPS parameter in the IOAPARM member is either JES2 or JES3.

If the return code is 8, certain load modules are missing from the IOA LOAD library. Restore the original LOAD library.

If the return code is 24, the IOADEST table (the dynamic destination table for group Shout messages) is missing from the IOA PARM library.

CTM109I THE NUMBER OF INTERVALS TO WAIT FOR THE CONTROL-M DAILY IS SET TO `numberIntervals`

Explanation: This information message indicates that after a Control-M monitor issues message CTM113I, it is waiting for the displayed number of Control-M sleeping intervals for the New Day procedure to start executing. If the New Day procedure does not start executing, message CTML03W is issued, followed by message CTML06W.

Corrective Action: No action is required.

CTM111I JOURNAL COMMAND ACCEPTED: `cmd`

Explanation: This information message indicates that a JOURNAL=ENABLE or JOURNAL=DISABLE modify command was accepted. The command is echoed (as cmd) in the message.

Corrective Action: No action is required.

CTM112E SMFID `smfid` IS NOT DEFINED IN CONTROL-M INSTALLATION PARAMETERS

Explanation: The Control-O or CMEM subsystem initialization routine is running under a CPU that was not defined in the IOACPRM member.

Possible causes are:

The CPU in which Control-O or CMEM runs is not defined in the IOACPRM member.
The computer in which Control-O or CMEM runs is a multi-CPU computer, and the SID parameter in the SMFPRM xx member in SYS1.PARMLIB does not define all the CPUs correctly.

Control-O or CMEM monitor shuts down.

Corrective Action: Do the following:

Check that the SMFID of the computer in which Control-O or CMEM is being initialized is defined in the list of SMFIDs in the IOACPRM member.
If the IOACPRM definition appears correct, check the SMFID defined in SYS1.PARMLIB.
In a multi-CPU computer, issue from the console the MVS command D M=CPU to receive a listing of all CPU serial numbers, and compare them with the PARMLIB definition.

CTM112I `fileName` SUPPORT NOT ACTIVATED

Explanation: This information message indicates that History/Journal support is not set to Y in the CTMPARM member.

This message is generated in response to a HISTALOC/JOURNAL=ENABLE or HISTALOC/JOURNAL=DISABLE modify command. This command could not be processed because History/Journaling is not enabled.

Corrective Action: Set HIST/JRNL to Y in the CTMPARM member.

CTM113I CONTROL-M MONITOR `monName` NEW DAY PROCESSING STARTED

Explanation:Highlighted, unrollable message.

This information message indicates that the monName Control-M monitor has begun performing a number of housekeeping tasks prior to submitting the New Day procedure.

Control-M suspends processing at the time specified in CTMPARM to allow the New Day procedure to run.

The Control-M monitor remains suspended until the New Day procedure is successfully completed. At the successful completion of the New Day procedure, the monitor resumes normal execution.

Corrective Action: No action is required.

CTM113W CONTROL-M MONITOR SHUTTING DOWN FOR A NEW DAY

Explanation:Highlighted, unrollable message.

See RUN113W.

Corrective Action: No action is required.

CTM114E JOB HANDLED AT TIME OF ABEND: ID= `id` MEMBER= `memName` USER-ID= `userId`

Explanation: A subtask abended.

As a result of the subtask abend, the RUN106S message is issued. This message follows RUN106S with additional information. The ID (id), member name (memName), and user ID (userId) displayed in the message are from the Master Index file (MIT) that was handled by the subtask when it abended.

Corrective Action: No action is required.

CTM116S OPEN OF ACTIVE JOBS FILE FAILED - DDNAME "DACKPT"

Explanation:Highlighted, unrollable message.

Open of Control-M Active Jobs file failed (the DACKPT DD statement). Possible causes are:

The DACKPT DD statement missing.
The data set described by the DACKPT DD statement is not the Control-M Active Jobs file.
The data set described by the DACKPT DD statement is the Control-M Active Jobs file, but of another Control-M monitor, or of a different version of Control-M.

Control-M monitor shuts down.

Corrective Action: Correct the JCL for the Control-M monitor.

CTM117S ACTIVE JOBS FILE IS BEING FORMATTED NOW

Explanation:Highlighted, unrollable message.

Control-M monitor was started while the Active Jobs file was being formatted.

The New Day procedure did not finish formatting the file, either because it is still working, or because it abended. It is impossible to start the Control-M monitor until the New Day procedure finishes executing successfully.

The Control-M monitor shuts down.

Corrective Action: Check how the New Day procedure finished executing. All the problems of the New Day procedure must be corrected before restarting the Control-M monitor. Note, however, that if an IPL occurred during the previous run of the New Day procedure, it will correct itself when restarted. Therefore, it can be restarted without correction. If the New Day procedure is abended, it may be necessary to set all dates in the date control record (the DATREC member in the CTM PARM library) to one day prior to the current day and rerun the New Day procedure. If the procedure ends successfully, the user will be able to restart the Control-M monitor.

CTM118S FILE ALLOCATED TO DDNAME "DACKPT" IS NOT THE EXPECTED ACTIVE JOBS FILE

Explanation:Highlighted, unrollable message.

The data set described by the DACKPT DD statement is not the expected Control-M Active Jobs file.

This could be due to one of the following:

The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.
The file allocated to the DACKPT DD statement is the Control-M Active Jobs file, but it is of a different version or of a different Control-M monitor.

Control-M monitor will shut down.

Corrective Action: Correct JCL for the Control-M monitor.

CTM119S ACTIVE JOBS FILE IS DAMAGED - NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

The contents of the Active Jobs file have been corrupted.

The Active Jobs file is marked as FORMAT during New Day processing, and marked as FREE at successful completion. Currently, the file is not marked as FORMAT, nor as FREE.

Control-M monitor will shut down.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, call your IOA Administrator.

CTM120I CONTROL-M MONITOR SHUTTING DOWN

Explanation:Highlighted, unrollable message.

This information message is issued by Control-M or Control-D when shutting down the Control-M monitor in response to a P command, or on certain internal Control-M events.

The IOA Log contains additional messages concerning the reason for shutting down.

Control-M monitor shuts down.

Corrective Action: No action is required.

CTM121S CONTROL-M MONITOR ENDED WITH ERROR

Explanation:Highlighted, unrollable message.

Control-M monitor ended with an error.

The IOA Log should contain additional messages concerning the specific error.

Control-M monitor will shut down.

Corrective Action: Check the IOA Log (or the computer log) for the reason. Call the system programmer for assistance if needed. Try to start the Control-M monitor again as soon as possible.

CTM122W YOUR CONTROL-M IS ALREADY ACTIVE. QNAME `qName`

Explanation:Highlighted, unrollable message.

An attempt has been made to start a Control-M monitor which is already active. Two Control-M monitors with the same qname cannot run at the same time.

The newly started Control-M monitor will shut down.

Corrective Action: No action is required.

CTM123I CONTROL-M INTERVAL IS SET TO `nn` SECONDS

Explanation: This information message is issued when an operator command is used to set a Control-M sleeping interval. For more details, see the INCONTROL for z/OS Administrator Guide.

Control-M monitor wakes up every nn seconds, and checks what to do.

Corrective Action: No action is required.

CTM124E VALID PARAMETERS FOR KEYWORD `keywrd` ARE: `parms`

Explanation: A MODIFY command containing invalid syntax was entered for the Control-M monitor.

In this message, parms is a list of the valid parameters.

Corrective Action: Enter one of the parms parameters.

CTM125I validParm

Explanation: This message indicates that an erroneous parameter was passed to the Control-M monitor by an operator modify command (F). The message follows the CTM103E message with a valid modify parameter.

Corrective Action: Enter a correct modify parameter.

CTM126I NEW EXIT CTMX004 LOADED

Explanation: This information message indicates successful execution of the CTMX004 operator modify command. A new Control-M resource acquisition user exit was loaded.

Corrective Action: No action is required.

CTM127I NEWDEST COMMAND ACCEPTED: NEWDEST= `tableName`

Explanation: A NEWDEST operator command has been passed successfully to the Control-M monitor.

The Control-M monitor replaces the current destination table with the tableName destination table.

Corrective Action: No action is required.

CTM128S OPEN OF DUAL ACTIVE JOBS FILE FAILED-DDNAME "DAALTCKP"

Explanation:Highlighted, unrollable message.

Open of the Control-M Alternate (dual) Active Jobs file failed (the DAALTCKP DD statement).

This is due to one of the following:

The DAALTCKP DD statement is missing.
The data set described by the DAALTCKP DD statement is not a Control-M Active Jobs file.

This message will be produced only if Control-M is working in dual file mode, which is selected by setting the DUALDB parameter in the IOAPARM member in the IOA PARM library to Y.

The Control-M monitor will shut down with an error message.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again. If you do not wish to run in dual file mode, correct the Control-M Installation Parameters (IOAPARM).

CTM129W EXIT `exitName` WAS NOT LOADED

Explanation: Control-M failed to load the exitName user exit. Common reasons for failure are:

The IOA Load library is in the Linklist, and someone has updated the library without performing a refresh for the LLA.
The last assembly or linkage of the exit failed.
There is insufficient memory to load the new exit.

Control-M will bypass the exit and continue to run.

Corrective Action: Check the computer Log for the cause of the failure.

CTM12AE CONTROL-M EXTENDED MCS INITIALIZATION FAILED. RC= `rc`, MCSOPER RC= `mcsoper_rc` REASON= `rsn`

Explanation: Initialization of the extended MCS console component of Control-M failed.

The second return code (mcssoper_rc) and the reason code (rsn) are displayed only if the value of rc, the first reason code, is 16 or 20.

Possible values for rc, the first return code, are shown in the following table.

rc	Explanation
8	Authorization failed
12	Version of operating system not supported
16	See the Note below this table.
20	See the Note below this table.
24	There is insufficient memory
32	ENQ for the console already held.

If the value of rc is 16 or 20, the second return code (mcssoper_rc) and the reason code (rsn) from the MCSOPER facility are also displayed.

All services relying on an extended MCS console function are inoperable.

Corrective Action: Correct the problem according to the return code displayed in the message.

For the meanings of the MCSOPER return and reason codes displayed if the return code is 16 or 20, see the description of the MCSOPER macro in the IBM Application Development Reference - Services for Authorized Assembler Language Programs.

Once the cause of the problem has been corrected, bring the Control-M monitor down and up again.

CTM130E SYNTAX ERROR. "QUIESQRES" COMMAND IGNORED

Explanation: The Control-M monitor attempted to evaluate the QUIESQRES command identified in the preceding CTML18I message, but found invalid command syntax.

For a detailed description of the command syntax, see the section on activating and deactivating quiesced quantitative resources in the Control-M chapter of the INCONTROL for z/OS Administrator Guide.

The Control-M monitor ignores the command.

Corrective Action: Enter another QUIESQRES command using valid syntax.

CTM131I NO QUIESCE TIME ASSIGNED TO RESOURCE `resourceName`

Explanation: The following command was given:

F CONTROLM,QUIESQRES=resourceName,DISPLAY|OFF

with the DISPLAY or OFF parameter. However, no QUIESCE time was assigned to the resourceName resource.

Corrective Action: No action is required.

CTM132I NO QUIESCE TIME ASSIGNED TO ANY RESOURCE

Explanation: The following command was given:

F CONTROLM,QUIESQRES=resourceName,DISPLAY|OFF

with the DISPLAY or OFF parameter. However, no resource had a QUIESCE time assigned.

Corrective Action: No action is required.

CTM133I `yyyy-mm-dd hh:mm` QUIESCE TIME ASSIGNED TO RESOURCE `resourceName`

Explanation: This information message displays the action of the Control-M monitor in response to the following command:

F CONTROLM,QUIESQRES=resourceName,DISPLAY|NOW|OFF|hh:mm

The date and time assigned in response to this command depend on the setting of the DISPLAY | NOW | OFF parameter, as follows:

DISPLAY - the time that is currently assigned
NOW - the time assigned is the time current at the time the command is processed
hh:mm - the time assigned is the time specified in the command

Corrective Action: No action is required.

CTM145E `taskTypememNamejobName` /`jobId` OID=`orderId` ERROR IN IOAMEM FUNCTION `func` : RETURN CODE `rc`

Explanation:Highlighted, unrollable message.

Internal error in Control-M monitor.

In this message, rc consists of eight digits that include a 4-digit reason code and a 4-digit return code. For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

Job submission stops. In some cases, the Control-M monitor will shut down.

Corrective Action: Do the following:

Ask your INCONTROL administrator for assistance.
If the Control-M monitor shuts down repeatedly, use the H option of the Control-M Active Environment screen (Screen 3) to hold the order that is causing the problem.
If the return code indicates that an abend has occurred, check the Control-M system log for system messages associated with the abend.

CTM14AE JOB `memName` OID=`orderId` NOT SUBMITTED, MIGRATED DSN `lib` WTO for SUB14AE.

Explanation:Highlighted, unrollable message.

The job was not submitted because the library that contains its member migrated.

The job is not submitted and is assigned a NOTOK status with the NOLIB reason.

Corrective Action: Restore the library to disk and submit the job again.

CTM15CI `memName...` THE MEMBER HAS BEEN COPIED INTO OVERLIB `lib`

Explanation: The memName member has been copied from the MEMLIB library into the OVERLIB library, because the COPMEM20 installation parameter was set to Y.

Corrective Action: No action is required.

CTM15CW `memName...` THE MEMBER HAS NOT BEEN COPIED INTO OVERLIB. REASON: `rc-rsn`. LIBRARY: `lib`

Explanation: Although the COPMEM20 Control-M installation parameter was set to Y, Control-M failed to copy the memName member into the OVERLIB library.

The variables in this message are:

memName - the name of the member that was not copied
rc - the return code from the IOAMEM program
rsn - the reason code from the IOAMEM program
lib - the name of the OVERLIB library

For explanation of the values of rc and rsn, see the description of the IOAMEM Assembler Macro in the INCONTROL for z/OS Administrator Guide.

Corrective Action: Take corrective action on the basis of the values of rc and rsn.

CTM15DI `memName...` THE MEMBER HAS BEEN DELETED FROM OVERLIB `lib`

Explanation: The memName member has been deleted from the lib OVERLIB library, because either the DELOVRER or the DELOVRUN Control-M installation parameter was set to Y.

Corrective Action: No action is required.

CTM15DW `memName...` THE MEMBER HAS NOT BEEN DELETED FROM OVERLIB. REASON: `rc-rsn`. LIBRARY: `lib`

Explanation: Although either the DELOVRER or the DELOVRUN Control-M installation parameter was set to Y, Control-M failed to delete the memName member from the OVERLIB library.

The variables in this message are:

memName - the name of the member that was not deleted
rc - the return code from the IOAMEM program
rsn - the reason code from the IOAMEM program
lib - the name of the OVERLIB library

For explanation of the values of rc and rsn, see the description of the IOAMEM Assembler Macro in the INCONTROL for z/OS Administrator Guide.

Corrective Action: Take corrective action on the basis of the values of rc and rsn.

CTM161E `taskTypememNamejobName` /`jobId` OID=`orderId` SEVERE INTERNAL ERROR WHILE PROCESSING AUTOEDIT INSTRUCTIONS, RC=`rc`. SUBMISSION CANCELLED

Explanation: Severe Control-M internal error during submission of member.

The error occurred in the AutoEdit language interpreter.

Depending on the severity of the error, Control-M monitor will shut down, or at least job submission will be cancelled.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support. You will probably be able to submit the member if you change (or omit) your AutoEdit control statements in the member, but keep a copy of the original member for problem resolution. If you hold the job order, Control-M monitor will not shut down.

CTM166E SUBMITTER FAILURE. CTMLIB ABENDED `abCode` ON FUNCTION `func`

Explanation:Highlighted, unrollable message.

An abend has occurred while trying to read a member.

The abend code (abCode) and function (func) can suggest the cause of the problem.

Control-M monitor does not abend. Processing of other jobs continues, but the job submission is terminated.

Corrective Action: Resolve the problem according to the abend code and rerun the job.

CTM168S CONTROL-M SHUTTING DOWN - COMMUNICATION TO "JES" NOT AVAILABLE

Explanation:Highlighted, unrollable message.

The Control-M monitor cannot communicate with JES, and therefore shuts down.

This can be due to the following:

JES is not working or is in the process of shutting down.
A subsystem of JES stopped working. JES will probably shut down soon with error, or may get stuck.
There is some problem with JES operation.
An error occurred in the Control-M interface to JES.

The Control-M monitor shuts down as a precaution. If something is wrong with JES, the results of job submission or the initiation of a started task may be unpredictable.

Corrective Action: If the problem is JES-related, after the JES problem is solved, start the Control-M monitor again.

If you cannot find the cause of the problem, have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support. The sysout of the DD statement DADUMP2 of the Control-M monitor procedure should contain a dump of problem-related areas which can help BMC Customer Support.

In any case, try to start Control-M monitor again, for production to continue.

CTM169E SEVERE INTERNAL ERROR WHILE STARTING A STARTED TASK RC=`rc`. TASK WAS NOT STARTED

Explanation: A severe Control-M monitor error occurred while starting a started task.

The problem is probably in the Control-M monitor communication with JES. The return code rc can be interpreted by BMC Customer Support.

The Control-M monitor may:

abend on U0006
terminate with a non-zero return code
hang. See the IOA Administrators Guide, Chapter 3, section ‘Shutting Down the Control-M Monitor’ to perform a manual shutdown.

Corrective Action: Re-start the Control-M monitor.

If the problem occurs again, hold the started task which causes the problem (it is in WAIT START state on the Active Environment screen).
If the problem continues to appear for every started task, hold all the started tasks that should be started by Control-M. This will allow the jobs to run while someone tries to resolve the problem.
Keep the dumps and contact your INCONTROL administrator.

CTM170E SEVERE INTERNAL ERROR WHILE RELEASING AN ON SPOOL JOB RC=`rc`. JOB NOT RELEASED

Explanation: When the On Spool Facility tried to get the status of the job before releasing it, it received an unknown return code rc from the subsystem request.

The job is not released.

Corrective Action: Have your INCONTROL administrator prepare the Control-M monitor full output and contact BMC Customer Support.

CTM180I ENABLED FOR THE AUTOMATIC RESTART MANAGEMENT FUNCTION. ELEMENT `elemName`

Explanation: This information message is issued by the Control-M monitor when the Automatic Restart Management function is enabled at monitor initialization time.

The Control-M monitor was requested to enable the Automatic Restart Management function under the elemName element name. When this succeeds, this information message is issued.

Corrective Action: No action is required.

CTM181I AUTOMATIC RESTART IN PROGRESS AFTER UNEXPECTED FAILURE

Explanation: If Automatic Restart Management support is enabled and the Control-M monitor fails unexpectedly, this information message is issued when the Control-M monitor is restarted automatically by MVS.

If the Control-M monitor fails unexpectedly when Automatic Restart Management support is enabled, this information message is issued when the Control-M monitor is automatically restarted by MVS.

Corrective Action: No action is required.

CTM182W AUTOMATIC RESTART MANAGEMENT REQUEST FOR ELEMENT `elemName` FAILED R15=`nn` REASON=`rsn shortDesc`

Explanation: This warning message is issued if the Control-M monitor fails to enable the Automatic Restart Management function under the elemName element.

The return and reason codes are documented in the Return and Reason Codes part of the “IXCARM Macro Instruction” section in the IBM manual MVS Programming: Sysplex Services References. The short description is only displayed for common errors.

The Control-M monitor continues without Automatic Restart Management support.

Corrective Action: Investigate why the enable request was refused and rectify the situation.

CTM183E JOB WAS PUT ON HOLD BY THE AUTOMATIC RECOVERY FEATURE

Explanation:Highlighted, unrollable message.

A job was put into Held status after a subtask abended.

As a result of the abending of the subtask, the CTM114E message is issued. If the MAXJBHLD parameter in the CTMPARM member is set to a value greater than zero, this message is issued following the CTM114E message.

The MAXJBHLD parameter sets the maximum number of jobs that can be put into Held status.

Corrective Action: No action is required.

CTM184E MAXIMUM NUMBER REACHED FOR AUTOMATIC RECOVERY FEATURE - DISABLED

Explanation: A job was previously put into Held status after a subtask abended. As a result of the abending of the subtask, the CTM114E and CTM183E messages are issued.

This message is issued following the CTM183E message if both the following conditions are satisfied:

The MAXJBHLD parameter in the CTMPARM member is set to a value greater than zero.
The number of jobs already put into Held status is equal to the value set in the MAXJBHLD parameter.

The MAXJBHLD parameter sets the maximum number of jobs that can be put into Held status.

Corrective Action: No action is required.

CTM188W `subtaskName` IS PROCESSING JOB `jobName` ORDID `orderId` FOR MORE THAN `number` MINUTES

Explanation: The subtaskName subtask has been processing the job for an unreasonable amount of time. The task is most likely hung or in a loop.

Possible causes are:

If CPU utilization by the Control-M monitor is not unusually high, most probably the subtask is waiting for completion of a system action (for example, recall of migrated data set), or it may point to a problem in MVS or JES.
If CPU utilization by the Control-M monitor is unusually high, it may indicate a loop (in the base code or in a user exit).

The Control-M monitor continues processing as usual. The subtask continues processing of the indicated job.

Note that the jobname and orderID might not be specified in the message if the issue was detected before these fields were populated.

Corrective Action: Review the system log for additional messages related to the problem.

If the reason for the problem is unclear, take the system (SVC) dump of the Control-M monitor's address space using the DUMP console command. Specify parameter SDATA=(CSA,GRSQ,SUM,RGN,TRT).

If the problem is outside Control-M, holding the job being processed and restarting the Control-M monitor may have only temporary effect.

CTM1A3S OID=`orderId` SEVERE INTERNAL ERROR READING AJF. RC=`rc`

Explanation: Severe error on Control-M Active Jobs file.

Possible causes are:

An I/O error
the file allocated to DD statement DACKPT is not the Control-M Active Jobs file
the Active Jobs file was corrupted.

The 2TF Control-M program ends with errors.

Corrective Action: Have your INCONTROL administrator prepare the Control-M monitor full output and contact BMC Customer Support. Check if the file has been updated from multiple computers without global ENQ control, or updated by an unauthorized program.

CTM1A6S OPEN OF STATISTICS FILE FAILED. RC=rc ERROR=errCode

Explanation: Open of Control-M Job Statistics file failed.

Possible causes are:

a missing DASTAT DD statement
a VSAM open error

Corrective Action: Look for VSAM messages or other system messages, and correct the JCL for the Control-M monitor procedure.

CTM1ADW VM COMMAND OUTPUT TRUNCATED

Explanation: The response of the IOA VM command interface exceeded the 4096 bytes that the buffer can hold. The remainder of the response is truncated.

Corrective Action: Change the command so it can be held in the available buffer of 4096 bytes.

Messages CTM200 through CTM2xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM20AE ERROR IN CTMPPE RC=`rc`, INFORM YOUR IOA ADMINISTRATOR

Explanation: An internal error was detected in MAINVIEW Batch Optimizer (MVBO) support.

Control-M ends with an error and shuts down.

Corrective Action: Perform the following steps:

Activate debug level 75.
Restart the Control-M monitor.
Recreate the error.
Send full output of the Control-M monitor to your INCONTROL Administrator.

CTM20BE OID=`orderId`, MAXIMUM PIPES IN COLLECTION EXCEEDED (255), PIPES IGNORED

Explanation: Too many pipes were specified for the collection or the job added too many pipe definitions to the collection.

This message is issued by Control-M. This message may occur if:

The job definition includes more than 255 pipe definitions.
The collection contains the maximum number of pipes and the job tries to add additional pipe definitions.

The pipe definitions in the job (and in other jobs belonging to the same collection) will be ignored.

Corrective Action: Ensure that no more than 255 pipes are defined in the collection.

CTM221I IOA SUBSYSTEM `subsys` INITIALIZATION OF CONTROL-`x` FUNCTIONS STARTED

Explanation: This information message indicates that initialization of the INCONTROL application functions of the IOA subsystem started.

If x is M, this message is a result of one of the following:

a START (S) command to the IOASINIT procedure with OPTIONS set to M
Control-M (CMEM) subsystem function initialization as a result of Control-O shutdown process

If x is D, this message is issued as a result of a START command to the IOASINIT procedure with OPTIONS set to D.

If x is O, this message is issued as a result of a START command to Control-O.

The variables in this message are:

subsys - Subsystem name.
x - One of the following:
- M - Control-M (CMEM) subsystem functions
- D - CDAM subsystem functions
- O - Control-O subsystem functions

Corrective Action: No action is required.

CTM224S SUBSYSTEM NAME `subsys` DOES NOT EXIST IN THE MVS TABLES

Explanation: If OPTION was set to D for IOASINIT, the subsystem name does not exist, and possible causes of this message are:

There is a mismatch between the name specified in the AMNAME parameter (in the Control-D Installation Parameters) and the name specified in the IEFSSNxx member on SYS1.PARMLIB.
The IEFSSNxx member on SYS1.PARMLIB was not modified to include the subsystem name.

If OPTION was set to M for IOASINIT, or Control-O is started, the subsystem name does not exist and dynamic allocation of the MVS subsystem tables is not allowed. In this case, possible causes of this message are:

There is a mismatch between the name specified in the SSNAME parameter (in the IOA Installation Parameters) and the name specified in the IEFSSN xx member on SYS1.PARMLIB, and dynamic allocation for the subsystem tables in not allowed (SSALLOC was set to N).
The IEFSSN xx member on SYS1.PARMLIB was not modified to include the subsystem name and dynamic allocation for the MVS subsystem tables is not allowed (SSALLOC was set to N).

Initialization of the subsystem fails.

Corrective Action: Define the subsystem name in the MVS table.

If OPTION was set to D for IOASINIT, see the sections on Control-D operational parameters for details about the AMNAME parameter, about defining the subsystem name in the MVS tables, and about installing the Compressed Dataset Access Method (CDAM), in the Control-D chapter of the INCONTROL for z/OS Installation Guide.
If OPTION was set to M for IOASINIT or Control-O is started, see the section on IOA operational parameters in the IOA chapter of the INCONTROL for z/OS Installation Guide for details about the SSNAME and SSALLOC parameters.

For details about defining the subsystem name in the MVS tables, see the section on installing the Control-M Event Manager Subsystem (CMEM) in the Control-M chapter of the INCONTROL for z/OS Installation Guide.

CTM225S IOA SUBSYSTEM `subsys` INITIALIZATION OF CONTROL-`x` FUNCTIONS FAILED

Explanation:Highlighted, unrollable message.

Initialization of the Control- x subsystem functions failed.

The variables in this message are:

subsys - Subsystem name.
x - One of the following:
- M - Control-M (CMEM) subsystem functions
- D - CDAM subsystem functions
- O - Control-O subsystem functions

If x is D, the following components of Control-D do not function:

Report Decollation - You cannot decollate reports.
Batch CDAM - You cannot create or read compressed CDAM data sets.
Online Viewing - You cannot view reports.
Printing - You cannot print reports.

If x is M, the CMEM subsystem functions are inactive.

If x is O, Control-O is not active.

Corrective Action: Check the system log for a earlier message concerning the error, and correct the error accordingly. If no error message preceded this one, the error is internal. Contact BMC Customer Support.

If x is D, the CTDAMUTI Control-D utility can be used for emergency situations. This utility decompresses the sysout to its original non-compressed form, even when the CDAM subsystem is inactive. For more information, see the CTDAMUTI utility in the INCONTROL for z/OS Utilities Guide.

CTM226E CMEM IS NOT SUPPORTED - ALL CMEM RELATED PARAMETERS WERE NOT DEFINED IN CTMPARM

Explanation: No values were entered for the ONSPTAB, CTM2SBS and CPUS CMEM-related parameters in the CTMPARM member. This message is issued by the CMEM subsystem initialization routine.

Initialization of the Control-M functions of the IOA subsystem fails.

Corrective Action: Refer to the section in the Control-M chapter of the INCONTROL for z/OS Installation Guide that describes the installation consideration when installing CMEM when Control-M is already installed.

CTM227I IOA SUBSYSTEM `subsys` INITIALIZATION OF CONTROL-`x` FUNCTIONS COMPLETED

Explanation: This information message indicates that initialization of the Control- x subsystem functions was successful. It is the normal termination message during initialization of the Control- x subsystem functions.

The variables in this message are:

subsys - the subsystem name
x - one of the following:
- M - Control-M (CMEM) subsystem functions
- D - CDAM subsystem functions
- O - Control-O subsystem functions

Corrective Action: No action is required.

CTM228I IOA SUBSYSTEM `subsys` DEACTIVATION OF CONTROL-`x` FUNCTIONS STARTED

Explanation: This information message indicates that Control- x subsystem functions are being shut down. It is the normal message issued during shutdown of Control- x subsystem functions.

If x is M, this messages is issued as a result of either a START (S) command to the IOASTERM procedure with OPTIONS set to M, or starting Control-O monitor, in which case, the Control-O monitor takes over the CMEM functions and therefore stops the CMEM subsystem functions.

If x is D, this message is issued as a result of a START command to the IOASTERM procedure with OPTIONS set to D.

If x is O, this message is issued as a result of a Control-O shutdown.

The variables in this message are:

subsys - the subsystem name
x - One of the following:
- M - Control-M (CMEM) subsystem functions
- D - CDAM subsystem functions
- O - Control-O subsystem functions

Corrective Action: No action is required.

CTM229I SUBSYSTEM `subsys` WAS USED BY ANOTHER IOA ENVIRONMENT (IOA QNAME)

Explanation: The subsys subsystem was used in the past for another IOA environment. Currently, there are no active components of this subsystem.

Control-O issues message CTM22AA.

Corrective Action: Respond to message CTM22AA.

CTM229S OPEN FAILED FOR DDNAME "DARES"

Explanation: Open of a debugging output file failed (the DARES DD statement).

This is probably because the DARES DD statement is missing in the Control-M procedure.

The Control-M monitor will shut down with error message.

Corrective Action: Correct the JCL for the Control-M monitor procedure and start it again.

CTM22AA ENTER "YES" TO RE-USE THE SUBSYSTEM OR "NO" TO STOP THE INITIALIZATION

Explanation: The situation described in message CTM229I prevents subsystem initialization. The response to this message determines the next action.

The task is suspended until a response to this message is received.

Corrective Action: Do one of the following:

YES - re-use the subsystem by the new environment.
NO - do not re-use the subsystem by the new environment; terminate subsystem initialization.

CTM22CI SUBSYSTEM INITIALIZATION TERMINATED DUE TO OPERATOR REQUEST

Explanation: This information message indicates that the user requested not to re-use the subsystem by the new environment, in response to message CTM22AA.

The subsystem initialization request is terminated.

Corrective Action: No action is required.

CTM22DI `monitorType` SWT CONTROL BLOCK IS REALLOCATED DUE TO VERSION CHANGE FROM `oldVersion` TO `newVersion`

Explanation: During initialization, Control-O or CMEM could not reuse the SWT control block, because it was allocated by version oldVersion. A new control block is allocated.

Corrective Action: No action is required.

CTM230S OPEN FAILED FOR DDNAME "DARESF"

Explanation: Open of Control-M Resources file failed (the DARESF DD statement).

Possible causes are:

The DARESF DD statement is missing.
The data set described by the DARESF DD statement is not the Control-M Resources file.
The data set described by the DARESF DD statement is the Control-M Resources file of a different version or a different Control-M monitor.

The Control-M monitor shuts down.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again.

CTM231I IOA SUBSYSTEM `subsys` DEACTIVATION OF CONTROL-`x` FUNCTIONS COMPLETED

Explanation: This information message indicates that shutdown of the Control- x subsystem functions was completed. It is the normal message issued during shutdown of the Control- x subsystem functions.

The variables in this message are:

subsys - the subsystem name
x - one of the following:

M - Control-M (CMEM) subsystem
D - CDAM subsystem
O - Control-O subsystem

If x is D, the CDAM access method is inactive. The following components of Control-D do not function:

Report Decollation - You cannot decollate reports.
Batch CDAM - You cannot create or read compressed CDAM datasets.
Online Viewing - You cannot view reports.
Printing - You cannot print any reports.

If x is M, the CMEM subsystem functions are inactive unless Control-O is active and took over the CMEM subsystem functions.

If x is O, Control-O is not active. If Control-O was stopped with the P CONTROLO command, then CMEM subsystem functions are active.

Corrective Action:No action is required.

CTM232S IOA SUBSYSTEM `subsys` DEACTIVATION OF CONTROL-`x` FUNCTIONS FAILED

Explanation:Highlighted, unrollable message.

Shutdown of the Control- x subsystem functions failed.

The variables in this message are:

subsys - the subsystem name
x - one of the following:
- M - Control-M (CMEM) subsystem
- D - CDAM subsystem
- O - Control-O subsystem

If the Control-x subsystem functions were active, they are not shut down.

Corrective Action: Check the system log for a previous message concerning the error, and correct the error accordingly.

If no error message preceded this one, the problem is an internal error. Contact BMC Customer Support.

CTM233E INVALID PARAMETER. ONLY "D" IS VALID

Explanation: The subsystem initialization routine was given a null or invalid parameter. The subsystem initialization routine requires the parameter D.

Corrective Action: If the subsystem is initialized manually, specify the correct OPTION parameter in the START command. If the subsystem is initialized through the COMMND xx member in SYS1.PARMLIB, correct the OPTION parameter specified in the START command in the member.

CTM236E SUBSYSTEM NAME IS NOT SPECIFIED IN IOAPARM

Explanation:This is one of two messages with the same ID, but different text.

The subsystem initialization routine found a blank subsystem name definition in the IOAPARM member.

Corrective Action: Correct the SSNAME parameter in the IOAPARM member to specify a valid subsystem name, and check that the other subsystem-related parameters were defined correctly.

If Control-D subsystem functions are requested, check the AMNAME parameter in CTDPARM and correct if necessary.

CTM236E ERROR WHILE ATTEMPTING TO OPEN THE STEPLIB DATASET

Explanation:This is one of two messages with the same ID, but different text.

Control-O could not open file STEPLIB.

Control-O encountered an error opening the STEPLIB file while attempting to activate the alternate subsystem.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that a STEPLIB library or concatenation of libraries exists. Reactivate Control-O.

CTM237E ERROR WHILE ATTEMPTING TO LOCATE (BLDL) ONE OF THE SUBSYSTEM FUNCTION ROUTINES

Explanation: Control-O could not find at least one of the alternate subsystem function routines.

While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries, and reactivate Control-O.

CTM238E ERROR WHILE ATTEMPTING TO LOAD ONE OF THE SUBSYSTEM FUNCTION ROUTINES

Explanation: Control-O could not load at least one of the alternate subsystem function routines.

While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries, and reactivate Control-O.

CTM239E DYNAMIC SSI FAILED TO PERFORM REQUEST FOR `subsys` IOA SUBSYSTEM

Explanation:This is one of two messages with the same ID, but different text.

The Dynamic Subsystem Interface Service (SSI) was not able to define the specified subsystem.

The Dynamic SSI Service IEFSSI,REQUEST=ADD was used to define SSCT but failed to do so. More detailed information follows in the message: IEFSSIm: RETURN CODE =s# , REASON CODEO= #

The specified subsystem is not activated. The monitor shuts down.

Corrective Action: Call your system programmer.

CTM239E ERROR WHILE ATTEMPTING TO ACQUIRE STORAGE FOR SUBSYSTEM FUNCTION ROUTINES OR THE SSVT

Explanation:This is one of two messages with the same ID, but different text.

Control-O could not acquire enough CSA (Common Storage Area) storage to load alternate subsystem function routines or to build the SSVT for the alternate subsystem.

Control-O continues without activating the alternate subsystem.

Corrective Action: If storage defined for CSA is not large enough, increase the CSA size and perform an IPL.

CTM240I NEWCONLIST COMMAND RECEIVED. THE CMEM TABLE WAS RELOADED SUCCESSFULLY

Explanation: This information message indicates that the Control-M or Control-O subsystem functions received the NEWCONLIST request from the Control-M monitor, and accordingly reloaded (refreshed) the CMEM table.

The Control-M or Control-O subsystem functions reloaded the CMEM table.

Corrective Action: No action is required.

CTM241W `taskType memName jobName /jobId` OUTPUT CONDITION `condNameDate` NOT UPDATED - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

No more space to add output conditions to the conditions file. The date is in mmdd format.

The record for the specified day of the month is full. For example, if a condition with date reference of January 3 cannot be added, then an entry in the conditions file that contains conditions for the third day of every month is full.

The condition is not added, and a highlighted message is displayed on the operator console. Control-M continues to function, but the jobs that depend on the condition are not submitted.

Corrective Action: Immediate actions:

Enter Control-M Online Facility Resource Map (Screen 4). By changing the date range limit, find conditions with the same day (but a different month) as the condition that could not be added, and manually delete those that are not needed.
Add the failing condition manually, to maintain production flow.
Report the event to your system programmer.

Long term actions:

Run the IOACLCND Control-M utility more often.
Increase the record length of the IOA Conditions file. For more information on how to do this, see the description of expanding IOA files in the INCONTROL for z/OS Administrator Guide.

CTM244S OPEN OF DD NAME "DAALTRES" AND/OR "DAALTSNC" FAILED. DUAL RESOURCE FILE IS NOT AVAILABLE

Explanation: Open of IOA alternate (dual) Conditions file (the DAALTCND DD statement) failed.

Possible causes are:

The DAALTCND DD statement is missing.
The data set described by the DAALTCND DD statement is not an IOA Conditions file.

This message will be produced only if Control-M is working in dual file mode (indicated in IOAPARM).

The Control-M monitor will shut down with an error message.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again. If you do not wish to run in dual file mode, correct the Control-M Installation Parameters (IOAPARM).

CTM245E IOA SUBSYSTEM `subsys` FUNCTIONS FOR CONTROL-`x` ARE ALREADY ACTIVE. RUN IOASTERM BEFORE REACTIVATING THEM

Explanation: The Control- x subsystem functions cannot be activated (initialized) because they have already been activated. If x is O, Control-M and Control-O are activated concurrently.

The variables in this message are:

subsys - the subsystem name
x - One of the following:
- M - Control-M (CMEM) subsystem
- D - CDAM subsystem
- O - Control-O subsystem

The request is ignored.

Corrective Action: No action is required.

If x is O, stop the active Control-O with a P CONTROLO or F CONTROLO,STOP command. For more information, see the description of shutting down Control-O in the INCONTROL for z/OS Administrator Guide.
If x is D, run the IOASTERM procedure with OPTIONS set to D to deactivate the Control-D subsystem functions.
If x is M, stop the active CMEM facility with a P CTMCMEM command. For more information, see the description of shutting down the CMEM facility in the INCONTROL for z/OS Administrator Guide.

CTM246W CMEM FACILITY SUSPENDED - COMM FILE IS FULL. CHECK IF CONTROL-M IS ACTIVE

Explanation: The subsystem communication file is full, and therefore the CMEM subsystem functions overwrite the oldest messages. The file that is used by subsystem functions to communicate with the Control-M monitor is full. Old information will be lost.

Possible causes are:

The Control-M monitor is down, and the communication file has filled up.
A small communication file was allocated, and the subsystem adds information to it more quickly than the Control-M monitor can process.
The communication file was put on a disk that is often inaccessible by the monitor, because of hardware reserves and so on.

Corrective Action: Check if the monitor is active; if it is not, bring it up. If the monitor is active, then check:

the accessibility of the disk on which the file resides
the size of the file
the performance of the monitor

CTM247E SUBSYSTEM-TO-MONITOR COMM FILE IS NOT FORMATTED, OR IS INVALID

Explanation: The subsystem-to-monitor communication file has an invalid format or contains invalid data.

The Control-M (CMEM) subsystem functions shut down.

Corrective Action: Check the Control-M Installation Parameters (CTMPARM) definitions, and check whether the relevant file was formatted by the FORMSUB2 utility. To build the FORMSUB2 job, use the TAILOR JOB option, available from ICE by selecting Maintain your Environment => ICE refresh=> OPTION 3. After the problem is solved, use the IOASINIT JCL procedure to reactivate the Control-M subsystem functions.

CTM248W IOA SUBSYSTEM `subsys` FUNCTIONS FOR CONTROL-`x` WERE ALREADY DEACTIVATED

Explanation: The Control- x subsystem functions cannot be deactivated because they are already inactive.

The variables in this message are:

subsys - Subsystem name.
x - One of the following:
- M - Control-M (CMEM) subsystem functions
- D - CDAM subsystem functions
- O - Control-O subsystem functions

The request is ignored.

Corrective Action: No action is required.

CTM250I CONTROL-M IS TERMINATING. TERMINATION SHOULD BE COMPLETED IN LESS THAN TWO MINUTES

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-M monitor is about to shut down because of an internal problem. Due to a unique situation, the termination process may take longer than usual.

Control-M monitor shuts down after approximately one minute.

Corrective Action: Do not cancel the Control-M monitor. If it does not shut down after 5 minutes, cancel it with DUMP, prepare the Control-M monitor full output, and notify BMC Customer Support. Find out why the Control-M monitor shut down and start it again as soon as possible.

CTM252S SEVERE INTERNAL ERROR

Explanation: Severe Control-M monitor internal error while processing the above mentioned job order.

Control-M monitor will abend with the user code 0006. The internal task CTMSPY will abend with the user code 0040.

Corrective Action: Control-M Log should contain additional messages describing the type of error.

CTM255S CONTROL-M SHUTTING DOWN - SEVERE ERROR WHILE PROCESSING JOB SYSOUT

Explanation:Highlighted, unrollable message.

Control-M monitor had a severe error while reading the output of the job and is shutting down.

Control-M monitor will shut down.

Corrective Action: Check the contents of the IOA Log for prior messages that will clarify the picture. If you cannot correct the reason, and whenever you start the Control-M monitor, the monitor shuts down again for the same reason, then enter Screen 3 of the Online Facility and hold the job order. Prepare the Control-M monitor full output and contact BMC Customer Support.

CTM256S CONTROL-M SHUTTING DOWN - COMMUNICATION TO "JES" NOT AVAILABLE

Explanation:Highlighted, unrollable message.

The Control-M monitor detected some problem in communication to JES, and shuts down as a precaution. The Control-M monitor is usually one of the first components of the computer environment to detect problems in JES operation. Usually this is because JES was brought down, or is about to get stuck because of an internal JES problem.

The Control-M monitor will shut down.

Corrective Action: Correct the JES problem and restart the Control-M monitor.

CTM258S INSUFFICIENT MEMORY FOR CONTROL-M MONITOR

Explanation:Highlighted, unrollable message.

There is insufficient memory for Control-M monitor to trace a started task.

The started task has just been initiated by the Control-M monitor, and the Control-M monitor requires a small work area in order to try to locate the job ID assigned by JES to the started task. Unfortunately, there is insufficient memory for the required work area.

The Control-M monitor will try again after a few seconds (it is possible that memory will be released by other components of the Control-M monitor). Meanwhile, the started task will remain with a STARTED status and the job ID is “blank.” Under severe circumstances of this event, the Control-M monitor may shut down.

Corrective Action: Increase the Control-M monitor region size and start it again. You are working on the limits.

CTM260S OPEN OF DDNAME `ddName` FAILED

Explanation: Control-M monitor failed to open a work data set defined by the DD name ddName.

This data set must be defined as a temporary or fixed work area for Control-M monitor. The ddName DD statement is probably missing.

Control-M monitor will shut down with errors.

Corrective Action: Correct the JCL for the Control-M monitor, and start again.

CTM261S `taskTypememNamejobName/ jobId` OID=`orderId` ALLOCATION OF {SYSOUT FILE | ARCHIVE FILE} `dsn` FAILED: R15 = `rc` ERR=`erc` INFO=`irc`

Explanation: Dynamic allocation to the specified data set failed.

Control-M dynamically allocates the job sysout data sets, and or the archive data set. The allocation failed for the specified reasons. For an explanation of the return codes displayed as part of this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The return codes in this message are:

rc - the contents of R15 in hexadecimal notation
erc - the error reason code in hexadecimal notation
irc - the information reason code in hexadecimal notation

The requested function is stopped. If analysis of job results was in process, the job terminates NOTOK with the REASON UNKNOWN (*UKNW).

Corrective Action: Check the relevant IBM publication for the reason.

For sysout data sets, check if the sysout was purged while the Control-M monitor was trying to read it.
For archive files, the Control-M monitor allocates archive files with DISP=(NEW,CATLG). Therefore, the same data set name should not be used in different sysout archive instructions, even for the same job.

If your system programmer is unable to resolve the problem, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM262W `num` UNSUCCESSFUL ATTEMPTS TO READ JOB DATA BY SUBSYSTEM REQUEST. RETRY CONTINUES

Explanation: This message is issued every num unsuccessful attempts to read job data by subsystem request.

Whenever the Control-M monitor does not succeed in reading job sysout, this message appears on the operator console. For example, when a job is not run due to a JCL error, then the third sysout data set is missing and this message is issued.

Control-M continues to retry reading the job data for a predefined number of times. If the error persists, this job is not read, and the CTMD50S message is issued.

Corrective Action: For the appropriate action, see the section on the Control-M Monitor and JES in the Control-M for z/OS Administrator Guide.

CTM263S OPEN OF SMB FILE DSNAME `dsn` FAILED. RC=`rc`

Explanation: Open of the sysout data set of the job by Control-M monitor failed. Control-M cannot read and analyze the sysout of the job.

Possible causes are:

Someone purged the output of the job while Control-M monitor was trying to read it.
An internal Control-M monitor error occurred.
Some general problem with JES caused JES to terminate.

The job finishes with the status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM264S POINT TO DSNAME `dsn` FILE FAILED. FDBK `code`

Explanation: Control-M reads the output of the job as a VSAM file. For some reason it failed in a VSAM operation. Control-M cannot read and analyze the sysout of the job.

Possible causes are:

Someone purged the output of the job while Control-M monitor was trying to read it.
An internal Control-M monitor error occurred.
Some general problems with JES caused JES to terminate.

The job finishes with the status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM265S GET TO DSNAME `dsn` FILE FAILED. FDBK `code`

Explanation: Control-M reads the output of the job as a VSAM file. For some reason it failed in a VSAM operation. Control-M cannot read and analyze the sysout of the job.

Possible causes are:

The output of the job was purged while Control-M monitor was trying to read it.
An internal Control-M monitor error occurred.
Some general problem with JES caused JES to terminate.

The job finishes with the status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM266S `taskType memName jobName /jobId` READING JOB DATA BY SUBSYSTEM REQUEST FAILED

Explanation: Control-M monitor could not read all the data sets of the job, and analyze the data.

Possible causes are:

An internal Control-M monitor error occurred.
Some general problem with JES caused JES to terminate.
Someone has purged the output of the job while the Control-M monitor was trying to read it.

The job finishes with status FAILED - REASON UNKNOWN.

Corrective Action: Look for prior messages in the IOA Log. If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM267S ARCHIVE FUNCTION ABENDED ON `abCode`

Explanation: An abend occurred during sysout archiving function. Archiving stops.

Common abend codes are:

SB37, SE37 - no more space for the sysout in the file
S913 - security violation

Corrective Action: No action is required.

For an S x37 type of abend, consult your INCONTROL administrator for the possibility of changing the default Control-M archive file allocation size in the Control-M installation parameters (CTMPARM).
For an S913 abend, check with your security administrator.
For other abends, check IBM publications for the reason.

CTM268S INVALID INSTALLATION PARAMETERS FOR SYSOUT ARCHIVING

Explanation:Highlighted, unrollable message.

Invalid values were set for the Control-M Installation Parameters (CTMPARM) that control the sysout archiving function.

The archiving function is terminated. Control-M does not perform any sysout archiving, and valuable data may be lost.

Corrective Action: Consult your INCONTROL administrator immediately.

For valid values for the sysout archiving parameters, see the section on Control-M operational parameters in the Control-M chapter of the INCONTROL for z/OS Installation Guide.

To load new parameters, shut down the Control-M monitor and start it again.

CTM26AS ABEND `code` WHILE READING SYSOUTS. JOBORDER `joborder` HELD

Explanation: Control-M could not read the output of a job from the spool.

Control-M may be unable to read the output of a job because the OUT180 data set in which the data is placed overflows. The reason for this abend is either that the job output is unusually large, or that a spool corruption occurred that caused Control-M to read a very large amount of information, not related to the specific job, into its OUT180 data set.

The Control-M monitor changes the job status to HELD PROBLEMS READING SYSOUT.

Corrective Action: If the OUT180 data set is too small for the job output, increase the space value in the OUT180 DD, restart Control-M monitor, and free the job order in the Active Jobs file (AJF).

CTM271E OPEN OF DDNAME "OUT180" FAILED

Explanation:Highlighted, unrollable message.

Open of Control-M work data set described by the OUT180 DD statement failed.

This may be due to the following:

The OUT180 DD statement is missing.
The OUT180 DD statement cannot be opened for sequential processing.

The Control-M monitor shuts down with an error message.

Corrective Action: Correct the JCL for the Control-M monitor and start it again.

CTM28JE OID=`orderId` ERROR ANALYZING PARM MEMBER "UNITDEF" AT LINE `lineNum`

Explanation: An error was detected in the specified line of UNITDEF.

There is probably a syntax error.

The Automatic Tape Adjustment facility is turned OFF for the job, and processing continues.

Corrective Action: To implement automatic tape adjustment, correct the error in the specified line and restart Control-M.

CTM280I MAILDEST TABLE WAS {LOADED | RELOADED}

Explanation: This information message indicates that the MAILDEST table was LOADED during Control-M initialization, or was RELOADED as a result of a NEWMAILDST command.

The MAILDEST table must be loaded before shout messages can be sent to their specified addresses.

If there are jobs in the Active Jobs File (AJF) when a NEWMAILDST command is issued, the MAILDEST table is reloaded, this message is issued and shout messages are sent.

If the AJF is empty, when a NEWMAILDST command is issued, the MAILDEST table is not reloaded. As soon as a job is put into the AJF, MAILDEST is reloaded, this message is issued and shout messages are sent.

Corrective Action: No action is required.

RUN280W OPTIMIZE SUPPORT NOT ACTIVATED

Explanation: A Load-Index-related modify command has been issued but the Control-M Workload Optimization feature is not enabled.

Corrective Action: Enable the Workload Optimization feature by setting the OPTMODE parameter to Y, as discussed in Optimization section in the INCONTROL for z/OS Installation Guide: Customizing.

CTM281W MAILDEST TABLE WAS NOT FOUND IN ANY LIBRARY REFERENCED BY DD STATEMENT DAPARM. UNABLE TO SEND SHOUT

Explanation: The MAILDEST member is not in the IOA PARM library.

The IOAMAIL module reads the MAILDEST member to prepare a full address for each name on the mail list.

This message is produced when a job scheduling definition or rule issues a SHOUT or DO MAIL action to a destination specifying an e-mail address that cannot be resolved due to the absence of a MAILDEST member in the IOA PARM library.

The MAILDEST member is not loaded and SHOUT messages are not sent.

Corrective Action: Build a new MAILDEST member in the IOA PARM library and try again.

CTM282I `text` (`usr`)

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT facility. The usr user ID is for the job order requesting the SHOUT.

Corrective Action: No action is required.

CTM284I DEST TABLE LOAD SUCCESSFUL: NEWDEST=`tableName`

Explanation: This information message indicates that as a result of an operator NEWDEST command, the Control-M monitor successfully loaded the destination table identified in the message.

Corrective Action: No action is required.

CTM285E NEWDEST PARAMETER MISSING OR INVALID

Explanation: The destination table passed to the Control-M monitor by means of an operator NEWDEST command is invalid or missing.

The specified destination table is not loaded.

Corrective Action: Enter the NEWDEST command specifying a destination table which has been previously defined in a library concatenated to the STEPLIB DD statement of the Control-M procedure.

CTM285W DYNAMIC DESTINATION TABLE NOT LOADED

Explanation: Loading of the Dynamic Destination Table by the Control-M monitor failed.

It could be due to one of the following:

There is insufficient memory for loading the table.
The IOADEST table does not exist in the IOA PARM library.

If the failure happens during the initialization of the Control-M monitor, then SHOUT notifications will not be controlled by the Dynamic Destination Table. If this happens as a result of an F CONTROLM,NEWDEST command (operator command instructing the Control-M monitor to load a new Destination Table), the old destination table will remain in effect.

Corrective Action: Check the MVS Log for the reason for the failure (probably a system abend code). Correct the problem and then, in order to load the table, issue the operator command F CONTROLM,NEWDEST.

CTM286E4 OPEN DAM2G FILE BY CTWWMG FAILED

Explanation: The CTWWMG program is unable to open the DAM2G communication file.

To send SHOUT messages to Control-M/Enterprise Manager, Control-M uses the CTWWMG program to first write those messages and their records to DAM2G.

Corrective Action: Ask your INCONTROL administrator to correct the problem.

CTM287E INVALID OPERATION CODE FROM CTWWMG

Explanation: The CTWWMG program cannot write SHOUT message records to the DAM2G communication file because an invalid operation code was used to write the record.

To send SHOUT messages to Control-M/Enterprise Manager, Control-M uses the CTWWMG program to first write those messages and their records to DAM2G.

Corrective Action: Ask your INCONTROL administrator to correct the problem.

CTM288E ERROR IN PREPARING SHOUT TO MAIL, RC = `rc`

Explanation: The rc error occurred during preparation to send Shout messages.

Valid values for rc are:

rc	Explanation
01	GETMAIN failure in IOAMAIL.
02	Error occurred while loading modules in IOAMAIL.
03	Error occurred in the PRPGRP routine during preparation of group addresses.
04	Error occurred while reading or writing to the buffers.
05	Error in DOMAIL routine.
06	Error in MAILDEST structure.
07	Error in FREEMAIN.
08	Error in input parms.
11	GETMAIN failure in CTMMAL.
12	Error occurred while loading modules in CTMMAL.
13	FREEMAIN error in CTMMAL.

Corrective Action: Do one of the following:

If rc is 03, 04 or 05, correct errors in the MAILDEST table.
For all other rc values, contact your INCONTROL administrator or system programmer for help.

CTM289E CONTROL-M EXTENDED MCS TRACKING STOPPED. RC=`rc`

Explanation:Highlighted, unrollable message.

A system error occurred when Control-M monitor attempted an extended MCS console operation.

Control-M stops using the extended MCS console.

Corrective Action: Check for a preceding system or IOA message related to this message, and proceed accordingly.

CTM28HW OID=`orderId` AUTO TAPE DRIVE RESOURCE ADJUSTMENT IS BYPASSED DUE TO PREVIOUS MESSAGE

Explanation: Resource adjustment for the Automatic Tape Adjustment facility was bypassed for current job end processing.

An error occurred during resource adjustment for the Automatic Tape Adjustment facility. The reason is described in the preceding message.

Job end processing continues without tape drive adjustment.

Corrective Action: Check the reason described in the preceding message.

CTM28KW OID=`orderId` DAUNITDF DD CARD MISSING

Explanation: There is no valid DD statement that points to UNITDEF.

Either the statement is missing or it contains a syntax error .

The Automatic Tape Adjustment facility is turned OFF for the current job, and processing continues.

Corrective Action: To implement automatic tape adjustment, correct the DD statement that points to UNITDEF and restart Control-M.

CTM28LS OID=`orderId` GETMAIN FAILED IN CTMATD AUTO TAPE PROCESSING

Explanation: There is not enough memory to perform Automatic Tape adjustment.

The region may be too small.

The Automatic Tape Adjustment facility is turned OFF for the current job, and processing continues.

Corrective Action: To implement automatic tape adjustment, increase the size of the region and restart Control-M. If there still is not enough memory, contact your local systems analyst.

CTM28ME OID=`orderId` TAPE UNIT `unitId` IS NOT DEFINED IN "UNITDEF" MEMBER

Explanation: During Automatic Tape Adjustment facility processing, a Tape Unit address was specified in the job log. However, this unit address was not defined in the UNITDEF member.

Resource adjustment for the Automatic Tape Adjustment facility of Control-M was unable to assign Tape Unit address unitId to a defined tape drive type.

The unknown tape drive is ignored for the job and processing continues.

Corrective Action: Check the UNITDEF member of the Control-M PARM library. Verify that the unit address is properly defined.

CTM28TE CNDJNL FILE SIZE DOES NOT MATCH CND FILE SIZE -- JOURNALING DISABLED

Explanation: The size of the IOA Conditions base image file differs from the size of the production Conditions file.

The IOA Conditions base image file CNDJNL is created after New Day processing and is used by the CTMRSTR restore utility. The size of this file must be identical to that of the production Conditions file.

The Control-M monitor deallocates the file and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W.

CTM28UE RESJNL FILE SIZE DOES NOT MATCH RES FILE SIZE -- JOURNALING DISABLED

Explanation: The size of the Control-M Resource file base image file differs from the size of the production Resource file.

The Control-M Resource file RESJNL is created after New Day processing and is used by the CTMRSTR restore utility. The size of this file must be identical to that of the production Resource file.

The Control-M monitor deallocates the file and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W.

CTM28VE FILE `fileName` DEALLOCATED. RESIZE FILE AND USE JOURNAL=ENABLE COMMAND TO REALLOCATE

Explanation: This message accompanies message CTM921E, CTM287E, or CTM288E and indicates that the problematic base image file has been deallocated.

Corrective Action: Define a file of correct size matching the corresponding production file and use the ENABLE command to allocate the new file to the Control-M monitor.

CTM290S MEMBER `memName` NOT FOUND

Explanation: The designated HELP member does not exist in the partitioned data set allocated to the CTMHELP DD statement. The CTMHELP DD statement should be allocated to the IOA MSG library.

Corrective Action: The designated member was on the original library. Restore it.

CTM291S INTERNAL ERROR - INVALID RETURN CODE `rc` IN HELP FACILITY

Explanation: Internal error in the IOA Online Help Facility.

Corrective Action: Contact BMC Customer Support.

CTM292E HELP MEMBER `memName` IS EMPTY

Explanation: The designated HELP member does not contain any data.

Corrective Action: Check whether the IOAHELP DD statement is allocated to the IOA MSG library. The original supplied member was not empty.

CTM293S INSUFFICIENT STORAGE FOR HELP MEMBER `memName`

Explanation: Not enough storage to enter the Online Help Facility for the memName member.

Corrective Action: Try to exit a few unnecessary screens using the END command. If it does not help, increase the region size of your logon procedure.

CTM294I UTILITY CTMBLT STARTED

Explanation: This information message indicates that the CTMBLT utility, which is used to create Control-M scheduling tables, has started.

Corrective Action: No action is required.

CTM295I BUILDING JOB CALENDARS STARTED

Explanation: This information message indicates that the CTMRCAL utility started to create the calendars. Calendars will be built for each job in the table, according to its date scheduling criteria.

Corrective Action: No action is required.

CTM296I BUILDING JOB CALENDARS ENDED OK

Explanation: This information message indicates that the CTMRCAL utility finished creating the calendars.

Corrective Action: No action is required.

CTM297E INVALID RETYPE PARAMETER VALUE - ‘S’ SUBPARAMETER REQUIRED

Explanation: The CTMRCAL utility ran with an invalid value for the RETYPE parameter. Valid values for the RETYPE parameter in the CTMRCAL utility are 0S, 1S, or 2S.

The utility terminates with a return code of 16.

Corrective Action: Correct the value of the RETYPE parameter, and rerun the CTMRCAL utility.

CTM298W THE IOAXREF DATABASE DOES NOT CONTAIN THE ITEM

Explanation: Information was requested from the IOAXREF database by pressing PF01/PF13, but no information is available, because the data collection process did not collect any information about this item.

Corrective Action: No action is required.

Messages CTM300 through CTM3xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM310I IOACPRM M2S=`ctm2sbs`

Explanation: This information message provides you with the name of the CTM2SBS file.

Corrective Action: No action is required.

CTM311I SMFID=`smfid` SYSTEM=`system_name` S2M=`sbs2ctm`

Explanation: This information message provides you with the SMFID, the system name, and the SBS2CTM file name.

Corrective Action: No action is required.

CTM312I SMFID `smfid` WAS {EXPLICITLY SPECIFIED | SELECTED BY DEFAULT}

Explanation: This information message indicates whether the FORMSUB3 utility was given an explicit SMFID with the SMFID= parameter or it selected the default SMFID, which is the SMFID of the LPAR under which it was running.

Corrective Action: No action is required.

CTM313I SMFID `smfid` WAS SUCCESSFULLY RESET

Explanation: This information message indicates that the FORMSUB3 utility has successfully reset an existing SMFID entry in the Monitor-to-Subsystem (M2S) communication file.

Corrective Action: For the reset to take effect, restart the Control-M monitor and the Control-O or CMEM monitor on the system with the SMFID.

Ensure that the Subsystem-to-Monitor (S2M) communication file of the SMFID is empty, otherwise, Control-M might re-execute old CMEM requests once it restarts.

CTM314I ADDING SMFID `smfid` WAS SUCCESSFUL

Explanation: This information message indicates that a new SMFID was added successfully to subsystem file M2S on the CMEM monitor by the FORMSUB3 job.

Corrective Action: To make the definition active, stop and restart the Control-M monitor and the Control-O or CMEM monitor on the system with the SMFID.

CTM315I {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS STARTED

Explanation: This information message indicates that the FORMSUB1 and FORMSUB2 utilities, which allocate and format Console Subsystem communications files, have started.

Corrective Action: No action is required.

CTM316I {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS ENDED

Explanation: This information message indicates that the FORMSUB1 and FORMSUB2 utilities, which allocate and format Console Subsystem communications files, have ended normally.

Corrective Action: No action is required.

CTM317S {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS FAILED

Explanation: The FORMSUB1 or the FORMSUB2 utility failed.

Corrective Action: Look for a previous error message which describes the cause of the error.

CTM318S OPEN OF DDNAME ddName FAILED

Explanation: Open of the ddName DD statement failed. Possible causes are:

The ddName DD statement is missing.
The ddName DD statement does not define a valid communication file.

Corrective Action: Correct the JCL of the formatting job.

CTM319S I/O ERROR OCCURRED WHILE BUILDING THE SUBSYSTEM COMMUNICATION DATASETS

Explanation: An I/O error occurred while the FORMSUB1 or FORMSUB2 utility was formatting a subsystem communication file.

Possible causes are:

The utility loaded old and incorrect IOACPRM installation parameters.
The file size defined in the IOACPRM member is different from the size that was defined in the JCL.
The JCL references an invalid data set.

Corrective Action: Check the JCL of the formatting job, and the location and content of the IOACPRM module.

CTM322S CTM2SBS FILE UPDATE IS NOT ALLOWED WHEN CONTROL-M MONITOR IS UP

Explanation: The FROMSUB3 utility cannot update the M2S data set while the Control-M monitor is up.

Corrective Action: Stop the Control-M monitor and rerun the utility.

CTM323S CTM2SBS FILE UPDATE IS NOT ALLOWED WHEN CMEM/CONTROL-O MONITOR IS UP

Explanation: The FROMSUB3 utility cannot update the M2S data set while the CMEM or Control-O monitor is up.

Corrective Action: Stop the CMEM or Control-O monitor on the LPAR with the SMFID that needs to be added or reset, and rerun the utility.

CTM325S SMFID `smfid` IS NOT DEFINED IN IOA INSTALLATION PARAMETERS

Explanation: The FORMSUB1 or FORMSUB2 utility is running under a CPU that was not defined in the IOACPRM parameters member.

Possible causes are:

The CPU in which the utility was run was not defined in IOACPRM.
The utility loaded an incorrect copy of the IOACPRM member.
The computer in which the utility was run is a multi-CPU computer, and the SID parameter in the SMFPRM xx member in SYS1.PARMLIB does not define all of the CPUs correctly.

Corrective Action: Do the following:

Check what CPUs were defined in IOACPRM.
Check where the IOACPRM member was placed.
If the IOACPRM definition seems to be correct, check the SMFID that was defined in SYS1.PARMLIB.
In a multi-CPU computer, issue the MVS command D M=CPU from the console to get a listing of all CPU serial numbers, and compare them with the PARMLIB definitions.

CTM326E MISSING/INVALID SUBSYSTEM PARAMETERS IN IOACPRM

Explanation: The FORMSUB1 or FORMSUB2 utility encountered one or more subsystem-related parameters in the IOACPRM member that were defined incorrectly or were not defined at all.

Corrective Action: Check the following parameter definitions in the IOACPRM member, and correct them if needed:

SUBSYS
CTM2SBS
CPUS

CTM328W SMFID `smfid` ENTRY IS ABOUT TO BE RESET, ENSURE THAT ITS SBS2CTM FILE IS EMPTY

Explanation: The FROMSUB3 utility found an entry for the SMFID in the M2S data set and is about to reset its contents. Resetting the M2S entry for an SMFID when the corresponding Subsystem-to-Monitor (S2M) communication file is not empty might cause Control-M to re-execute old CMEM requests when it restarts.

Corrective Action: Ensure that the corresponding S2M file is empty and then reply appropriately to the CTM329W message following this message.

CTM329W REPLY 'RESET' TO CONTINUE OR 'ABORT' TO STOP THE UTILITY

Explanation: While executing, the FORMSUB3 utility detected a potential problem. This message is accompanied by another message explaining the potential problem. The FORMSUB3 utility waits for a reply to this message.

Corrective Action: Type RESET or ABORT and press Enter, with the following results:

RESET – The utility execution proceeds with performing the modification.
ABORT – The utility execution is stopped without performing any modifications.

CTM334E READING DATEMEM (CALENDAR) `calName` FAILED

Explanation: Reading of the specified regular calendar or periodic calendar failed.

This message is issued in the following scenarios:

The calendar was specified in a job order or mission. The message is issued online and the job order or mission is not scheduled.
The calendar was specified in a Workload Policy rule, in the advanced scheduling parameters (that is, in a time period of Type 6). The message is issued to the Control-M monitor, and is followed by message CTMWLGE, which provides more details about the Workload Policy. The Workload Policy rule is ignored.
- Look for prior messages in the IOA Log that explain why the calendar could not be read.
- If the error occurred during the New Day procedure or a User daily, correct date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (DD statement DACHK), to the values of date-2 (or date-4).
- For a rerun of the same Daily, correct all the dates to the value of the day before. Beware of ordering the same job or mission twice during a rerun on the same day. We suggest that you delete the ordered jobs or missions from the Active Jobs file and then rerun the Daily again.
- If the previous abend happened after many jobs or missions had been ordered, BMC recommends a manual request (the CLIST CTMJOBRQ for jobs; the CLIST CTDMISRQ for missions).

Corrective Action: Recommended actions depend on where the calendar was specified:

Calendar specified in job order or mission:

Calendar specified in Workload Policy rule:

Correct the name of the calendar specified in the Workload Policy rule. Alternatively, define a new calendar with the specified name through the IOA Calendar Facility (Screen 8).

CTM337I `text`

Explanation: This information message indicates that at KeyStroke Language Report termination, the variable %MSG contained the text text.

It is usually a message which is intentionally issued as part of the report definition.

Corrective Action: No action is required.

CTM341S AUTOMATION LOG FILE LEVEL INCONSISTENT WITH LEVEL OF CONTROL-O

Explanation: The Automation Log file is not compatible with this release of Control-O. While opening an Automation Log file, the CTODVL program checks the file validity and usability. A mismatch was found between the release number of the Automation Log file and the release number of the program accessing it.

The action fails. The Automation Log file is not accessed.

Corrective Action: Do either or both of the following:

Check if the libraries specified in the STEPLIB and LINKLIST concatenation contain modules from different releases.
Check the Automation Log file data set name. If you are using an older release of the program or an old file, correct the error.

CTM342S ERROR OPENING AUTOMATION LOG FILE

Explanation: The CTODVL program was unable to open the Automation Log file.

The action fails. The Automation Log file is not accessed.

Corrective Action: Do any or all of the following

Check the definitions in the CTOPARM member.
Check the JCL for errors.
Check the data set name for the Automation Log file.

CTM343S AUTOMATION LOG DYNAMIC ALLOCATION ERROR `rc /rsn /dsn`

Explanation: The CTODVL program was unable to dynamically allocate the Automation Log file.

The action fails. The Automation Log file is not accessed.

Corrective Action: Do any or all of the following:

See documentation on dynamic allocation in the IBM Authorized Guide to Assembler Services for explanations of the return code (rc) and the reason code (rsn), and proceed accordingly.
Check the CTOPARM member.
Ensure that an Automation Log file exists for this CPU.

CTM344S AUTOMATION WRITE ERROR

Explanation: An I/O error occurred. The CTODVL program did not succeed in performing an I/O operation on the Automation Log file.

The action fails. The Automation Log file is not accessed.

Corrective Action: If you cannot determine the reason for this I/O error (for example, a disk failure), contact BMC Customer Support.

CTM345S ERROR EXECUTING RDJFCB

Explanation: The CTODVL program received a non-zero return code from the RDJFCB system service. The CTODVL program failed to read the JFCB of the dynamically allocated Automation Log file.

The action fails. The Automation Log file is not accessed.

Corrective Action: Contact BMC Customer Support.

CTM346S ABEND `abCode` INTERCEPTED WHILE PROCESSING THE AUTOMATION LOG

Explanation: The CTODVL program intercepted an abend while processing the Automation Log.

The action fails. The Automation Log file is not accessed.

Corrective Action: Contact BMC Customer Support.

CTM347S THE ALLOCATED AUTOMATION LOG FILE BELONGS TO ANOTHER CONTROL-O INSTALLATION

Explanation: The specified Automation Log file refers to another Control-O. While opening an Automation Log file, the CTODVL program checks the validity and usability of the file being opened. A mismatch was found between the current value specified for the CTOQNAME parameter in the CTOPARM member and the value of that parameter when the Automation Log file was formatted.

The action fails. The Automation Log file is not accessed.

Corrective Action: Do either or both of the following:

Ensure that you are not using load libraries that belong to another installation of Control-O.
Check if the CTOPARM member has changed.

CTM348S FILE NOT AN AUTOMATION LOG FILE

Explanation: The specified file is not a Control-O Automation Log file. While opening an Automation Log file, CTODVL checks the validity and usability of the file. The specified file was not an Automation Log file.

The action fails. The Automation Log file is not accessed.

Corrective Action: Check if the formatting of the Automation Log file ended successfully. If it failed, redefine (reformat) the Automation Log.

CTM349S AUTOMATION LOG FILE IS BEING FORMATTED IT CANNOT BE ACCESSED

Explanation: The specified Automation Log file is currently being formatted. While opening the Automation Log file, the CTODVL program checks the validity and usability of the file. The specified file has a status incompatible with the requirements of the program.

The action fails. The Automation Log is not accessed.

Corrective Action: Check if the formatting of the Automation Log file ended successfully. If it failed, redefine (reformat) the Automation Log.

CTM390S OPEN OF DDNAME `ddName` FAILED.

Explanation: Open of the ddName DD name failed. Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement does not exist.

Execution stops.

Corrective Action: Correct the JCL of the job and rerun.

CTM391S INVALID COMBINATION OF PARAMETERS ENCOUNTERED

Explanation: An invalid combination of parameters was specified for the CTMBLT Control-M utility.

Corrective Action: Correct the parameters and rerun the job. For information about valid parameter combinations, see the INCONTROL for z/OS Utilities Guide.

CTM391I NIGHT SCHEDULE REPORT STARTED

Explanation:This is one of two messages with the same ID, but different text.

This information message is the regular start message of the Night Schedule Report.

Corrective Action: No action is required.

CTM391I OVERNIGHT EXECUTION REPORT STARTED

Explanation:This is one of two messages with the same ID, but different text.

This information message indicates that processing of the Overnight Execution Report has begun.

Corrective Action: No action is required.

CTM392S OPEN OF DDNAME `ddName` FAILED

Explanation: The opening of the data set referenced by the ddName DD statement failed.

Possible causes are:

the DD statement referring to the data set referenced by the ddName DD statement is missing.
The data set referenced by the ddName DD statement does not exist.

Corrective Action: Correct the JCL and rerun.

CTM393I NIGHT SCHEDULE REPORT ENDED

Explanation:This is one of two messages with the same ID, but different text.

This information message is the regular termination message of the Night Schedule Report.

Corrective Action: No action is required.

CTM393I OVERNIGHT EXECUTION REPORT ENDED

Explanation:This is one of two messages with the same ID, but different text.

This information message indicates that processing of the Overnight Execution Report has ended.

Corrective Action: No action is required.

CTM393S RULE-BASED CALENDAR `rbc_calendar_name` NOT FOUND

Explanation: A job or table schedule definition contains a reference to an RBC that does not exist in the RBC library.

Corrective Action: Either define the RBC or reference the correct RBC from the job or the table.

CTM394S INVALID PARAMETER - `parm`

Explanation: An invalid parameter was specified to the report or utility.

If this message was issued during execution of the CTMBLT utility, it is followed by message BLT895I and/or BLT896I, which identify the problematic job, keyword, and value. This message may be issued by other utilities as well.

The report or utility stops executing with a condition code of 08 or 12.

Corrective Action: For the syntax of the parameter for the report or utility, see either the INCONTROL for z/OS Administrator Guide or the INCONTROL for z/OS Utilities Guide, as appropriate.

CTM395S INVALID PARAMETER FORMAT. "`yymmddhhmm`" EXPECTED

Explanation: The parameter that specifies the date and time does not use the right format.

The report stops executing with a condition code of 08 or 12.

Corrective Action: For the correct syntax of the report parameters, see the appropriate user guide.

CTM396S MULTIPLE USE OF PARAMETER. ONLY ONE OCCURRENCE IS ALLOWED

Explanation: A parameter that should be specified only once was specified multiple times.

Corrective Action: Delete the additional occurrences and rerun the job. For more information, see the chapter on job production parameters in the Control-M for z/OS User Guide.

CTM397S REPORT START TIME IS GREATER THAN REPORT END TIME

Explanation: The date and time specified as the report start time are greater than the date and time specified as the report end time.

The report will stop executing with a condition code of 08 or 12.

Corrective Action: Correct the parameters and rerun the report.

CTM398S MISSING OBLIGATORY REPORT/UTILITY PARAMETERS

Explanation: Parameters that are required for this report or utility are missing.

The report or utility stops executing with a condition code of 08 or 12.

Corrective Action: For the syntax of the report or utility parameters, see the appropriate user guide, the INCONTROL for z/OS Administrator Guide or the INCONTROL for z/OS Utilities Guide.

CTM399S REDUNDANT SORTBY PARAMETERS

Explanation: Too many sort parameters specified in a report command.

The report stops executing with a condition code of 08 or 12.

Corrective Action: For the correct syntax of the report parameters, see the appropriate user guide.

Messages CTM400 through CTM4xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM400S INVALID RETURN CODE FROM SORT = `rc`. CHECK THE SORT MANUAL

Explanation: A sort program that has been activated internally by a report ended with an unexpected return code (rc).

The report stops executing with a condition code of 08 or 12.

Corrective Action: To clarify the reason, see the documentation for the sort program and to the sort messages of the job.

CTM401I A KEYSTROKE REPORT STARTED

Explanation: This information message is a normal start message of a KeyStroke Language Report.

Corrective Action: No action is required.

CTM402I KEYSTROKE REPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that a KeyStroke Language Report ended successfully.

The report ended successfully from the point of view of report syntax and execution. A user may set the condition code to any condition code and send a message indicating otherwise. It is recommended to check the condition code as well (using the Control-M or Control-D facilities).

Corrective Action: No action is required.

CTM409E A KEYSTROKE REPORT ENDED WITH ERROR(S)

Explanation: A syntax or execution error occurred during processing of a report.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Look for the error in the report listing (the DAKSLOUT DD statement).

CTM411S OPEN OF DDNAME "DAPROG" FAILED

Explanation: This message is issued by the New Day procedure. The data set described by the DAPROG DD statement contains a list of programs to be activated by the New Day procedure. Possible causes are:

The DAPROG DD statement is missing.
The data set described by the DAPROG DD statement cannot be opened for sequential read.

For more details, see the chapter that discusses implementation issues in the appropriate user guide.

The New Day procedure stops executing.

Corrective Action: Correct the JCL for the job and rerun it.

CTM413E PROGRAM `pgm` WAS NOT FOUND

Explanation: The pgm program was not in the load list of the Daily subsystem. The DAPROG DD statement describes a data set that contains a list of programs to be activated as part of the Daily subsystem.

The Daily subsystem terminates with errors.

Corrective Action: Check whether IOA Load library is concatenated as STEPLIB to the Daily subsystem. Correct the JCL and consult your system programmer about running the Daily subsystem again.

CTM414E INVALID CONDITION CODE FOR PROGRAM `pgm`

Explanation: The pgm Control-M or Control-D internal program, which was activated by New Day processing, finished with return code higher than the maximum allowed in the program list. Positions 10 through 11 in the program list indicate the highest return code that is still considered OK for this program.

Corrective Action: No action is required.

CTM415I PROGRAM `pgm` IS BEING INVOKED

Explanation: This information message indicates that an internal Control-M or Control-D program was activated by New Day processing.

Corrective Action: No action is required.

CTM416I {CTMILY | CTDILY} ENDED

Explanation: This information message indicates that New Day processing is finished.

Corrective Action: No action is required.

CTM417E UNRECOGNIZED PARAMETER ON EXEC STATEMENT: `expression`

Explanation: The CTMTDAY procedure was executed with an unsupported or invalid NEWDAY parameter value expression. (For more information on the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”)

The CTMTDAY procedure is not executed.

Corrective Action: Correct and re-execute the CTMTDAY procedure.

CTM418E UNRECOGNIZED PARAMETER ON EXEC STATEMENT: `expression`

Explanation: The CTMTDAY procedure was executed with the following NEWDAY parameter: date. However, the date format or contents are invalid. For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”

The CTMTDAY procedure is not executed.

Corrective Action: Correct and re-execute the CTMTDAY procedure.

CTM419I PROCESSING MODE IS `mode`

Explanation: The CTMTDAY procedure was executed with one the following NEWDAY mode parameters:

ORDERONLY[,date]
FORMATONLY

Special NEWDAY processing will be performed according to the mode (FORMATONLY or ORDERONLY) specified in the procedure. For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”

Corrective Action: No response is required.

CTM41AW DATE IGNORED IN 'FORMATONLY' REQUEST: `xxxxxxx`

Explanation: The CTMTDAY procedure is executed with the following NEWDAY parameter:

FORMATONLY,xxxxxx

where the operator probably intended xxxxxx as a date value. (A date is not valid with the FORMATONLY mode.)

Special NEWDAY processing is performed according to the FORMATONLY mode, ignoring xxxxxx. (For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”)

Corrective Action: No response is required.

CTM422S OPEN OF USER DATE CONTROL-RECORD FAILED - DDNAME "DACHK"

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement).

This message is issued by the CTMCHK, CTDCHK, or CTBCHK program, which is usually activated by the New Day procedure.

Possible causes are:

The DACHK DD statement is missing.
The data set (member) described by the DACHK DD statement does not exist.

The CTMCHK, CTDCHK, or CTBCHK program ends with errors.

Corrective Action: Correct the JCL for the job or CLIST.

CTM424S INVALID ORIGINAL SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 1-6)

Explanation: Invalid original scheduling date in User Date Control Record (positions 1 through 6). This date should be earlier than the current installation working date. The valid format is ddmmyy or mmddyy.

Valid formats are:

ddmmyy
mmddyy

Possible causes are:

The previous run of the CTDCHK or CTMCHK program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (DD statement DACHK).

For more information, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure ends with errors.

Corrective Action: Correct your Date Control Record (DD statement DACHK).

CTM425S INVALID POST DATE IN USER DATE CONTROL-RECORD POSITIONS 67-72

Explanation: The contents of the Date Control Record for this Daily are invalid.

Valid formats are:

ddmmyy
mmddyy

This message usually indicates that the User Date Control Record was incorrectly modified. The date should be earlier than or equal to the original scheduling date defined in positions 1 through 6.

The New Day procedure ends with errors.

Corrective Action: Correct the Date Control Record (the DACHK DD statement).

CTM426W {GENERAL `|dailytype` } "DAILY" DID NOT RUN FOR `nnn` DAYS

Explanation:Highlighted, unrollable message.

The difference between the current working date and the original scheduling date (positions 1 through 6 in the Date Control Record) is more than one day. The New Day procedure has not run for nnn days. A New Day procedure is expected to run once a day.

This message is usually generated due to one of the following:

The computer has not been working for at least one day.
The Control-M or Control-D monitor has not been working for over 24 hours.
The contents of the Date Control Record were incorrectly modified for this Daily.
In the case of the New Day procedure, the computer may have been IPLed with the wrong date.
In the case of a User Daily, the Daily has not run for a few days.

The value of dailytype can be:

GENERAL for the New Day procedure
the job name of a regular User Daily job

The system action is determined by the process or procedure:

For the New Day procedure, this message appears highlighted on the operator console, together with messages CTM427W or CTD427W and CTM428W or CTD428W. If the operator answers YES, processing continues, taking the RETRO parameter of each job into consideration. If the operator answers NO, the New Day procedure stops executing with an error message.
For User Daily jobs, processing continues. Missions are selected according to the RETRO parameter.

Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.

CTM427W IS IT TRUE? (ANSWER "YES" OR "NO")

Explanation:Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK428W, CTM428W, or CTD428W messages. For more details, see the CHK426W message.

The General New Day procedure waits for the operator response.

CTM428W YOUR ANSWER IS:

Explanation:Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK427W, CTM427W, or CTD427W messages. For details, see the CHK426W message.

The New Day procedure waits for the operator response.

CTM429S {CTMCHK | CTDCHK | CTBCHK} ENDED WITH ERRORS

Explanation: The CTMCHK, CTDCHK, or CTBCHK program ended with errors. It is activated as part of the New Day procedure. IOA Log should contain an earlier message about the error.

The New Day procedure finishes executing with a condition code of 08.

Corrective Action: Check the IOA Log for error messages. If necessary, manually correct the Date Control Record (date-3 and date-5) to allow the next run of the User Daily job. For details, see the INCONTROL for z/OS Administrator Guide.

CTM430E POSSIBLE ABEND OF PREVIOUS DAILY RUN!

Explanation: A previous run of the same New Day procedure probably abended.

The New Day procedure terminates with errors.

Corrective Action: Correct the Date Control Record and rerun the New Day procedure. As a result of the last abend, dates 2, 3 and dates 4, 5, in the Date Control Record are not identical, but they should be. If you correct them to the values of date 3 or date 6, a rerun of the New Day procedure schedules all the jobs in the New Day procedure for the days after dates 2-5 until the date designated in date 1 (the current original scheduling date). Do not schedule the same job twice.

For more information, see the Control-D and Control-V User Guide.

CTM431I {CTMCHK | CTDCHK | CTBCHK} STARTED

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, started executing.

Corrective Action: No action is required.

CTM432I {CTMCHK | CTDCHK | CTBCHK} ENDED

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, ended normally.

Corrective Action: No action is required.

CTM433S DIFFERENCE BETWEEN CURRENT AND LAST RUN OF THIS DAILY IS NEGATIVE BY `num` DAYS

Explanation: The current working date in the computer is before the last original scheduling date of this New Day procedure.

This message is issued by the New Day procedure as a result of incorrect dates in the Date Control Record. For more details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

The New Day procedure stops executing with an error message.

Corrective Action: Correct the contents of the Date Control Record, and rerun the Daily. If this problem occurs under the New Day procedure, call your system programmer. The problem should be resolved immediately as the Control-M or Control-D monitor will not be able to operate. Check whether the computer has been IPLed with the correct date.

CTM434W THIS DAILY HAS ALREADY BEEN RUN TODAY

Explanation: The same New Day procedure has already been run today. The current working date in the computer is equal to the last original scheduling date - positions 1 through 6 in the Date Control Record (the DACHK DD statement).

For details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

Processing terminates with a return code of 8.

Corrective Action: Check the result of the run carefully for possible errors. If the Control-M or Control-D monitor is up and running, there is no need to run the New Day procedure, because it was probably started by accident. In any case, have your INCONTROL administrator look at the problem. It is possible that the computer was IPLed with the wrong date.

CTM435S OPERATOR RESPONDED "NO"

Explanation: The operator answered NO to the CHK428W, CTM428W, or CTD428W message.

The New Day procedure stops executing.

Corrective Action: Correct the problem, which is usually date-related, and rerun the New Day procedure.

CTM436S USER DATE CONTROL-RECORD IS EMPTY

Explanation: The data set described by the DACHK DD statement is empty (the New Day procedure).

The New Day procedure terminates with errors.

Corrective Action: Correct the JCL for the job and rerun it.

CTM437E INVALID DATE `date` SPECIFIED FOR `action`

Explanation: While processing a CMEM or Control-O request for the FORCEJOB, ADDCOND, or DELCOND action, the Control-M monitor encountered an invalid date.

Either the date was not a valid date, or it was not in the format specified by the DATETYP parameter in IOAPARM.

This message is followed by the WKJA59E or WKJC39E message, which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Make sure that the date format corresponds to the DATETYP parameter in IOAPARM.

CTM437I `date control record content`

Explanation: This informational message is generated when Newday processing is initiated. In place of date control record content, it displays the contents of the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK in the Newday procedure. For explanations of the dates displayed, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”

Corrective Action: No response required.

CTM438E INTERNAL ERROR ON THE COMMUNICATION FILE. A SNAP IS PRODUCED

Explanation: Control-M has detected mismatches in the communications file while processing SHOUT to Log records from Control-O.

The affected records are not written to the IOA Log. A snap dump is written to the DADUMP DD statement.

Corrective Action: There are two possible causes for this problem. The user response varies according to the cause of the problem.

Problem Cause	User Response
The number of subsystem-to-monitor file (S2M) records is not the same in the CTMPARM member and in the FORMSUB2 job, the file allocation and format job.	Compare the CTMCPU statements in CTMPARM with the FORMSUB2 job that was run for each system. If the problem persists, save the snap (dump), prepare the Control-M monitor full output, and contact BMC Customer Support.
The value of the SMODE parameter in CMMPARM or CTOPARM is not F.	Ensure that the SMODE parameter in CMMPARM or CTOOPARM is set to F.

CTM438W REPLY 'U' TO UPDATE DATEREC TO CURRENT DAY EXECUTION OR 'E' TO END

Explanation:Highlighted, unrollable message.

An error condition is detected while processing the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK in the Newday procedure. This message is usually preceded by another error message detailing the error encountered. Some reasons that this message might be issued are:

Invalid date date1 (see message CHK424S).
Invalid dates date2- date7 (see message CHK43BE).
The difference between the current working date and the date on which Newday was last run (date7) is negative (see message CHK433S).
The current working date is equal to date1 (Newday was already run--see message CHK434W).
The DATEREC member is empty (see message CHK436S).
An attempt was made to run the New Day procedure twice in the same day (see message FRM454E).
date7 is later than date1 (see message FRM455S).
date7 is more than 28 days in the past (see message FRS476S or JOB50S).
For an explanation of the dates in question, see INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”

The Newday procedure waits for the operator response.

Corrective Action: Review the preceding error messages to determine the actions necessary to correct the problem. If the problem can be corrected by setting the dates in the DATEREC record to the current working date, enter U. After Control-M automatically updates the DATEREC record, Newday processing resumes.

Otherwise, enter E and then correct the problem manually. For example, if the computer was IPLed with the wrong date, enter E, correct the computer date, and then reactivate the New Day procedure manually.

CTM439E MISSING JOB `jobName` IN TABLE `tableName` IN `lib`

Explanation: The jobName job was not found in the tableName table.

A FORCEJOB request for the jobName job in the tableName table failed.

This message is followed by the WKJA59E message, which contains more details about the error.

No additional action will be taken for the failed job order.

Corrective Action: Check that the job exists in the indicated scheduling table. For further actions, see the WKJA59E message.

CTM439W REPLY 'C' TO CONTINUE, 'U' TO UPDATE DATEREC TO CURRENT DAY EXECUTION, OR 'E' TO END

Explanation:Highlighted, unrollable message.

Following initiation of the Newday procedure, Control-M issued message CHK426W (warning that more than a day has passed since the previous run of Newday).

The Newday procedure waits for operator response.

Corrective Action: Examine the explanation of message CHK426W to help determine the situation and then respond according to one of the following situations:

If the computer has not been working for a few days (for example, a hardware failure or holiday), enter one of the following:
- C — All conditions in the IOA conditions file whose date corresponds to the intermittent days will be DELETED! Newday processing proceeds, using the existing dates in the Date Control Record (DATEREC). If RETRO is enabled in the scheduling definition, jobs for all intermittent days will also be ordered.
- U — Control-M automatically updates the Date Control Record (DATEREC) to the current system date and the Newday processing resumes. (Only jobs scheduled for the current working day will be ordered.)

If the computer was IPLed with the wrong date, enter E to end the Newday processing. Check and correct the date on the computer, and then restart the Newday procedure manually.
If the date on the computer is correct and was working the previous day, contact the INCONTROL administrator to check the cause of the problem.
If the ControlM monitor has been down for more than 28 days, the previous working date (the current working date minus 1) must be manually specified as date values 1 through 6.

CTM43AI NEWDAY EXECUTION CONTINUING WITH ODATE `odate`

Explanation: This informational message is generated when the response to message CTM438W or CTM439W was U. It informs the user that Newday processing continues, using odate as the current working date.

The Newday procedure resumes.

Corrective Action: No response needed.

CTM43BE DATE CONTROL RECORD CONTAINS AN INVALID DATE AT POSITION `col`

Explanation: During Newday initiation, an invalid date was detected in the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK. The date in error is in column col of the record. (For explanations of the dates displayed, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”)

Message CHK438 is generated.

Corrective Action: Respond to message CHK438.

CTM43CI CONTENTS OF DATE CONTROL RECORD:

Explanation: This message serves as a header for message CTM437I, which follows.

Corrective Action: No response needed.

CTM43DW REQUESTED ODATE IS `odate`

Explanation:Highlighted, unrollable message.

This message is issued in response to any of the following operator commands:

F CONTROLM,NEWDAY=hhmm [ ,date ]
F CONTROLM,NEWDAY=hhmm,ORDERONLY [ ,date]
F CTMTROLM,NEWDAY=hhmm,RERUN
S CTMTDAY,NEWDAY=date
S CTMTDAY,NEWDAY='ORDERONLY,date'

For more information, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Message CTM43GW is issued.

Corrective Action: Respond to message CTM43GW as instructed.

CTM43EW JOB `jobName` (OID=`orderId`) HUNG IN SUBMISSION

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job has been hung in submission status for several seconds.

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Consider manually forcing the job identified in the DO FORCEJOB command.

CTM43FI TRIGGER JOB `jobName` (`jobId`) NOT FORCED

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job is one of the following:

a cyclic job found on the Active Jobs file
in Hung in Submission status
currently being handled by one of the local sysplex monitors

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Do the following:

Check to see if JES is hung. If it is, find out why, and address that problem.
Consider how to act in relation to
the jobName job, that is, the job that is hung
the job identified in the DO FORCEJOB command

CTM43GW REPLY 'C' TO CONTINUE OR 'E' TO END

Explanation:Highlighted, unrollable message.

Upon entry of the F CONTROLM,NEWDAY=hhmm,date command, message CTM43DW displayed the ODATE entered. The current message asks the operator to either confirm that the Newday procedure continue with the specified ODATE or not continue.

The Newday procedure waits for operator response.

Corrective Action: One of the following responses:

C --confirm Newday execution using the ODATE displayed by message CTM43DW. (Dates in the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK are not modified.)
E --cause the NEWDAY command to be ignored.

CTM440I CONTROL-M MONITOR IS READY TO RECEIVE CMEM REQUESTS

Explanation: This information message indicates that the CMEM facility in the Control-M monitor was successfully initialized and the Control-M monitor is ready to accept requests from Control-O or from CMEM subsystem functions.

Corrective Action: No action is required.

CTM441E CONTROL-M MONITOR CMEM FACILITY IS DEACTIVATED AS A RESULT OF A FAILURE

Explanation:Highlighted, unrollable message.

A severe error has occurred while processing requests from one of the following:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB

Information about the error that caused the deactivation of the On Spool Jobs Facility was previously displayed on the operator console.

Control-M monitor stops processing requests from:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB.

Other parts of Control-M monitor will not be affected.

Corrective Action: Look for previous error messages. Correct the error, shut down the Control-M monitor and start it again.

CTM442E ERROR WHILE LOADING CTMJOB\CTMMEM FOR CMEM PROCESSING

Explanation:Highlighted, unrollable message.

The CTMJOB or CTMMEM modules could not be loaded by the Control-M monitor for one of the following reasons:

There was insufficient storage.
The modules could not be found in the libraries specified in the STEPLIB DD statement or in the Linklist.

Control-M monitor will not process requests from:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB

Corrective Action: Correct the error, shut down the Control-M monitor and start it again.

CTM443E OPEN ERROR OCCURRED DURING CMEM PROCESSING, DSN=`dsn`

Explanation: The Control-M monitor has encountered an open error while processing CMEM or Control-O requests.

An open error occurred on one of the Control-M communication data sets. Possible causes are:

An incorrect communication file was defined.
A security product failed the OPEN request.

Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Do the following:

Check that CTMPARM points to the correct communication file.
Check the dsn communication file, and make sure that it is properly defined, formatted, and cataloged.
Make sure that no restrictions are imposed by MVS, a security package, and so on.
Correct the error, shut down the Control-M monitor and start it again.

CTM444E I/O ERROR OCCURRED DURING CMEM PROCESSING, DSN=`dsn`

Explanation: The Control-M monitor has encountered an I/O error while processing CMEM or Control-O requests.

An I/O error occurred on one of the Control-M communication data sets.

Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Do the following:

Check the dsn communication file, and make sure that it is properly defined and formatted.
Check that CTMPARM points to the correct communication file. If the file and CTMPARM appear correct:

Check the MVS LOGREC file for a physical disk error.
Reallocate and reformat the dsn communication file.

After correcting the error, stop the Control-M monitor and start it again.

CTM445E DYNAMIC ALLOCATION ERROR, RC=`rc`, REASON CODE=`rsn`, DSN=`dsn`

Explanation: The Control-M monitor has encountered a dynamic allocation error while processing CMEM or Control-O requests.

A dynamic allocation error occurred on one of the Control-M communication data sets. Possible reasons for this failure include:

The dsn communication file is not cataloged on the correct disk.
The dsn communication file is cataloged in a catalog which cannot be accessed by the Control-M monitor.
The wrong communication file name, or no communication file name, was specified in IOACPRM.
The MVS allocation exit failed the allocation request.
A security product failed the allocation.

For information about the return code (rc) and the reason code (rsn) see the IBM manual MVS Programming: Authorized Assembler Services Guide. Reallocate and format or re-catalog the file if necessary.

The Control-M monitor stops processing CMEM and Control-O requests.

Corrective Action: Check the definitions in CTMPARM, and correct them as necessary. After the error is corrected, stop the Control-M monitor and start it again.

CTM446W SYSPLEX TABLE MISSING - SYSTEM LOGGER INTERFACE DISABLED

Explanation: Control-M attempted to read the Sysplex Table and failed.

Control-M could not find the Sysplex Table or encountered errors while reading the Sysplex Table. This could be due to one of the following:

The Sysplex Table is not present in the STEPLIB concatenation of load libraries.
The Sysplex Table has an invalid internal format.
The Sysplex Table has no valid, active table entries.

Control-M attempts to allocate, open and use the subsystem-to-monitor (S2M) communication files to implement CMEM-Control-M communication.

Corrective Action: Check why the Sysplex Table is not in the load library or has an invalid format. Correct the problem and recycle Control-M.

CTM447E SYSTEM LOGGER REQUEST `req` FAILED: R15=`r15` RETURN=`rc` REASON=`rsn`

Explanation: A System Logger request failed.

One of the following System Logger requests failed:

Request	Explanation
DEFCFS, IXGINVNT	Define coupling facility structure
DEFLGS, IXGINVNT	Define log stream
CONLGS, IXGCONN	Connect to log stream
WRITEL, IXGWRITE	Write a log stream log block
BRWSEL, IXGBRWSE	Browse a log stream log block
DELETL, IXGDELET	Delete a log stream log block
DISLGS, IXGCONN	Disconnect from log stream
DELLGS, IXGINVNT	Delete log stream
DELCFS, IXGINVNT	Delete coupling facility structure

r15 is provided by Control-M and is one of the following:

R15	Explanation
08	Minor System Logger request error
12	Intermediate System Logger request error
16	Major System Logger request error
20	Permanent System Logger request error
24	Internal Control-M error
28	Operating system does not support System Logger interface
32	Internal Control-M error

The return code rc and the reason code rsn are documented in the IBM manual MVS Programming: Assembler Services Reference. Check that publication for the system action relevant to the return code and reason code in the message. Each System Logger request is in a separate section of the guide. The return and reason codes are described in the topic “Return and Reason Codes” for each System Logger request.

Corrective Action: When a System Logger error occurs, check the system log or the console that displays error messages for the IXGLOG System Logger address space for further details. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM448E CMEM LOST `num` TRANSACTIONS FROM THE CPU WITH SMFID=`smfid`

Explanation: Control-M was down, or stopped processing CMEM and Control-O requests.

During the time that the Control-M monitor was inactive (due to a problem or daily maintenance), the CMEM subsystem functions or Control-O wrote to the Communication file more records than its size allowed. Therefore the oldest CMEM or Control-O requests were overwritten and lost.

No additional action is performed.

Corrective Action: Take one of the following steps in order to prevent this situation from recurring:

Make sure that the Control-M monitor will not remain inactive for a long time.
Increase the size of the Communication files.

CTM449E MISSING TABLE `tableName` IN `lib`.

Explanation: The tableName table was not found in the specified library, or the table was empty.

A FORCEJOB request for a scheduling table or a specific job failed.

This message is followed by the WKJA59E message, which contains more details about the error.

This message may also be issued in the following situations:

the library in which the member resides is being compressed
the disk volume on which the library resides on is being reorganized or defragmented

These actions should be avoided during job ordering periods.

No additional action is taken for the failed job or table order.

Corrective Action: Check that the table exists in the indicated library. For further actions, see the WKJA59E message.

CTM44AI SYSTEM LOGGER INTERFACE ACTIVATED

Explanation: This information message indicates that Control-M has successfully initialized the System Logger interface.

Control-M can now begin communicating with CMEM.

Corrective Action: No action is required.

CTM44BE SYSTEM LOGGER NOT SUPPORTED ON THIS OPERATING SYSTEM

Explanation: Control-M cannot utilize the System Logger interface on the host operating system.

The host operating system does not support the System Logger interface.

The CMEM facility is deactivated.

Corrective Action: Change the parameters in the appropriate IOA PARM library members to use the Subsystem-to-Monitor (S2M) communication files to implement communication between CMEM or Control-O and Control-M.

CTM44CI ATTEMPTING TO RECONNECT TO MVS SYSTEM LOGGER

Explanation: Control-M has detected an MVS System Logger error, and is attempting to reconnect to the MVS System Logger.

Control-M tries several times to reconnect to the MVS System Logger.

Corrective Action: No action is required.

CTM44DE ATTEMPT TO RECONNECT TO MVS SYSTEM LOGGER FAILED

Explanation: Control-M detected an MVS System Logger error, and attempted several times to reconnect to the MVS System Logger, without success.

Corrective Action: No action is required.

CTM44EE MVS SYSTEM LOGGER ERROR - CMEM FEATURE DISABLED

Explanation: Control-M detected an MVS System Logger error. Either this error was so severe as not to be recoverable, or Control-M attempted several times to reconnect to the MVS System Logger, without success.

Control-M has stopped attempting to reconnect to the MVS System Logger. The CMEM facility is deactivated.

Corrective Action: If and when the MVS System Logger becomes operational, stop and restart the Control-M monitor.

CTM44FI TRIGGER JOB `jobName` (`jobId`) FOUND ON AJF. JOB NOT FORCED

Explanation: This information message refers to a Control-O or CMEM ON JOBARRIV or ON JOBEND rule with a DO FORCEJOB command. The job used to trigger this DO FORCEJOB was found on the Active Jobs file.

Control-M does not order and submit the DO FORCEJOB.

Corrective Action: No action is necessary.

CTM44GA REPLY "ABORT", "CONTINUE", OR "RETRY"

Explanation: After displaying a CMEM-related error message, Control-M disables communication between CMEM or the Control-O monitor and Control-M. Control-M then displays message CTM44GA giving the user the choice of how to continue.

The subtask is suspended until a response to this message is received.

Corrective Action: Enter one of the following responses:

ABORT - terminate the Control-M monitor
CONTINUE - disable communication between CMEM or the Control-O monitor and Control-M, but allow the Control-M monitor to continue processing
RETRY - retry the failed dynamic allocation request

CTM450S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". PLEASE CHECK THE CONTROL-M MESSAGES AND CODES MANUAL

Explanation: The New Day procedure was unable to open the file pointed to by the DAJOBLST DD name for update.

After reading the list of CDAM files to be deleted from the file pointed to by DAJOBLST, the New Day procedure empties the file and writes one record indicating that there are no more entries. Possible causes are:

file not found on the disk
incorrect security authorization

Corrective Action: Determine the reason for the problem, and correct it. Reinstall Control-M/Restart.

CTM452I FORMATTING OF `activeFile` FILE STARTED

Explanation: This information message indicates that the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) is currently being formatted.

Corrective Action: No action is required.

CTM453S OPEN OF DATES CONTROL-RECORD FAILED. DDNAME "DACHK"

Explanation: Open of the Control-M or Control-D Date Control record failed in the DACHK DD statement). This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program as part of the New Day procedure. Possible causes are:

The DACHK DD statement is missing.
The data set (member) described by the DACHK DD statement is not the Control-M or Control-D Date Control Record.

Corrective Action: Correct the JCL for the New Day procedure.

CTM454E FOR4MAT (`format_pgm`) ALREADY RUN TODAY

Explanation: An attempt was made to run the New Day procedure twice in the same day. The New Day procedure issues format_pgm. This program should not run more than once a day.

Possible values of format_pgm:

CTMFRM - formats the Active Jobs file (AJF) in Control-M
CTDFRM - formats the Active Missions file (AMF) in Control-D

The AJF or AMF is not formatted, but the New Day procedure continues to execute other programs in the program list.

Corrective Action: Check why the New Day procedure is being run twice, and whether jobs or missions were accidentally ordered twice because the General Date Control Record was erroneously modified.

CTM455S LAST FORMAT DATE GREATER THAN ORIGINAL SCHEDULING DATE IN CONTROL-M DATES CONTROL-RECORD

Explanation: The last format date is later than the original scheduling date in the Control-M Date Control record or the Control-D Date Control record. The New Day procedure issues this message. For more details, see the appropriate user guide.

New Day processing stops.

Corrective Action: Correct the Control-M or Control-D Date Control record, and run the New Day procedure again.

CTM456S OPEN OF `activeFile` FILE FAILED. DDNAME "`ddName` "

Explanation: Open of the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) defined in the ddName DD statement failed. The New Day procedure calls the program that issues this message.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement is not the AJF or the AMF.
The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

CTM457S OPEN OF BACKUP FILE FAILED. DDNAME "DABKUP"

Explanation: Open of backup file for the Active Jobs file (AJF) or Active Missions file (AMF) defined in the DABKUP DD statement failed. This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

Possible causes are:

The DABKUP DD statement is missing.
The data set described by the DABKUP DD statement is not the Active Jobs Backup file or Active Missions Backup file.
The data set described by the DABKUP DD statement is the Control-M Active Jobs Backup file or the Control-D Active Missions Backup file, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

CTM458S ERROR IN `activeFile` - RECORD 0. SHOULD BE FORMAT OR FREE

Explanation: Record 0 of the activeFile file contains incorrect data. This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Possible causes are:

The activeFile file is corrupt.
The data set described by the DACKPT DD statement (Control-M) or the DAAMF DD statement (Control-D) is not the activeFile file, but is very similar to it.

Program execution stops with a condition code of 08.

Corrective Action: Check the validity of the data set described by the DACKPT or DDAMF DD statement. If necessary, correct the JCL, and rerun the New Day procedure.

If activeFile is corrupt, use a standard copy utility, like IEBGENER, to copy activeFile, and send it to BMC Customer Support. If necessary, run the FORMCKP utility to reformat the Active Jobs file or the CTDFRAMF utility to reformat the Active Missions file. However, these utilities also erase all the jobs or missions in the respective files.

CTM459I `activeFile` IS RESTORED FROM BACKUP

Explanation: This information message indicates the beginning of a rerun of the New Day procedure after an earlier abend during the format of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

activeFile is restored from the appropriate backup file, and processing continues normally.

Corrective Action: No action is required.

CTM460S DATE CONTROL-RECORD IS EMPTY

Explanation: The DACHK DD statement describes an empty data set or member. For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M or Control-D Date Control Record and run the New Day procedure again.

CTM461S ERROR WHILE FORMATTING IOA CONDITIONS FILE

Explanation: I/O error while formatting the IOA Conditions file.

Possible causes are:

The data set described by the DARESF DD statement is not the IOA Conditions file.
An I/O error occurred while reading the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct and run the New Day procedure again. In case of an I/O error, you may need to recreate the IOA Conditions file. This erases all the conditions from the file.

CTM462S INVALID LAST FORMAT DATE IN DATE CONTROL RECORD

Explanation: Invalid format of last format date in the Date Control Record. This message is issued by the CTMFRM or CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy. Possible causes are:

Someone has modified the contents of the Date Control Record incorrectly.
The record described by the DACHK DD statement is not the Control-M Date Control Record or the Control-D Date Control Record.

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the Daily Subsystem, and rerun it.
Correct the format date in the Date Control Record, and rerun the New Day procedure.

CTM463S INVALID ORIGINAL SCHEDULING DATE IN DATE CONTROLRECORD

Explanation: Invalid original scheduling date in the Date Control Record. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy.

Possible causes are:

The record described by the DACHK DD statement is not the Control-M General Date Control Record or the Control-D General Date Control Record.
Someone modified the contents of the General Date Control Record incorrectly.

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the New Day procedure and rerun it.
Correct the original scheduling date in the General Date Control Record and rerun the New Day procedure.

CTM464S FILE ALLOCATED TO DDNAME "`ddName` " IS NOT YOUR `activeFile`

Explanation: The data set described by the ddName DD statement is not the file specified by activeFile.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

The data set described by the ddName DD statement is not the AJF or the AMF.
The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the problem in the data set name indicated by the ddName DD statement, and run the New Day procedure again.

CTM465S FILE ALLOCATED TO DDNAME "DABKUP" IS NOT A BACKUP OF `activeFile`

Explanation: The data set described by the DABKUP DD statement is not a backup of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Possible causes are:

The data set described by the DABKUP DD statement is not the AJF or the AMF.
The data set described by the DABKUP DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M Date Control Record and rerun the affected procedure.

CTM466S NEED MORE MEMORY TO FORMAT `activeFile`

Explanation: There is not enough memory to format the activeFile file.

In Control-M, activeFile is the Active Jobs file (AJF) or the History file (HST).

In Control-D, activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08. Control-M and Control-D monitors will not start after this error.

Corrective Action: To enable monitors to start, set REGION=0M and rerun the affected procedure. If the REGION is already set to 0M, then ensure that the MVS exit IEFUSI allows sufficient virtual storage memory to be allocated above the 16M line. For example, since each record of the above files requires 1024 bytes of storage, a file containing 200,000 records requires 200M of storage above the line.

CTM468I FORMATTING OF `activeFile` ENDED

Explanation: This information message indicates that the New Day procedure finished formatting the activeFile file. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Corrective Action: No action is required.

CTM469S OPEN OF IOA LOG FILE FAILED

Explanation: Open of IOA Log file failed. The message is produced by the New Day procedure. Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL and run the Daily again.

CTM470S ERROR WHILE FORMATTING THE `activeFile`, FILE WAS NOT FORMATTED

Explanation: An error occurred during formatting of the activeFile file. The New Day procedure issues this message.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08.

Corrective Action: Look for a previous message that describes the type of error. Correct it and rerun the New Day procedure.

CTM471S OPEN OF IOA CONDITIONS FILE FAILED. DDNAME "DARESF"

Explanation: Open of IOA Conditions file failed (the DARESC DD statement). This error message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day Procedure. Possible causes are:

The DARESC DD statement is missing.
The data set described by the DARESC DD statement is not the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the Daily Subsystem and rerun it.

CTM472S OPEN OF IOA SYNCHRONIZATION FILE FAILED. DDNAME "DASINC"

Explanation: Open of IOA Synchronization file failed in the DASINC DD statement. This error message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day procedure. Possible causes are:

The DASINC DD statement is missing.
The data set described by the DASINC DD statement is not the IOA Synchronization file.
The data set described by the DASINC DD statement is an IOA Synchronization file, but it is of another Control-M or Control-D monitor, or of a different Control-M or Control-D version.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure and rerun it.

CTM475S INVALID LAST FORMAT DATE IN DATE CONTROL-RECORD

Explanation: Invalid format of last format date in the Date Control record. This message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy. Possible causes are:

The record described by the DACHK DD statement is not the Control-M or Control-D Date Control record.
Someone modified the contents of the Date Control Record incorrectly.

For more information, see the sections on NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

Correct the JCL for the New Day procedure, and rerun it.
Correct the format date in the Date Control Record.

CTM476S LAST FORMAT DATE IN DATE CONTROL-RECORD WAS MORE THAN 28 DAYS AGO

Explanation: The difference between the current working date (date-1) and the last format date in the Date Control Record is greater than 28 days. Possible causes are:

Someone modified the contents of the Date Control Record incorrectly.
The Control-M or Control-D monitor has not been used for more than 28 days. Correct the date to “yesterday.”

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the Date Control Record in the DACHK DD statement, and rerun the Daily Subsystem.

CTM477S FILE ALLOCATED TO DDNAME "DASINC" IS NOT YOUR IOA SYNCHRONIZATION FILE

Explanation: The data set described by the DACNDF DD statement is not the required IOA Conditions file. The CTMFRM or CTDFRM program issues this error message as part of the New Day procedure when one of the following occurs:

The file allocated to the DACNDF DD statement is not the IOA Conditions file.
The file allocated to the DACNDF DD statement is an IOA Conditions file, but for a different version, or for a different Control-M or Control-D monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure and rerun it.

CTM478I FORMATTING OF IOA CONDITIONS FILE STARTED

Explanation: This information message indicates that the formatting of the IOA Conditions file was started by the New Day procedure. The CTMFRM or CTDFRM program clears all the conditions from the day following the last formatting date until the next working date, that is, the first date in the General Date Control Record.

Corrective Action: No action is required.

CTM479I FORMATTING OF IOA CONDITIONS FILE ENDED

Explanation: This information message indicates that the New Day procedure formatted the IOA Conditions file. The CTMFRM or CTDFRM formatting program called by the New Day procedure ended.

Corrective Action: No action is required.

CTM480S ERROR WHILE FORMATTING IOA CONDITIONS FILE.

Explanation: An error occurred while formatting the IOA Conditions file by the New Day procedure. An earlier error message describes the type of error.

Program execution stops with a condition code of 08.

Corrective Action: Check the IOA Log or the utility output for a previous message concerning the error.

CTM481S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". DELETE OF ARCHIVED SYSOUTS FAILED

Explanation: Open for the DAJOBLST file failed during the execution of the New Day procedure.

This error message is issued by the CTMDAS program, which is usually activated as part of the New Day procedure. The DAJOBLST DD statement is probably missing.

Program execution stops with a condition code of 16.

Corrective Action: Make sure that CTR (CONTROL-M/Restart) is set to Y in IOAPARM, in the PRODUCTS section.

CTM482S INIT OF RES FILE FAILED

Explanation: The New Day procedure failed to initialize the Control-M Resources file. An accompanying message identifies the reason for the failure.

The New Day procedure stops with an error code of 12.

Corrective Action: Check the accompanying message to determine the reason for the problem, and correct the problem accordingly.

CTM484I FORMAT OF RESOURCE FILE HAS STARTED

Explanation: This information message indicates that the Control-M Resources file is currently being formatted. This procedure is usually part of the New Day procedure.

Corrective Action: No action is required.

CTM488I FORMAT OF RESOURCE FILE HAS ENDED

Explanation: This information message indicates that formatting of the new Control-M Resources file is complete and the resource is available.

Corrective Action: No action is required.

CTM48CI Preceding clear history did not complete. Process may run longer.

Explanation: During the AJF compression process, Control-M detected that the last clear process of the history file (HST), which followed the preceding AJF compression, did not successfully complete or did not run at all.

The AJF compression process continues, but the process might take longer than usual to complete.

Corrective Action: Usually the issue is resolved automatically by the next run of the history clear process, which either runs by default as part of the Control-M Daily run (step CLRHIST, program CTMHSC) or as a standalone utility (CTMHCLN). Make sure that the clear history process is included in the Control-M Daily run, or that the CTMHCLN utility runs on a daily basis. Make sure the process ends without errors.

CTM491S OPEN OF DDNAME "DA34F" FAILED

Explanation: Open of the file containing the operator commands failed (the DA34F DD statement). The CTM34F program is usually activated as part of the New Day procedure. Possible causes are:

The DA34F DD statement is missing.
The data set described by the DA34F DD statement does not exist, or cannot be opened for sequential read, or record length is not 80.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL of the job. For more information, see the INCONTROL for z/OS Administrator Guide.

CTM493I {IOA34F | CTM34F} STARTS EXECUTING COMMANDS

Explanation: This information message indicates that the IOA34F or CTM34F program is ready to execute the operator commands from the supplied list. This program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM495I {IOA34F | CTM34F} FINISHED EXECUTING COMMANDS

Explanation: This information message indicates that the IOA34F or CTM34F program finished executing the list of operator commands. This program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM496E PROGRAM {IOA34F | CTM34F} IS NOT APF-AUTHORIZED

Explanation: The MVS operating system rejected the operator commands issued by the CTM34F program. The CTM34F program should reside in an APF-authorized library and must be link edited with the AC attribute set to 1 in order to be able to issue operator commands.

The issued commands are rejected. The CTM34F program terminates with a condition code of 08.

Corrective Action: The IOA34F or CTM34F program already has the AC attribute set to 1. The INCONTROL administrator should verify that the library in which CTM34F resides is APF-authorized.

CTM497S VM HOST NOT AVAILABLE

Explanation: An attempt was made to issue a VM command while MVS was not running under VM. A command whose name starts with the prefix CP was passed to the IOAOPR utility. This prefix signals to Control-M that the command is intended for a host VM operating system, but the IOAOPR utility detected that no VM environment was available.

Corrective Action: Verify that a VM environment is running before issuing VM CP commands.

CTM498S LOAD OF MODULE IOAVMC FAILED

Explanation: The IOAOPR utility could not load the IOAVMC module.

Corrective Action: Verify that the IOAVMC module resides in the STEPLIB library.

CTM499E INVALID VALUE "val " FOR "RESPONSE" KEYWORD

Explanation: The user entered a value other than YES or NO for the Response keyword.

Corrective Action: Correct the entry to either YES or NO.

Messages CTM500 through CTM5xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM501I CTMJOB STARTED

Explanation: This information message indicates that the CTMJOB program has started.

The CTMJOB program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM502S OPEN OF SCHEDULE DATA FAILED. DDNAME "DAJOB"

Explanation: Open of scheduling tables data set failed (the DAJOB DD statement).

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure, and could be due to one of the following:

The DAJOB DD statement is missing.
The data set described by the DAJOB DD statement cannot be opened for sequential read or the record length is not 80.

The CTMJOB program will end with errors.

Corrective Action: Correct the JCL for the job/CLIST.

CTM502E CONVCON INVALID RC=`rc` REASON =`rsn` CONSOLE ID=`consId` CONSOLE NAME=`consName`

Explanation: A command was issued to a console specified by CONSOLE ID= consId or CONSOLE NAME= consName, and the CONVCON service return code is not 0. When a command is issued to a console, the CONVCON service is called to verify the console. The return code from the CONVCON service that validates the console response is rc.

The command may be rejected depending on the CONVCON action.

Corrective Action: To determine the reason for the error, see the Authorized Assembler Services Guide. Correct the error, and reissue the command.

CTM503S OPEN OF USER DATE CONTROL-RECORD FAILED - DDNAME "DACHK"

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). Issued by the CTMJOB program which is usually activated by the New Day procedure.

Possible causes are:

The DACHK DD statement is missing.
The data set (member) described by the DACHK DD statement does not exist.

The CTMJOB program will end with errors.

Corrective Action: Correct the JCL for the job/CLIST.

CTM504S USER DATE CONTROL-RECORD IS EMPTY

Explanation: The data set described by the DACHK DD statement is empty.

The CTMJOB program will end with errors.

Corrective Action: Correct the JCL for the job/CLIST.

CTM505S PREVIOUS RUN OF CTMJOB DID NOT FINISH OK

Explanation: A previous run of the CTMJOB program did not finish OK. This program is usually activated as part of the New Day procedure.

Date-2 and date-3 (or date-4 and date-5) of the Date Control Record are not equal. Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has modified the contents of the User Date Control Record (the DACHK DD statement).

For more information, see the Control-M chapter in the INCONTROL for z/OS Administrator Guide.

The CTMJOB program ends with errors.

Corrective Action: Change date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement) to the values of date-2 (or date-4).

To rerun the same Daily, correct all the dates to the value of the day before. Be careful not to order the same job twice during a rerun on the same day. BMC recommends that you delete the ordered jobs from the Active Jobs file and then run the Daily again.

If the previous abend happened after many jobs had been ordered, BMC recommends requesting the remaining jobs manually by means of CLIST CTMJOBRQ.

CTM506S SCHEDULING FAILED FOR MEMBER `memName`

Explanation: Scheduling failed for the memName member. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

The IOA Log or the job output should contain an additional message concerning the reason for failure.

The job order of member is not placed in the Active Jobs file. Depending on the severity of the problem, the New Day procedure will either continue to the next job order or terminate with the condition code 08.

Corrective Action: Check the IOA Log or the job’s output for the reason.

CTM507S LAST MONTHLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATE

Explanation: Invalid last monthly Scheduling Date.

The last monthly Scheduling Date (positions 18-23) in the User Date Control Record is greater than the current original Scheduling Date (positions 1-6). Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has modified the contents of the User Date Control Record (DD statement DACHK).

For more details, see the INCONTROL for z/OS Administrator Guide.

The CTMJOB program will end with errors.

Corrective Action: Correct the User Date Control Record (the DACHK DD statement).

CTM508S LAST MONTHLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK IT

Explanation: The last monthly scheduling date is more than 28 days ago.

Possible causes are:

The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to “yesterday.”
Someone has modified the contents of the General Date Control Record incorrectly.

For more details, see the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the User Date Control Record (the DACHK DD statement).

CTM509S INVALID YEAR IN ORIGINAL SCHEDULING DATE OF USER DATE CONTROL-RECORD

Explanation: Invalid year in the original scheduling date of the User Date Control record. This year is not yet supported by Control-M.

The CTMJOB program will end with errors.

Corrective Action: Please correct the year field (the DACHK DD statement).

CTM510S SEVERE ERROR IN THE SCHEDULING DATA - NOTIFY THE IOA ADMINISTRATOR

Explanation: Severe error in the scheduling data.

This message is produced when the scheduling tables (described by the DAJOB DD statement) contain erroneous data. This can be due to the following:

The contents of the table were incorrectly modified using an editor or program, and the format of the table is invalid.
Internal error in Control-M.

'The program terminates with a condition code of 08.

Corrective Action: Try to restore the table to its original state. If you cannot, prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

If it is a batch Daily using a permanent Date Control Record, correct the contents of the record before running the Daily again. If issued during a User Daily or New Day procedure, see message CTM505S for further details.

CTM513I SCHEDULE FAILED FOR `num` CONTROL-D CATEGORIES

Explanation: This information message indicates that num Control-D decollating missions categories were not found in the library allocated to the DAREPMIS DD statement.

The Control-M New Day procedure continues processing.

Corrective Action: Look at the IOA Log for the failed categories and associated reasons for failure.

CTM514S INSUFFICIENT STORAGE FOR THE JOB

Explanation: Insufficient storage for processing the job order.

The program terminates with a condition code of 08.

Corrective Action: Increase the REGION size of the task which issued the request.

CTM515S ERROR IN SCHEDULING DATA - TOO MANY CARDS FOR ONE JOB

Explanation: Too many statements for one job. Scheduling data used to describe the job order are too large to be processed by Control-M.

The job order will not be placed on the Active Jobs file. The New Day procedure will terminate with a condition code of 08.

Corrective Action: Check the contents of the job order, using the Online Scheduling Facility, and remove unnecessary scheduling data. Prepare the Control-M monitor full output and contact BMC Customer Support.

CTM516S ERROR IN SCHEDULING DATA - FIRST CARD SHOULD START WITH "D"

Explanation: Invalid scheduling data in the first data set described by the DAJOB DD statement. The first statement of valid scheduling table should start with D.

Possible causes are

The data set described by the DAJOB DD statement is not a scheduling table.
The scheduling data has been manually modified incorrectly.

The CTMJOB program ends with errors.

Corrective Action: Check contents of the data set described by the DAJOB DD statement and if the problem is not solved, check to find the person who may have manually changed the scheduling data.

CTM517S SCHEDULING DATA NOT AVAILABLE

Explanation: The DD statement pointing to the job scheduling tables is empty or missing.

The program ends with errors.

Corrective Action: Correct the JCL for the job/CLIST.

CTM518S INVALID YEAR IN USER DATE CONTROL-RECORD

Explanation: Invalid year in the User Date Control record used by the New Day procedure. This year is not supported by the release of Control-M you are using.

The CTMJOB program ends with errors.

Corrective Action: Please correct the year field (the DACHK DD statement).

CTM519S INVALID PREVIOUS WEEKLY SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 43-48)

Explanation: Invalid previous weekly Scheduling Date in the User Date Control record (positions 43-48). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

This date (date-4 of User Date Control record) might not be equal to date-5 (positions 50-55) or in invalid format. Valid format is ddmmyy or mmddyy.

Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM522S INVALID ORIGINAL SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 1-6)

Explanation: Invalid original scheduling date in the User Date Control Record (positions 1-6). Valid format is ddmmyy or mmddyy.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM523S INVALID PREVIOUS MONTHLY SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 18-23)

Explanation: Invalid previous monthly scheduling date in the User Date Control Record (positions 18-23). This date (date-2 of User Date Control Record) should be equal to date-3 (positions 24-29) or in valid format. The valid format is ddmmyy or mmddyy.

This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The CTMJOB program will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM524S CTMJOB ENDED WITH ERRORS

Explanation: The CTMJOB program ended with errors.

The IOA Log usually contains prior messages concerning the errors.

The CTMJOB program finishes executing with a condition code of 08.

Corrective Action: Do the following:

Check the IOA Log for errors.
If CTMJOB is being executed from within the New Day procedure or from a User Daily, correct the Date Control Record (date-3 and date-5) manually, if necessary, to allow the next run of the Daily.

For more details, see the INCONTROL for z/OS Utilities Guide.

CTM525I CTMJOB ENDED

Explanation: This information message is a normal message issued when the CTMJOB program terminates. CTMJOB is activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM528I MEMBER `memName` ID=`orderId` ODATE `odate` PLACED ON ACTIVE JOBS FILE-`descr`

Explanation: This information message is issued when a job order is placed on the Active Jobs file. The task is now on the Active Jobs file in WAIT SCHEDULE state.

Corrective Action: No action is required.

CTM529S LAST WEEKLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATE

Explanation: The last weekly scheduling date in the Date Control Record is greater than the current original scheduling date.

This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure. Date-4 (positions 43-48) should not be greater than date-1 (positions 1-6) in the Date Control Record.

Possible causes are:

The previous run of the CTMJOB program did not finish OK.
Someone modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the User Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM530S LAST WEEKLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK IT

Explanation: The last weekly scheduling date is more than 28 days ago.

Possible causes are:

The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to yesterday.
Someone has modified the contents of the General Date Control Record incorrectly.

For more details, see the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the Date Control Record (the DACHK DD statement) and rerun.

CTM531W MEMBER `memName` ODATE `odate` - SCHEDULING CANCELLED BY USER EXIT

Explanation: Scheduling cancelled by the CTMX001 user exit; the member did not pass user checking. The CTMX001 user exit is activated for each job order before it is placed on the Active Jobs file. The exit can direct the New Day procedure not to place the job order on the Active Jobs file, in which case this message is issued.

The job order is not placed on the Active Jobs file.

Corrective Action: Look for additional messages in the IOA Log clarifying the reason for the cancel (usually security). If you cannot find a reason, consult your system programmer.

CTM532S OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED. DDNAME "DACKPT"

Explanation: Open of Control-M Active Jobs file failed.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure, and is due to one of the following:

The DACKPT DD statement is missing.
The data set described by the DACKPT DD statement is not the Control-M Active Jobs file.
The data set described by the DACKPT DD statement is the Control-M Active Jobs file but of a different version of Control-M, or of a different Control-M monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job/CLIST and rerun it.

CTM533S CONTROL-M ACTIVE JOBS FILE IS FULL. NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

Control-M Active Jobs file is full. There is no more space for new job orders.

The job order is not placed in the Active Jobs file.

Corrective Action: Consult your system programmer immediately. You may need to increase the size of the Active Jobs file.

CTM534S SEVERE ERROR ON CONTROL-M ACTIVE JOBS FILE. NOTIFY THE IOA ADMINISTRATOR

Explanation: Severe error on Control-M Active Jobs file.

This could be due to one of the following:

An I/O error occurred.
The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.
The Active Jobs file has been corrupted.

The CTMJOB Control-M program, which is activated as part of the New Day procedure, ends with errors.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support. Check whether the file has been updated from two computers without global ENQ control, or maybe by an unauthorized program.

CTM535S CONTROL-M ACTIVE JOBS FILE IS BEING FORMATTED. TRY AGAIN LATER

Explanation: Control-M Active Jobs file is currently being formatted. This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. The General New Day procedure is currently running and is formatting the file.

Corrective Action: Try again later.

CTM536S SEVERE ERROR IN SCHEDULING DATA CARDS

Explanation: A severe error was found in the scheduling data statements. This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Scheduling fails for the job order. The CTMJOB program terminates with a condition code of 08.

Corrective Action: Look for additional messages concerning the error, correct the error and rerun.

CTM537S NO MORE INTERNAL WORK AREA. SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Internal work areas of the New Day procedure have been exhausted. The job order contains more data than can be handled by the current release of Control-M.

The New Day procedure will terminate with a condition code of 08.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

CTM538S LOADING OF CONTROL-M/ANALYZER INSTALLATION PARAMETERS FAILED

Explanation: Loading of Control-M/Analyzer Installation Parameters, which are in the CTBPARM member in the IOA PARM library, failed.

Possible causes are:

There is insufficient memory to load the IOA Installation Parameters.
The CTBPARM member does not exist in the IOA PARM library.
The IOA PARM library was updated while you were working and the position of the CTBPARM member has changed.

The requested function is terminated.

Corrective Action: Look in the system log for additional related messages. Try one of the following:

If loading failed because of lack of memory: increase the REGION size for batch missions; for TSO, try to log on again using a larger SIZE parameter.
If you are using many IOA screens concurrently, try to exit a few using the END command. This releases memory used by the screens.
If the PARM library has been modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again.

CTM53AS AJF IS ALMOST FULL AND REACHED THE 'STOP ORDER' THRESHOLD. JOB IS NOT ORDERED.

Explanation: When the amount of used space in the AJF increases and reaches the percentage threshold specified in the STOPORDR CTMPARM parameter, Control-M stops ordering jobs.

Control-M stops ordering jobs but all other functions (for example, job submission and post-processing) continue normally.

Corrective Action: The user must compress the AJF.

CTM53BE JOB CAN NOT BE ADDED BECAUSE THE MOST RECENT GROUP ON THE AJF IS DELETED

Explanation: An attempt was made to use the DYNAMIC INSERT JOB INTO GROUP option "R" (recent) to add a job to a deleted group.

Corrective Action: No action is required.

CTM53CW CONTROL-M AJF/HST WAS NOT INDEXED, NOTIFY THE IOA ADMINISTRATOR

Explanation: Control-M was unable to index the Active Jobs file or History file because there is not enough space for additional text index records. See Optional Wish M11262.

Corrective Action: Consult your system programmer. You might need to apply Optional Wish M11262.

CTM53DE CONTROL-M AJF CAN NOT BE INDEXED, USE CTMCAJF TO COMPRESS IT

Explanation: Control-M monitor was unable to index an entry in the Active Jobs file because there is no more space for new text index records.

Corrective Action: Consult your system programmer immediately. Run CTMCAJF to compress the AJF and see Optional Wish M11262.

CTM540E ERROR IN CARDS. REASON=`rsn`, CODE=`field`

Explanation: A severe error was found in the scheduling data statements. This message is issued by Control-M (the CTMINP program) when it encounters an invalid value in a data statement.

The variables in this message are:

rsn - a reason code that describes the probable cause of the error
field - the field in which the error was found

Possible values of rsn and field, with explanations, are shown in the following tables.

rsn	Explanation
01	Invalid option
02	Nonnumeric character
03	Out of bounds. Field exceeds its limits.
04	Invalid time format
05	Plus or minus sign expected
06	Invalid date format
07	Conflict with a previous field
08	Minus or blank expected
09	Invalid or missing parameter or scheduling data statement
10	Internal format error

field	Explanation
00	Internal parameter
01	TASKTYPE
02	MAXWAIT
03	TIME FROM
04	TIME UNTIL
05	DUE OUT
06	MEMLIB
07	CTB STEP
08	IN Condition
09	CONTROL or RESOURCE
10	OUT
11	MAXDAYS
13	MAXRUNS
14	RETENTION, either # OF DAYS TO KEEP or # NUMBER OF GENERATIONS TO KEEP
15	MAXRERUN or INTERVAL
16	Invalid DO action
17	SYSOUT or DO SYSOUT
18	ON PGMST
19	SHOUT or DO SHOUT
20	DO COND or DO MAIL
21	PIPE
22	STATISTICS

Job order scheduling will fail. The User Daily will terminate with a condition code of 08.

Corrective Action: Use the values of rsn and field to locate the problem in the job definition. Correct the problem and run the User Daily again.

CTM540W LOAD OF SECURITY MODULE `modName` FAILED. SECURITY CHECKING WILL BE BYPASSED

Explanation: Loading of the modName IOA security module failed. Possible causes are:

The installation is not using the specified user security module, and has erased the default IOA-supplied module.
The IOA Load library is not in the load modules search lists of the job (STEPLIB + Linklist).
There is insufficient memory.
Another system oriented reason which can be found in the syslog.

As a result, no security checking is performed. For more details, see the sections on Security Interface Modules appropriate security guides.

Corrective Action: Notify the INCONTROL administrator. This is a potentially serious situation. Someone may be attempting to violate security.

CTM543E ID=`id` TASK=`taskName` OID=`orderId` - NOT FORCED OK, JOB IS ALREADY {DELETED | CHANGED | TERMINATED}

Explanation: A request was made to force the taskName task specified in the message. By the time the monitor accepted the request, the job was running, was being changed, or had already been deleted, so the request could not be performed. This message is written to the IOA Log file only.

The user request is ignored.

Corrective Action: If the entry was DELETED, it cannot be forced. If not, wait until the job ends, and if it ends NOTOK, try to force it again.

CTM544E UNABLE TO FORCE OK A CYCLIC JOB

Explanation: The user issued line command O (Force OK) for a cyclic job. Cyclic jobs cannot be Forced OK.

The user request is ignored.

Corrective Action: No action is required.

CTM545E I/O ERROR ON "AJF". CONTROL-M SWITCHES TO DUAL "AJF"

Explanation: An I/O error occurred while the Control-M monitor accessed the Active Job File (AJF). Control-M starts using the Dual AJF (CTM ALTCKP data set) instead of the primary AJF.

The Control-M monitor continues running using the Dual AJF.

Corrective Action: To use the Dual AJF in the Control-M Active Environment screen (Screen 3), reallocate the DACKP DD statement in the online environment so that it specifies the Dual AJF instead of the primary AJF.

To return to using the primary AJF, perform the following steps:

Fix the problem that caused the I/O error.
Reallocate the AJF file if necessary.
Stop the Control-M monitor.
Copy the Dual AJF to primary AJF, using the CTMCAJF or IEBGENER utility.
Restart the Control-M monitor.

CTM546S "CTMPARM" USED TO FORMAT THE "AJF" DIFFERS FROM YOUR "CTMPARM"

Explanation: The CTMPARM member used by the job that formatted the Active Jobs file (AJF) differs from the online user CTMPARM member. This can occur for a variety of reasons, including the following:

The user is migrating from one release to another.
The user is enlarging the AJF using a STEPLIB different from the one used by the online users.
The QNAME specified in the CTMPARM member does not match the QNAME specified in Record 0 of the AJF.

The Active Environment screen is not updated.

Corrective Action: Exit from the Control-M Online facility and reenter. If the problem recurs, contact your system programmer. Your logon procedure may point to an old CTMPARM member.

CTM547E I/O ERROR ON DUAL "AJF". USAGE OF DUAL "AJF" TERMINATED

Explanation: An I/O error occurred while the Control-M monitor accessed the Dual Active Job File (AJF) (CTM ALTCKP data set).

The Control-M monitor continues running without using the Dual AJF (CTM ALTCKP data set). No mirror AJF is supported; if errors occur in the primary AJF, no valid Active Jobs file will be available.

Corrective Action: Correct the problems that cause the I/O error. Reallocate the Dual AJF file, if needed. Stop and restart the Control-M monitor.

CTM548E SEVERE ERROR IN CALENDAR `calName` OR YEAR NOT FOUND IN CALENDAR

Explanation: Severe error in the calName IOA calendar. Either the year is not defined in the calendar, or the calendar has been incorrectly modified.

The job order is not issued. Processing of other job orders continues.

Corrective Action: Check the contents of the job order and the calendar.

CTM549E NO AVAILABLE "AJF" EXISTS. Control-M MONITOR SHUTS DOWN

Explanation: Control-M could not access a valid Active Jobs file (AJF) due to one of the following situations:

An I/O error occurred when the Control-M monitor accessed the Active Job File while no Dual AJF was available.
An I/O error occurred while the Control-M monitor accessed the Dual AJF, which was being used instead of the primary AJF because of a previous I/O error in the primary AJF.

The Control-M monitor shuts down.

Corrective Action: Do the following:

Correct the problem that caused the I/O error.
Reallocate the AJF files, if needed.
Restart the Control-M monitor.

CTM54DE MAXIMUM 50 INSTREAM JCL ENTRIES ALLOWED

Explanation: More than 50 lines of Instream JCL were specified in the job scheduling definition.

Corrective Action: Reduce the number of Instream JCL lines to 50 or fewer.

CTM54EE DAYS MUST BE BLANK, OR 000 TO 120

Explanation: This message is produced when specifying a value greater than 120 in the FROM TIME + DAYS, UNTIL TIME + DAYS, or the DUE OUT TIME + DAYS job definition parameters.

The cursor remains positioned on the invalid value.

Corrective Action: Correct the + DAYS parameter as required.

CTM54FE FOR JOB ENDED NOTOK, VALUE MUST BE BLANK OR K (KEEP THE RESOURCE)

Explanation: For the CONTROL job definition parameter, the onFail subparameter was specified with an invalid value.

Corrective Action: Specify a valid value of blank or K (keep the resource).

CTM54GE FOR JOB ENDED OK, VALUE MUST BE BLANK OR D (DISCARD THE RESOURCE)

Explanation: For the RESOURCE job definition parameter, the onOK subparameter was specified with an invalid value.

Corrective Action: Specify a valid value of blank or D (discard the resource).

CTM54LE TO DAYS CAN NOT BE SMALLER THAN FROM DAYS

Explanation: This message is produced when the + DAYS value in the FROM TIME is greater than the + DAYS value in the UNTIL TIME job definition parameter.

The cursor remains positioned on the invalid value.

Corrective Action: Correct the + DAYS parameter as required.

CTM54ME INTERNAL ERROR IN CONTROL-M. ERROR CODE = `rsn`

Explanation: The AJF Space Reuse Facility has encountered an internal error.

The possible values of rsn are explained in the following table:

rsn	Explanation
FUNCODE	Undefined or missing function code
MI0MIF0	No index record pointer in AJF record 0
FINDRB0	Process found RBA 0 available
COMPRB0	Process found RBA 0 different
FINDNUM	Error in 'number of records' parameter
FNXTNUM	Error in 'number of records' parameter
FNXTRBA	Error in RBA parameter
FREENUM	Error in 'number of records' parameter
FREERBA	Error in RBA parameter
COMPOLM	Error in old MIF parameter
BADGTMN	GETMAIN error
BADGTMO	GETMAIN error

The AJF Space Reuse Facility is disabled.

Corrective Action: Do the following:

Contact BMC Customer Support.
To reactivate the AJF Space Reuse Facility, format or compress the AJF and recycle the Control-M monitor.

CTM54NS "CTMPARM" USED TO FORMAT THE "HST" DIFFERS FROM YOUR "CTMPARM"

Explanation: The CTMPARM member used by the job that formatted the HST differs from the online user CTMPARM member. This can occur for a variety of reasons, including the following:

The user is migrating from one release to another.
The user is enlarging the HST using a STEPLIB different from the one used by the online users.
The QNAME specified in the CTMPARM member does not match the QNAME specified in Record 0 of the HST.

The History Environment screen is not updated.

Corrective Action: Exit from the Control-M Online facility and reenter. If the problem recurs, contact your system programmer. Your logon procedure may point to an old CTMPARM member.

CTM551E INVALID SCROLL AMOUNT

Explanation: Invalid scroll amount specified. The scrolling amount should be PAGE, HALF, CRSR, or MAX. For details, see the chapter that describes online facilities in the user guide for the active INCONTROL product.

Corrective Action: Correct the scroll amount field.

CTM552E INVALID DATE

Explanation: Invalid date specified. Valid date format is usually ddmmyy or mmddyy. In some screens, the date format is ddmm or mmdd.

In some cases, the date value may be valid but its value relative to another date is invalid, for example, when a FROM DATE is later than the TO DATE in the date prompt screen of the P (PLAN) option in Screen 2.

Corrective Action: Correct the DATE field or the DATE parameter as appropriate.

CTM552S GETMAIN FAILED IN CTMRSG GROUP PROCESSING

Explanation: The CTMRSG program could not allocate storage.

Group processing is terminated.

Corrective Action: Increase the region size.

CTM553E "UNTIL DATE" IS BEFORE "FROM DATE"

Explanation: UNTIL DATE is before FROM DATE.

Corrective Action: Correct either UNTIL DATE or FROM DATE.

CTM554E READ ERROR ON IOA LOG

Explanation: I/O error while reading the IOA Log file. Possible causes are:

The file allocated to the DALOG DD statement is not the IOA Log.
The file allocated to the DALOG DD statement is the IOA Log, but it is of a different version.
A read disk I/O error occurred.

Corrective Action: Check the TSO log of the job for additional messages. If necessary, correct the JCL for the job or the allocations for the CLIST.

CTM555S OID=`orderId` INSUFFICIENT STORAGE. INCREASE THE REGION SIZE

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter, or exit one of the screens.

CTM556I TOP OF DATA REACHED

Explanation: This information message indicates that a FIND PREV command did not find another string from the current position to the top of the scrolled data.

Corrective Action: No action is required.

CTM557I BOTTOM OF DATA REACHED

Explanation: This information message indicates that a FIND command did not find another string from the current position to the bottom of the scrolled data.

Corrective Action: No action is required.

CTM558E INTERNAL ERROR - INVALID PARAMETER TO CTMSROL

Explanation: Internal error in IOA scroll routine.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

CTM559I STRING NOT FOUND

Explanation: The string specified in the FIND command is not found in the list at all in the first search from the current position, or the prefix specified in a LOCATE command is not found in the list.

Corrective Action: No action is required.

CTM55AI INVALID SCROLL AMOUNT HAS BEEN ENTERED, CHANGED TO THE PREVIOUS VALUE

Explanation: An invalid value has been entered in the SCROLL field.

Valid values are:

PAGE - to scroll a full page
HALF - to scroll a half page
CRSR - to scroll by cursor position
MAX - to scroll the maximum amount available

The scroll amount is changed to the last valid value.

Corrective Action: No action is required.

CTM560I PLEASE SPECIFY A VALID FIND STRING

Explanation: A FIND or LOCATE command was specified without a string. The string cannot contain blanks.

Corrective Action: No action is required.

CTM561E INTERNAL ERROR - INVALID RETURN CODE FROM CTMSROL

Explanation: Internal error in IOA scroll routine.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

CTM562E ADD OPTION INVALID FOR NEGATIVE CONDITIONS

Explanation: In screen 3.? (Scheduling Analysis), the A (Add) option is not valid for negative (inverted) conditions. Negative conditions may only be deleted.

Corrective Action: Correct the option and try again.

CTM563E DELETE OPTION ONLY VALID FOR NEGATIVE CONDITIONS

Explanation: In screen 3.? (Scheduling Analysis), the D (Delete) option is only valid for negative (inverted) conditions. Use the A (Add) option for regular conditions.

Corrective Action: Correct the option and try again.

CTM564E READ ERROR ON IOA CONDITIONS FILE

Explanation: Internal error reading the IOA Conditions file.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

CTM566E INVALID OPTION

Explanation: Invalid option specified in the field.

Corrective Action: Correct the option and try again.

CTM567E USER NOT AUTHORIZED

Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.

Corrective Action: Check with your system security administrator.

CTM567I COND `cond` ODATE `odate` {ADDED | DELETED | FOUND} BY USER `userId / jobName` (`jobId`)

Explanation: This information message indicates that the ADD, DELETE, or CHECK option completed successfully and the cond condition with the odate original scheduling date was added to or deleted from, or found in the IOA Conditions file.

In this message, odate is the date on which the message is issued. If the ADD, DELETE, or CHECK option is run by the IOACND utility in batch mode, the user ID (userId), job name (jobName), and job ID (jobId) of the batch file are also displayed.

Corrective Action: No action is required.

CTM568E MISSING PARAMETER OF ADD REQUEST

Explanation: The ADD command was supplied without an additional parameter. At least one parameter is expected after the ADD command. The valid parameters are COND, LCOND, CONDITION, CONTROL, or RESOURCE.

Corrective Action: Supply the correct command parameter.

CTM569E INVALID TYPE IN ADD REQUEST

Explanation: Invalid ADD type supplied. At least one parameter is expected after the ADD command. The valid parameters are COND, LCOND, CONDITION, CONTROL, or RESOURCE.

Corrective Action: Specify the requested ADD type.

CTM571E PFK UNDEFINED

Explanation: You have pressed an undefined PFkey.

Corrective Action: Type the SHPF command and press Enter to see the PFkey assignments in the current screen.

CTM572E AMBIGUOUS COMMAND

Explanation: There is more than one command starting with the specified abbreviation. The abbreviated command is too short to identify a specific command. When the cursor is positioned in the COMMAND field, command abbreviations are represented on the Help line by the highlighted letter or letters.

Corrective Action: Specify the correct abbreviation.

CTM573E INVALID DATA ON PFK MEMBER OR COMMAND MEMBER

Explanation: An error occurred in an IOA command or PFK member. The IOA Online facility is controlled by command members and PFKs members. The members are located in the IOA PARM library. Possible causes are:

The data set allocated to DD statements DACMDLIB, DAPFLIB is not the IOA PARM library.
Somebody erroneously modified the IOA command (PFK) members of this screen.
An internal IOA error. This is not likely.

The current screen is locked. No command can be entered.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA online interface, the computer operator will have to cancel the TSO session. To resolve the problem do the following:

Correct the allocations of the IOA Allocation Parameter on the IOA PARM library.
Ask for help from your INCONTROL administrator, who probably knows what was modified in the command member and how to restore the old copy. For more information, see the INCONTROL for z/OS Installation Guide.
Try again. If the problem continues, contact BMC Customer Support.

CTM574E UNRECOGNIZED COMMAND

Explanation: The command that appears in the command window is not a valid command under this screen.

Corrective Action: Type the correct command syntax and press Enter.

CTM575E INVALID PARAMETERS - SCREEN DOES NOT EXIST

Explanation: Internal error in Control-M or Control-D screen or commands management routines. Possible causes are:

The IOA command member of the screen was incorrectly modified. The reserved areas in the command line description were altered.
Internal IOA error.

The current screen is locked. No command can be entered.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not escape the IOA Online interface, the computer operator must cancel the TSO session. To resolve the problem, do the following:

Restore the original command member. For more information, see the INCONTROL for z/OS Installation Guide.
Try again. If the problem continues, contact BMC Customer Support.

CTM576E INVALID COMMAND

Explanation: The command in the command window is not valid for this screen.

Corrective Action: Type the correct command syntax and press Enter.

CTM577E UNABLE TO ACCESS PFK MEMBER

Explanation: The IOA Online facility failed to access the PFK member of this screen. The IOA Online facility is controlled by command members and PFKs members. The members are located in the IOA PARM library. Possible causes are:

The data set allocated to the DAPF DD statement is not the IOA PARM library.
Someone erroneously modified the IOA PFK member or members of this screen.
The PFK member of this screen is not in the library described by the DAPFLIB DD statement. It may have been renamed during local adaptation.
The REGION size is exhausted, during an open command.
Internal IOA error.

You will be locked in the current screen without the ability to enter any command.

Correct the allocations of the IOA Allocation Parameter on the IOA PARM library.
Have your INCONTROL administrator look at the PFK member to undo what was modified, or restore the old copy. For more information, see the INCONTROL for z/OS Installation Guide.
Restore the member from the original IOA PARM library.
Increase the size of your TSO logon procedure. If you work with ISPF and IOA on the same terminal concurrently, we recommend a 2-3MB region size.
Try again. If the problem continues, contact BMC Customer Support.

CTM578E UNABLE TO INITIALIZE COMMANDS ENVIRONMENT

Explanation: The IOA Online facility failed to access the command member of this screen. The IOA Online facility is controlled by command members and PFKs members. The members are located in the IOA PARM library. Possible causes are:

The data set allocated to the DACMD DD statement is not the IOA PARM library.
Someone has erroneously modified the IOA command member of this screen.
The command member of this screen does not exist in the library described by the DACMD DD statement. It may have been renamed during local adaptation.
The REGION size has been exhausted (during an open command).
Internal IOA error.

The current screen is locked. No command can be entered.

Correct the allocations of the IOA Allocation Parameter on the IOA PARM library.
Check that the product parameters in IOAPARM match the products which are installed.
Ask your INCONTROL administrator, who probably knows what was modified, to restore the old copy. For more information, see the INCONTROL for z/OS Installation Guide.
Restore the member from the original IOA PARM library.
Increase the size of your TSO log on procedure. If you are working with ISPF and IOA on the same terminal concurrently, we recommend 2-3MB region size.
Try again. If the problem continues, contact BMC Customer Support.

CTM579E INVALID PARAMETERS TO COMMAND ANALYZER

Explanation: Internal IOA Online facility error.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA Online interface, your computer operator will have to cancel the TSO session.

Try again. If the problem continues, contact BMC Customer Support.

CTM57AE CONTROL-M IS ACTIVE IN COMPATIBILITY MODE, OPTION NOT ALLOWED

Explanation: The Control-M compatibility mode in the IOAPARM is 2 (MODECTM=3). This option is new and requires that Control-M be set to no compatibility mode (MODECTM=3)

The option is disabled.

Corrective Action: No action is required.

CTM580E INVALID RETURN CODE FROM COMMAND ANALYZER

Explanation: Internal IOA Online facility error.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA Online interface, the computer operator will have to cancel the TSO session.

Try again. If the problem continues, contact BMC Customer Support.

CTM581S OPEN OF IOA SYNCHRONIZATION FILE FAILED. DDNAME "DASINC"

Explanation: Open of IOA Conditions Synchronization file failed (DD statement DASINC). Possible causes are:

The DASINC DD statement is missing.
The file allocated to the DASINC DD statement is not the IOA Synchronization file.
The file allocated to the DASINC DD statement Synchronization file, but it is of a different version or of a different Control-M monitor.

Corrective Action: Correct the JCL for the job or the allocations for the CLIST.

CTM582S INVALID REQUEST PASSED TO CTMURS ROUTINE

Explanation: The CTMURS IOA internal utility received an invalid request. For example, the CHANGE command was used for an undefined resource.

The requested function is not performed.

Corrective Action: Contact your system programmer. If necessary, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM583S INTERNAL ERROR - INVALID RESOURCE TYPE (CTMURS). NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error. Invalid resource type passed to the CTMURS IOA internal utility.

The function requested is not performed.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

CTM584E COND `cond` ODATE `odate` DOES NOT EXIST

Explanation: The condition marked for deletion (option D) was already deleted from the IOA Conditions file, while you were working on the screen by another IOA user or IOA monitor.

This message may also be issued when:

You are not using an enqueue management product or have not specified a QNAME to the enqueue product. An enqueue product synchronizes requests to the IOA Conditions file.
You enlarged the IOA Conditions file incorrectly. For example, you did not use the IOACCND utility or you failed to update the IOAPARM that indicates that the file was enlarged (CNDREC#).

Corrective Action: Correct the condition that caused the error.

CTM585E AT LEAST ONE OF "CONTROL", "RESOURCE" OR "CONDITION" MUST BE "Y"

Explanation: None of the CONTROL, RESOURCE, or CONDITION options has been marked as Y.

Corrective Action: Mark at least one of the retrieval options as Y.

CTM586S OPEN OF IOA CONDITIONS FILE FAILED. DDNAME "DACNDSF"

Explanation: Open of IOA Conditions file failed (the DACNDF DD statement). Possible causes are:

The DACNDF DD statement is missing.
The file allocated to the DACNDF DD statement is not an IOA Conditions file.
The file allocated to the DACNDF DD statement is the IOA Conditions file, but it is of a different version or of a different IOA Installation.

Corrective Action: Correct the JCL for the job or the allocations for the CLIST.

CTM587I COND `cond` ODATE `odate` ALREADY EXISTS

Explanation: A condition added using the ADD command already exists in the file.

The addition request is ignored.

Corrective Action: No action is required.

CTM589E CONDITIONS FILE IN USE. PLEASE TRY AGAIN LATER

Explanation: Another user is currently updating the file. The file is momentarily in use by another user or by one of the IOA monitors.

The command requested is not performed.

Corrective Action: Try again.

CTM590E PLEASE SPECIFY CONDITION/RESOURCE NAME

Explanation: Missing condition or resource name in ADD command window.

Corrective Action: Specify the missing condition or resource name.

CTM591I PLEASE USE THE "ADD" COMMAND

Explanation: An A line command has been specified for a condition or resource name. Only an ADD primary command can be used to add a condition or resource.

Corrective Action: Use the ADD command in the commands window.

CTM592E ONLY ONE OPTION AT A TIME

Explanation: More than one option has been specified. Only one option is allowed for each Enter.

Corrective Action: Select only one option.

CTM593E INVALID OPTION. SPECIFY EITHER "Y" OR "N"

Explanation: Invalid retrieval criteria option. The valid options are either Y for Yes, or N for No.

Corrective Action: Select Y or N.

CTM594E ONLY TRAILING BLANKS ALLOWED

Explanation: The condition or resource name contains embedded blanks. A condition or resource name cannot contain embedded blanks.

Corrective Action: Correct the condition or resource name.

CTM595E UNEXPECTED RETURN CODE FROM CTMURS. SEE MESSAGES AND CODES

Explanation: Internal error. Invalid return code from the CTMURS IOA internal utility.

The function requested is not performed.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

CTM596E ADD OF COND `cond` ODATE `odate` FAILED. FILE IS FULL

Explanation:Highlighted, unrollable message.

The Conditions file is full.

The condition is not added to the file.

Corrective Action: Try to manually delete conditions from the specified day of the odate, but in other months. If you need all the conditions in the file, ask your system programmer to increase the capacity of the IOA Conditions file. Also, run the IOACLCND utility periodically to erase unnecessary conditions from the Conditions file and prevent the problem.

CTM597E INVALID CONTROL-TYPE. USE "E" - EXCLUSIVE OR "S" - SHARED

Explanation: Invalid control type specified in the ADD Control-command window. A control type should be E for exclusive or S for shared.

Corrective Action: Correct the control type field.

CTM598I CONTROL-RESOURCE `resourceName` ALREADY EXISTS

Explanation: A control resource being added by means of the ADD command already exists in the file.

The addition request is ignored.

Corrective Action: No action is required.

CTM599E ADD OF CONTROL-RESOURCE `resourceName` FAILED. FILE IS FULL

Explanation:Highlighted, unrollable message.

The Control-M Resources file is full.

The control resource is not added to the file.

Corrective Action: Consult your system programmer about the possibility of increasing the capacity of Control-M Resources file. It is not clear to us why a user would want to add a control resource. Call BMC Customer Support for advice.

CTM5A1E OPEN OF CONTROL-M STATISTICS FILE FAILED. RC=`VSAM_return_code` ERROR=`VSAM_reason_code`

Explanation: Error when trying to open the Control-M Statistics File for updating the Jobs Counting data. If the Control-M Statistics File was already successfully opened previously, then the error is considered as recoverable and Control-M tries to later update the Jobs Counting data. However, if it was the first attempt to open the Control-M Statistics File, then the error is considered as unrecoverable and Jobs Counting Facility is terminated (message CTM5A3E issued).

Corrective Action: If the message is issued frequently or the message CTM5A3E is also issued (Jobs Counting Facility is terminated) then contact IOA Technical support.

CTM5A2E ERROR IN `operation` JOB ACCOUNTING RECORD. RC=`VSAM_return_code` ERROR=`VSAM_reason_code`

Explanation: Error when trying to process the Jobs Counting Record (in the Control-M Statistics File) for accessing/updating the Jobs Counting data. The Jobs Counting Facility is terminated, the message CTM5A3E is issued.

Corrective Action: Contact IOA Technical support.

CTM5A3E JOB ACCOUNTING FACILITY TERMINATED

Explanation: The Jobs Counting Facility is terminated as the result of an error in accessing the Control-M Statistics File or the Jobs Counting Record in that file. It is preceded by the CTM5A1E or CTM5A2E message.

Corrective Action: Contact IOA Technical support.

CTM5A4W JOB ACCOUNTING RECORD NOT FOUND

Explanation: The message is issued by the Jobs Counting Report Utility when it detects that the Jobs Counting Record (which would contain the Jobs Counting Data) does not exist in the Control-M Statistics File. Usually it means that the Jobs Counting Facility was not activated or it was terminated and the corresponding error messages (CTM5A1E / CTM5A2E / CTM5A3E) will be issued by Control-M Monitor.

Corrective Action: Check the job log of Control-M Monitor and contact IOA Technical support.

CTM5A5W JOB ACCOUNTING RECORD IS EMPTY

Explanation: The message is issued by the Jobs Counting Report Utility when it detects that the Jobs Counting Record (which would contain the Jobs Counting Data) is empty. Usually it means that the Jobs Counting Facility was not activated or it was terminated and the corresponding error messages (CTM5A1E / CTM5A2E / CTM5A3E) will be issued by Control-M Monitor.

Corrective Action: Check the job log of Control-M Monitor and contact IOA Technical support.

CTM5B1I RECOVERY PROCEDURE INVOKED TO PREVENT DUPLICATE JOB PROCESSING

Explanation:During the start of Control-M monitor, it was detected that the previous monitor execution terminated abnormally and there are jobs whose processing might cause duplicate submissions or DO FORCEJOB execution. The Recovery Mode processing is invoked. It will scan the IOA LOG, extract information regarding the jobs whose statuses are ambiguous and set their statuses appropriately. In a CTMPLEX environment, this message can be issued not only during the start of Control-M monitor, but it can also be issued by the Global monitor if it detects a Coupling Facility failure or the abnormal termination of any Local monitor. The message can be also issued by a Local monitor when it switches to Global as a result of an abnormal termination of the previous Global.

For a general description about the Control-M Recovery Facility, see the Recovery Tools sub-section in Chapter 3, Control-M, in the INCONTROL for z/OS Administrator Guide. For more information about the installation parameters, RECENA and RECLEVEL, which control the Recovery Mode processing, see Chapter 2, Customizing Control-M, in the INCONTROL for z/OS Installation Guide: Customizing.

Corrective Action:Check the following messages issued by the Recovery Mode processing. Some messages indicate customer analysis and manual intervention might be required.

CTM5B2I JOB `member_name / Order_ID` PUT IN SUBMITTED STATUS BY RECOVERY PROCEDURE

Explanation:The Control-M Recovery processing analyzed the job in WAIT SUBMISSION status to prevent duplicate job submission. As a result of the analysis of the IOA LOG, the procedure detected that the job has already been submitted (before the Control-M abnormal termination) and extracted its JOBNAME and JOBID from the IOA LOG. The job is automatically put into SUBMITTED status so that Control-M can continue tracking and performing the regular Post Processing when the job finishes.

Corrective Action:No user action required.

CTM5B3W JOB `member_name / Order_ID` PUT IN HOLD BY RECOVERY PROCEDURE TO PREVENT DUPLICATE action

Explanation:Control-M Recovery processing placed the job into HOLD status because it detected the possibility of duplicate submission or DO FORCEJOB execution and the analysis of the IOA LOG did not determine the job status at the moment of the Control-M abnormal termination. 'action' can either be 'SUBMISSION' or 'FORCEJOB'.

Corrective Action:Check the actual status of the indicated job. If the job was not submitted or no DO FORCEJOB executed before the Control-M abnormal termination, then FREE the job so that Control-M can submit the job or execute its DO FORCEJOB.

If the job was already submitted or at least some of its DO FORCEJOB were already executed before the Control-M abnormal termination, more detailed analysis and manual actions are required. Check the results of the job execution (for the job put into HOLD to prevent duplicate submission) or check the DO FORCEJOB executed (for the job put into HOLD to prevent duplicate DO FORCEJOB). The customer might then have to manually make up the Post Processing actions according to the jobs execution results (for example, adding OUT CONDITIONS). In some situations the Force OK request might be applicable here.

CTM5B4W `number` JOBS PUT IN HOLD STATUS BY RECOVERY PROCEDURE TO PREVENT DUPLICATE ACTIONS

Explanation:Control-M Recovery processing placed number jobs into HOLD status because it detected the possibility of their duplicate submission or DO FORCEJOB execution and the analysis of the IOA LOG did not determine the job statuses at the moment of the Control-M abnormal termination. The CTM5B3W messages, which were issued before CTM5B4W, indicate the jobs put into HOLD statuses.

Corrective Action:Analyze the previous CTM5B3W messages and handle the jobs listed by these messages as explained in the User Action part for CTM5B3W.

CTM5B6E ERROR IN LOG FILE DURING RECOVERY PROCEDURE

Explanation:During the Control-M recovery procedure, Control-M recovery could not open the IOA log file and extract the needed information.

Corrective Action:Check the IOA Log file and fix the issue.

CTM5C5I JOB `job_member_name` IS RECYCLED WITH CYCLIC SMART TABLE `Table_Name` RECYCLE

Explanation:The job belongs to a Cyclic SMART Table. When the Cyclic SMART Table is recycled for possible re-execution, all of its jobs (excluding ones in HELD or DELETED statuses) are recycled.

Corrective Action:No action is required.

CTM5C6I PERFORMING CONDITION ADJUSTMENT TO ALLOW CYCLIC SMART TABLE `Table_Name` RECYCLE

Explanation:The recycling processing of Cyclic SMART Tables includes the Internal Smart Table Conditions cleanup, which guarantees the correct order of execution of the SMART Table jobs. This message is followed by the SEL250I message, which contains the name of the Conditions deleted.

Corrective Action:No action is required.

CTM5C7I TABLE IS MARKED TO BE COMPLETED BY JOB `jobName` (`orderId`)

Explanation:This message is issued to the Smart Table’s log, indicating that it was completed by the job’s ‘End Table’ Post Processing parameter.

Corrective Action:No action is required.

CTM5C8I END-TABLE PERFORMED. TABLE `tableName` (`orderId`) IS MARKED TO BE COMPLETED

Explanation:This message is issued to the log of the job that marked the specified Smart Table as ‘To be Completed’ as a result of processing the job’s ‘End Table’ parameter.

Corrective Action:No action is required.

CTM5CAI TABLE `TableName` (`OrderId`) IS MARKED TO BE COMPLETED BY AJF COMPRESS

Explanation: Control-M New Day processing or AJF Compress forced Smart Table completion because the MAXWAIT of all its jobs (and the Smart Table itself) had expired. For additional information, see the description of Control-M Installation parameter FRMAXWT in the INCONTROL for z/OS Installation Guide: Customizing.

Corrective Action: No action is required.

Messages CTM600 through CTM6xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM600I CONTROL-RESOURCE `resourceName` (CONTROL-`type`) `action`

Explanation: This information message indicates that as a result of an ADD or DELETE option, the resourceName control resource of Control-type was either deleted from the Control-M Resources file, or added to the Control-M Resources file.

Corrective Action: No action is required.

CTM601E CONTROL-RESOURCE `resourceName` (CONTROL-`type`) DOES NOT EXIST

Explanation: The control resource marked for deletion (D option) was already deleted from the Control-M Resources file. While you were working on the screen, another user or one of the IOA monitors deleted the control resource from the Control-M Resources file.

Corrective Action: No action is required.

CTM602E QUANTITY MUST BE A FOUR DIGIT NUMBER

Explanation: An invalid quantity specified in the window. Quantity must be a 4-digit number.

Corrective Action: Correct the quantity field.

CTM603E QUANTITATIVE RESOURCE `resourceName` IN USE - CANNOT DELETE

Explanation: The resourceName quantitative resource is in use by an active job under Control-M. Therefore, the resource cannot be deleted.

The resource is not deleted.

Corrective Action: Wait until the job finishes executing, and try again.

CTM604E FILE IS FULL. CANNOT ADD QUANTITATIVE RESOURCE resourceName

Explanation:Highlighted, unrollable message.

The Control-M Resources file is full.

The resourceName quantitative resource is not added to the file.

Corrective Action: Consult your system programmer about the possibility of increasing the capacity of the Control-M Resources file.

CTM605I QUANTITATIVE RESOURCE `resourceName` ALREADY EXISTS

Explanation: A quantitative resource (resourceName) being added using the ADD command already exists in the file.

The addition request is ignored.

Corrective Action: No action is required.

CTM606E QUANTITATIVE RESOURCE `resourceName` DOES NOT EXIST

Explanation: The resourceName quantitative resource that was marked for deletion (the D option) was already deleted from the Control-M Resources file. While you were working on the screen, another Control-M user deleted the quantitative resource from the Control-M Resources file.

Corrective Action: Check who did it and why (by entering the IOA Log screen).

CTM607I QUANTITATIVE RESOURCE `resourceName action`

Explanation: As a result of an ADD or DELETE option, the resourceName quantitative resource has been deleted from the Control-M Resources file, or added to the Control-M Resources file.

Corrective Action: No action is required.

CTM608E ONLY QUANTITATIVE RESOURCES MAY BE CHANGED

Explanation: A change request was issued for a condition or a control resource. The change option can be specified only in order to change the quantity of a quantitative resource.

The change request is ignored.

Corrective Action: No action is required.

CTM609E SIGN OF QUANTITY MUST BE EITHER "+", "- " OR BLANK

Explanation: Invalid sign of quantity change in the CHANGE window. The quantity sign must be "-" for subtracting the amount from the maximum available quantity, "+" for adding the amount to the maximum available quantity, or blank for setting a new quantity.

Corrective Action: Supply the correct sign.

CTM60AE CONTROL RESOURCE `res` (E) HELD BY A JOB, OR TYPE MISMATCH

Explanation: This message is issued when the IOACND utility fails to delete control resource res from the Control-M Resources file. The specified control exists in the Control-M Resources file but the IOACND utility cannot delete it for one of the following reasons:

The control was created by a running job. The IOACND utility can only delete controls added by IOACND or screen 4 (RBA 0000 controls).
The type specified in the Delete statement (E/S) does not match the type of the control in the file.

Corrective Action: No action is required.

CTM60BE INSUFFICIENT STORAGE, INDEXING FORCED OFF

Explanation: The Control-M Active Environment screen cannot use indexing because the user region size is too small. This might cause the screen response time to slow significantly.

Corrective Action: Enlarge the user region size. If the size of the Active Jobs file and/or the History Active Jobs file have increased recently, make sure that all user region sizes are enlarged accordingly.

CTM610E VALUE OF CHANGE IS NEGATIVE OR MORE THAN 9999

Explanation: The quantity resulting from the CHANGE operation is either negative, or more than 9999.

The change request is ignored.

Corrective Action: Try again with a correct value.

CTM611E INTERNAL ERROR. INVALID RETURN CODE FROM CTMURS

Explanation: Internal error. Invalid return code from the CTMURS IOA internal utility.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

CTM612I QUANTITY OF RESOURCE `resourceName` CHANGED `quant` === > `snnnn`

Explanation: As a result of a change command, the quantity of the resourceName resource changed from quant by snnnn (s is the sign).

Corrective Action: No action is required.

CTM613E DEL OF RESOURCE `res` FAILED

Explanation: IOACND was asked to delete the res resource, but the resource was not found in the RES file.

The resource is not deleted.

Corrective Action: Check if the correct resource was specified, and if it was not, specify the correct resource.

CTM613I DELETE OF ARCHIVED SYSOUTS STARTED

Explanation: This information message indicates that the New Day procedure started deleting archived SYSDATA sysouts.

Corrective Action: No action is required.

CTM613S `modName` INTERNAL ERROR, R15=`rsn`, RC=`rc`

Explanation: An internal error was detected in the modName module.

The Application Server becomes unstable.

Corrective Action: Stop and restart IOAGATE and the Application Server CTOGATE. If the error persists, contact BMC Customer Support.

CTM614I DELETE OF ARCHIVED SYSOUTS ENDED

Explanation: This information message indicates that the New Day procedure finished deleting archived SYSDATA sysouts.

Corrective Action: No action is required.

CTM615W DELETION OF `num` ARCHIVED SYSOUT DATASET(S) FAILED

Explanation: Some Archived Sysout Data Sets were not deleted by the Control-M New Day procedure or during compression of the Control-M Active Jobs file.

This message follows other messages that explain the nature of the error for each archived sysout data set.

The Control-M New Day procedure or CTMCOP utility continues processing.

Corrective Action: See the messages that precede this message for the reasons for deletion failure.

CTM617E INTERNAL ERROR - INVALID NAME OF THE ARCHIVED SYSOUT DATASET. DSNAME=`dsn`

Explanation: The name of Archived Sysout Data Set does not follow the Control-M/Restart naming conventions for this type of data set. This message is issued either by the Control-M New Day procedure, or by the CTMCOP utility, during compress of the Control-M Active Jobs file.

Corrective Action: Contact BMC Customer Support for assistance.

CTM618E TOO MANY SYSOUT DATASETS SCHEDULED FOR DELETE - SOME WILL BE SKIPPED THIS TIME

Explanation: The number of Archived Sysout Data Sets scheduled for deletion exceeds the permitted number. This message is issued either by the Control-M New Day procedure or by the CTMCOP utility during compress of the Control-M Active Jobs file. The permitted value is one fifth of the Active Jobs file size.

Deletion of Archived Sysout Data Sets will be resumed during the next run of the Control-M New Day procedure or the CTMCOP utility.

Corrective Action: No action is required.

CTM618S ERROR IN SYSPLEX QUERY, MOD=`modName`, RC=`rc /rsn`

Explanation: An Sysplex query error was detected in the modName module.

The Application Server becomes unstable.

Corrective Action: Stop and restart IOAGATE and the Application Server CTOGATE. If the error persists, contact BMC Customer Support.

CTM619I IOANOTE YOU HAVE NOT ENTERED A MESSAGE PARAMETER !

Explanation: When executing the IOANOTE utility, no message was specified in the PARM of the JCL EXEC statement or no PARM was specified on the JCL EXEC statement.

The utility terminates with a return code of 4.

Corrective Action: Add a message in the PARM of the EXEC JCL statement.

CTM621E THE UTILITY CTMRELRS MAY BE ACTIVATED ONLY FROM BATCH JOBS

Explanation: The CTMRELRS utility (the CTMRLR program) has been activated from a started task or from a TSO session. The CTMRELRS utility may be activated only from batch jobs which are submitted by the Control-M monitor.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: For usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide.

CTM622E THIS JOB WAS NOT SUBMITTED FROM CONTROL-M. THE RESOURCE IS NOT RELEASED

Explanation: The CTMRELRS utility (the CTMRLR program) was activated from a job that was not submitted by the Control-M monitor. Only a job that is submitted by the Control-M monitor can release its own quantitative resources.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: For more information on usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide.

CTM623I QUANTITATIVE RESOURCE `resourceName` - `quant` RELEASED

Explanation: This information message indicates that the quant quantity of the resourceName quantitative resource has been released for general use, or has been changed by the CTMRLRES utility.

The specified action is either RELEASED or CHANGED.

Corrective Action: No action is required.

CTM625S INVALID FUNCTION. USE "RELEASE"

Explanation: Invalid function supplied as a parameter to the CTMRELRS utility.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released or changed.

Corrective Action: Specify either the RELEASE or CHANGE function for the utility.

CTM627E YOU CANNOT RELEASE MORE `resourceName` THAN THOSE ALLOCATED TO THIS JOB

Explanation: The quantity requested to be released by the job using the CTMRELRS utility is greater than the quantity of the resource currently allocated to the job.

The utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: Correct the parameters of the utility.

CTM628E RESOURCE `resourceName` IS NOT ALLOCATED TO THIS JOB

Explanation: The quantitative resource to be released by the CTMRELRS utility is not allocated at all to the job that activates the utility.

A job can only release resources which are allocated to it.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: For more information on usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide.

CTM629S OPEN OF PARAMETER LIST FAILED. DDNAME "DARELIN"

Explanation: Open of control statements file failed (the DARELIN DD statement in the CTMRELRS utility).

Possible causes are:

The DARELIN DD statement is missing.
The data set described by the DARELIN DD statement does not exist, or cannot be opened for sequential read, or the record length is not 80.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job and run it again.

CTM630E YOU CANNOT INCREASE THE NUMBER OF `quantResourceName` ALLOCATED TO THIS JOB

Explanation: The quantity requested to be changed using the CTMRELRS utility is greater than the quantity of the resource currently allocated to the job. The CTMRELRS utility can only be used to decrease the quantity of the resource allocated to a job.

The utility stops executing with a condition code of 4. The resource amount allocated to the job is not changed.

Corrective Action: Correct the parameters of the job.

CTM630S OPEN OF PARAMETER LIST FAILED. DDNAME "DACNDIN"

Explanation: Open of control statements file failed (the DACNDIN DD statement in the IOACND utility or program).

It may be due to one of the following:

The DACNDIN DD statement is missing.
The data set described by the DACNDIN DD statement does not exist, or cannot be opened for sequential read, or the record length is not 80.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job or the CLIST, and run it again.

CTM631E RESOURCE `quantResource` WAS NOT FOUND IN THE RESOURCE FILE

Explanation: The quantResource Quantitative resource does not exist. The missing resource was named as input to the CTMRLR program.

Corrective Action: Ensure that the name of the resource specified as input to the program matches the resource name in the job scheduling definition.

CTM631S INVALID FORMAT OF INPUT PARAMETERS

Explanation: Severe syntax error in the parameters to the IOACND or CTMRELRS utility.

The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.

Corrective Action: Correct the parameters and reactivate utility.

CTM632S INVALID DATE FORMAT

Explanation: Invalid date format in ADD COND or DELETE COND statement (the IOACND utility or program). The date format should be mmdd or ddmm, depending on the site standard.

The utility stops executing with a condition code of 12. The condition is not added or deleted.

Corrective Action: Correct the parameters and reactivate utility.

CTM633S INTERNAL ERROR IN IOACNP. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the IOACND and CTMRELRS utilities.

The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.

Corrective Action: Call your IOA administrator for assistance.

CTM634S OPEN OF PRINT FILE FAILED. DDNAME "DAPRINT"

Explanation: Open of messages file failed in the IOACND and CTMRELRS utilities. Possible causes are:

The DAPRINT DD statement is missing.
The data set allocated to the DAPRINT DD statement cannot be opened for sequential write.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the JCL for the job or the CLIST and run it again.

CTM635E INVALID FUNCTION. USE ADD/DELETE/CHECK

Explanation: An invalid function has been passed to the IOACND utility.

Valid functions are ADD, DELETE or CHECK.

The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.

Corrective Action: Correct the parameters syntax and reactivate.

CTM636E INVALID FUNCTION OR FUNCTION NOT SUPPORTED YET

Explanation: An attempt was made to add or delete a Quantitative Resource or Control Resource using the IOACND utility. These are privileged operations for Control-M or Control-D support personnel.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameters syntax and reactivate.

CTM637E LOAD OF PROGRAM "CTMRS0" FAILED

Explanation: An attempt to load the CTMRS0 program failed.

Corrective Action: Check that the name of the load library is correct. If that does not solve the problem, contact your INCONTROL Administrator.

CTM638E FUNCTION "RDIF" OF PROGRAM "CTMRS0" FAILED

Explanation: The IOACND utility failed in one of the initialization steps of the Control-M Resources file. Either the file accessed is not a valid Resources file, or the Resources file is being formatted.

The utility stops with a return code of 16.

Corrective Action: Ensure that the DARESF DD statement points to a valid resource file, and that the file is not corrupted.

CTM639E TABLE DOES NOT EXIST - TABLE NOT SAVED

Explanation: You are trying to save a table that does not exist.

The table is not saved.

Corrective Action: To save a new production parameters table, erase the Y in the SAVE field, enter Y in the CREATE field, and press Enter.

CTM639S ACTIVE JOBS FILE (CKP) SIZE - PARM TABLE MISMATCH

Explanation: The CKPSIZE parameter in CTMPARM is not the same as when the Active Jobs file (AJF) referenced by the DACKPT DD statement was formatted. A change was made in the CKPSIZE parameter in CTMPARM after the Active Jobs file was formatted.

The job step or request terminates without performing the requested function.

Corrective Action: Adjust the CKPSIZE parameter according to the real size of the AJF, or reformat the AJF.

CTM639W LOG WRAP AROUND HAS BEEN DETECTED. SOME MESSAGES MAY BE LOST

Explanation: While looking at a certain part of the IOA Log file, an IOA component updated that part of the Log. When the IOA Log file is full, a wraparound is performed and new records are written starting at the top of the Log. If you are at the top of the Log, a wraparound might cause some messages to be lost.

The Online facility issues a warning to inform of the possible loss of messages.

Corrective Action: No action is required.

CTM63BI WISH WI2232 IS ENABLED - UPPERCASING CONDITION NAME

Explanation: This information message is generated by the IOACND utility when optional wish WI2232 is applied.

The IOACND utility translates a condition name from the PARM= parameter in the EXEC card of this utility to upper case.

Corrective Action: No action is required.

CTM640E INVALID VALUE. USE "Y" OR "N"

Explanation: Invalid value specified in the field. The cursor points to the field that contains the invalid value.

Corrective Action: Enter either Y for yes, or N for no.

CTM641E AT LEAST ONE MESSAGE TYPE MUST BE "Y"

Explanation: No MESSAGE TYPE field has been marked for selection (Y). At least one of the MESSAGE TYPES must be marked as Y.

Corrective Action: Enter Y for at least one MESSAGE TYPE.

CTM641S INVALID JOB RECORD DETECTED: `jobName`

Explanation: A job record with an invalid format was detected during the New Day procedure. If the User Daily is run on a different computer without proper ENQ distribution software, such as GRS or MIM, a faulty record may be created in the Active Jobs file.

The faulty record is erased from the Active Jobs file.

Corrective Action: To avoid this problem, run all User Daily procedures on the CPU in which the Control-M monitor is running.

CTM642E ONLY TRAILING BLANKS ALLOWED IN FIELD

Explanation: The field contains leading blanks or two strings separated by blanks. Leading or embedded blanks are not allowed in this field.

The cursor points to the first blank.

Corrective Action: Correct the field contents.

CTM643E AT LEAST ONE URGENCY TYPE MUST BE "Y"

Explanation: No URGENCY field was marked for selection (Y). At least one of the URGENCY fields must be marked Y.

Corrective Action: Enter Y for at least one URGENCY field.

CTM644E AT LEAST ONE TASK TYPE MUST BE "Y"

Explanation: No TASK TYPE field has been marked for selection (Y). At least one of the TASK TYPEs must be marked Y.

Corrective Action: Enter Y for at least one TASK TYPE.

CTM645I MONITOR USER PGM APPLID TERMINAL START LASTUSED ST

Explanation: After an operator DISPLAY command to one of the Online monitors, this header message for message CTM646I is issued.

Corrective Action: No action is required.

CTM646I `monName userIdpgmapplIdterminalstart lastUsedst`

Explanation: After an operator DISPLAY command to one of the Online monitors, this message is displayed for each active user.

The variables in this message are:

monName - the name of the monitor started task
userId - the user name (ID)
pgm - the program name
applId - the application ID
terminal - VTAM terminal ID
start - user sign-on time
lastUsed - time stamp of last user entry
st - status Valid values are:
- W - waiting for user data
- A - active user waiting for response

Corrective Action: No action is required.

CTM647E `monName` - LOAD OF `pgm` FAILED. SIGNON OF USER `usr` FAILED

Explanation: Load for the requested pgm module during user sign-on to the Online facility failed. The user main program as specified by Online monitor sign-on exit or by default (CTMXMAN, CTMXMAND, CTDXMAN, or CTDXMANU) cannot be found in the Online monitor STEPLIB libraries.

Sign-on to the specified IOA Online monitor is terminated.

Corrective Action: Contact your INCONTROL administrator to find out why the program is missing. If the problem is not resolved, contact BMC Customer Support for assistance.

CTM647W RBC NAME IS 20 CHARS LONG AND CANNOT BE USED AS AN EXCLUDE RBC

Explanation:The maximum number of characters allowed for an RBC name is 20 characters, including the exclamation mark (!) prefix used to specify an Exclude RBC. Since the name of this RBC already consists of 20 characters, an exclamation mark (!) cannot be added as a prefix to this RBC name, in the event it is required for an Exclude RBC.

Corrective Action: Rename the RBC with 19 or less characters.

CTM648S `monName` - ONLINE MONITOR ENDED WITH ERROR

Explanation:Highlighted, unrollable message.

A severe error has occurred. The IOA Online monitor is shutting down.

Detailed information on this error is available in the messages which were previously displayed on the operator console.

The monName IOA Online monitor is shutting down.

Corrective Action: Check the system log for additional messages.

CTM649E `monName` - INVALID MODIFY PARAMETERS. VALID PARAMETERS ARE:

Explanation: An invalid parameter was passed to the monName IOA Online monitor by an operator modify command (F). A list of valid modify parameters will appear on the operator console following this message.

The modify command is rejected.

Corrective Action: Enter a correct modify parameter.

CTM650S OPEN OF ACTIVE JOBS FILE FAILED. DDNAME "DACKPT" (SENSE=`sense_code`)

Explanation: Open of Control-M Active Jobs file failed (the DACKPT DD statement). Possible causes are:

The DACKPT DD statement is missing.
The data set described by the DACKPT DD statement is not the Control-M Active Jobs file.
The data set described by DACKPT DD statement is the Control-M Active Jobs file of another IOA Installation, or of a different version of Control-M.

Corrective Action: Check the contents of the system log for additional messages which may clarify the picture, or logon again. If the sense code appears in the message, supply it to the INCONTROL administrator when requesting assistance.

CTM651S READ ERROR ON CONTROL-M ACTIVE JOBS FILE. (SENSE=`sense_code`, RBA=`rba`)

Explanation: I/O error while reading Control-M Active Jobs file. Possible causes are:

The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.
The file allocated to the DACKPT DD statement is the Control-M Active Jobs file, but it is of a different version.
Real I/O error.
The Active Jobs file indexes are corrupted.

Corrective Action: Check the contents of the system log for additional messages which may clarify the picture, or logon again. If this does not solve the problem, notify the INCONTROL administrator informing him of the sense code and RBA.

CTM652S INTERNAL ERROR - INVALID REQUEST TO CTMUCK `req`

Explanation: Internal error. Invalid request to the CTMUCK Control-M internal program.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTM653E CANNOT `action` TASK `taskName` ODATE `odate` - {NOT HELD | DELETED}

Explanation: Result of DELETE, CHANGE or UNDELETE commands.

For DELETE or CHANGE commands, the taskName task of the original scheduling date (odate) is not in the HELD state and therefore cannot be deleted or changed.

For an UNDELETE command, the task of the original scheduling date was not deleted, therefore cannot be undeleted.

The DELETE, CHANGE or UNDELETE request is ignored.

Corrective Action: In the case of DELETE or CHANGE commands, hold the task using the H option. Wait until the REQUESTED HELD status is changed to HELD, and then you can perform the change or delete.

CTM654E CANNOT `action` TASK `taskName` ODATE `odate` - ALREADY `status`

Explanation: The taskName task with the odate original date already has the requested status.

The user request is ignored.

Corrective Action: No action is required.

CTM655E ACTIVE JOBS FILE IS IN USE, TRY AGAIN LATER

Explanation: Another user is currently updating the file. The file is currently in use by another user or by the Control-M monitor.

The requested action is not performed.

Corrective Action: Try again later.

CTM656E action OF TASK `taskName` ODATE `odate` IGNORED - STATUS HAS CHANGED

Explanation: Result of HOLD (H), RERUN (R), FREE (F), AESIM (%) (AutoEdit simulation), or CHANGE request for the taskName task of the odate original scheduling date whose status has already been changed. While you were looking at the screen, another user or Control-M monitor changed the status of the task, or the contents of the production parameters.

The requested action is ignored.

Corrective Action: Check the task status and act accordingly.

CTM657E CANNOT `action` TASK `taskName` ODATE `odate` - MAX CHANGES OVER, TRY AGAIN LATER

Explanation: Cannot do more actions on the taskName task of the odate original scheduling date. The maximum number of requests for action has been exceeded. Control-M monitor must accept the requests before another action can be performed.

The user request is ignored.

Corrective Action: If the Control-M monitor is up, try again. If it is down, it should be brought up again.

CTM658S CANNOT `action` TASK `taskName` ODATE `odate` - UNEXPECTED CODE FROM CTMUCK

Explanation: The CTMUCK Control-M internal utility has issued an unexpected return code.

The user request is ignored.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM659I `action` OF TASK `taskName` TABLE `grpname` ODATE `odate` PERFORMED

Explanation: This information message indicates the specified action was performed by the taskName task to the grpname group on the odate date.

When this message is produced as the result of an action in screen 2, the date is the current Control-M working date in YYMMDD format.

Corrective Action: No action is required.

CTM65AI `taskType memName` OID=`orderId` ODATE `odate action` PERFORMED BY `userId`

Explanation: This information message indicates that the action action requested by the userId user was performed by the taskName task on the odate date.

This message is issued to the log only.

Corrective Action: No action is required.

CTM65BE STEP CANNOT BE SELECTED. STEP NAME NOT UNIQUE - MATCHES STEP # `num`

Explanation: The selected step has the same name as the step with the number num. A From, To, or Only RESTART was specified in the Control-M/Restart Step List window for a step with a name that is not unique in the job.

The cursor is placed on the line in which the non-unique step was selected.

Corrective Action: Clear the entry and choose another step.

CTM65CE UNSUPPORTED COMMAND/PFK

Explanation: The command that was requested, or the function key that was pressed, is not supported in this screen or this window.

The request is ignored.

Corrective Action: No action is required.

CTM65DI NO ARCHIVED SYSOUT OR NO MEANINGFUL DATA TO BUILD STEP LIST

Explanation: The Step List display requested under Screen 3.R (the Restart window) cannot be built, either because the job has no archived sysout, or because the existing archived sysout contains no steps from which a step list can be built. To build a step list, a meaningful archived sysout must exist.

The step list is not displayed.

Corrective Action: Select FROM and TO steps manually.

CTM65EE HISTORY FILE ("DAHIST") IS NOT INITIALIZED

Explanation: The History command was entered in the Control-M Active Environment (Job Status) screen. However, the DAHIST file is not allocated to the user or could not be accessed.

This message is also generated if Control-M/Restart is not installed.

The command is ignored.

Corrective Action: Make sure the DAHIST DD statement correctly references the History Jobs file.

CTM65FE Option "G" CANNOT BE ISSUED FOR NON-GRP ENTRY/JOB

Explanation: Option G (Group) was requested in the Control-M Active Environment (Job Status) screen for a task that is not part of a Group scheduling table. Option G can only be specified for a Group entity (GRP) or job (JOB) that is part of a Group scheduling table.

The request is ignored.

Corrective Action: Request an option that is valid for the particular line entry in the screen.

CTM660E INVALID VALUE, USE "Y" OR "N"

Explanation: Invalid value specified in the field. The cursor points to the field that contains the invalid value.

Corrective Action: Select Y for yes, or N for no.

CTM661E AT LEAST ONE TASK-TYPE MUST BE "Y"

Explanation: At least one task type must be Y.

Corrective Action: Mark at least one of the task types as Y.

CTM662E AT LEAST ONE MESSAGE TYPE MUST BE "Y"

Explanation: At least one message type must be Y. All of the Y/N options are marked N.

Corrective Action: Mark at least one of the message types as Y.

CTM663E AT LEAST ONE OF THE FIRST TWO TYPES OF JOB STATUS MUST BE "Y"

Explanation: At least one of the first two types of job status must be Y (both are marked NO).

Corrective Action: Mark at least one of the first two types of job status Y.

CTM664S INTERNAL ERROR BEFORE CALLING CTMUCK

Explanation: Internal error.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTM665E CANNOT RERUN TASK `taskName` ODATE `odate` - TASK NOT ENDED

Explanation: The taskName task of the odate original scheduling date did not finish executing, therefore it cannot be rerun.

The rerun request is ignored.

Corrective Action: No action is required.

CTM666S INTERNAL ERROR - UNEXPECTED RETURN CODE FROM CTMTWHY

Explanation: Internal error. Invalid return code from the CTMTWHY Control-M internal program (Why screen).

Corrective Action: Have your system programmer contact BMC Customer Support for assistance.

CTM667E "WHY" OPTION CAN BE USED ONLY ON TASK IN "WAIT SCHEDULE" STATE

Explanation: The WHY ("?") option is used to determine the reason that a task is waiting to be scheduled; it cannot be used unless the task is in the WAIT SCHEDULE state.

The user request is ignored.

Corrective Action: No action is required.

CTM668S INTERNAL ERROR - UNEXPECTED RETURN CODE FROM `pgm`. RC=`rc`

Explanation: Internal error. Invalid return code from the pgm Control-M internal program.

The CTMTSVY, CTMTWHY, or IOATOLV programs can return the following return codes:

rc	Explanation
20	Insufficient REGION allocated to online environment
1008	First CLS entry is an inserted/deleted entry
1012	No CTDBOX vectors were processed
1016	Insufficient memory for CTDBOX vector
1020	Maximum number GETMAINS for CTDBOX vector exceeded
1024	VSAM record for first CLS entry not found
1028	VSAM record for first CLS entry is not a primary record
1032	All compressed data sets were deleted. May also indicate that the SYSOUT file was deleted manually, by a system utility or another program.
1036	Internal error in page fix environment
1040	Error in GETMAIN of work areas
1044	Error while reading a ruler
2000	Error in CTDBOX
2004	End of data sets
2016	Unrecognized request
2020	Allocation error
2024	Open error
2028	Subsystem not up

Corrective Action: When the program identified in the message is CTMTSVY or IOATOLV, try to solve the problem according to the return code. If you are unable to solve the problem, and for all other return codes, record the program name and return code, then contact BMC Customer Support.

CTM669E ERROR ON ACTIVE JOBS FILE. CANNOT BUILD ZOOM SCREEN

Explanation: Result of the ZOOM (Z) command. Error in the contents of the Active Jobs file. Possible causes are:

The Active Jobs file has been corrupted, perhaps by incorrect usage of one of the Control-M user exits.
An internal Control-M error occurred.

Corrective Action: Call your system programmer for assistance. A dump of the file will be needed to solve the problem.

CTM66AE CANNOT ISSUE `cmd` IN `mode` DISPLAY

Explanation: The requested command or option (cmd) is not supported in the current display mode.

The command or option is ignored.

Corrective Action: Request a command or option that is valid in the current display mode.

CTM66BS ABEND "`abCode` " OCCURRED IN "`imod` "

Explanation: Due to an internal error, an abCode abend occurred in the imod module

Execution stops following the abend.

Corrective Action: Ask your system programmer to prepare the Control-M monitor full output and contact BMC Customer Support. If requested, issue the command DUMP ON, so that a dump is generated the next time this abend occurs.

CTM66CE ENTER `cmd` PARAMETER

Explanation: The cmd command was entered without mandatory parameters.

The command is ignored.

Corrective Action: Supply the required parameters and re-enter the command.

CTM66DI STRING NOT FOUND

Explanation: This information message indicates that the string specified in a FIND command or the prefix specified in a LOCATE command was not found.

Corrective Action: No action is required.

CTM66FE OPTION "F" CANNOT BE ISSUED FOR TASK IN "<GROUP HELD>" STATE

Explanation: When the status of a group is Held, the status of all the jobs belonging to that group changes to GRP Held. Individual jobs with the status GRP Held cannot be freed. Only the group itself can be freed.

The status of the job remains unchanged.

Corrective Action: If required, you can use the F (Free) option to free the group. This will free all the jobs belonging to the group.

CTM670S INTERNAL ERROR. CANNOT BUILD ZOOM SCREEN

Explanation: Internal Control-M error while building the Zoom screen.

Corrective Action: Have your system programmer contact BMC Customer Support for assistance.

CTM671E CANNOT `action` TASK `taskName` ODATE `odate` - IN REQUESTED CHANGE MODE

Explanation: A user tried to FREE or DELETE a task that is still in the REQUESTED CHANGE mode.

The request is ignored.

Corrective Action: Wait until the REQUESTED CHANGE status disappears and then try again.

CTM672E CANNOT SAVE JOB DATA. INSUFFICIENT SPACE IN FILE. USE LESS DATA

Explanation: Additional data were added to the job on the Zoom screen and the message appears as a result of the SAVE command. When a job order is placed on the Active Jobs file a certain amount of space is reserved for possible future addition of data by the user. This message appears whenever this space is exhausted.

The new job data are not saved.

Corrective Action: Try to delete some data in the Zoom screen. If you are trying to add ON STEP statements, try to delete other ON STEP statements, for OUT conditions, delete unnecessary OUT statements, and the like. Deleting all SHOUT WHEN messages usually releases enough space.

If all the above fail, delete the job order and reissue it manually with the new data (using the CLIST CTMJOBRQ). If the problem persists, contact BMC Customer Support.

CTM673E CANNOT `action` TASK `taskName` ODATE `odate` - TASK IN PROCESS

Explanation: A request to delete a task in process or to Force OK a Group task that is not in ENDED status could not be performed. Only a task that awaits scheduling or has ended can be deleted. Force OK is valid only for a Group Task that has ended (in other words, all its jobs have ended).

The requested action is not performed.

Corrective Action: Depending on the requested action, take the necessary steps and repeat the request if desired.

CTM674E CANNOT `action` TASK `taskName` ODATE `odate` - PATH REQUEST ACTIVE

Explanation: An attempt was made to delete a task in Wait Schedule state, after the task, which is of critical path priority, already reserved the resources for execution. A critical path priority task reserves Control Resources and Quantitative Resources, to obtain all the runtime resources required for its execution. You cannot delete such a task as long as the resources are still reserved.

The request is ignored.

Corrective Action: To delete the task, do the following:

HOLD the task, and wait until it is in the HELD status.
Enter the Status Zoom screen.
Clear the Priority field of the task, and save it.
Wait until the REQUESTED CHANGE status disappears.
FREE the task, and wait until the REQUESTED FREE status disappears.
HOLD the task again, and wait until the REQUESTED CHANGE status disappears indicating that the task is HELD.
Delete the task.

CTM675S INTERNAL ERROR - UNEXPECTED RETURN CODE FROM CTMTVEW

Explanation: Internal error. An unexpected return code was received from the CTMTVEW Control-M program (View screen).

Corrective Action: Have your system programmer contact BMC Customer Support for assistance.

CTM676E PLEASE ERASE STEP NAMES WHEN SPECIFYING RESTART=N

Explanation: RESTART was set to N with either FROM stepname or TO stepname. FROM stepname and TO stepname describe how the job is restarted by Control-M/Restart. Therefore, they cannot be specified when RESTART is set to N.

Corrective Action: For restart processing set RESTART to Y. When rerun is needed without restart processing, erase the FROM step and the TO step fields.

CTM677E ACTION IGNORED - STATUS OF TASK CHANGED

Explanation: A CONFIRM (C), or RERUN (R) was issued for a job whose status was already changed. While you were looking at the screen, another user or the Control-M monitor changed the status of the job or the contents of the production parameters.

The requested action is ignored.

Corrective Action: Press Enter again, check the job status, and act accordingly.

CTM678I `taskTypememNameorderIdodate` MODIFIED: BY `userId` FROM `pgmStepName1.procStepName1` TO `pgmStepName2.procStepName2`

Explanation: The restart decision was changed from pgmStepName1.procStepName1 to pgmStepName2.procStepName2 during rerunning (R) of the task or confirmation of the restart of the task (C). Restart determines in which steps Control-M/Restart tries to start and end a restarted job. The original restart decision was manually modified, and this message indicates the new restart decision.

If and when this task is restarted, the new restart decision will be used.

Corrective Action: No action is required.

CTM679E TASK IS NOT WAITING FOR CONFIRMATION

Explanation: A request to confirm (C) the restart of a task that is not waiting for confirmation failed. Confirm is valid only for tasks which are in WAIT CONFIRMATION status.

Confirm is ignored.

Corrective Action: No action is required.

CTM67BI "BROWSE" FORCED - JOB DID NOT COMPLETE PROCESSING

Explanation: The customer issued 3.Z (ZOOM) command for the job in HELD ENDED status, but Control-M did not completely finish the processing of the job. The last step of post-processing (the handling of SHOUTs and OUTPUT CONDITIONS) was not completed. In this situation, the SAVE command (under ZOOM) may prevent Control-M from executing DO COND and DO SHOUT actions. For this reason, 3.Z is forced to BROWSE mode, where change/save is not possible.

3.Z is forced to BROWSE mode.

Corrective Action: If the job should be changed (and BROWSE mode is not acceptable), the user should FREE the job, wait several seconds (to enable Control-M to finish processing of the job), then HOLD and ZOOM again.

CTM67CI JCL WAS SAVED TO LIBRARY=`library` MEMBER=`member`

Explanation: Edit JCL was performed through IOA Online option 3.J. The change was saved to the specified library and member.

Corrective Action: No action is required.

CTM680E MEMBER `memName` DOES NOT EXIST IN THE LIBRARY

Explanation: The memName member that was requested is not in the library.

Possible causes are:

New Day procedure - Failure to read a calendar from the data set described by the DACAL DD statement.
Control-M AutoEdit facility - Failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - You are trying to save a table, mission, tree, or rule that does not exist.

The system action depends on the cause, as follows:

New Day procedure - This job order is not scheduled, and the New Day processing ends with errors.
Control-M AutoEdit facility - Job submission stops.
IOA Online facility - The table, mission, tree, or rule is not saved.

Corrective Action: The appropriate response depends on the cause, as follows:

New Day procedure - Correct the name of the calendar in the production parameters table. Correct the contents of the Date Control Record (dates 2,3,4,5), and, if necessary, run the New Day procedure again. If New Day processing already placed job orders on the Active Jobs file, they may be placed there twice. Therefore, add the corrected job order manually, using the CLIST CTMJOBRQ.
Control-M AutoEdit facility - Correct the JCL of the job and rerun it.
IOA Online facility - To save a new table, mission, tree, or rule, delete the Y in the SAVE field, type Y in the CREATE field, and press Enter.

CTM681E `[[taskType memName] jobName|jobId orderId]` DSN `dsn` - IS NOT A LIBRARY

Explanation: The requested DSN is not a partitioned data set.

Possible causes are:

New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.
Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.

The system action depends on the cause, as follows:

New Day procedure - ends with errors.
AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.

Corrective Action: The appropriate response depends on the cause, as follows:

New Day procedure - Correct the name of the data set described by the DACAL DD statement to the name of your calendar library.
AutoEdit facility - Correct the JCL for the job and rerun it.
Online facility - Correct the library name and retry.

CTM682E MEMBER `memName` ALREADY EXISTS

Explanation: The memName member that you are trying to create already exists in the specified library.

The memName member is not created.

Corrective Action: Correct the member name and try again.

CTM683E ERROR WHILE READING RECORD

Explanation: A problem has occurred during the reading of a record.

Corrective Action: Make sure you chose the correct library.

CTM684E `[[taskType memName] jobName|jobId orderId]` DSN `dsn` IN USE (DISP=OLD)

Explanation: The DSN is held exclusively by another user. Possible causes are:

Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.
Control-O - initialization.
CMEM - initialization.
IOA/Control-M utility - schedule definition or calendar definition.

The system action depends on the cause, as follows:

AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.
Control-O is not started.
CMEM is not started.
IOA/Control-M utility - utility terminates with a nonzero return code.

Corrective Action: Try again.

CTM685E `[[taskType memName] jobName|jobId orderId]` INTERNAL ERROR ON GETMEM: `func`. SEE MESSAGES AND CODES

Explanation: Internal Control-M error while trying to read a member from a library.

Possible causes are:

New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.
Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.
IOA/Control-M utility - schedule definition or calendar definition.

The system action depends on the cause, as follows:

New Day procedure - terminates with errors.
AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.
IOA/Control-M utility - utility terminates with a nonzero return code.

Corrective Action: Look for additional messages on IOA Log that may clarify the picture. If you can, correct the problem, and continue according to the CTM680 message. Under the Online facility, it may be helpful to log off and log on again.

In any case, prepare the Control-M monitor full output and contact BMC Customer Support. Note the function code (func), which will help the BMC support team resolve the problem.

CTM686E `[[taskType memName] jobName|jobId orderId]` DSN `dsn` IS NOT IN CATALOG

Explanation: The requested DSN (dsn) is not in the catalog.

Possible causes are:

Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.
New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.

The system action depends on the cause, as follows:

AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.
New Day procedure - ends with errors.

Corrective Action: The appropriate response depends on the cause, as follows:

AutoEdit facility - correct the JCL for the job and rerun it.
Online facility - correct the library name and retry.
New Day procedure - correct the New Day procedure and retry.

CTM687E `[[taskType memName] jobName|jobId]` OID=`orderId` DSN `dsn` - DYNAMIC ALLOCATION FAILED

Explanation: Dynamic allocation for the requested DSN (dsn) failed. Possible causes are:

Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement)
IOA Online facility - schedule, calendar or rule definition.

This can also happen when the Control-M Online facility is activated under the Control-M Online facility (nesting) and you are trying to access the same library in two screens.

The system action depends on the cause, as follows:

AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.

Corrective Action: Exit the Online facility and retry. If this happens under batch environment or in Control-M AutoEdit facility, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTM688E `[[taskType memName] jobName|jobId orderId]` INTERNAL ERROR - INVALID REQUEST TO IOAMEM. INFORM IOA ADMINISTRATOR

Explanation: Internal IOA error while trying to read a member from a library. Possible causes are:

New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.
IOA AutoEdit facility - failure to allocate or read a symbols member (a %%GLOBAL statement, or a %%LIBSYM %%MEMSYM statement, or a %%INCLIB %%INCMEM statement). When using the %%INCMEM DDNAME= ddn format, ensure that ddn is allocated by the required procedure (Control-M monitor, IOA Logon procedure, and so on).
IOA Online facility - Schedule, calendar or rule definition.

The system action depends on the cause, as follows:

New Day procedure - ends with errors.
AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTM689E `[[taskType memName] jobName|jobId orderId]` MAXIMUM NUMBER OF MEMBERS/LINES IN MEMBER EXCEEDED

Explanation: An attempt to read a large member from the library failed.

The system action and appropriate user response depend on the circumstances at the time the message is issued, as follows:

If this message was issued during the New Day procedure, the cause is failure to read a calendar from the data set described by the DACAL DD statement. In this case, job submission fails. Increase the REGION size or LOGON size, and try again.
If this message was issued while you were using the Control-M AutoEdit facility, the cause is failure to read one of the following symbols members:

a %%GLOBAL statement
a %%LIBSYM %%MEMSYM statement

In this case, job submission fails. Increase the REGION size or LOGON size, and try again.

If this message was issued while you were using the Control-M Online facility, the cause is failure to access a schedule or calendar definition. Increase the REGION size or LOGON size, and try again.
If this message was issued while you were using the CTMTBUPD or CTMXRF Control-M utilities, the cause is failure to access a schedule definition. In this case, utility execution fails. Increase either the SLINMAX or the SCHDMAX utility control statements, as appropriate. For more information, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTM68AE `[[taskType memName] jobName|jobId] orderId` MEMBER NAME IS MISSING

Explanation: The parameter list passed to IOAMEM must include the requested member name, which is missing.

The request to IOAMEM is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTM68BE `[[taskType memName] jobName|jobId] orderId` DDNAME `ddName` HAS ALREADY BEEN ALLOCATED

Explanation: IOAMEM received a request to allocate a DD name (ddName) that has already been allocated.

The request to IOAMEM is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTM68CE `[[taskType memName] jobName|jobId] orderId` DSN `dsn` - OPEN FAILED

Explanation: The open process of the dsn data set failed.

The request to IOAMEM is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTM68DE `[[taskType memName] jobName|jobId] orderId` DSN `dsn` IS NOT FOUND ON VOLUME

Explanation: IOAMEM detected that the requested data set (dsn) does not exist on the volume pointed to by the MVS catalog

The request to IOAMEM is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTM68EE `[[taskType memName] jobName|jobId] orderId` DDNAME `ddName` IS NOT ALLOCATED TO DSNAME `dsn`

Explanation: IOAMEM received a request to access a data set (dsn) allocated to the ddName DD name, but that dsn is not, in fact, allocated to the ddName DD name.

The request to IOAMEM is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTM68FE `[[taskType memName] jobName|jobId] orderId` LIBRARY NAME IS MISSING

Explanation: The parameter list passed to IOAMEM must include a library name, which is missing.

The request to IOAMEM is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTM68GE `[[taskType memName] jobName|jobId] orderId` DATASET `dsn` IS MIGRATED

Explanation: IOAMEM detected that the requested data set (dsn) is migrated by a space management product such as DFSMSHSM, and it cannot be accessed

The request to IOAMEM is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTM68IE FORMCND MUST BE RUN WITH //DACNDF DD DISP=NEW OR DISP=OLD

Explanation: This messages is issued by the FORMCND procedure (program IOABCN), which formats the conditions file when it is submitted with DISP=SHR instead of DISP=NEW or DISP=OLD.

The format is not run.

Corrective Action: Stop all Control-X monitors and re-run the FORMCND procedure with DISP=OLD.

CTM68JE LIBRARY libName MEMBER memName DYNAMIC ALLOCATION FAILED

Explanation: The IOAMEM program failed to allocate memory to the specific member in the specific library.

Corrective Action: Troubleshoot your environment for memory issues.

CTM690E `[[taskType memName] jobName|jobId orderId]` INVALID RETURN CODE FORM CTMMEM - INFORM IOA ADMINISTRATOR

Explanation: Internal IOA error while trying to read a member from a library. Possible causes are:

New Day procedure - Failure to read a calendar from the data set described by the DACAL DD statement.
IOA AutoEdit facility - Failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - Schedule definition or calendar definition.

The system action depends on the cause, as follows:

New Day procedure ends with errors.
AutoEdit facility - Job submission stops.
Online facility - Reading or updating of the table or calendar is not performed.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTM691E `[[taskType memName] jobName|jobId orderId]` ERROR WHILE PROCESSING DIRECTORY OF LIBRARY

Explanation: Internal Control-M error while trying to read a directory of a library during schedule definition, calendar definition, batch utility, etc.

Online facility - Tables or calendars list is not shown.

Corrective Action: For batch utility, correct the error and rerun the job.

CTM692E `[[taskType memName] jobName|jobId orderId`] LIBRARY OPERATION FAILED. REASON `rsn`

Explanation: Internal Control-M error while trying to process a member from a library. Possible causes are shown in the following table:

Circumstances	System Action	Possible Cause
New Day procedure	New Day procedure terminates with errors	Failure to read a calendar from the data set described by the DACAL DD statement
Control-M AutoEdit facility	Job submission is stopped	Failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement)
Control-M Online facility	Processing of schedule, mission, rule or calendar definition is not performed	Internal failure to process the schedule, mission, rule or calendar definition

Corrective Action: Examine any prior system message. If there is no such message, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTM693E `orderId` {TABLE | MISSION | TREE | RULE} DOES NOT EXIST {TABLE | MISSION | TREE | RULE} NOT SAVED

Explanation: You are trying to save a table, mission, tree, or rule that does not exist.

The table, mission, tree, or rule is not saved.

Corrective Action: To save a new table, mission, tree, or rule, erase the Y in the SAVE field, mark Y in the CREATE field, and click Enter.

CTM694E `orderId` {TABLE | MISSION | TREE | RULE} ALREADY EXISTS - CANNOT BE CREATED

Explanation: The table, mission, tree, or rule you are trying to create already exists in the specified library.

The table, mission, tree, or rule is not created or saved.

Corrective Action: Either specify Y in the SAVE field to replace the existing table, mission, tree, or rule with the changed one, or change its name to a new name.

CTM695I `taskType memName odate orderId` RESTART DECISION DELETED BY `userId`. RESTART WILL NOT BE PERFORMED

Explanation: While rerunning or confirming the rerun of the job, the user deleted the restart decision of the job.

The job will be rerun without restart processing.

Corrective Action: No action is required.

CTM696E DSN RECORD FORMAT DOES NOT MATCH THE REQUESTED RECORD FORMAT

Explanation: An error occurred in the CTMMEM module.

The CTMMEM module detected that the record format of the library to be opened differs from the requested record format.

The library or DD name is not allocated.

Corrective Action: If the CTMMEM module was invoked from a user-written program or from one of the user exits, check the parameters passed by the calling program to CTMMEM, and ensure that they match the DCB parameters of the library that the user-written program intends to access.

If the call was not made by a user exit or user-written program, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTM697I `jobName orderId odate` WAS DELETED BECAUSE ITS GROUP ENTITY `grp` (ID=`groupId`) DELETED

Explanation: This information message indicates that the jobName job with the orderId order ID and odate order date was deleted, because the grp group entity with the groupId order ID, to which this job belongs, was deleted.

Corrective Action: No action is required.

CTM698I `grp orderId odate` WAS UNDELETED BECAUSE JOB `jobName` (OID=`jobId`) UNDELETED

Explanation: This information message indicates that the grp group entity with the odate order date and the orderId order ID was undeleted because the jobName job with the jobId order ID, to which this job belongs, was undeleted by an UNDELETE command.

Corrective Action: No action is required.

CTM699E `grp orderId odate` NOT DELETED, NOT ALL JOBS ARE ELIGIBLE FOR DELETION

Explanation: A request to delete the grp group entity with the odate order date and the orderId order ID was issued. However, not all jobs in this group are eligible for deletion.

Jobs belonging to the specified group that can be deleted are deleted. Jobs that are not ready for deletion remain in their original queue. The group entity is not deleted.

Corrective Action: Wait until all the jobs that belong to the specified group have finished execution, then try again to delete the group.

CTM69AE NO SPACE LEFT IN THE DIRECTORY

Explanation: The library directory is full.

Corrective Action:Compress or enlarge the appropriate library.

CTM69BI NO MEMBERS MATCH THE MEMBER-NAME FILTER

Explanation: No matching member was found in the library or the library had no members.

Corrective Action:Correct the member-name used in the filter or ensure that the library is not empty, then try again.

CTM69CE "JSORT" MUST BE FOLLOWED BY "RBA" OR "ORDERID"

Explanation: The JSORT command requires either a RBA or ORDERID subparameter. The order in which the jobs are displayed in screen 3 can be controlled by the JSORT command.

Corrective Action:Do one of the following:

Type JSORT RBA on the command line, to display the jobs in the order of their physical location on the AJF (relative byte address).
Type JSORT ORDERID on the command line, to display the jobs in order-id sequence.

CTM6A0I ARCHIVED SYSOUTS DO NOT EXIST FOR THIS TASK

Explanation: This information message indicates that there are no sysouts to be viewed. You can only view an existing sysout. Either no sysout was generated, or the existing sysout was manually deleted.

Corrective Action: No action is required.

CTM6A1E LOCATE RBA COMMAND REQUIRES RBA AS PARAMETER

Explanation: A Locate RBA command (RBAL) was specified with no, or more than one, RBA parameter. Only one RBA parameter, consisting of from 1 through 6 hexadecimal digits, must be specified for the Locate RBA command.

The Locate RBA command is not executed.

Corrective Action: Specify the Locate RBA command correctly.

CTM6A2E RBA INVALID

Explanation: An invalid RBA value was specified in the Locate RBA command (RBAL). The value specified for the RBA parameter in the Locate RBA command must contain from 1 through 6 hexadecimal digits.

The Locate RBA command is not executed.

Corrective Action: Enter the Locate RBA command with a valid RBA value.

CTM6A3E RBA OUT OF RANGE

Explanation: The Locate RBA command was specified with an RBA parameter which exceeded the highest RBA in the Active Jobs file.

The Locate RBA command is not executed.

Corrective Action: Enter the Locate RBA command with a correct RBA value.

CTM6A4S INITIALIZATION OF MAIN LIB FAILED. DDNAME "DALIB"

Explanation: An attempt was made to edit the JCL of a job by using line command J in the Control-M Active Environment screen or the Schedule Setup screen. The job in question had MEMLIB set to GENERAL, but the DALIB is not allocated to the user.

Corrective Action: Allocate DALIB to the user, and reenter line command J.

CTM6A5S AN ERROR OCCURRED (REASON=`rsn`, RBA=`rba`) INDEXING FORCED OFF

Explanation: An error occurred while trying to process the indexing in the Control-M Active Environment screen. The displayed reason code (rsn) indicates the reason for the error.

Possible values for rsn are:

01 through 03 - The record the program tried to read was not an index record.
04 - GETMAIN for the indexing area failed.
05 - Loading of the CTMHSR module failed.

The Active Environment screen response time may slow significantly.

Corrective Action: Press Enter to return to the Active Environment screen. Inform the INCONTROL administrator, indicating the reason code and the RBA specified in the message. The INCONTROL administrator should proceed according to the reason code, as follows:

01 through 03 - Ensure that the Active Jobs file (AJF) is not corrupted, and run the CTMCAJF COMPRESS utility to rebuild the indexes. This action can be delayed, but until it is performed, online response may be slow.
04 - Enlarge the user region.
05 - Ensure that the CTMHSR load module appears in the IOA load library.

CTM6ABE "KILL" COMMAND NOT ALLOWED FOR NJE

Explanation: The Kill command cannot issued in screen 3 for a job that is executing on a remote NJE node.

Corrective Action: To clear the job, manually set the job to non-NJE (by setting the NJE field to N or blank via 3.Z).

This can be done by doing the following:

HOLD the Job.
ZOOM and blank out the NJE field (it will probably be found set to 'Y').
SAVE and FREE the Job.

After a short time, the Job goes to ENDED status.
Now the Job can be HELD and DELETE-ed.

CTM6ACE "RSORT" MUST BE FOLLOWED BY "FLOW" OR "NAME"

Explanation: The RSORT command requires either a FLOW or NAME subparameter. The order in which the Rerun Flow jobs are displayed in screen 3 can be controlled by the RSORT command.

Corrective Action: Do one of the following:

Type RSORT FLOW on the command line, to display the jobs in the order of the flow(with predecessor jobs displayed before their successors).
Type RSORT NAME on the command line, to display the jobs in alphabetical order.

CTM6ADE SUMMARY HAS MORE THAN 128 CHARACTERS

Explanation: The total number of characters in the summary exceeds 128 characters.

Corrective Action: Shorten the summary so that it contains fewer than 128 characters. Each line of the summary may contain up to 70 characters.

CTM6AEE DESCRIPTION HAS MORE THAN 1024 CHARACTERS

Explanation: The total number of characters in the description exceeds 1024 characters.

Corrective Action: Shorten the description so that it contains fewer than 1024 characters.

CTM6AFE DO REMEDY IS NOT SUPPORTED IN THIS RELEASE

Explanation: The DO REMEDY parameter is only supported in INCONTROL for z/OS version 6.2.18 and later.

Corrective Action: Install version 6.2.18 or later.

CTM6AGE SUMMARY AND DESCRIPTION LINES MUST BE ENTERED

Explanation: The summary and description lines have been left blank.

Corrective Action: Enter information into the summary and description lines.

CTM6AHE URGENCY MUST BE L, M, H, U, OR BLANK

Explanation: The URGENCY parameter must be set to one of the following values:

L - Low
M - Medium
H - High
U - Urgent
Blank - Default, which is equivalent to Low urgency

Corrective Action: Enter a valid value.

CTM6B1I JOB `jobName` / ORDERID `orderId` WAS ORDERED BUT CANNOT BE BRIDGED

Explanation: The ADJUST CONDITIONS parameter for the SMART Table is set to B (Bridge), but a bridge could not be applied to this job. The SMART Table is ordered without applying the bridge.

This message is followed by message CTM6B2I, which contains more information about the reason for the issue.

Corrective Action: Consider adjusting job conditions, based on the information in message CTM6B2I.

CTM6B2I REASON: `reason`

Explanation:This message provides one of the following reasons for the failure to apply a bridge, as reported in message CTM6B1I:

Complex conditions logic – The scheduled job contains a complex IN condition, such as a condition with OR, Not, or parentheses.
Condition is added by more than one job – A condition that is used by multiple jobs was detected. Message CTM6B3I provides the name of the condition.
Complex conditions logic in not-ordered predecessor – The unscheduled predecessor job contains a complex condition. Message CTM6B3I provides the name of the predecessor job and the name of the condition.

Corrective Action: Consider adjusting job conditions, based on the information in this message.

CTM6B3I CONDITION `conditionName` |
CTM6B3I PREDECESSOR JOB NAME `jobname` CONDITION `conditionName`

Explanation: This message follows message CTM6B2I and provides the name of the condition that prevented the bridge from being applied. In certain cases, the name of the predecessor is provided, as well.

Corrective Action: Consider adjusting job conditions, based on the information in this message and the preceding messages.

CTM6B4I INPUT CONDITION `condition` REMOVED BY ADJUST BRIDGE PROCESSING

Explanation: This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).

This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.

Corrective Action: No action is required.

CTM6B5I INPUT CONDITION `condition` ADDED BY ADJUST BRIDGE PROCESSING

Explanation: This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).

This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.

Corrective Action: No action is required.

CTM6B6I OUTPUT DELETE CONDITION `condition` OF JOB `jobName` ADDED BY ADJUST BRIDGE

Explanation: This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).

This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.

Corrective Action: No action is required.

CTM6B7I OUTPUT DELETE CONDITION `condition` ADDED TO SMART TABLE BY ADJUST BRIDGE

Explanation:This information message describes a step performed during the process of applying a bridge in a SMART Table (with ADJUST CONDITIONS set to B).

This message is issued only if the level of detail is set by the ADJBCMSG parameter to Y.

Corrective Action: No action is required.

CTM6B8E ADJUST CONDITIONS FAILED DUE TO `reason`

Explanation: The process of applying a bridge in a SMART Table failed due to an internal error or insufficient memory. The SMART Table is ordered without applying the bridge.

Corrective Action: For a memory issue, try increasing the region size specified in the JOB or EXEC JCL. For an internal error, contact BMC Support.

CTM6B9E SMART TABLE CANNOT BE ADJUSTED. ADDED BRIDGES WILL EXCEED THE MAXIMUM TABLE/JOB SIZE.

Explanation:The process of applying a bridge in a SMART Table failed because adding a condition would cause the job or table to exceed the maximum allowed size. The SMART Table is ordered without applying the bridge.

Corrective Action: Consider adjusting your job or table.

CTM6BAI JOB'S CONDITIONS WERE ADJUSTED BY ADJUST BRIDGE PROCESSING

Explanation:During the process of applying a bridge in a SMART Table, conditions were successfully adjusted in a job.

Corrective Action: No action is required.

CTM6BBI JOB'S CONDITIONS WERE PARTIALLY ADJUSTED BY ADJUST BRIDGE PROCESSING

Explanation: During the process of applying a bridge in a SMART Table, adjustments to a job’s conditions were only partially successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I.

Corrective Action: No action is required.

CTM6BCI JOB'S CONDITIONS WERE NOT ADJUSTED BY ADJUST BRIDGE PROCESSING

Explanation: During the process of applying a bridge in a SMART Table, adjustments to a job’s conditions were not successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I.

Corrective Action: No action is required.

CTM6BDI SMART TABLE WAS ADJUSTED BY ADJUST BRIDGE PROCESSING

Explanation: The SMART Table was successfully adjusted during bridge processing.

Corrective Action: No action is required.

CTM6BEI SMART TABLE WAS PARTIALLY ADJUSTED BY ADJUST BRIDGE PROCESSING

Explanation: Adjustments to the SMART Table during bridge processing were only partially successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I.

Corrective Action: No action is required.

CTM6BFI SMART TABLE WAS NOT ADJUSTED BY ADJUST BRIDGE PROCESSING

Explanation: Adjustments to the SMART Table during bridge processing were not successful. More information is provided in messages CTM6B1I, CTM6B2I, and (sometimes) CTM6B3I. The SMART Table is ordered without applying the bridge.

Corrective Action: No action is required.

Messages CTM700 through CTM7xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM700E PLEASE FILL IN LIBRARY NAME

Explanation: The library name is missing.

Corrective Action: Specify the library name.

CTM701E PLEASE FILL IN TABLE NAME OR OMIT JOB NAME

Explanation: The job name is specified, but the table name is missing. A job must be defined in a table.

Corrective Action: To get a list of tables in the library, either fill in a table name, or omit the job name.

CTM703E ELAPSE VALUE CANNOT EXCEED 1440 MINUTES (ONE DAY)

Explanation: An invalid value is specified in the ELAPSE parameter. The maximum ELAPSE time for a job is 1440 minutes.

Corrective Action: Enter a value not greater than 1440.

CTM704E MAXIMUM NUMBER OF STEP RANGE LINES EXCEEDED

Explanation: More than 100 STEP RANGE lines were specified on the Job Scheduling Definition screen or on the Job Zoom screen. The maximum number of STEP RANGE lines permitted on a Job Scheduling Definition screen is 100.

Corrective Action: Remove the excess STEP RANGE lines.

CTM705E INVALID OPTION FOR GROUP DEFINITION

Explanation: The line command is invalid for a group definition.

The command is not executed.

Corrective Action: Either choose a line command that is valid for group definitions, or select a job definition for which the line command is valid.

CTM706E ORDER COMMAND NOT ALLOWED FOR GROUP TABLE

Explanation: The O (ORDER) line command was entered for a job that is part of a group. The O line command is valid only for jobs that do not belong to a group.

Control-M prompts for a new line command.

Corrective Action: Change the line command.

CTM707E INVALID CALENDAR REFERENCE OR SCHEDULING ERROR

Explanation: The P option was used to view the scheduling dates of a job containing an error in its basic scheduling criteria. The basic scheduling criteria of this job had at least one parameter that could not be correctly evaluated by the CTMRPLN utility.

Possible causes are:

The DCAL or WCAL parameter points to a member that does not exist in the calendar library.
The calendar member does not contain the date range specified by the user. Both the current and next year following the end date should be defined in the calendar.

The P option is not executed for this job.

Corrective Action: Check the DCAL and WCAL parameters in the basic scheduling criteria for the job. Check the date range in the calendar member. Correct accordingly, and reactivate the P option.

CTM708E DELETE COMMAND NOT ALLOWED FOR LAST JOB IN GROUP TABLE

Explanation: An attempt to delete the last remaining job definition in a group table failed. Every group table must have at least one job definition.

The D (Delete) option is not executed for this job definition.

Corrective Action: Delete the entire group table.

CTM709I COPY CANCELLED DUE TO USER REQUEST

Explanation: A copy process was cancelled by the PF03 key. A window is displayed when a request is submitted to copy a job definition.

The copy process is terminated.

Corrective Action: No action is required.

CTM70AE REQUIRED FIELD IS MISSING

Explanation: The user failed to specify a mandatory field. Values must be specified for several fields, for example, the destination table name.

The copy request is not processed.

Corrective Action: Press PF03 to cancel the copy request or fill in the required data.

CTM70BE CANNOT COPY TO THE SAME TABLE

Explanation: The specified destination table is the table that currently contains the job definition. An attempt to copy a job definition from a table into the same table failed.

The copy request is not processed.

Corrective Action: Press PF03 to cancel the copy request or specify a different destination table name.

CTM70CI COPY WAS EXECUTED SUCCESSFULLY

Explanation: The message is issued when one of the following components has been successfully copied:

IOA component job definition
CTO rule
CMEM rule
CTT rule
CTD mission definition
IOA calendar definition

Corrective Action: No action is required.

CTM70DE SPECIFIED LIBRARY DOES NOT EXIST

Explanation: The user tried to copy a job definition into a destination data set that does not exist.

The copy process is not implemented.

Corrective Action: Allocate the destination data set and try again to copy the job definition.

CTM70EE THIS ENTRY TYPE CANNOT BE COPIED

Explanation: An attempt to copy a group job into another table failed. A job that is part of a group cannot be copied into another table.

The copy process is not implemented.

Corrective Action: No action is required.

CTM70FE GENERAL ERROR DURING COPY PROCESS RC = `rc`

Explanation: Usually, an error has occurred during the copy process, causing a return code (rc) of 004 to be generated.

The copy process is terminated.

Corrective Action: Contact BMC Customer Support.

CTM70GE CANNOT COPY TO THE SAME RBC

Explanation: The current RBC definition is specified as the RBC destination. The copy request is not processed.

Corrective Action: Cancel the copy request or specify a different RBC definition.

CTM70HI RBC RENAMED SUCCESSFULLY

Explanation: An RBC definition has been successfully renamed.

Corrective Action: No response needed.

CTM70II RENAME CANCELLED DUE TO USER REQUEST

Explanation: A rename process was cancelled by the PF03 key. A window is displayed when a request is submitted to rename an RBC definition. The rename process is terminated.

Corrective Action: No response needed.

CTM710E PLEASE FILL IN A VALID OPTION - "Y" OR "N"

Explanation: An invalid exit option was specified. The cursor points to the invalid value.

Valid options are:

Y (Yes)
N (No)

Corrective Action: Type Y (Yes) or N (No) in one of the exit options.

CTM711E ONE (AND ONLY ONE) EXIT OPTION MUST BE MARKED AS "Y" OR "N"

Explanation: Both exit options were marked either as Y or N. One exit option must be marked Y the other N.

Corrective Action: Change one of the exit options to Y or N accordingly.

CTM712E MISSING CONTINUATION CONDITION NAME

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the continuation condition field is empty. In this case, the continuation condition field must contain at least one character.

Corrective Action: Do one of the following:

For a short condition, remove CONT from the first dateref field.
For a long condition, type at least one character in the continuation condition field.

CTM713E LENGTH OF CONTINUATION CONDITION MAY NOT EXCEED 19 CHARACTERS

Explanation: The continuation condition field contains more than 19 characters, which is the maximum allowed.

Corrective Action: Ensure that the text of the continuation condition contains at least one, but no more than 19 characters.

CTM714E INVALID DATE REF 'CONT' - COND NAME MUST BE 20 CHAR

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the first condition field has less than 20 characters. In this case, all 20 spaces in the first condition field, and at least one in the continuation condition field, must be used.

Corrective Action: Do one of the following:

For a short condition, remove CONT from the first dateref field.
For a long condition, use all 20 spaces in the first condition field, and at least one in the continuation condition field.

CTM715E RIGHT PARENTHESIS IS NOT VALID IN CONTINUATION CONDITION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the first condition field contains a Boolean right (closing) parenthesis character ')'. In this case, the condition must continue into the continuation condition field. A Boolean closing parenthesis may not end the condition in the first condition field.

Corrective Action: Do one of the following:

For a short condition, remove CONT from the first dateref field.
For a long condition, remove the closing parenthesis from the first condition field, use all 20 spaces in the first condition field, and use at least one space in the continuation condition field.

CTM716E LEFT PARENTHESIS IS NOT VALID IN CONTINUATION CONDITION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the continuation condition field contains a Boolean left (opening) parenthesis character '('. In this case, the condition must begin in the first condition field. A Boolean opening parenthesis may not start the condition in the continuation condition field.

Corrective Action: Do one of the following:

For a short condition, remove CONT from the first dateref field and clear the continuation condition field.
For a long condition, move the opening parenthesis to the beginning of the first condition field and use all 20 spaces in the first condition field, and use at least one space in the continuation condition field.

CTM717E OR SIGN '|' IS NOT VALID IN CONTINUATION CONDITION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the continuation condition field of a long condition contains a logical OR symbol '|'. In this case, the condition must begin in the first condition field. The logical OR symbol is valid only at the beginning of the first condition field of a long condition.

Corrective Action: Do one of the following:

For a short condition, remove CONT from the first dateref field and clear the continuation condition field.
For a long condition, move the logical OR symbol to the beginning of the first condition field, use all 20 spaces in the first condition field, and use at least one space in the continuation condition field.

CTM718E ONLY BLANK ALLOWED IN CONTINUATION CONDITION DATE-REF OPTION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the first opt field for the condition is not blank. In this case, the first opt field must be blank and the second opt field, after the continuation condition and the second dateref field, controls condition handling at the end of the job.

For short conditions, the value in the first opt field controls whether the condition is added to the Conditions file at the end of the job (+) or removed from it (-).

Corrective Action: Do one of the following:

For a short condition, remove CONT from the first opt field and clear the continuation condition field.
For a long condition, clear the first opt field and enter a valid value (+ or -) in the second one.

CTM719E TOO MANY "DO COND" - ONLY 245 ARE ALLOWED

Explanation: There are more that 245 DO COND statements in a single job scheduling definition. The maximum number of DO COND statements in each job scheduling definition is 245.

Corrective Action: Remove any extra DO COND statements.

CTM71AE PLEASE FILL IN AT LEAST ONE ADDRESS IN THE "TO" FIELD

Explanation: No address was entered in the TO field of a DO MAIL statement.

Corrective Action: Enter at least one address in the TO field of the DO MAIL statement.

CTM71BE TOO MANY DO MAIL "TO" LINES - ONLY 255 ARE ALLOWED

Explanation: More than 255 lines were entered in the TO field of a DO MAIL statement.

Corrective Action: Correct the contents of the TO field in the DO MAIL statement so that the field contains no more than 255 lines.

CTM71CE TOO MANY DO MAIL "CC" LINES - ONLY 255 ARE ALLOWED

Explanation: More than 255 lines were entered in the CC field of a DO MAIL statement.

Corrective Action: Correct the contents of the CC field in the DO MAIL statement so that the field contains no more than 255 lines.

CTM71DE TOO MANY DO MAIL TEXT LINES - ONLY 255 ARE ALLOWED

Explanation: More than 255 lines were entered in the TEXT field of a DO MAIL statement.

Corrective Action: Correct the contents of the TEXT field in the DO MAIL statement so that the field contains no more than 255 lines.

CTM71EE PLEASE FILL IN A VALID OPTION - "Y" OR "N" OR "D"

Explanation: An invalid value was entered for ATTACH SYSOUT.

Corrective Action: Correct the field contents.

CTM720E PLEASE FILL IN MEMBER NAME

Explanation: Missing MEMBER NAME. The MEMNAME field is obligatory.

Corrective Action: Fill in the name of the member you wish to submit in the MEMNAME field. In the case of a started task, fill in its name.

CTM721E INVALID TASK TYPE

Explanation: Invalid tasktype.

Valid values for the TASKTYPE parameter are:

JOB - batch job (default)
CYC - cyclic job
STC - started task (STC)
CST - cyclic STC
EMR - emergency job
ECJ - emergency cyclic job
EST - emergency STC
ECS - emergency cyclic STC
WRN - warning message

For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the TASKTYPE field.

CTM722E INVALID OPTION (USE "Y", "N" OR BLANK)

Explanation: An invalid option has been entered in the NCT2 field.

Valid options for running NCT2 (NOT CATALGD2) are:

Y (Yes) - Prevent errors by removing old data sets. This option is not valid for started tasks (STCs).
N (No) - Do not prevent errors.
Blank (Default) - Use the site-defined default, which is set during Control-M/Restart installation.

Corrective Action: Specify Y or N, or leave the field blank to use the site default.

CTM723E MAXWAIT SHOULD BE 00-98 OR 99

Explanation: An invalid value was entered for the MAXWAIT parameter.

The value of MAXWAIT should be from 00 through 98, meaning the number of extra days that the job can wait to be executed, or 99, meaning that the job remains in the Active Jobs file forever, even after executing).

Corrective Action: Correct the value in the MAXWAIT field.

CTM724E FIELD MUST BE BLANK OR NUMERIC WITH LEADING ZEROES

Explanation: The field contains data which are neither numeric characters nor blank. If numeric values are used, then no trailing (or preceding) blanks are allowed. The cursor points to the invalid field value.

Corrective Action: Correct field contents.

CTM725E INVALID FORMAT OF DAYS PARAMETER

Explanation: An invalid format was set for the DAYS parameter.

The DAYS parameter should contain 1 through 31, ALL, +1, +3, and so on. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct field contents.

CTM726E "ALL" PARAMETER MIXED WITH SPECIFIC - CORRECT

Explanation: The ALL parameter was specified together with specific days in the DAYS parameter or the WDAYS parameter. You cannot use specific WDAYS or DAYS together with the ALL option.

Corrective Action: Omit either the ALL option or the specific days options.

CTM727E INVALID FORMAT OF WDAYS PARAMETER

Explanation: Invalid format of WDAYS parameter. WDAYS parameter should contain 0 through 6, ALL, +1, and so on. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the WDAYS field.

CTM728E INVALID CONDITION DATE REFERENCE

Explanation: An invalid condition date reference has been specified. Date reference should be ODAT, PREV, ****, or mmdd (or ddmm, depending on the site standard). For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Correct the date reference.

CTM729E MISSING/INVALID CONTROL-TYPE. USE "E" - EXCLUSIVE OR "S" - SHARED

Explanation: A CONTROL resource was specified, but the CONTROL type is invalid or missing. The CONTROL type should be E (Exclusive) or S (Shared). For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Type E or S in the CONTROL type field.

CTM72AE DESCRIPTION LENGTH CAN'T EXCEED 4000 CHARACTERS

Explanation: The length of the description cannot exceed 4000 characters.

Corrective Action: Shorten the description.

CTM72BE INVALID OPTION (USE "Y", "N", "L", "F" OR BLANK)

Explanation: An invalid option has been entered in the NCT2 field.

Valid options for running NCT2 (NOT CATALGD2) are:

Y (Yes) - Prevent errors by removing old data sets. This option is not valid for started tasks (STCs).
N (No) - Do not prevent errors.
L (List) - List GDG data sets with the corresponding level from the original job in the SYSOUT file using CTR301I messages.
F (Flush) - Upon finding an error, prevent further processing.
Blank (Default) - Use the site-defined default, which is set during Control-M/Restart installation.

Corrective Action: The only value that is valid for a started task is N, or leave the field blank.

CTM72CE INTERVAL LIMIT IS EITHER 45 DAYS, 1080 HOURS, OR 64,800 MINUTES

Explanation: An interval specification exceeded one of the following:

64,800 minutes
1080 hours
45 days

For more information, see the INTERVAL parameter in the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the INTERVAL field.

CTM72DE VALID DISPLAY VALUES ARE 'M' MINUTES, 'H' HOURS, OR 'D' DAYS

Explanation: An interval type specification was invalid. The valid interval types are:

M - minutes
H - hours
D - days

For more information, see the INTERVAL parameter in the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the type.

CTM72EE VALID SYSTEM ID FORMATS ARE: XXXX OR /XXXX

Explanation: The length of the system ID value may be up to 4 characters. In a JES3 system this value may be preceded by a slash character, indicating NOT.

Corrective Action: Correct the value in the SYSID field according to the format indicated in the message.

CTM72FE DUPLICATE CONTROL RESOURCE NAMES ARE NOT ALLOWED

Explanation: Two CONTROL resources with the same name are not allowed.

Corrective Action: Remove one of the CONTROL resources.

CTM72GE 5 CHARACTER SYSID VALUE NOT ALLOWED IN COMPATIBILITY MODE

Explanation: Compatibility mode implies conformity to previous Control-M versions in which a maximum of 4 characters could be specified for the SYSID field.

Corrective Action: Specify a maximum of 4 characters in the SYSID field.

CTM730E QUANTITY MUST BE A FOUR DIGIT NUMBER

Explanation: Invalid quantity (for a quantitative resource). Quantity should be a non-zero, 4-digit number. For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Correct the quantity field.

CTM731E INVALID TIME

Explanation: Invalid time specified. The format of the TIME parameter should be hhmm. For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Correct the TIME field (FROM or UNTIL).

CTM732E MISSING/INVALID CONDITION OPTION. TRY "+" TO ADD OR "- " TO DELETE

Explanation: Invalid or missing condition option. The value of the condition option should be + for add, or - for delete. For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Specify + or - in the condition option field.

CTM733E INVALID SYSOUT OPTION

Explanation: An invalid sysout option was specified.

Valid SYSOUT option are:

Some SYSOUT options require additional sysdata.

For more details see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the SYSOUT field.

CTM734E MAXRERUN LIMIT IS 255

Explanation: More than 255 reruns were specified. The maximum number of times a cyclic job may be rerun or restarted is 255. For more information, see MAXRERUN in the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the MAXRERUN field.

CTM735E INVALID FINISH CODE

Explanation: An invalid job or step finish code was specified. For valid codes, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the finish code field.

CTM736E INVALID ACTION

Explanation: An invalid action was specified in a DO statement. For valid actions, see the job production parameters chapter in the Control-M for z/OS User Guide. This message can also be produced when specifying DO statements valid only if certain products are installed, for example, specifying DO IFRERUN when Control-M/Restart is not installed.

Corrective Action: Correct the DO action field.

CTM737E INVALID URGENCY. USE "R" - REGULAR, "U" - URGENT OR "V" - VERY URGENT

Explanation: An invalid value was specified for the SHOUT URGN (urgency) subparameter.

Valid values for SHOUT URGN are:

R - regular
U - urgent
V - very urgent.

For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Type R, U, or V in the SHOUT urgency field.

CTM738E INVALID "WHEN" ATTRIBUTE

Explanation: An invalid WHEN attribute was specified in a SHOUT statement.

For valid values, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the WHEN field.

CTM739E PLEASE FILL IN USER ID

Explanation: Missing user ID. The USER ID field is obligatory.

Corrective Action: Insert a user ID.

CTM73AE Finish code must be C`nnnn`/U`nnnn`, where `nnnn` is asterisk or 0000 to 4095

Explanation:Finish code was not correctly defined.

Corrective Action: Correct the finish code.

CTM73BE Finish code must be S`hhh`, where `hhh` are hex digits (0 to F) or asterisk

Explanation:Finish code was not correctly defined.

Corrective Action: Correct the finish code.

CTM73CE INVALID OPTION, SPECIFY "W" (WORD),"C" (CHAR) OR BLANK

Explanation:An invalid option was specified.

Corrective Action: Specify W for word, C for character, or leave blank.

CTM73DE INVALID VALUE. SPECIFY A NUMERIC VALUE (00-255)

Explanation:An invalid value was specified.

Corrective Action: Specify a numeric value in the range from 0 to 255.

CTM73FE INVALID VALUE. SPECIFY A NUMERIC VALUE (00-99999999)

Explanation:An invalid value was specified.

Corrective Action: Specify a numeric value in the range from 0 to 99999999.

CTM73GE INVALID VALUE. SPECIFY A BLANK OR NUMERIC VALUE (00-44)

Explanation:An invalid value was specified.

Corrective Action: Specify a blank or a numeric value in the range from 0 to 44.

CTM73HE PLEASE SPECIFY AN AUTO-EDIT VARIABLE NAME (%%VARNAME)

Explanation:An invalid AutoEdit name was specified.

Corrective Action: Specify a valid AutoEdit name beginning with the %% characters.

CTM73JE CAPTURED VARIABLE NAME LENGTH CANNOT EXCEED 18 CHARACTERS.

Explanation:The variable name that was specified is too long.

Corrective Action: Specify a variable name with not more than 18 characters.

CTM73KE POOL NAME LENGTH CANNOT EXCEED 20 CHARACTERS.

Explanation:The pool name that was specified is too long.

Corrective Action: Specify a pool name with not more than 20 characters.

CTM740E EXPECTED CONTINUATION NOT RECEIVED (AFTER ",")

Explanation: The DAYS or WDAYS parameter ended with a comma. Additional data is expected after comma.

Corrective Action: Correct the parameter.

CTM741E INVALID SHOUT DESTINATION CODE

Explanation: Invalid SHOUT destination code.

For valid destination codes, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the SHOUT destination field.

CTM742E CANNOT MIX DAYS OPTION WITH WDAYS OPTION

Explanation: Values were set for the DAYS parameter and the WDAYS parameter. The DAYS parameter conflicts with the WDAYS parameter.

Corrective Action: Delete either the value in the DAYS parameter or the value in the WDAYS parameter.

CTM743E DATES PARAMETER CONFLICTS WITH DAYS OR DCAL OPTION

Explanation: Both the DATES parameter and the DAYS, WDAYS or MONTHS parameters were specified.

The DATES parameter must appear alone.

Corrective Action: Erase any data in the DAYS, WDAYS and MONTHS parameters.

CTM744E CANNOT MIX DATES OPTION WITH CALENDAR OPTION

Explanation: The DATES parameter and the DCAL, WCAL or CONFCAL parameters were specified simultaneously.

The DATES parameter cannot be specified if the DCAL or WCAL or CONFCAL parameter is specified.

Corrective Action: Delete the value in the DATES field or in the DCAL, WCAL and CONFCAL fields.

CTM745E CANNOT MIX MINIMUM/PDS WITH OPTIONS DAYS, WDAYS, MONTH, DATES OR CALENDAR

Explanation: The MINIMUM or PDS parameter was specified simultaneously with the DAYS, WDAYS, MONTHS, DATES or CALENDAR parameters.

The MINIMUM and PDS parameters cannot be specified with date-related parameters.

Corrective Action: Specify either the MINIMUM and PDS parameters or one of the date-related parameters.

CTM746E MINIMUM AND PDS MUST BE FILLED IN TOGETHER

Explanation: A value was set for the MINIMUM parameter, but the PDS field is empty (or vice versa).

The MINIMUM and PDS parameters must be filled in together.

Corrective Action: Fill in both the MINIMUM and PDS fields.

CTM747E PLEASE FILL IN THE "IN" PREREQUISITE CONDITION NAME

Explanation: There is no IN prerequisite condition name.

The condition date reference was specified without a corresponding prerequisite condition name.

Corrective Action: Fill in the IN prerequisite condition name field.

CTM748E PLEASE FILL IN THE "CONTROL" RESOURCE NAME

Explanation: Missing control resource name. The control resource type was specified without a corresponding control resource name.

Corrective Action: Fill in the control resource name field.

CTM749E PLEASE FILL IN THE "QUANTITATIVE" RESOURCE NAME

Explanation: Missing quantitative resource name. The quantitative resource quantity was specified without a corresponding quantitative resource name.

Corrective Action: Fill in the quantitative resource name field.

CTM750E PLEASE FILL IN THE PREREQUISITE CONDITION NAME

Explanation: Missing prerequisite condition name in DO COND statement.

At least one condition is expected in DO COND statement.

Corrective Action: Fill in the prerequisite condition name.

CTM751E PLEASE FILL IN NEW CLASS (ONE LETTER)

Explanation: Missing new class on SYSOUT option C.

When you specify C (Change sysout class) as the SYSOUT option, a 1-letter new class parameter is needed.

Corrective Action: Fill in the new class (one letter).

CTM752E PLEASE FILL NEW DESTINATION (1-8 LETTERS)

Explanation: Missing new destination on SYSOUT option N. When SYSOUT option N is specified to change the sysout destination, a destination code is needed. Maximum length is 8 characters.

Corrective Action: Fill in the new destination (1-8 characters).

CTM753E PLEASE FILL IN FILE NAME

Explanation: Missing file name on SYSOUT option F. When SYSOUT option F is specified to copy the sysout to a file, a file name is needed. Maximum length is 44 letters.

Corrective Action: Fill in the file name.

CTM754E REDUNDANT TEXT IN SYSOUT DATA FIELD

Explanation: The sysout data field contains data which is not relevant to the sysout option specified.

Corrective Action: Erase the redundant text.

CTM755E USE OF PREV/NEXT DATE REFERENCE CONFLICT PDS/MINIMUM OPTIONS

Explanation: A PREV (or NEXT) date reference has been specified for a job scheduled by the PDS parameter. There is no next date or previous date when the job is scheduled according to the status of the library.

Corrective Action: Use another valid date reference.

CTM756E ONLY CODE OPTION "-" ALLOWED FOR DATE REFERENCE $$$$/****

Explanation: Code option + specified for a generic date reference. It is impossible to ADD a prerequisite condition on all possible dates of the year.

Corrective Action: Either enter "-" in the code option or use a different date reference.

CTM757E RERUN OPTION CONFLICTS WITH CYCLIC TASK TYPE

Explanation: The RERUN option has been specified for a CYCLIC task type. You cannot use the RERUN option for a CYCLIC task type.

Corrective Action: Omit the RERUN option.

CTM758E PLEASE FILL IN STEP NAME BEFORE THE FINISHING CODE

Explanation: A job or step finishing code appears without a step name. A step name is obligatory in an ON STEP CODES statement. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Fill in the step name or erase the finishing code.

CTM759E MAXIMUM 245 FINISHING CODES FOR ONE STEP

Explanation: Too many finishing codes for one step. The maximum number of finishing codes for one step is 245.

Corrective Action: If you want to use more finishing codes, you can open a new ON STEP statement.

CTM760E AT LEAST ONE FINISHING CODE IS EXPECTED AFTER PREVIOUS STEP NAME

Explanation: A step name is not followed by at least one finishing code. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Specify a finishing code.

CTM761E PLEASE FILL IN THE PREVIOUS STEP/CC LINE

Explanation: A DO statement is filled in, but the previous STEP/CC line is empty. The ON STEP CODES line is obligatory in CODES statement.

Corrective Action: Fill in the previous ON STEP CODES line or erase the DO statement.

CTM762E REDUNDANT TEXT IN SHOUT PARAMETER

Explanation: The SHOUT WHEN statement contains data which is not relevant to the shout option specified.

Corrective Action: Erase the redundant text.

CTM763E PLEASE FILL IN PREREQUISITE NAME FOR SHOUT OPTION "COND"

Explanation: A prerequisite name for a SHOUT option is missing. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Fill in a prerequisite name.

CTM764E INVALID SHOUT REFERENCE. USE "- " OR BLANK

Explanation: A SHOUT reference is invalid.

Valid SHOUT references are:

" " (Blank) - for checking the existence of a condition
" - " - for checking the absence of a condition.

Corrective Action: Type " - " in the SHOUT reference field, or leave the field blank.

CTM765E PLEASE FILL IN THE SHOUT LINE BEFORE THIS MESSAGE LINE

Explanation: A message is filled in, but the SHOUT line that precedes it is empty.

Corrective Action: Fill in the SHOUT WHEN field. If necessary, fill in the TO destination field also.

CTM766E PLEASE FILL IN THE MESSAGE

Explanation: There is no message in the SHOUT statement.

Corrective Action: Fill in the message.

CTM767E CONFLICT BETWEEN "OK", "NOTOK" AND "RERUN" FOR THE SAME STEP

Explanation: There is a conflict of actions for the same ON STEP statement. A job cannot at the same time be OK and NOTOK, or OK and RERUN.

Corrective Action: Select one of the options: OK, NOTOK and RERUN, and omit the rest.

CTM768I TOP OF JOBS LIST

Explanation: This information message indicates that the current job is the first job in the jobs list. The message may appear after entering the command PREVJOB in the Job Zoom screen.

Corrective Action: No action is required.

CTM769I BOTTOM OF JOBS LIST

Explanation: This information message indicates that the current job is the last job in the jobs list. The message may appear after entering the command NEXTJOB in the Job Zoom screen.

Corrective Action: No action is required.

CTM76BE INVALID VARIABLE NAME, USE '%%VARNAME' OR '%%\VARNAME'

Explanation: You specified an invalid variable name in the ON VAR statement. The variable name must begin with %% for a local variable, or with %%\ for a global variable.

Corrective Action: Correct the variable name and try again.

CTM76CE INVALID OPERATOR CODE

Explanation: You specified an invalid operator code in the ON VAR statement.

The following operators are valid for an integer:

EQ - Equal to (=)
NE - Not equal to (!=)
GT - Greater than (>)
GE - Greater than or equal (>=)
LT - Less than (<)
LE - Less than or equal (<=)
IR - In range (a<=x<=b)
NR – Not in range (x<a or x>b)

The following operators are valid for a string:

LK - Like
NL - Not like
IX - Is exactly
NX - Is not exactly
SW - Starts with
EW - Ends with
CO - Contains
NC - Does not contain
MP - Is empty
NP - Is not empty

Corrective Action: Correct the operator code and try again.

CTM76DE WHEN UFLOW IS 'Y' THE JOB NAME MUST BE EMPTY

Explanation: The UFLOW option is performed for all jobs in a forced table. It is relevant only when the JOB name is empty.

Corrective Action: If you are forcing a single job, leave the UFLOW field empty or enter a value of 'N'. On the other hand, if you want to force a unique job flow for all jobs in a table, ensure that the JOB field is empty.

CTM76EE INVALID VALUE, THE VALUE MUST BE AN INTEGER UP TO 10 DIGITS

Explanation: This message indicates that you specified an invalid variable value in the ON VAR statement. For an integer operator, the VAL, MIN, and MAX fields must contain an integer value up to 10 digits.

You can include a plus (+) or minus (-) sign as the first character of the numeric string, and this character is not counted as one of the 10 digits of the number.

When one of these fields contains the ‘%%’ characters, no verification is performed for the on-screen fields, and the value is validated only at the execution stage of the job or table.

The following strings are examples of valid values: +1234567890, -1234567890, 1234567890, %%VALUE1

Corrective Action: Correct the variable value and try again.

CTM770E PLEASE FILL IN LIBRARY NAME

Explanation: In Control-M, this message indicates that the library name is missing. LIBRARY name is obligatory.

Corrective Action: Fill in a LIBRARY name. For started tasks type the computer ID and started task parameters.

CTM770I INVALID TRACE LEVEL WAS SPECIFIED: `xxxxxxxxxxxxxxxx`

Explanation: This information message is issued when TRACE is turned on for the IOA online monitor and the trace level is invalid.

When the F IOA-monName, TRACE is set to nnn, the command ON or OFF is used to turn TRACE ON or OFF, and the TRACE level is invalid, this message is issued. The TRACE level may be set to any value from 1 through 256.

The system ignores the command and continues processing.

Corrective Action: Reset the TRACE level to a valid value and try again.

CTM771E PROC STEP MUST BE PRECEDED BY PGM STEP

Explanation: A PROCST (procstep) name has been filled in, but the PGMST field is empty. A PGMST name is obligatory when using PROCST.

Corrective Action: If you really want to reference all the steps in the procedure designated in the PROCST field, insert ANYSTEP in the PGMST field.

CTM771I FORMATTING OF CONTROL-D COMMUNICATION FILE STARTED

Explanation: This information message indicates that the Control-D Communication file is currently being formatted.

Corrective Action: No action is required.

CTM772E OK, NOTOK AND EXERR CANNOT BE SPECIFIED FOR A SPECIFIC STEP NAME

Explanation: OK, NOTOK, or EXERR events have been specified in the same ON STEP statement.

Corrective Action: To specify any event (in any case), use the event *****.

CTM772I FORMATTING OF CONTROL-D COMMUNICATION FILE ENDED

Explanation: This information message indicates that the formatting of Control-D Communication file by the CTDFRCOM utility has ended.

Corrective Action: No action is required.

CTM773E REQUIRED CALENDAR DEFINITION IS MISSING

Explanation: The option used in the DAYS or WDAYS parameter requires a name of a calendar to work with.

Corrective Action: Either correct the DAYS or WDAYS definition, or enter a calendar name.

CTM773S FORMATTING OF CONTROL-D COMMUNICATION FILE - WRITE I/O ERROR

Explanation: An I/O error occurred during formatting of the Control-D Communication file. This may occur when there is incompatibility between the definition of the Communication file in the Installation Parameters (COMSIZE in CTDPARM) and the JCL SPACE or DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters.

CTM774E PERIOD IDENTIFIER SPECIFIED IS INVALID

Explanation: The period identifier specified in a DnPi date selection is invalid. It must be A-Z, 0-9, or * (except Y and N).

Corrective Action: Specify a valid period identifier.

CTM774S CONTROL-D COMMUNICATION FILE WAS NOT BUILT

Explanation: The CTDFRCOM utility failed.

Corrective Action: Look for previous error messages that describe the type of error.

CTM775I `monName` - `validModifyParm`

Explanation: This information message follows the CTM649E message, which is issued when a MODIFY command parameter is invalid.

Corrective Action: No action is required.

CTM776I `monName` - SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message indicates that the specified Online monitor is shutting down because of an operator’s request.

Corrective Action: No action is required.

CTM777E "FROM" FIELD SHOULD BE BLANK

Explanation: A value was specified in the FROM field, but the field should be blank. The FROM field indicates how the next run time of the job should be calculated. A value should only be specified in one of the following circumstances:

The TASKTYPE value is CYC, indicates a cyclic job (valid values are CYC, CST, ECJ, or ECS)
The MAXRERUN field contains a value

Neither of these criteria applies to this job. Therefore, no value should be specified.

Corrective Action: Delete the value in the FROM field.

CTM777I `monName` - ONLINE MONITOR INITIALIZATION STARTED

Explanation: This information message indicates that the specified Online monitor was started and is currently building the required internal environment.

Corrective Action: No action is required.

CTM778E VALID VALUES ARE 'TRGT', 'STRT', OR 'END'

Explanation: Either an incorrect value or no value was specified in the FROM field. This message displays available valid values, one of which should be specified.

The FROM field indicates how the next run time of the job should be calculated. A valid value must be specified when TASKTYPE is set to CYC, indicating a cyclic job, or if the MAXRERUN field contains a value. This job satisfies one of those criteria.

Valid values are:

STRT - The interval between runs from the start of execution of a job.
END - The interval between runs from the end of the job run.
TRGT - The interval between runs from the start of the previous interval.

Corrective Action: Specify one of the above values for the job.

CTM778I `monName` - ONLINE MONITOR INITIALIZATION COMPLETED

Explanation: The monName Online monitor is ready to serve the user’s sign-on request.

Corrective Action: No action is required.

CTM779E `monName` - ONLINE MONITOR INITIALIZATION FAILED RC `rc` IN STEP `step#`

Explanation: The specified Online monitor initialization has encountered an internal error.

The following step and return codes can appear in the message:

Step Code	Return Code	Explanation
0001		Subsystem initialization error.
	04	IOA component already active.
	08	Subsystem name not supplied.
	12	Subsystem executor not found.
	16	Insufficient storage.
	20	Subsystem already active for a different IOA release.
	24	IOAOMON already active for a different IOA release.
	28	Invalid parameters passed to the initialization routine.
	32	Internal error.
0002		ECBLIST could not be obtained in CSA/ECSA
0003		Cross-memory environment establishment error AXSET).
0004		Cross-memory environment establishment error (LXRES).
0005		(ETCRE).
0006		(ETCON).
0007		IOAOMON could not be made non-swappable.
0009
	08	IOAOMON own ASCB not found.

The specified online monitor will shut down.

Corrective Action: Act according to the step number and return code as follows:

Step Code	Return Code	Action
0001
	08	Verify that the subsystem name is defined.
	12	Verify that the subsystem name is defined.
	16	Try again.
	20	Verify that the subsystem is used solely by the current IOA version of IOAOMON.
	24	Verify that the subsystem is used solely by the current IOA version of IOAOMON.
	28	Forward problem to IOA representative.
	32	Forward problem to IOA representative.
Step 0002		Try again.
From 0003 through 0009		Forward problem to your INCONTROL representative.

CTM77AI USER `userId` WAS CANCELED DUE TO TIMEOUT

Explanation: This information message indicates that the communication session with the specified user was terminated because no data was transmitted during a period of time which exceeded the timeout interval.

This message is generated by the CTMXSND program, which communicates with the OMON cross-memory monitor.

Corrective Action: No action is required.

CTM77BE VALID VALUES ARE 'S' 'R' 'N' OR 'A'

Explanation: An invalid value was specified in the DYNAMIC INSERT JOB INTO GROUP field of the Confirmation Window for a FORCE/ORDER option in a Job List Screen.

Valid value for this field are:

S - This opens a panel with a list of all group entities, and allows the user to select the group entity to force the job into the Active Job File. The Order ID of each group is displayed.
R - Add the job to the group entity (in the Active Job File) that was most recently ordered.
N - Force a job belonging to a group entity, and the group entity itself, to the Active Jobs File.
A - Default value. Force a job or a group entity to the Active Jobs File.

Corrective Action: Specify a valid value.

CTM77DE VALUE 'N' NOT ALLOWED FOR REGULAR JOB

Explanation: The value specified in the DYNAMIC INSERT JOB INTO GROUP field of the Confirmation window for the FORCE/ORDER option for a regular job definition is invalid.

Corrective Action: Specify one of the following values:

S - Selects the group entity to force the job into the Active Jobs file.
R - Adds the job to the group entity that was most recently ordered.
A - Forces the job into the Active Jobs file.

CTM77FE VALID VALUES ARE 'STRT' AND 'END'

Explanation: For CYCLIC type 'V' (Varying intervals), the FROM value must be either STRT or END.

Corrective Action: Correct the field contents.

CTM780I `monName` - NO USER IS SIGNED ON TO THIS ONLINE MONITOR

Explanation: This information message is displayed when the operator inquires about active users in the specified Online monitor, but there are none.

Corrective Action: No action is required.

CTM781E `monName` - INSUFFICIENT STORAGE FOR USER `usr`. SIGN ON FAILED

Explanation: There is insufficient virtual storage in the Online monitor address space.

The user sign-on request is terminated.

Corrective Action: Do the following:

Increase the REGION size of the Online monitor.
If the problem persists, reduce the number of users allowed to sign on to the Online monitor by lowering the value of the MAXSESS parameter of the specific monitor in IOAXPRM. For more details, see the description of installing the IOA Online monitor in the INCONTROL for z/OS Installation Guide.

CTM782E `monName` - INSUFFICIENT STORAGE FOR INITIALIZATION

Explanation:Highlighted, unrollable message.

There is insufficient memory for the online monitor.

The monName online monitor will shut down.

Corrective Action: No action is required.

CTM783W `monName` - CONTROLM YES PARAMETER WILL BE IGNORED

Explanation: There is a contradiction between the CONTROLM parameter in Control-D Installation Parameters (CTDPARM) and the parameters file (member) allocated by the DAXMMIN DD statement.

The CONTROLM YES parameter is ignored.

Corrective Action: Correct the parameters file allocated to the DAXMMIN DD statement and correct CTDPARM.

CTM784E `monName` - AN ONLINE MONITOR WITH THE SAME STC NAME IS ALREADY ACTIVE

Explanation: The operator entered a START command in order to activate a monitor.

Control-D and Control-M online monitors may work simultaneously provided that each monitor uses a unique name.

The newly started online monitor terminates.

Corrective Action: If an additional online monitor is needed, define another JCL procedure with a different name to support it.

CTM785I EXISTING USERS (IF ANY) ARE NOT USING A TREE

Explanation: A DISPLAY TREES inquiry has been made, but no users are using a Control-D Recipient Tree.

Corrective Action: No action is required.

CTM786I `monName` - NEW TREE LOADED. NEW USERS WILL BE SIGNED ON TO THE NEW TREE

Explanation: This information message indicates that the operator has modified the Online monitor with the LOADTREE command.

A new tree was loaded from the data set (member) allocated to the DATREE DD statement. The new tree will be in effect for all users who sign on from this point in time.

Corrective Action: No action is required.

CTM787W `monName` - MAXIMUM NUMBER OF TREES LOADED. A TREE MUST BE FREED IN ORDER TO LOAD A NEW ONE

Explanation: The operator entered a LOADTREE command but there are already five trees in storage. Only five tree copies can be loaded.

Corrective Action: Wait and retry. A tree is freed when the last user session working with that tree leaves the user screen, or is cancelled.

CTM788I `monName` - THE FOLLOWING USERS ARE SIGNED ON TO TREE NUMBER num

Explanation: This information message is the result of a DISPLAY TREES inquiry to one of the online monitors. It acts as a header for the CTM789I message. The message is displayed for each Recipient Tree that is loaded in the online monitor.

Corrective Action: No action is required.

CTM789I `monName` - `userId1 userId2` ...

Explanation: This information message displays the result of a DISPLAY TREES inquiry to one of the online monitors. It is displayed for each group of six users.

The variables in this message are:

monName - the name of the online monitor started task
userId - the user ID of the person that is using the Recipient Tree

Corrective Action: No action is required.

CTM78AE `ioaomon stc name` INITIALIZATION OF THE LIBRARY `ddName` FAILED

Explanation: The IOA online monitor could not process the library referenced by the ddName DD statement. The error occurred when the IOA online monitor address space attempted to initialize processing for the library or a member within the library.

The IOA online monitor terminates with a return code of 8.

Corrective Action: Check for the presence of the ddName DD statement, the library referenced by it, and the member name in the ALC allocation member and in the JCL for the monitor. Add the missing entry or correct the entry in error. Restart the IOA online monitor.

CTM78BE `ioaomon stc name` MEMBER PRMXMM WITH COMMON COMMANDS AND PFKEYS IS NOT FOUND

Explanation: The IOA online monitor did not find the PRMXMM member in the IOA PARMCMD library. The library referenced by the DACMDCU DD statement under the IOA online monitor does not contain the PRMXMM member, which internally defines common COMMANDS and PFKEYS.

The IOA online monitor terminates with a return code of 8.

Corrective Action: Ensure that the DACMDCU DD statement correctly refers to the IOA PARMCMD library. Ensure that the PRMXMM member exists in the library. If the problem persists, contact BMC Customer Support.

CTM78CI `ioaomon stc name` MEMBER `memName` WITH COMMANDS OR PFKEYS IS NOT FOUND

Explanation: The IOA online monitor did not find the COMMAND or PFKEYS member in the IOA PARMCMD library. The libraries referenced by the DACMDCU and DAPFCMD DD statements under the IOA online monitor do not contain the COMMAND member or the PFKEYS associated with the currently displayed screen.

The IOA online monitor continues execution. Problems may occur when attempting to execute commands entered on the user’s screen.

Corrective Action: Do the following:

Ensure that the DACMDCU and DAPFCMD DD statements correctly refer to the IOA PARMCMD library.
Ensure that all necessary COMMAND and PFKEYS members exist in the library.
If the problem persists, contact BMC Customer Support.

CTM78DE `jobName` JOBNAME NOT DEFINED IN IOAXPRM

Explanation: When starting up, the jobName IOA Online monitor was not found in IOAXPRM (either explicitly, or by mask).

The IOA Online monitor terminates.

Corrective Action: Use a valid job name, or make the necessary changes to IOAXPRM, and restart the monitor.

CTM78EE `jobName` WRONG LEVEL OF IOAXPRM

Explanation: The eye-catcher of the IOAXPRM member was not found in storage.

The probable cause is that the eye-catcher was overwritten by another module.

The startup of the IOA monitor stops.

Corrective Action: Contact your INCONTROL administrator. If no solution can be found for the problem, contact BMC Customer Support.

CTM790E SECURITY VIOLATION `details`

Explanation: where details is PASSWORD IS NOT AUTHORIZED or PASSWORD HAS EXPIRED.

An invalid or expired password has been specified in the IOA Online Entry Panel.

The logon request is denied.

Corrective Action: If details is PASSWORD IS NOT AUTHORIZED, reenter your password (three attempts to enter the correct password are allowed). If details is PASSWORD HAS EXPIRED, renew your password and try again.

CTM791S USER IS NOT AUTHORIZED TO ENTER IOA ENVIRONMENT

Explanation: The IOAX006 or IOAX009 IOA user exit indicated that the user cannot use the IOA Online facility.

The IOA Online facility terminates.

Corrective Action: No action is required.

CTM792E PLEASE FILL IN THE USER ID AND PASSWORD AND PRESS ENTER

Explanation: Either the USER ID or PASSWORD field in the IOA Online Entry Panel is empty.

Corrective Action: Fill in the missing information, either USER ID field or PASSWORD field.

CTM793I `monName` - ONLINE MONITOR SHUTTING DOWN

Explanation:Highlighted, unrollable message.

The monName Online monitor is shutting down.

Corrective Action: No action is required.

CTM794I `monName` - USER `usr` NOT FOUND

Explanation: A DISPLAY USER= usr inquiry was entered with a user name (usr) which is not active in the specified Online monitor.

Corrective Action: No action is required.

CTM795I `monName` - USER `usr` CANCELLED

Explanation: The usr Online user was cancelled upon operator’s request. The usr user session will be terminated.

Corrective Action: No action is required.

CTM796E INVALID "ON STEP CODES" ARGUMENTS FOR A "DUMMY" JOB

Explanation: Arguments are specified in the ON PGMST statement of a DUMMY job. The ON PGMST, PROCST and CODES fields in the ON PGMST statement must be blank for a DUMMY job. Since DUMMY jobs are not actually submitted, you cannot check how they finished. They always finish OK.

Corrective Action: Clear the ON PGMST, PROCST and CODES fields for this DUMMY job.

CTM797E ONLY ONE IF RERUN STATEMENT IN EACH "ON PGMSTEP"

Explanation: A second DO IF RERUN action was entered for the same ON PGMSTEP. Only one DO IF RERUN action is allowed per ON PGMSTEP.

Corrective Action: Use the existing DO IFRERUN for defining the requested restart processing for this ON PGMSTEP.

CTM798E "IFRERUN" CANNOT BE USED WITH "RERUNMEM"

Explanation: A DO IFRERUN action was entered for a task that has a recovery member defined in the RERUNMEM field. RERUNMEM and DO IFRERUN are mutually exclusive. Restart is only allowed for the same member.

Corrective Action: Decide whether RERUNMEM or restart processing is needed and define the job accordingly.

CTM799E {IF RERUN | CTBSTEP | OVERLIB} IS NOT SUPPORTED FOR A STARTED TASK

Explanation: The user has typed a DO IF RERUN, DO IF OVERLIB, or DO IF CTBSTEP action for a started task (STC) task type. STC and DO IF RERUN, DO IF OVERLIB, DO IF CTBSTEP are mutually exclusive.

Corrective Action: Decide whether STC type or restart processing is needed and define the task accordingly.

CTM79AE "STOPCYCL" OPTION IS VALID FOR CYCLIC TASK TYPE ONLY

Explanation: A DO STOPCYCL post-processing parameter was specified in the job scheduling definition for non-cyclic job or task. DO STOPCYCL can only be specified for cyclic jobs or cyclic started tasks.

Corrective Action: Delete the DO STOPCYCL parameter.

CTM7A0I `monName` - VTAM MONITOR INITIALIZATION STARTED

Explanation: This information message indicates that the monName VTAM monitor started, and is currently building the required internal and external environments. This is a normal start message for the VTAM monitor initialization process.

Corrective Action: No action is required.

CTM7A1I `monName` - VTAM MONITOR INITIALIZATION COMPLETED

Explanation: This information message indicates that the monName VTAM monitor is ready to serve the user’s sign-on requests.

Corrective Action: No action is required.

CTM7A2E `monName` - VTAM MONITOR INITIALIZATION FAILED IN STEP `stepName`

Explanation: The monName VTAM monitor initialization has encountered an internal error.

The monName VTAM shuts down.

Corrective Action: Check the contents of the IOA Log and the system log for prior messages to determine the reason for the failure. If you cannot determine the reason, and the problem recurs whenever you start the VTAM monitor, contact BMC Customer Support.

CTM7A3S `monName` - VTAM MONITOR ENDED WITH ERROR

Explanation: A severe error has occurred. The monName IOA VTAM monitor is shutting down. Detailed information on this error is available in the messages which were previously displayed on the operator console.

The monName IOA VTAM monitor shuts down.

Corrective Action: Check the system log for additional messages.

CTM7A4I `monName` - VTAM MONITOR SHUTTING DOWN

Explanation: This information message is displayed when the monName VTAM monitor is shutting down.

Corrective Action: No action is required.

CTM7A5E `monName` - VTAM ACB FOR APPLID `applId` IS NOT DEFINED TO VTAM OR IT IS NOT CURRENTLY ACTIVE

Explanation: The monName VTAM monitor is unable to open the ACB for the specified application ID, such as, CTMS. The VTAM monitor opens the ACB as part of its initialization. This action is required before a LOGON can be issued. Possible causes are:

VTAM is down.
The VTAM application ID is inactive.
The application is not defined to VTAM.

The monName VTAM monitor shuts down.

Corrective Action: Check that the application ID is defined, and that it is active. The command VARY NET,ACT,ID= applId activates the application. Start the VTAM monitor again.

CTM7A6E `monName` - VTAM MONITOR CANNOT OPEN THE VTAM ACB. CHECK THE VTAM APPLICATION DEFINITION

Explanation: The monName VTAM monitor is unable to open the VTAM ACB. The VTAM monitor opens the ACB as part of its initialization. This action is required before a LOGON can be issued. Generally, this message is issued when the cause of the error is not one described in CTM7A5E. Possible causes are:

VTAM is down.
The VTAM application ID is inactive.
The application is not defined to VTAM.

Generally, this message is issued when the cause of the error is not one described in CTM7A5E.

The monName VTAM monitor shuts down.

Corrective Action: Check the application definition in VTAM. The command D NET,ID= applId displays the status of the application.

CTM7A7E `monName` - VTAM MONITOR CANNOT ISSUE THE SETLOGON COMMAND

Explanation: The monName VTAM monitor is unable to start the logon process. The VTAM monitor cannot accept any logon until the SETLOGON operation completes successfully. Possible causes are

A temporary shortage of storage exists for VTAM.
Some other VTAM problem has occurred.
A problem exists in the application definition.

The VTAM monitor monName shuts down.

Corrective Action: Check the application definition in VTAM. The command D NET,ID= applId displays the status of the application.

CTM7A8I `monName` - VTAM MONITOR SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message indicates that the monName VTAM monitor is shutting down based on an operator’s request.

Corrective Action: No action is required.

CTM7A9E `monName` - VTAM MONITOR UNABLE TO CLOSE ACB

Explanation: The monName VTAM monitor is unable to close the VTAM ACB. During shutdown processing, the VTAM monitor closes the ACB to ensure successful future initialization.

The monName VTAM monitor shuts down.

Corrective Action: Refer to prior messages in the system log to determine cause of the VTAM monitor shutdown.

CTM7AAE `monName` - INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

Explanation: An invalid parameter was passed to the monName IOA VTAM monitor by an operator modify command (F). A list of valid modify parameters appear on the operator console following this message. This is a header message for message CTM7ABI.

The modify command is rejected.

Corrective Action: Enter a correct modify parameter.

CTM7ABI `monName` - `validModifyParm(s)`

Explanation: This message is issued when an invalid modify parameter has been entered. The header for this message is message CTM7AAE.

Corrective Action: No action is required.

CTM7ACI `monName` ACCEPTING LOGONS TO `access_ctrl_blk`

Explanation: This information message indicates that the monName IOA VTAM monitor started successfully and is accepting logons to the access_ctrl_blk access control block.

Corrective Action: No action is required.

CTM7AEI `monName` - NO USER IS SIGNED ON TO THIS VTAM MONITOR

Explanation: This information message is issued if the operator inquires about active users in the monName VTAM, but there are none.

Corrective Action: No action is required.

CTM7AFI `monName` SETLOGON GNAMEADD FAILED FOR `gname` RTNCD=`rtcnd`,FDB2=`fdb2`

Explanation: The VTAM generic resource name was not added at logon.

The variables in this message are

monName - the identity of the VTAM monitor
gname - generic resource name
rtcnd - VTAM return code
fdb2 - VTAM FDB2

The monName IOA VTAM monitor ignores the failure and proceeds.

Corrective Action: Check the VTAM return code and FDB2 in the IBM manuals and correct the problem.

CTM7B0I `monName` - TERMINAL TRANSID

Explanation: This information message is issued as the result of an operator DISPLAY command to the monName VTAM monitor. This is a header for message CTM7B1I.

Corrective Action: No action is required.

CTM7B1I `monName` - `terminal transid`

Explanation: This information message is the result of an operator DISPLAY command to the monName VTAM monitor. It is displayed for each active user.

The variables in this message are

monName - the identity of the VTAM monitor
terminal - the identity of the VTAM terminal
transid - the identity of the current transaction supplied as the DATA parameter of the LOGON command.

Corrective Action: No action is required.

CTM7B2E `monName` - VTAM MONITOR SHUT DOWN UPON VTAM FAILURE OR VTAM OPERATOR COMMAND

Explanation: The monName VTAM monitor is shutting down due to VTAM failure or upon operator request. When VTAM fails, or an operator closes the application, such as, by using an INACT command, the VTAM monitor shuts down.

The monName VTAM shuts down.

Corrective Action: Refer to prior messages in the system log to determine the cause of the VTAM monitor shutdown.

CTM7B3W `stc` - VTAM MONITOR, WAITING FOR VTAM STARTUP TO COMPLETE

Explanation:Highlighted, unrollable message.

The VTAM monitor (IOAVMON) cannot be initialized because VTAM is not active. This message is displayed on the console if the VTAM monitor (IOAVMON) is started before VTAM is active, usually at IPL time. When VTAM becomes available, the VTAM monitor will start its initialization process and this message will be deleted.

Wait for VTAM startup to be completed.

Corrective Action: No action is required.

CTM7B5I `oper` FROM TERMINAL `terminal` FAILED, WAITING TIME IS OVER

Explanation: This information message is issued if there is a delay of 30 seconds or more in either the IOAVMON logon or the IOAVMON logoff process. The process terminates.

The variables in this message are:

oper--the identity of the IOAVMON logon or the IOAVMON logoff process
terminal--the identity of the VTAM terminal

Corrective Action: If the delay occurs in the IOAVMON logon process, determine the reason for the delay and then try to logon again.

Messages CTM800 through CTM8xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM800E COMMAND NOT FOUND

Explanation: Invalid TSO command supplied.

Corrective Action: Correct the command and re-enter.

CTM801S PROGRAM `pgm` ABEND CODE `abCode`

Explanation: The pgm TSO program, which has been activated by the IOA Online interface, abended with the abend code abCode.

Corrective Action: You can continue working on any of the IOA screens.

CTM802S BLDL/LOAD FAILED FOR CTMTCON - "CT`x` TTRA" FACILITY NOT AVAILABLE

Explanation: BLDL/LOAD for the CTMTCON module failed (the DATRA DD statement). The DATRA DD statement should describe the IOA MINILOAD library which is used by the IOA screen transfer facility.

Corrective Action: Press Enter to enter the TSO command. To return to other IOA screens, exit the TSO command or application. Trying to use the TSO CTMTTRA or CTDTTRA command causes an error.

Correct the CLIST used to enter the IOA online interface so that you will not have to enter or exit TSO applications, such as ISPF, in an inconvenient way.

CTM803S PROGRAM `pgm` ACTIVE, CANNOT EXIT

Explanation: You entered an X command in one of the IOA screens, but the TSO program is still active. IOA expects you to exit the TSO application in an orderly manner.

Corrective Action: Press Enter to enter the TSO application. Exit from the TSO application. You will exit the IOA online interface. You cannot return to one of the IOA screens after you have entered the X command.

CTM804S OPEN FAILED FOR DDNAME "DATRA"- "CTxTTRA" FACILITY NOT AVAILABLE

Explanation: Opening of IOA MINILOAD file failed (the DATRA DD statement) during activation of a TSO application.

Activation of the IOA Online Transfer Facility requires loading of a special module from the IOA MINILOAD library. When this module is not loaded, the transfer facility does not function, but the TSO command is executed normally.

Possible causes are:

The DATRA DD statement is missing.
There is insufficient memory.

Corrective Action: Press Enter and you will enter the TSO command. To return to other IOA screens, exit the TSO command or application. Trying to use the CTMTTRA or CTDTTRA TSO command causes an error.

Correct the CLIST used to enter the IOA online interface so that you will not have to enter or exit TSO applications, such as ISPF, in an inconvenient way.

CTM805I CLISTS NOT SUPPORTED YET

Explanation: This information message states that CLISTs are not yet supported by Control-M or Control-D.

Corrective Action: Perform the CLIST under ISPF.

CTM806E MISSING OR INVALID TRANSFER PARAMETER

Explanation: A missing or invalid transfer parameter was supplied to the CTMTTRA or CTDTTRA TSO command. The transfer parameter should be one of the IOA screens or X. It must be specified in the command line of the TSO application (for example, ISPF).

Transfer is not performed.

Corrective Action: Press Enter to return to the TSO command, and enter a correct parameter.

CTM807E MAXIMUM TSO LEVELS EXCEEDED. CANNOT OPEN "CT`x`TTRA" ENVIRONMENT

Explanation: More than four levels of IOA Online interface have been opened, one under the other. Only four TSO levels are allowed for the transfer facility.

You can open more than four TSO levels, but the system will not allow a transfer between them.

Corrective Action: Either use the END command to exit at least one TSO level, or do not transfer between TSO levels.

CTM808E MEMBER $$ID IS IN USE BY ANOTHER USER (RC=`rc`)

Explanation: The $$ID member in the JCL library that was specified in the //*CONTROLM statements is being held by you or another user. This member is being held for editing. It must be released if the job is to be ordered.

The job is not ordered.

Corrective Action: Try to resubmit the job. If it fails again, find out who is holding the member, and have the member released.

CTM809E DYNAMIC ALLOCATION OF DDNAME "DAINTRDR" FAILED, RC=`rc,errCode`

Explanation: Dynamic allocation of internal reader (INTRDR) by the Control-M Quick Submit command failed. This message appears while trying to submit a job under ISPF by the Control-M Quick Submit command.

The variables in this message are:

rc - the return code of the failed allocation
errCode - the error code and information code that were returned from that SVC

The job is not submitted.

Corrective Action: Refer to IBM documentation on dynamic allocation. Compare with the data in the message and correct accordingly.

CTM810E SUBMIT FAILED - OPEN OF DDNAME "DAINTRDR" FAILED

Explanation: Open of the DAINTRDR dynamically allocated DD statement failed (Control-M Quick Submit command).

The job is not submitted.

Corrective Action: Look for additional information that will clarify the reason for the problem, for example, the console log, TSO sysout, and the like.

CTM811E INTERNAL ERROR IN CTMQSB - NOTIFY THE IOA ADMINISTRATOR `error_code,rc`

Explanation: An internal error occurred in either the Quick Submit program (CTMQSB) or a user program that calls the CTMAJO Control-M routine.

The job is not ordered.

Corrective Action: If error_code,rc is SELECTAB, xx the CTMAJO routine returned an unknown return code (xx) to the calling program.

If this error was encountered during an ISPF submit command, call the INCONTROL administrator.
If it occurred in a user program, correct it to support all the possible return codes that the CTMAJO routine can return.
Otherwise, call your INCONTROL administrator.

CTM812E MISSING/INVALID INFORMATION IN "//*CONTROLM" CARDS (RC=`rc`)

Explanation: The //*CONTROLM statement or statements in the job contain invalid or insufficient information for performing the job-order (Control-M Quick Submit Command).

Return codes values:

Return Code	Explanation
04	Only one type of Control-M statement has been found; there should be two: TABLE and JCL.
08	Invalid keyword as the first parameter in a //*CONTROLM statement.
12	Missing tables scheduling library parameter.
16	Missing table name parameter.
20	Missing JCL library parameter.

The job is not ordered.

Corrective Action: Correct the error and submit again.

CTM813E UNABLE TO READ TABLE `tableName` (RC=`rc`)

Explanation: The Control-M Quick Submit command failed to locate the table member specified in the //*CONTROLM TABLE statement.

Valid values for rc are:

Return Code	Explanation
8	There is insufficient memory.
12	The `tableName` table member was not found in the specified scheduling library.
36	The library specified was not found.

The job is not ordered.

Corrective Action: Correct the error and submit the job again.

CTM814E UNABLE TO READ THE $$ID MEMBER. (RC=`rc`)

Explanation: Open or read of the $$ID member in the JCL library failed. (Control-M Quick Submit command).

Possible return code values, and their explanations, are:

12 - The $$ID member is not in the library specified in the //*CONTROLM JCL statement.
36 - The library specified in the //*CONTROLM JCL statement was not found.

The job is not submitted.

Corrective Action: Look for additional information that will clarify the reason (for example, the console log, TSO sysout, and so on).

CTM815E ERROR WHILE UPDATING THE $$ID MEMBER. (RC=`rc`)

Explanation: Update of the $$ID member in the JCL library failed (Control-M Quick Submit command). A return code of 56 indicates a D37 abend on the library specified in the //*CONTROLM JCL statement.

The job is not submitted.

Corrective Action: Look for additional information that will clarify the reason. For a return code of 56, compress or enlarge that library.

CTM816E ERROR WHILE SAVING THE JOB. (RC=`rc`)

Explanation: Writing the job to the JCL library failed (Control-M Quick Submit command).

Possible values of rc, and their explanations, are:

56 - There is insufficient space (abend D37) in the library specified in the //*CONTROLM JCL statement. Possible reasons are:
The directory is full in the library specified in the //*CONTROLM JCL statement.
The data set needs a secondary extent, but DASD space is not available.
A security violation has occurred.
64 - The member already exists or there is no space in the directory.

The job is not submitted.

Corrective Action: Do one of the following:

If the return code is 56, compress or enlarge the appropriate library.
If the return code is 64, there is a member in that library with the same name. Determine the reason and correct the problem.

CTM817E INVALID ID-NUMBER IN THE $$ID MEMBER

Explanation: The five characters in the first line of the $$ID member in the JCL library are not numeric. There should be one line containing the current ID. It should be five numeric digits, and left-justified.

The job is not submitted.

Corrective Action: Correct the $$ID member accordingly.

CTM821I MANUAL-COND `cond` ODATE `odate action`

Explanation: This information message displays the results from NEW or ERASE command. The condition cond of the odate original scheduling date was either erased from the Manual Conditions file or added to the Manual Conditions file.

Corrective Action: No action is required.

CTM822E MISSING PARAMETER OF NEW REQUEST

Explanation: The NEW command was supplied without any additional parameter. At least one parameter is expected after the NEW command. Valid parameters are COND, LCOND or CONDITION.

Corrective Action: Supply the correct command.

CTM823E INVALID TYPE IN NEW REQUEST

Explanation: Invalid NEW type supplied. At least one parameter is expected after the NEW command. Valid parameters are COND, LCOND or CONDITION.

Corrective Action: Specify the requested NEW type.

CTM824I MANUAL-COND `cond` ODATE `odate` EXISTS

Explanation: This information message indicates that the condition added by the NEW command already exists in the file.

Addition request ignored.

Corrective Action: No action is required.

CTM825E NEW FOR `cond` ODATE `odate` FAILED. FILE IS FULL

Explanation: The Manual Conditions file is full.

The condition is not added to the file.

Corrective Action: Try to delete conditions from the specified day in other months of the year. If you need all the conditions in the file for all the months, then consult your system programmer about the possibility of increasing the capacity of the IOA Manual Conditions file.

CTM826E CONDITIONS FILE OR MANUAL CONDS FILE IN USE, PLEASE TRY AGAIN LATER

Explanation: Another user or another IOA component is currently updating the file.

The command requested is not performed.

Corrective Action: Try again.

CTM828E UNEXPECTED RETURN CODE FROM CTMUNR

Explanation: Internal error. Invalid return code from the CTMUNR Control-M internal utility.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM829S INTERNAL ERROR - INVALID REQUEST TO CTMUNR

Explanation: Internal error. Invalid request to the CTMUNR IOA internal utility.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM830S INTERNAL ERROR - INVALID RESOURCE TYPE (CTMUNR)

Explanation: Internal error. Invalid resource type passed to the CTMUNR IOA internal utility.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM831E MANUAL-COND `cond` ODATE `odate` IS NOT IN THE FILE

Explanation: The cond condition that was marked for addition (the A option) has been deleted from the Manual Conditions file. While you were working on the screen, another IOA user deleted the condition from the Manual Conditions file.

The condition is not added to the Conditions file.

Corrective Action: Manually add the deleted condition to the Manual Conditions file using Screen 4.

CTM832E AT LEAST ONE OF "PENDING" OR "ADDED" MUST BE "Y"

Explanation: Neither the PENDING nor the ADDED option is marked as Y.

Corrective Action: Mark one retrieval option as Y.

CTM833S INTERNAL ERROR. INVALID RETURN CODE FROM CTMUNR

Explanation: Internal error. Invalid return code from the CTMUNR Control-M internal utility.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM834S OPEN OF IOA MANUAL CONDITIONS SYNC FILE FAILED

Explanation: Open of the IOA Manual Conditions Synchronization file failed. Possible causes are:

The DANSINC DD statement is missing.
The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but is a different version or for a different IOA installation.

Corrective Action: Correct the JCL for the job or the allocations of the CLIST.

CTM835S FILE ALLOCATED TO DDNAME "DANSINC" IS NOT THE MANUAL SYNC FILE

Explanation: The file allocated to the DANSINC DD statement is not the Manual Conditions Synchronization file. Possible causes are:

The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is a different version or for a different IOA installation.

Corrective Action: Check your TSO user allocations, and check for specific messages on the system log.

CTM836E VALID VALUES ARE 'P' 'N' '-' OR '+'

Explanation: The SAC job scheduling parameter for a Group entity scheduling definition contains an invalid value.

Valid values for SAC for a group entity job definition are:

P - previous day
N - next day
- (minus sign) - previous day only
+ (plus sign) - next day only

Corrective Action: Correct the value.

CTM837E VALID VALUES ARE 'P' OR 'N'

Explanation: The SAC job scheduling parameter for a job scheduling definition contains an invalid value.

Valid values for SAC for a job scheduling definition are:

P - previous day
N - next day

Corrective Action: Correct the value.

CTM846S INSUFFICIENT SPACE FOR `type cond odate`

Explanation: The output IOA Conditions file has insufficient space for all the prerequisite conditions from the input file. The combination of the LRECL parameter with the CNDREC# parameter is smaller in the output file than in the input file, and some prerequisite conditions in the input file could not be copied to the output file.

The variables in this message are:

type - the type of condition
cond - the condition name
odate - the original date

Conversion or copying of the file stops. The content of the output file is unpredictable.

Corrective Action: Create a larger output file and run the utility again.

CTM850S `modName` BLDL FAILED FOR MODULE

Explanation: BLDL for the modName module failed.

Probable causes are:

The module is not in one of the load module libraries used by the IOA Online Facility (Linklist, STEPLIB or invoked CALL library).
There is insufficient memory to load the program.

The modName module is not activated. Control is returned to the calling program. The IOA Online Facilities may abend on initialization.

Corrective Action: Verify whether the module appears in IOA Load library or any other concatenated load module library.

CTM855S INVALID PARAMETER SUPPLIED TO MODULE `mod-name - parm`

Explanation: Either an input parameter was omitted from, or an invalid input parameter (parm) was supplied to, the modName main IOA online module.

The variables in this message are:

modName - the name of the main IOA online module
parm -the identity of the missing or invalid parameter

The modName module expects a series of parameters to be input, describing the environment in which it is to be activated. The expected parameters are:

APPLTYPE=type,APPLID=id

In this expression:

type is S (for TSO), R (for KSL), I (for ISPF) or X (for OMEGAMON)
id is the user application ID

The IOA online environment is not built.

Corrective Action: Check for errors in the CLIST which activates the IOA online interface.

CTM856S DDNAME `ddName` NOT ALLOCATED

Explanation:Highlighted, unrollable message.

The DD name specified in the error message was not allocated before the user entered IOA.

The IOA Online facility terminates.

Corrective Action: Allocate the specified DD name and reenter IOA.

CTM857S PRODUCT `productName` NOT RECOGNIZED

Explanation:Highlighted, unrollable message.

A user tried to enter IOA using a user-defined transaction member which contained a definition of a product not recognized by IOA.

The IOA Online facility stops.

Corrective Action: Correct the product definition in the transaction member and reenter IOA.

CTM858S MEMBER NAME - `memName` IN TRANID `transMem` NOT FOUND IN PARM LIBRARY

Explanation:Highlighted, unrollable message.

A user tried to enter IOA using a user-defined transaction. The TRANID refers to a member which pointed to a PGM member name that did not exist in the parameter library referenced by the DD name DAONLPRM.

The Online facility terminates.

Corrective Action: Check that the PGM member is correctly specified in the transaction member. If it is correctly specified in this member, add it to the parameter library. Reenter IOA.

CTM859E INVALID RC `rc` FROM `routineName` ROUTINE

Explanation: The program ended with unexpected return code.

If the CTMRCAL utility is running, rc is 16, and routineName is IOABSR. In this case, the REPTYPE utility control statement is probably missing the S subparameter.

System action depends on the calling program. Execution may continue, or it may stop with a condition code of 08 or 12.

Corrective Action: If the REPTYPE utility control statement is missing the S subparameter, specify it with the S subparameter as REPTYPE nS, where n is 0, 1 or 2. Otherwise, notify your INCONTROL administrator.

CTM859S TRANID MEMBER NOT FOUND - `transMem`

Explanation: The user tried to enter IOA using a user-defined transaction. TRANID refers to a member that does not exist in the parameter library referenced by the DAONLPRM DD statement.

The IOA Online facility stops.

Corrective Action: Add the transaction member identified in the message to the parameter library and reenter IOA.

CTM85AS INVALID KEYWORD FOUND IN - `transMem`

Explanation: The user tried to enter IOA using a user-defined transaction. The TRANID refers to a member which contained an invalid keyword.

The Online facility stops.

Corrective Action: Check the keywords in the transaction member and correct them accordingly. See the section on transaction members in the INCONTROL for z/OS Administrator Guide. Reenter the IOA Online facility.

CTM85BS PLEASE CHECK THE TRANID MEMBER - `transMem`.

Explanation: An internal error occurred when a user tried to enter IOA using a user-defined transaction.

The internal error occurred when the IOA Online facility tried to initiate the IOA session using the transaction member identified in the message.

The IOA Online facility stops.

Corrective Action: Supply BMC Customer Support with a printout of the transaction member identified in the message.

CTM85CS ERROR OCCURRED DURING ALLOCATION PROCESS. PLEASE CHECK THE ALC MEMBERS

Explanation: IOA online system failed to allocate a file.

When the IOA Online facility starts up, it allocates all the files needed for the current session. At least one of these files could not be allocated.

Preceding messages detail the files that could not be allocated.

The IOA Online system stops.

Corrective Action: Correct the ALC xxx members according to information from the preceding messages and reenter IOA.

CTM85DS `ddName` DDNAME IS ALLOCATED. PLEASE FREE IT AND TRY AGAIN

Explanation: The ddName file was already allocated to the IOA Online environment when the IOA Online facility started up.

When the IOA Online facility starts up, certain files are dynamically allocated by it to the IOA environment. In this case, the ddName file identified in the message was already allocated to the IOA environment when IOA started up.

The Online facility terminates.

Corrective Action: Deallocate this DD name from the IOA environment.

CTM85ES MODULE `modName` RETURNED WITH RC=`rc`

Explanation: A severe error occurred in the modName module when the user tried to enter an IOA option. In most cases, the called program could not issue an error message.

Valid values for rc are:

rc	Explanation
08	There is no region below the line for the application.
12	There is no region above the line for the application.
16	A severe error occurred. The called program issued an error message.
20	A severe error occurred. An error message could not be issued.

The called program abends.

Corrective Action: The user response depends on the return code, as follows:

08 / 12 - In case of TSO, log off and log on again. In case of IOAOMON, stop and restart IOAOMON. If this does not help, reduce the number of IOAOMON users by modifying the MAXSESS parameter in the IOAXPRM member.
16 - Follow the instructions in the error message issued by the called program.
20 - Contact BMC Customer Support.

CTM85FS MAXIMUM NUMBER OF IOA SESSIONS REACHED

Explanation: TSO user tried to activate a fifth IOA session in his TSO address space.

In the TSO environment, the user can activate IOA sessions by executing the IOATSO or IOAISPF CLISTs. IOA allows a maximum of four sessions to be activated. If the user tries to activate a fifth session, this error message is generated.

The fifth session is not established.

Corrective Action: Terminate one of the previous sessions in order to initiate a new session.

CTM85IS GLOBAL PROFILE VARIABLES ($PROFILE) COULD NOT BE ACCESSED

Explanation: An attempt to access the $PROFILE member in the IOAENV library failed.

The most common cause is that the member is held by another user or program.

The IOA Online facility is not entered.

Corrective Action: Determine which user or program is holding the member, and try to obtain its release.

CTM860E OPTION NOT SUPPORTED YET

Explanation: The requested option is not yet supported. The option will be available in future IOA releases.

Corrective Action: No action is required.

CTM861I PLEASE SELECT OPTION

Explanation: No option selected.

Corrective Action: Select one option.

CTM862S ERROR IN COMMAND MEMBER - CALL SYSTEM PROGRAMMER

Explanation: Each IOA screen is controlled by an external command member that contains a list of all the commands and synonyms supported by the screen. Command members reside in IOA parameter libraries. They should be named T scrCMD1, where scr is the screen name.

Possible causes for this error message are:

Somebody incorrectly changed the contents of the command member.
The DACMD xx DD statement is allocated to the wrong library.

For more information on command members, see the section that describes how to define new application types in the IOA chapter of the INCONTROL for z/OS Installation Guide.

The screen is locked.

Corrective Action: To exit, press PA1 a few times. Allocate the parameters library to the DACMD xx DD statement, where xx is the application ID. If necessary, call your system programmer for assistance.

CTM863W THE CONTROL-M ACTIVE JOBS FILE IS NEARLY FULL

Explanation:Highlighted, unrollable message.

This message is issued when the threshold value specified by the AJFTHRSH CTMPARM parameter is reached. The message is issued in conjunction with message CTML17I, which displays the percentage of the Active Jobs file currently utilized.

Corrective Action: Contact your INCONTROL administrator immediately. It may be necessary to compress the Active Jobs file or to increase its size.

CTM864I PLEASE NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

This message is usually issued after a severe Control-M error that must be handled by an experienced Control-M person.

Corrective Action: Contact your INCONTROL administrator immediately.

CTM865E PLEASE FILL IN FROM STEP

Explanation: Possible causes for this message are:

RESTART is set to Y in the rerun or confirmation window, but the FROM field is blank.
A TO step name is specified in the restart decision line in the Zoom screen (Screen 3), but the FROM step field is blank.
STEP RANGE name is specified, but the FROM field in this STEP RANGE line is blank.

Corrective Action: Specify a step name in the FROM field, or set RESTART to N, erase the TO step name, and erase the STEP RANGE name.

CTM866E PLEASE FILL IN A VALID SET STATEMENT. FORMAT "%%VARNAME=VALUE"

Explanation: Invalid specification of an AutoEdit assignment in a DO SET statement.

The correct syntax for the SET statement line is: DO SET %%VARNAME=VALUE (for example, DO SET %%THISRUN=RERUN).

Corrective Action: Correct the AutoEdit variable assignment.

CTM867E INSUFFICIENT MEMORY, UNABLE TO PROCESS

Explanation: There is insufficient memory to perform the requested action.

The request is ignored.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM868E TABLE "`dsn` (`tableName`)" IS IN USE. TRY AGAIN LATER

Explanation: The specified member from an IOA definition library is currently in use by another user.

The variables in this message are:

dsn - the name of the data set containing the requested table
tableName - the name of the requested table

The request is ignored.

Corrective Action: Wait until the requested member is freed, then retry the request.

CTM869E TABLE "`tableName` " IS NOT A VALID SCHEDULING TABLE (CARD NUMBER `stmtNum`)

Explanation: The job table that was to be downloaded to Control-M/Enterprise Manager is not a valid scheduling table, for example, because the format of a statement is incorrect.

The variables in this message are:

tableName - the name of the problematic job table
stmtNum - the line number of the problematic statement within the job table

The download request is ignored.

Corrective Action: Either correct the errors in the scheduling table or specify the name of a valid scheduling table, then retry the download request.

CTM86AE INVALID VALUE, USE [0-9999]S or [0-9999]M FOR `Delayed_Submission_variable`

Explanation: Invalid value of a Delayed Submission variable in a DO SET or SETVAR statement.

Corrective Action: Correct the value of the Delayed Submission variable to a number between 0 and 9999, followed by S for a delay in seconds or M for a delay in minutes. The value cannot be more than 4 digits.

CTM86BE THIS IS A DELAYED SUBMISSION VARIABLE, USE ANOTHER VARIABLE NAME

Explanation: Incorrect use of a Delayed Submission variable in an INTO field of the CAPTURE BY option in the 2.Z or 3.Z screen.

Corrective Action: Do not use this variable name, as it is reserved for a Delayed Submission variable. Choose another variable name.

CTM86DE TOO MANY SETVAR STATEMENTS SPECIFIED

Explanation: More than 256 SETVAR statements have been specified in ORDER request.

The request is ignored.

Corrective Action: Specify up to 256 SETVAR statements.

CTM870E CTMMEM FAILED. TABLE=`tableName`, FUNCTION=`func`, RC=`rc`

Explanation: The CTMMEM internal service routine ended with an error.

The variables in this message are:

tableName - the name of the table for which CTMMEM was issued
func - the name of the relevant function
rc - the return code of the error

For more information about CTMMEM functions and return codes, see the DOCIMEM member in the IOAP DOC library.

The download request is ignored.

Corrective Action: Note the values of tableName, func, and rc, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTM871S CTMDUL INITIALIZATION FAILED: `descr`

Explanation: The initialization of the CTMDUL internal program failed.

In this message, descr is a brief description of the reason for the failure. Possible values for descr are:

LOAD FAILED FOR MODULE modName
GETMAIN FAILED

No tables are downloaded.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM872E TABLE `tableName` HAS BEEN CHANGED SINCE LAST DOWNLOAD. UPLOAD FAILED

Explanation: Uploading of a table to the mainframe was attempted. However, the table was changed following the last download to the Control-M/Desktop. Jobs can be uploaded to a table after another being downloaded by another user. However, this wipes out any jobs updated to the mainframe since the last download.

The upload utility terminates with a return code of 12.

Corrective Action: Either force the table to be uploaded or save the table under another table name. Force uploading a table will overwrite any earlier version currently on the mainframe. Use great caution with a forced upload. If a forced upload is used, jobs updated to the mainframe since the last download will be lost.

CTM873E ERROR CONVERTING TABLE "`tableName` " JOB "`jobName` ": `descr`

Explanation: The job could not be downloaded or uploaded.

The variables in this message are:

tableName - the identity of the problematic table
jobName - the identity of the problematic job
descr - a short description of the cause of the failure

The download or upload request is ignored.

Corrective Action: Proceed on the basis of the information contained in descr.

CTM874S NEW TABLE "`tableName` " IS TOO BIG (MORE THAN 200,000 CARDS)

Explanation: The job table could not be uploaded to Control-M because it would require more than 200,000 statements.

The maximum size of a job table is 200,000 statements.

In this message, tableName is the name of the problematic job table.

The upload request is ignored.

Corrective Action: Correct the contents of the tableName job table so that it requires less than 200,000 statements when uploaded to Control-M.

CTM875E PLEASE FILL IN CALENDAR NAME OR OMIT YEAR

Explanation: A year was specified, but the calendar name is missing. A year can be defined only in a calendar.

Corrective Action: Either fill in a calendar name or omit the year to get a list of calendars in the library.

CTM880E CANNOT ADD MORE YEARS TO CALENDAR (MAXIMUM 10)

Explanation: The calendar is full. The maximum number of years in a calendar is 10. You cannot add more years.

Corrective Action: Split the calendar into two calendars, or delete unnecessary years.

CTM881E CALENDAR TOO LARGE. ERASE UNNECESSARY YEARS

Explanation: The calendar is too large to be handled by IOA Online.

Possible causes are:

Insufficient storage to process the calendar.
The calendar is too large.

Corrective Action: Do one of the following:

Log on again using a larger size parameter.
If you are using many IOA screens concurrently, exit some of them using the END command.
Split the calendar into two calendars.
Erase redundant years from the calendar.

CTM885E INVALID YEAR (OR YEAR NOT IN VALID RANGE)

Explanation: The specified year is not a valid year, or is not in the range supported in IOA.

Corrective Action: Specify a valid year.

CTM886I TOP OF YEARS LIST

Explanation: This information message indicates that the current year is the first year in the years list. The message may appear after entering the command PREVYEAR in the Year screen.

Corrective Action: No action is required.

CTM887I BOTTOM OF YEARS LIST

Explanation: This information message indicates that the current year is the last year in the years list. The message may appear after entering the command NEXTYEAR in the Year screen.

Corrective Action: No action is required.

CTM888E VALID OPTIONS ARE "Y", "+", "- ", "N" OR BLANK

Explanation: An invalid day selection option has been specified. The cursor points to the invalid day value.

Valid day selection options are:

Y - Yes
N - No
' ' (blank) - No
+ (plus) - the next date in a relative calendar
- (minus) - the previous date in a relative calendar

Corrective Action: Specify Y, N, +, -, or blank.

CTM891E OPTION SPECIFIED IS INVALID IN CASE OF A PERIODIC CALENDAR

Explanation: The characters Y, N, +, and - are not supported under periodic calendars.

Corrective Action: Use another period identifier.

CTM899E REDUNDANT PARAMETER

Explanation: The number of occurrences of the fields listed below exceeds the maximum number allowed:

DATES - 12
WDAYS=DnWm parameters - 11
MAIL-TO, MAIL-CC, MAIL-TX - 255
RMD-SUM - 2
RMD-DES - 15

Corrective Action: Delete the additional occurrences and rerun the job.

CTM89AS LIBRARY NAME IS NOT SPECIFIED

Explanation: Either the LIBRARY parameter was not specified, or the specified library does not exist.

Corrective Action: Depending on the cause, either correct the specification or create the specified library; then rerun the job.

CTM89BE PLEASE SPECIFY `parm`

Explanation: The parm parameter is missing. At least one TABLE parameter is required after the LIBRARY parameter. At least one MEMNAME parameter is required for each TABLE parameter.

Corrective Action: Add any missing statements, and rerun the job.

If an attempt is being made to create a group scheduling table with only a group entity and no job scheduling definitions, then set the EMPTYGRP parameter to Y in the CTMPARM member of the IOA PARM library, and then rerun the job.

CTM89CE SPECIFIED SUB-PARAMETER IS OUT OF SEQUENCE

Explanation: The parameter or subparameter specified is out of sequence.

The sequence in which certain parameters and subparameters appear in a CTMBLT input file is important. For more information on this sequence, see the Control-M chapter in the INCONTROL for z/OS Utilities Guide.

This message is accompanied by other messages that provide additional information, including a message that identifies the parameter or subparameter that was not coded in the correct sequence.

Corrective Action: Correct the sequence of the parameters and subparameters and rerun the job.

Messages CTM900 through CTM9xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM901E INVALID OPTION (TRY "Y", "N", "R" OR BLANK)

Explanation: The user entered an invalid value into a field which may only contain Y, N, R or blank.

Corrective Action: Correct the input field and press Enter.

CTM902E INVALID OPTION (TRY "Y", "N" OR BLANK)

Explanation: The user entered an invalid value into a field which may only contain Y, N, or blank.

Corrective Action: Correct the input field and press Enter.

CTM903E "FORCE" CODE MUST BE ALONE.

Explanation: Another code is entered with the FORCE code in the same ON PGMST statement. No other code may be specified with FORCE in the same ON PGMST statement.

Corrective Action: Remove any other code from the current statement and put it in a different ON PGMST statement or remove the FORCE code.

CTM904E "FORCE" CODE VALID ONLY ON ANYSTEP

Explanation: The step name is not ANYSTEP. When the code is FORCE, the step name in an ON PGMST statement must be ANYSTEP.

Corrective Action: Correct the step name or remove the FORCE code.

CTM905E "FORCE" CODE NOT VALID WITH PROC

Explanation: There is data in the PROC field, but the code is FORCE. When the code is FORCE, the PROC field in an ON PGMST statement must be empty and the step name must be ANYSTEP.

Corrective Action: Clear the PROC field or remove the FORCE code.

CTM906S ACCUMULATION STOPPED BECAUSE OF A REQUEST FROM USER EXIT 005

Explanation: The CTMX005 Control-M user exit issued a return code to stop the run of the CTMJSA utility.

The utility stops executing with a condition code of 12.

Corrective Action: Check for messages from the user exit that will clarify the reason.

CTM907E "FORCE" CODE NOT VALID IN MULTIPLE ON STATEMENTS

Explanation: The FORCE code is in an ON PGMST statement that is connected by AND or OR to another ON PGMST statement. When the code is FORCE, no other ON PGMST statement may have an AND or OR relationship with it.

Corrective Action: Separate the ON PGMST statement containing it from other ON PGMST statements or remove the FORCE code.

CTM908E INVALID DO ACTION FOR "FORCE" CODE

Explanation: Invalid DO actions follow an ON PGMST statement that has a code of FORCE. When the code is FORCE, only COND, FORCEJOB, SET VAR and SHOUT actions are allowed.

Corrective Action: Remove the invalid DO actions from the ON PGMST statement containing the FORCE code and put them in a separate statement or remove the FORCE code.

CTM909E JOB LEVEL CODES VALID ONLY ON ANYSTEP

Explanation: A job level code was specified for a specific job step or range of steps in the job scheduling definition. Examples of job level codes are: JNRUN, JLOST, OK, and NOTOK. Job level codes relate to the overall result of the entire job execution, not to specific steps. They can only be specified with ON PGMSTEP ANYSTEP.

Corrective Action: Do not specify job level codes for specific steps or step ranges.

CTM90AE ON +EVERY IS VALID ONLY FOR CNNNN, SXXX, UNNN, FLUSH, SNRUN AND *****

Explanation: An ON step value of ON PGMSTEP +EVERY can only be specified with codes C nnnn, S xxx, U nnn, FLUSH, SNRUN and *****.

Corrective Action: Correct the Step value or the Codes value in the job scheduling definition to a valid combination.

CTM90BE "SNRUN" CODE NOT VALID ON ANYSTEP

Explanation: Code SNRUN is not valid for an ON PGMSTEP ANYSTEP statement.

Corrective Action: Correct the Step value or the Codes value in the job scheduling definition to a valid combination.

CTM911S IOA LOG FILE - WRITE ERROR

Explanation: I/O error while writing on IOA Log file.

Possible causes are:

The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log, but it is of a different version of Control-M.
Real I/O error on the IOA Log.

Corrective Action: Check the contents of the computer log for additional messages which may clarify the picture.

CTM912S ERROR IN CONTROL-`x` INSTALLATION PARAMETERS - INVALID DAYTIME

Explanation: Invalid format of the DAYTIME Control- x installation parameter. DAYTIME is the start time of the Control-M work day in your installation. Valid formats are +hhmm or -hhmm.

For more details see the section that describes installation parameters in the chapter for the appropriate products in the INCONTROL for z/OS Installation Guide.

The requested function terminates.

Corrective Action: Call your system programmer to correct the DAYTIME parameter in the CT xPARM member.

CTM913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of the print file failed. Possible causes are:

The DD statement SYSPRINT is missing.
The data set described by the DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

CTM914S ERROR IN IOA INSTALLATION PARAMETERS - INVALID DATETYP

Explanation:Highlighted, unrollable message.

The DATETYP IOA Installation Parameter is invalid. DATETYP is the type of date format used in the installation. Valid formats are:

A - mmddyy
W - ddmmyy
J - yymmdd

For more details, see the section that describes how to set IOA installation parameters in the IOA chapter of the INCONTROL for z/OS Installation Guide.

The requested function stops.

Corrective Action: Call your system programmer to correct the DATETYP parameter in the IOAPARM member.

CTM916W PROGRAM `pgm` WAITING FOR `resourceName`

Explanation: One of the IOA monitor internal programs detected an IOA resource in use by a TSO user or batch job. This message normally appears a few times a day.

The variables in this message are:

pgm - the name of the internal program that is waiting for the resource that is in use
rname - the name of the resource that is in use

Valid values are:

rname	Meaning
CNDF	The IOA Conditions file
RESF	The Control-M Resources file
LOG	The IOA Log file
Control-M/D	The Control-M/D New Day procedure
AMFT	Control-D Active Missions file
JES_SSRQ	A JES subsystem request
CKPT	The Control-M Active Jobs file or the Control-D Active Missions file

The message is displayed on the operator console.

Corrective Action: The user response depends on the circumstances, as follows:

If the message appears many times every few seconds, the file may be hung. This situation must be resolved by determining which program is holding the specified rname. Look for the IOA QNAME that is specified in the IOA Installation Parameter and take appropriate corrective action.
If pgm is CTMFRM/CTDFRM and the rname is CONTROLM/CONTROLD, some possible reasons are:
- there are several Control-M/D monitors running with the same QNAME
- there is a user daily job running that has a date control record in which columns 60 through 65 are not blank, meaning that it is acting as the Control-M/D New Day procedure and therefore Control-M/D has been enqueued
- the Control-M/D New Day procedure was started externally (manually) rather than being started by the monitor, and as a result waits for the monitor to be suspended
  
  Take appropriate corrective action.
If the program name pgm is CTMJES and the resourceName is JES_SSRQ, then Control-M (in its postprocessing phase) has called the JES2 interface using IEFSSREQ (a JES2 subsystem request) and is waiting for some function to be executed by JES2, but the execution of that function is being delayed in JES2. If the message persists in this situation, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM918S INSUFFICIENT MEMORY TO RUN CONTROL-`x`

Explanation:Highlighted, unrollable message.

More memory is required for the INCONTROL monitor.

The specified monitor will shut down.

Corrective Action: Increase the REGION size of the specified monitor.

CTM919S INTERNAL ERROR IN CONTROL-M MONITOR

Explanation:Highlighted, unrollable message.

An internal error occurred in the Control-M monitor.

The Control-M monitor abends with the user abend 0008.

Corrective Action: Try to start the Control-M monitor again. In any case, prepare the dump and contact BMC Customer Support.

CTM91ES ENVIRONMENT ERROR. CONTROL-M MONITOR INITIALIZATION ABORTED.

Explanation: The Control-M monitor detected an environment initialization error at startup.

Control-M monitor initialization is aborted.

Corrective Action: Verify that Control-M is fully installed, and notify the INCONTROL administrator.

CTM91FS CONTROL-M NOT FULLY INSTALLED. MONITOR INITIALIZATION ABORTED.

Explanation: At startup, the Control-M monitor detected that Control-M is not fully installed, and cannot initialize the IOA environment.

Control-M monitor initialization is aborted.

Corrective Action: Verify that Control-M is fully installed, and notify the INCONTROL administrator.

CTM920S AJF SIZE IS NOT EQUAL TO AJFSIZE PARAMETER SPECIFIED IN CTMPARM.

Explanation:Highlighted, unrollable message.

The value of the AJFSIZE parameter in the CTMPARM file used by a Control-M monitor is different from the value of the AJFSIZE parameter in the Active Jobs file (AJF).

The AJF was formatted using an AJFSIZE parameter from a specific CTMPARM file. The Control-M monitor also uses an AJFSIZE parameter from a CTMPARM file, which is not necessarily the same CTMPARM file used to format the AJF. The value of the AJFSIZE parameter used by the Control-M monitor must match the value of AJFSIZE in the AJF.

The Control-M monitor shuts down.

Corrective Action: Ask the INCONTROL administrator to do one of the following:

Change the value of AJFSIZE in the CTMPARM file used by the Control-M monitor to the value of AJFSIZE in the AJF.
Reformat the AJF using a CTMPARM file in which AJFSIZE has the same value as the AJFSIZE used by the Control-M monitor.

Once one of these has been performed, restart the monitor.

CTM921I ACCUMULATION OF JOB EXECUTION STATISTICS STARTED

Explanation: This information message is a normal starting message of the CTMJSA utility.

Corrective Action: No action is required.

CTM922I ACCUMULATION OF JOB EXECUTION STATISTICS ENDED WELL

Explanation: This information message is a normal ending message of the CTMJSA utility.

Corrective Action: No action is required.

CTM923S OPEN OF PARAMETERS FILE FAILED. DDNAME "DAJSAIN"

Explanation: Open of parameters file for the CTMJSA utility failed.

This can be due to one of the following:

The DAJSAIN DD statement missing.
The data set described by the DAJSAIN DD statement cannot be opened for sequential read.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the JCL of the job and rerun it.

CTM92CS INVALID PARAMETER, VALID PARAMETERS ARE ACT=R/W, TYPE=F/V

Explanation: An invalid parameter was passed to the IOADIG utility.

Valid ACT parameter values are:

R - Perform a read-only check. Do not correct detected errors.
W - If an error is detected, correct it.

Valid TYPE parameter values are:

F - Fixed length records in data file.
V - Variable length records in data file.

The utility terminates with a return code of 24.

Corrective Action: Rerun the IOADIG utility after setting its parameters to valid values.

CTM92TE SIZE OF CKPJNL FILE DIFFERS FROM SIZE OF AJF -- JOURNALING DISABLED

Explanation: The size of the Active Jobs file (AJF) base image file differs from the size of the production AJF.

The CKPJNL base image file in the AJF is created after New Day processing and is used by the CTMRSTR restore utility. The size of this file must be identical to that of the production AJF.

The Control-M monitor halts processing and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W.

CTM92UE ALLOCATION OF FILE `fileName` FAILED RC `rc`

Explanation: The Control-M monitor failed to allocate the fileName file. The reason for the failure is described by a return code value of rc.

The Control-M monitor deallocates the file and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W. Note the message, including return code, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTM931I CLEAN FOR IOA CONDITIONS FILE STARTED

Explanation: This information message indicates that the IOACLCND utility started.

Corrective Action: No action is required.

CTM932I CLEAN FOR IOA CONDITIONS FILE ENDED

Explanation: This information message indicates that the cleaning of the IOA Conditions file by the IOACLCND utility ended successfully.

Corrective Action: No action is required.

CTM933S FILE ALLOCATED TO DDNAME "DASINC" IS NOT IOA SYNCHRONIZATION FILE

Explanation: The data set described by the DASINC DD statement is not IOA Synchronization file. This message is produced by the IOACLCND IOA utility.

Possible causes are:

The file allocated to the DASINC DD statement is not the Synchronization file.
The file allocated to the DASINC DD statement is the Synchronization file, but it is of a different version or of a different IOA installation.

The utility stops executing.

Corrective Action: Correct the JCL for the job.

CTM934E INVALID PARAMETER: - `parm`

Explanation: An invalid parameter (parm) was passed to the IOACLCND utility.

In this message, parm identifies the invalid parameter.

For a list of valid parameters, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CTM935E MISSING PARAMETER AFTER: - `parm`

Explanation: A subparameter of a parameter of the IOACLCND utility is missing. A subparameter is expected after the parm parameter.

For valid syntax, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CTM936E REDUNDANT PARAMETER: - `parm`

Explanation: There is a redundant parameter in a parameter line for the IOACLCND utility.

For details, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CTM937S IOA CONDITIONS FILE WAS NOT CLEANED

Explanation: Result of a previous error in the IOACLRES utility. A previous message should appear, containing the reason for not cleaning the Conditions file.

The utility stops executing.

Corrective Action: Correct the problem and rerun the utility.

CTM939E DATE RANGE IS GREATER THAN ONE YEAR

Explanation: The date range specified in the FROM and TO parameters is greater than one year (the IOACLRES utility). The TO date is greater than the FROM date by more than a year. There is no way to IGNORE more than one year.

The utility will stop executing with a condition code of 08.

Corrective Action: Correct the parameters and rerun.

CTM942S OPEN OF IOA MANUAL CONDITIONS FILE FAILED

Explanation: Open of the IOA Manual Conditions file failed. Possible causes are:

The DANRES DD statement is missing.
The file allocated to the DANRES DD statement is not the IOA Manual Conditions file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is of a different version or of a different IOA installation.

Corrective Action: Correct the JCL for the job or the allocations of the CLIST.

CTM943S OPEN OF IOA MANUAL CONDITIONS SYNCHRONIZATION FILE FAILED

Explanation: The IOAFRNRS utility, which is used to allocate and format the file, failed to open the file for formatting.

Possible causes are:

The DACKPT DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL, and rerun the job.

CTM944I BUILDING OF IOA MANUAL CONDITIONS FILE STARTED

Explanation: This information message indicates that the IOAFRNRS utility, which is allocates and formats the Manual Conditions file, started.

Corrective Action: No action is required.

CTM945I BUILDING OF IOA MANUAL CONDITIONS FILE ENDED

Explanation: This information message indicates that the IOAFRNRS utility, which allocates and formats the Manual Conditions file, ended normally.

Corrective Action: No action is required.

CTM945W < `resource name`>/< `resource amount`> RELEASED BY CTMRLR, WILL BE FREED FROM WORKLOAD < `workload name`> AFTER JOB ENDS

Explanation: The resource name was released by the CTMRLR utility, and will be freed from the specified workload after the job ends.

Corrective Action: No action is required.

CTM946S IOA MANUAL CONDITIONS FILE WAS NOT BUILT

Explanation: The IOAFRNRS utility failed.

Corrective Action: Look for previous error messages which will describe the type of the error.

CTM947E INSUFFICIENT MEMORY IN CONTROL-M MONITOR - TOO MANY STCS WITH SAME NAME

Explanation:This message is also displayed on the output of the monitor.

There are too many STCs with the same name.

The STC will end NOTOK.

Corrective Action: Purge the unneeded STCs with the duplicate names from the spool.

CTM950S OPEN FAILED FOR DDNAME "DARESF"

Explanation: Open of Control-M Resources file failed (the DARESF DD statement). Possible causes are:

The DARESF DD statement is missing.
The data set described by the DARESF DD statement is not the Control-M Resources file.
The data set described by the DARESF DD statement is the Control-M Resources file of a different version or a different Control-M monitor.

The Control-M monitor shuts down.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again.

CTM955I OID=`orderId` ORPHAN CONTROL `contResource` MODE {E | S} WAS AUTOMATICALLY DELETED BY THE MONITOR

Explanation: This information message indicates that the monitor released the contResource Control resource, with the mode Exclusive (E) or Shared (S), because there is no job that controls it.

Corrective Action: No action is required.

CTM956I OID=`orderId` ORPHAN CONTROL `quant-res` QUANTITY `num` WAS AUTOMATICALLY DELETED BY THE MONITOR

Explanation: This information message indicates that the monitor released the specified number (num) of the indicated Quantitative resource (quant-res), because there are no jobs that control them.

Corrective Action: No action is required.

CTM95BE OPEN OF CONTROL-M HISTORY FILE (DDNAME "DAHIST") FAILED. RC=`rc`

Explanation: The user entered the HISTORY command followed by the name of a History file, but there is an error in opening the specified history file.

Corrective Action: Verify that the specified History file is valid. Contact BMC Customer Support and report the received return code.

CTM95CE CLOSE OF CONTROL-M HISTORY FILE (DDNAME "DAHIST") FAILED. RC=`rc`

Explanation: The user entered the HISTORY command followed by the name of a History file, but there is an error in closing the specified history file.

Corrective Action: Verify that the specified History file is not being used by another application. Contact BMC Customer Support and report the received return code.

CTM95DE PARAMETER FOR "HIST" COMMAND IS NOT SUPPORTED UNDER ONLINE MONITOR

Explanation: The HISTORY command followed by the name of a History file cannot be used with the online monitor.

Corrective Action: No action is required.

CTM95ES RESOURCE FILE INTERNAL ERROR

Explanation: Severe Control-M internal error in the Resource file.

A snap dump is written to the DATRACE DD statement, and the monitor shuts down.

Corrective Action:Do the following:

Send the following to BMC Customer support:
1. the complete sysout from the Control-M monitor
2. the Resource file
3. the CKP file
4. IOAPARM
5. CTMPARM
6. IOA Log file
Re-start the Control-M monitor.

CTM95FS INTERNAL ERROR: ACTUAL NUMBER OF BASE SLOTS GREATER THAN RE0BASE#

Explanation: Severe Control-M internal error in the Resource file.

A snap dump is written to the DATRACE DD statement, and the monitor shuts down.

Corrective Action:Do the following:

Send the following to BMC Customer support:
1. the complete sysout from the Control-M monitor
2. the Resource file
3. the CKP file
4. IOAPARM
5. CTMPARM
6. IOA Log file
Re-start the Control-M monitor.

CTM95GE POST PROCESSING ERROR. INSUFFICIENT FREESPACE FOR 'SET VAR' STATEMENTS

Explanation: Control-M failed to handle a DO SETVAR post processing statement because there was not enough space in the corresponding job record in the AJF. The indicator POST-PROCESSING FAILED is set for the job.

Corrective Action:Contact IOA administrator to consider increasing the FREESPAC= installation parameter in CTMPARM. If it is not suitable or does not help, contact IOA Technical support.

CTM966E RULE-BASED CALENDAR `calName` NOT FOUND

Explanation: A rule-based calendar (RBC) specified in the advanced scheduling parameters (that is, in a time period of Type 6) in a Workload Policy rule was not recognized. The message is issued to the Control-M monitor, and is followed by message CTMWLGE, which provides more details about the Workload Policy. The Workload Policy rule is ignored.

Corrective Action: Correct the name of the RBC specified in the Workload Policy rule. Alternatively, define a new RBC with the specified name through the IOA Calendar Facility (Screen 8).

CTM971S OPEN OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE FAILED

Explanation: Either the FORMCKP utility (which allocates and formats the Active Jobs file) or the FORMHST utility (which allocates and formats the Active History file) failed to open the file for formatting.

Possible causes are:

The DACKPT DD statement (for the Active Jobs file) or the DAHIST DD statement (for the History Jobs file) is missing.
There is insufficient memory for the job.

The utility ends with a condition code of 08.

Corrective Action: If a DD statement is missing, add the correct DD statement are rerun the job. If the problem is memory, specify a higher value for the REGION parameter.

CTM972I BUILDING OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE STARTED

Explanation: This information message indicates the normal start of the FORMCKP utility or the FORMHST utility. The FORMCKP utility allocates and formats the Active Jobs file. The FORMHST utility allocates and formats the Active History file.

Corrective Action: No action is required.

CTM973I BUILDING OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE ENDED

Explanation: This information message indicates the normal termination of either the FORMCKP utility or the FORMHST utility. The FORMCKP utility allocates and formats the Active Jobs file. The FORMHST utility allocates and formats the Active History file.

Corrective Action: No action is required.

CTM974S Control-M {ACTIVE | HISTORY} JOBS FILE WAS NOT BUILT

Explanation: Either the FORMCKP utility, which allocates and formats the Active Jobs file, or the FORMHST utility, which allocates and formats the Active History file, failed.

Corrective Action: Check the previous error messages which describe the type of error, and correct the problem accordingly.

CTM975S Control-M {ACTIVE | HISTORY} JOBS FILE WRITE ERROR

Explanation: An I/O error occurred while formatting the Control-M Active Jobs file or History Jobs file. This error may be caused by an incompatibility between the installation parameters (CTMPARM) that define the Active Jobs file or History Jobs file, and the JCL SPACE and/or DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters file.

CTM982S OPEN OF IOA CONDITIONS FILE FAILED

Explanation: The IOAFRRES IOA utility, which is used to allocate and format the IOA Conditions file, failed to open the file for formatting.

Possible causes are:

The DARESC DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTM983S OPEN OF IOA SYNCHRONIZATION FILE FAILED

Explanation: The IOAFRRES IOA utility, which is used to allocate and format the Control-M Resources Synchronization file, failed to open the file for formatting.

Possible causes are:

The DASINC DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTM984I BUILDING OF IOA CONDITIONS FILE STARTED

Explanation: This information message indicates that the IOAFRRES utility, which allocates and formats the IOA Conditions file, has started.

Corrective Action: No action is required.

CTM985I BUILDING OF IOA CONDITIONS FILE ENDED

Explanation: This information message indicates that the IOAFRRES utility, which allocates and formats the IOA Conditions file, has ended normally.

Corrective Action: No action is required.

CTM986S IOA CONDITIONS FILE WAS NOT BUILT

Explanation: The IOAFRRES utility failed.

Corrective Action: Look for previous error messages that describe the type of error.

CTM988S DATE SHOULD NOT BE GREATER THAN YESTERDAY

Explanation: Invalid date specified for archival or backup (the CTMLGC utility). The archive date should not be greater than yesterday’s date.

The utility stops execution with a condition code of 08.

Corrective Action: Correct the date field.

CTM989S OPEN OF DDNAME "DALOGHIS" FAILED. LOG ARCHIVAL NOT PERFORMED

Explanation: Open of the log archival data set failed (the CTMLGC utility).

Possible causes are:

The DALOGHIS DD statement missing.
The DALOGHIS DD statement describes a file which is not in the format of the IOA Log.

The utility stops execution with a condition code of 08.

Corrective Action: Correct JCL for the job. You should run the CTMFRLOG utility to allocate and format an archival file in exactly the same format as the IOA Log.

CTM990I `action` OF IOA LOG STARTED

Explanation: This information message is a normal message which is issued when starting to backup the IOA Log (the CTMLGC utility).

Corrective Action: No action is required.

CTM991I `action` OF IOA LOG ENDED

Explanation: This information message is a normal message which is issued when the backup of the IOA Log ends (the CTMLGC utility).

Corrective Action: No action is required.

CTM992W OPEN OF DDNAME "DALOGBKP" FAILED, BACKUP OF IOA LOG NOT TAKEN

Explanation: Open of the data set described by the DALOGBKP DD statement failed.

Possible causes are:

The DALOGBKP DD statement missing.
The data set described by the DALOGBKP DD statement cannot be opened for sequential write.

Backup of IOA Log not taken. Processing continues.

Corrective Action: If you want to backup the entire Log file, correct the JCL for the job.

CTM993S OPEN OF DDNAME "DALGCIN" FAILED. LOG ARCHIVAL NOT PERFORMED

Explanation: Open of the data set described by the DALGCIN DD statement failed.

Possible causes are:

The DALGCIN DD statement missing.
The data set described by the DALGCIN DD statement cannot be opened for sequential read.

Log archival is not performed.

Corrective Action: Correct the JCL for the job.

CTM994S FILE CONNECTED TO DDNAME "DALGCIN" IS EMPTY

Explanation: The data set described by the DALGCIN DD statement is empty.

Log archival is not performed.

Corrective Action: Correct the JCL for the job.

CTM995S RECORD LENGTH OF DDNAME "DALGCIN" IS NOT 80

Explanation: Record length of data set described by the DALGCIN DD statement must be 80 bytes.

Log archival is not performed.

Corrective Action: Check the contents of data set described by the DALGCIN DD statement.

CTM996S "UNTIL DATE" OF LOG ARCHIVAL IS NOT A VALID DATE

Explanation: Invalid parameter for UNTIL date.

Corrective Action: Correct the UNTIL date parameter of the Log archival utility.

CTM997S NUMBER OF DAYS TO KEEP IN LOG FILE IS NOT NUMERIC

Explanation: Invalid number of days to keep in the Log file.

The number of days to keep in the Log file must be numeric.

Corrective Action: Correct the number of days.

CTM998S ARCHIVAL FILE ALLOCATED TO "DALOGHIS" IS FULL

Explanation: Archival file allocated to the DALOGHIS DD statement is full.

Archival will not be executed.

Corrective Action: No action is required.

CTM999S NOTHING TO DO. NEITHER BACKUP NOR ARCHIVAL IS NEEDED

Explanation: Neither file DALOGHIS nor file DALOGBKP has been opened by the CTMLGC utility.

The utility terminates with a return code of 12.

Corrective Action: No action is necessary.

CTM9B1E SYSTEM LOGGER CONNECT REJECTED, DASD-ONLY LOG STREAM IS ALREADY CONNECTED TO BY ANOTHER LOG STREAM IN THE SYSPLEX

Explanation: The System Logger rejected an attempt to connect to a DASD-only log stream because another log stream in the Sysplex is already connected. Only applications from the same system (LPAR) can connect simultaneously to the DASD-only log streams. If you are using DASD-only log streams, then Control-M, CMEM or Control-O, and IADDC (the CONNECT DIRECT interface) must all be running in the same LPAR.

The attempt to connect is rejected.

Corrective Action: Determine which system you want to connect to the log stream, and rerun the component that failed in the correct system.

If you want all members in a Sysplex to have access to the log stream, use coupling facility log streams rather than DASD-only log streams. For more information, see the description of sysplex configuration parameters in the INCONTROL for z/OS Installation Guide.

Messages CTMA00 through CTMAxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMA06E STATISTICS DO NOT EXIST FOR MEMBER `memName` GROUP `grp`

Explanation: There was an attempt to view statistics of a job for which no statistics are available. The Statistics file is updated only by the CTMJSA JCL procedure. If a job is run for the first time in this system, job statistics may not yet exist. If the job was previously run on this system, CTMJSA is probably not run regularly at your site.

Corrective Action:Check whether or not CTMJSA is runs regularly at your site. To get job statistics, run CTMJSA regularly.

CTMA07S VIEWING OF ARCHIVED SYSOUTS FAILED. RC=`rc`

Explanation: An error occurred in the CTMTSYV or CTRTSTP Control-M internal module. There was an attempt to perform a view (V) function or a step list display on the Active Jobs file. However, a problem indicated by the return code occurred in the module, and the SYSDATA could not be retrieved:

Valid values for rc are:

rc	Explanation
12	The name of Archived Sysout Data set does not follow the Control-M/Restart naming convention for this type of data set.
16	The Archived Sysout data sets (which are accessed to retrieve SYSDATA for viewing) belong to another job.
20	The loading of an internal module failed. Message CTM046S which preceded this message specifies the module in question.
24	The CTRTSTP module encountered an internal CDAM error.
28	ATTACH for the CTRTSTP module failed, probably because of insufficient memory.
32	The CTRTSTP module abended. A symptom dump probably exists in the JOBLOG or the SYSLOG.

Archived SYSDATA is not displayed.

Corrective Action: Record the return code, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMA08E INSUFFICIENT MEMORY TO VIEW ARCHIVED SYSOUTS

Explanation: The CTMTSYV or CTRSTP internal module failed to perform the view or step list display function on the Active Jobs file due to insufficient storage allocated to the Control-M online environment.

The archived SYSDATA is not displayed.

Corrective Action: Notify your INCONTROL administrator. The storage allocated to the online environment by the REGION parameter must be enough for all Control-M processing.

CTMA09E MEMNAME IS A REQUIRED PARAMETER

Explanation: The user issued a JOBSTAT command without specifying a member name. The JOBSTAT command, which displays job statistics, needs the name of the member whose statistics are to be displayed.

Corrective Action: Try again. Specify the member name with the JOBSTAT command.

CTMA10E PARAMETER LENGTH EXCEEDS MAXIMUM

Explanation: A parameter (JOBNAME or GROUPNAME) specified in the JOBSTAT command exceeded the maximum allowable length. The maximum length for the JOBNAME parameter is eight characters. This parameter is required for the JOBSTAT command. The maximum length for the GROUPNAME optional parameter is 20 characters. If this parameter is omitted, the group name is assumed to be blank.

Corrective Action: Correct the command and try again.

CTMA11E OPEN OF STATISTICS FILE FAILED. DDNAME "DASTAT"

Explanation: The Statistics file could not be opened. When you use option 3.S to view job statistics, Control-M attempts to open the Statistics file pointed to by the DASTAT DD statement. This message is displayed when the attempt fails.

Corrective Action: Check that the data set described by the DASTAT DD statement is allocated to the Statistics file. See the Control-M installation procedure for details.

CTMA12E CANNOT REACT JOB `jobName` ODATE `odate` - JOB NOT DISAPPEARED/FAILED

Explanation: Option A (Reactivate) was specified for a job that did not have a status of DISAPPEARED or FAILED REASON UNKNOWN. The Reactivate option can only be specified for jobs having a status of DISAPPEARED or FAILED REASON UNKNOWN. This option allows the search for the sysout to continue.

Corrective Action: No action is required.

CTMA13E INVALID AUTO REFRESH INTERVAL

Explanation: An invalid AutoRefresh interval was specified. The number of seconds specified for the interval in the AUTO command must be between 1 and 99.

AutoRefresh mode is not activated.

Corrective Action: Re-enter the AUTO command followed by a number between 1 and 99.

CTMA14I AUTO REFRESH EVERY `num` SECONDS - `counter`

Explanation: This information message displays the current AutoRefresh interval and counter value. It is displayed whenever the screen is in AutoRefresh mode to indicate that the screen display is being updated automatically every num seconds. The counter value indicates the number of times the screen was refreshed.

Corrective Action: No action is required.

CTMA15I AUTO REFRESH CANCELED

Explanation: This information message indicates that AutoRefresh mode was terminated. AutoRefresh mode is cancelled by a user request, or if an attempt is made to activate AutoRefresh mode in an environment that does not support it.

For more information, see the description of AutoRefresh mode in the Online Facilities chapter in the Control-M for z/OS User Guide.

Corrective Action: No action is required.

CTMA16E STORAGE SHORTAGE. UNABLE TO `action`

Explanation: The action requested in the Active Environment screen cannot be performed due to storage shortage.

The requested action is not performed.

Corrective Action: Increase the REGION size and try again.

CTMA16I TSO CMD ENDED WITH RC=0

Explanation: This information message indicates that a TSO command entered from the command line of an IOA screen was performed successfully.

Corrective Action: No action is required.

CTMA16S OPEN OF STATISTICS FILE FAILED. RC=`rc` ERROR=`errCode`

Explanation: The Control-M Statistics file (DD name DASTAT) failed to open. The return and error codes are VSAM codes.

Control-M will not accumulate statistics, and as a result deadline scheduling calculations may be inaccurate.

Corrective Action: Check the return and error codes in the IBM manual for DFP macro instructions for data sets under VSAM macro return and reason codes, and correct accordingly.

CTMA17E TSO CMD ERROR. R15=`r15`, RET-CODE=`rc`, RS-CODE=`rsn`, AB-CODE=`ab_code`

Explanation: An unsuccessful attempt was made to perform a TSO command entered from the command line of an IOA screen. A TSO command can only be activated from an IOA screen when running the IOA Online facility under ISPF or TSO. The variables displayed in the message are returned by TSO.

Corrective Action: Verify that you entered the command when running the IOA Online facility under ISPF or TSO. If the command was activated under one of these environments then the problem lies in TSO. Have the INCONTROL administrator correct the problem using the TSO codes appearing in the message and try the command again.

CTMA17I NO DEPENDENCIES EXIST FOR THIS JOB

Explanation: This information message indicates that the N line command in the Active Environment screen was used to display the net of dependencies for a specific job, but the job had neither predecessors nor successors.

Corrective Action: No action is required.

CTMA18W JOBS ADDED TO THE AJF. "REFRESH" MAY BE NEEDED

Explanation: Jobs have been added to the Active Jobs file (AJF). The Net file might have to be refreshed to display all the dependent jobs.

Corrective Action: Refresh the Net file by issuing command REFRESH NET using Screen 3.

CTMA19W NET FILE IS NOT UPDATED, "REFRESH" IS NEEDED

Explanation: The request to display net dependencies of a job cannot be performed because the Net file has not been updated.

Only the root job is displayed.

Corrective Action: Refresh the Net file by issuing command REFRESH NET using Screen 3.

CTMA1AE VALUE MUST BE TBL OR CTM

Explanation: When defining a SCHEDULE RBC parameter in a Smart Table Entity, either TBL (a SCHEDULE RBC defined in a Smart Table Entity and used by jobs in this Smart Table) or CTM (a SCHEDULE RBC defined by IOA Calendars Facility and can be used by any job) must be specified in the LEVEL field.

Corrective Action: In the LEVEL field, specify either TBL or CTM.

CTMA1BE PLEASE FILL IN RBC NAME

Explanation: Displayed under IOA Calendars Screen for RBC calendars when either a SAVE RBC or COPY RBC request is issued without specifying an RBC name. The SAVE or COPY request does not proceed.

Corrective Action: Either enter the RBC name to proceed or cancel the request.

CTMA1CE A VALUE OF "*" IS VALID ONLY IN A JOB THAT BELONGS TO A SMART TABLE

Explanation: The asterisk ("*") wild card character, which indicates all the RBCs of the Smart Table entity, can only be used to specify the SCHEDULE RBC scheduling parameter for a job that belongs to a Smart Table.

Corrective Action: Use * only for Schedule RBCs defined in Smart Tables.

CTMA1DE EXCLUDE RBC WITH NO INCLUDE RBC IS NOT A VALID DEFINITION

Explanation:A schedule cannot be defined with only Exclude RBCs. At least one Include RBC must be part of the schedule definition, besides the Exclude RBCs.

Corrective Action:Define or make reference to at least one include RBC, besides the Exclude RBC.

CTMA20W "REFRESH" IN PROGRESS, PLEASE WAIT

Explanation: The request to display net dependencies of a job cannot be performed because the Net file is being refreshed.

Only the root job is displayed.

Corrective Action: Wait a short while, then press Enter again. Repeat this until the refresh process is completed and the dependent jobs are displayed.

CTMA21W NET FILE IS BUSY, PLEASE TRY LATER

Explanation: The request to display net dependencies of a job cannot be performed because the Net file is busy.

Only the root job is displayed. No dependent jobs are displayed.

Corrective Action: Wait a short while and then press Enter again. Repeat this until the Net file is released and the dependent jobs are displayed.

CTMA22E MODULE=`modName`, FUNCTION=`func`, RC=`rc - text`

Explanation: An error occurred during display of the net dependencies of a job. If rc is 28, the QNAME in the GRF file in the first record, just after the constant JD0, differs from the QNAME specified in IOAPARM.

The variables in this message are:

mod-name - the module that caused the error.
func - the function requested.
rc - the code returned by the function.
text - the explanation of the error, such as LOAD FAILED and GETMAIN FAILED.

The Net screen is not displayed.

Corrective Action: Notify your INCONTROL administrator or system programmer, who should take required actions based on the information in the message. For example, depending on the type of error, the requested load module can be made accessible, or the region size can be enlarged.

If rc is 28, reformat the GRF file with the QNAME specified in IOAPARM.

CTMA23E INVALID "REFRESH" PARM - `parm`

Explanation: The user specified the REFRESH command in the Net screen (screen 3.N) with an invalid parameter.

The REFRESH process is not performed.

Corrective Action: Re-issue the REFRESH command with a valid parameter.

CTMA24W CONTROL-M IS DOWN - REFRESH PENDING

Explanation: The REFRESH NET command was issued but the Control-M monitor was down, so some jobs may not have been displayed in the Net Display screen.

Corrective Action: Wait until Control-M comes up again, then continue work as usual.

CTMA25I REFRESH "`refresh_type` " ISSUED

Explanation: This information message indicates that the REFRESH command was successfully submitted in the Net screen (screen 3.N).

The Refresh process starts.

Corrective Action: Wait until the refresh is complete, then continue working.

CTMA26E USER NOT AUTHORIZED

Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.

Corrective Action: Check with your system security administrator.

CTMA27I THE NEW LANGUAGE WILL BE USED FROM THE NEXT LOGON TO IOA

Explanation: This information message is a response to the use of the SET command to set a language. It indicates that the newly-set language will begin to be used when you next log on to IOA.

Corrective Action: No action is required.

CTMA29E INVALID TRACE LEVEL. USE:SET TRACE=`trace-lvl`

Explanation: Either the value or the setting of the specified trace is not valid. The trace level may be any value from 1 through 256. The trace level setting must be ON or OFF.

The system ignores the command and continues processing.

Corrective Action: Enter a valid value and/or a valid setting for the trace level, and try again.

CTMA2AI TRACE LEVEL `nnn` WAS SET {ON | OFF}

Explanation: This information message indicates that a trace level was turned ON or OFF, where nnn is the TRACE level number.

Corrective Action: No action is required.

CTMA2CE ONLINE TRACING IS NOT ALLOWED, PLEASE CONTACT YOUR IOA ADMINISTRATOR

Explanation: A user issued the SET TRACE command in order to turn on the trace, and the tracing is not allowed.

The trace is not turned on.

Corrective Action: Contact your IOA administrator in order to enable the online tracing.

CTMA30I OLD AJF NEEDED `#recs` RECORDS FOR `#jobs` JOBS

Explanation: The AJF conversion utility issues this information message to show the number of jobs on the old Active Jobs file, and the number of old Active Jobs file records that were needed to store these jobs.

Corrective Action: No action is required.

CTMA31I NEW AJF NEEDS `#recs` RECORDS FOR `#jobs` JOBS

Explanation: The AJF conversion utility issues this information message to show the number of jobs on the new Active Jobs file, and the number of new Active Jobs file records that are now needed to store these jobs.

The variables in this message are:

#recs - the number of new AJF records required to store #jobs
#jobs - the number of jobs on the new AJF

Corrective Action: No action is required.

CTMA32I PERCENTAGE OF RECORDS RELEASED IN NEW JOBS FILE: `nn` %

Explanation: The AJF conversion utility issues this information message to show the percentage of unused records in the new Active Jobs file (AJF).

In this message, nn% is the percentage of unused records in the new AJF.

Corrective Action: No action is required.

CTMA33I AVERAGE NUMBER OF RECORDS PER JOB IN NEW AJF: `nn.nn`

Explanation: The AJF conversion utility issues this information message to show the average number of records used to store one job on the new Active Jobs file.

Corrective Action: No action is required.

CTMA34I AVERAGE NUMBER OF FREE BYTES PER JOB IN NEW AJF: `#bytes`

Explanation: The AJF conversion utility issues this information message to show the average number of unused bytes in the records used to store one job on the new Active Jobs file.

Corrective Action: No action is required.

CTMA3AS OLD STEPLIB AND NEW STEPLIB ARE THE SAME

Explanation: The CTMCAF utility cannot convert the file from one version to another because only one Load library was indicated. The STEPOLD DD statement should point to the Load library of the previous version, but it points to the Load library of the new version.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Correct the STEPOLD DD statement so that it points to the Load library of the previous version, and rerun the job.

CTMA3BS SIZE OF OLD AJF/HST DIFFERS FROM SIZE OF NEW ONE

Explanation: The CTMCAF utility cannot convert the file from one version to another because the AJF or HST file sizes are not identical. The conversion requires the same size files for the new version and the old version. The file size should match the size specified in CTMPARM.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Correct the file sizes so that they are identical for both versions, and rerun the job.

CTMA3CS LOAD MODULE CTMLOGR FAILED

Explanation: An internal error occurred during the load of the CTMLOGR module.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Have your INCONTROL administrator record the return code, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMA3DS DELETE MODULE CTMLOGR FAILED

Explanation: An internal error occurred during deletion of the CTMLOGR module.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Have your INCONTROL administrator notify your INCONTROL administrator.

CTMA41E ERROR IN AJF CACHE PROCESSING. FUNCTION xxxxxxxx CODE xx

Explanation: Internal error in the Control-M Monitor logic of keeping Jobs in the memory. Control-M Monitor terminates abnormally.

Corrective Action: Keep the Control-M Monitor output and IOA LOG and contact IOA technical support.

CTMA42I AJF MEMORY IMAGE ALLOCATED ABOVE THE 2G BAR

Explanation: This information message notifies you that the memory image for the Active Jobs File (AJF) was allocated above the 2G bar.

Corrective Action: No action is required.

CTMA44W AJF IS LOADED ABOVE THE BAR. SPACE REUSE IS DISABLED (REUSTIME=0 ENFORCED)

Explanation: This message is issued when AJFABAR=Y is used for explicit loading of the AJF into 64-bit storage (above the 2GB BAR). Such an AJF is capable of supporting up to 10,000,000 records. As a result, the AJF Space Reuse facility, which allows reuse of space in smaller-sized AJFs that are loaded to 31-bit storage (below the 2GB BAR), is not required and is therefore disabled by enforcing the REUSTIME=0 setting in CTMPARM.

Corrective Action: You can choose the following alternative settings:

To load the AJF to 31-bit storage (below the 2GB BAR) and re-enable the Space Reuse Facility, use AJFABAR=A or AJFABAR=N.
To avoid this message, explicitly disable the Space Reuse Facility (by setting REUSTIME=0 in CTMPARM).

Note: The Space Reuse Facility can only be enabled when the AJF is loaded to 31-bit storage (below the 2GB BAR). Support for this facility will be discontinued in a future release of Control-M, and BMC advises that you disable it. Disabling the Space Reuse Facility allows the AJF to be loaded to 64-bit storage (above the 2GB BAR) and enables you to manage high volumes of jobs in the AJF.

CTMA45W AJF IS LOADED BELOW THE BAR DUE TO NON-ZERO REUSTIME SETTINGS (SPACE REUSE ENABLED)

Explanation: This message is issued when AJFABAR=A is used for automatic selection of the storage type to which the AJF is loaded (that is, either 31-bit “below the 2GB BAR” or 64-bit “above the 2GB BAR”). The message indicates that 31-bit storage (below the 2GB BAR) is selected, because the Space Reuse Facility is enabled (REUSTIME is set to a non-zero value in CTMPARM).

Corrective Action: If you want to allow the AJF to be loaded to 64-bit storage (above the 2GB BAR), disable the Space Reuse Facility by setting REUSTIME=0 in CTMPARM.

The AJF can be loaded to 64-bit storage (above the 2GB BAR) only if the Space Reuse Facility is disabled. Support for this facility will be discontinued in a future release of Control-M, and BMC advises that you disable it. Disabling the Space Reuse Facility allows the AJF to be loaded to 64-bit storage (above the 2GB BAR) and enables you to manage high volumes of jobs in the AJF.

CTMA55E TASK IS NOT APF AUTHORIZED

Explanation: A started task (STC) requiring APF authorization was not APF authorized. Certain STCs (for example, CTMVMON) must be run from APF authorized libraries.

The task stops after issuing the error message.

Corrective Action: Change the JCL or authorize the library so that the STC will be run from an authorized library.

CTMA56E MEMBER `memName` READ ERROR RC=`rc` IN `dsn`

Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered an error while reading table memName in data set dsn.

This message is followed by additional messages which identify the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: For information about the return code rc, see the DOCIMEM member in the IOA DOC library.

CTMA57E MEMBER `memName` IS EMPTY IN `dsn`

Explanation: While processing CMEM or Control-O request, the Control-M monitor encountered an empty table memName in data set dsn.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: Make sure that table memName contains valid scheduling information.

CTMA58E ABEND `abCode` WHILE PROCESSING `dsn`

Explanation: While processing a CMEM or Control-O request for data set dsn, the Control-M monitor encountered an abend condition abCode.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: Record the abend code, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMA59E FORCEJOB FAILED FOR JOB `jobName` IN TABLE `tableName` FROM `dsn`

Explanation: An error occurred while processing a FORCEJOB request for job jobName, or, in the case where jobName is blank, for the complete scheduling table tableName.

The source of the request may be:

Control-O request for a DO FORCEJOB
Control-M request for a DO FORCEJOB
CMEM FORCEJOB action

This message is preceded by another message, which gives more details of the cause of the error.

Control-M may try again to execute the job or table, depending on the values set for the FORCE#RT and FORCE#WI installation parameters. For more information, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: Correct the error as detailed in the preceding message. If scheduling is still required for the job or table for which the error occurred, then the job or table should be ordered manually. If the specification in the original request was incorrect, correct it and reload, if necessary. Reload the CMEM table or reorder the Control-O rule.

CTMA5AE ANOTHER MONITOR ALREADY READING FROM LOG STREAM STR=`structureName` L/S=`logStreamName`

Explanation: This error message is issued when an attempt is made to read an MVS System Logger log stream which is currently being read by another Control-M monitor.

To avoid a loop of FORCEJOB jobs, the same MVS System Logger log stream should not be read simultaneously by more than one Control-M monitor . Should a second Control-M monitor attempt to read the same log stream, this error message is issued.

The CMEM facility is deactivated for this Control-M monitor.

Corrective Action: Make sure only one Control-M monitor is reading the same MVS System Logger log stream simultaneously.

CTMA5BE FREEMAIN (`storage_add /len`) FAILED AT POINT `ref_point`

Explanation: A Control-M component attempted to free a block of working storage, but failed to do so.

The variables in this message are:

storage_add - the working storage address
len - the length of the working storage
ref_point - the reference point in the Control-M component

No additional action is performed.

Corrective Action: If this is a recurring problem, prepare the Control-M monitor full output and contact BMC Customer Support. If ignored, this may cause severe insufficient storage problems.

CTMA5CI CONTROL-M WILL RETRY PERFORMING THE FORCEJOB REQUEST FOR JOB `jobName` TABLE `tableName` IN `dsn`

Explanation: Control-M failed to execute a DO FORCEJOB request because a scheduling table was in use.

The source of the DO FORCEJOB request may be any of the following:

DO FORCEJOB a Control-O request for a DO FORCEJOB
DO FORCEJOB a Control-M request for a DO FORCEJOB
aa CMEM DO FORCEJOB action

Control-M queues the DO FORCEJOB request, and may try again to execute it, depending on the values set for the FORCE#RT and FORCE#WI installation parameters.

For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

CTMA5DI FORCEJOB SUCCEEDED AFTER RETRIES FOR JOB `jobName` IN TABLE `tableName` FROM `dsn`

Explanation: After failing to execute a DO FORCEJOB request because a scheduling table was in use, Control-M retried the request and succeeded in executing it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.

The source of the DO FORCEJOB request was one of the following:

a Control-O request for a DO FORCEJOB
a Control-M request for a DO FORCEJOB
a CMEM DO FORCEJOB action

No additional action is taken.

Corrective Action: No action is required.

CTMA5EI CONTROL-M WILL RETRY PROCESSING DATASET TRIGGER: `trigger_dsn`

Explanation: During the processing of a CONNECT DIRECT request, no successfully triggered events were processed, and a data set-in-use condition occurred.

The probable source of the CONNECT DIRECT request is the IOADCC utility.

Control-M queues the DO FORCEJOB request, and will try again to execute it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.

For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

CTMA5FE SCHEDULE LIBRARY `schedLib` IS MIGRATED

Explanation: A DO FORCEJOB command was issued for a table in the schedLib scheduling library, which has been migrated. An attempt was made to RECALL the library. An additional message follows describing whether the RECALL action was successful or not.

Corrective Action: Look for the following messages, which inform about the success of the RECALL action.

CTMA5IE CONTROL-M WILL NO LONGER RETRY THE REQUEST

Explanation: When a schedule table is not available because the data set is in use by another address space, Control-M retries the request several times based on the FORCE#RT parameter in CTMPARM. When this number of retries is exhausted and Control-M no longer retries the request, this message is displayed.

Control-M no longer retries the request.

Corrective Action: Determine why the data set is in use and retry the request manually. Messages CTMC53E and CTMA59E give details about the job name, table name, and schedule library name.

CTMA60I EXCEPTIONAL CONDITION RC=`rc`, ERROR=`err`, FEEDBACK=`feedback`, APPLID=`applId`

Explanation: This information message indicates that an exceptional VTAM condition was encountered during the execution of a KOA communication command.

This informational message is issued by the KOA Facility. Return code, error and feedback information are detailed in an appendix to the Control-O User Guide.

The KOA script continues processing. If an ON SCREENERROR statement was specified, the processing resumes at the label specified in the ON statement.

Corrective Action: Analyze the specific VTAM error, and take the corresponding corrective actions. Make sure that the error is handled correctly by the KOA script.

CTMA64E KEYSTROKE UTILITY DETECTED INTERNAL ABEND `abCode`

Explanation: An internal abend was intercepted by the KeyStroke utility.

The KSL/KOA script is terminated.

Corrective Action: Check the associated error messages. Correct the KOA script accordingly, and resubmit.

CTMA70E THERE IS AN ERROR IN IOAKPRM MEMBER. PLEASE CHECK THE SMFID FIELD.

Explanation: The SMFID of the CPU to which the KSL job was submitted does not appear in the IOAKPRM member in the IOA PARM library.

The KSL stops running.

Corrective Action: Add the SMFID by making the appropriate entry in the IOAKPRM member. The best way of doing this is by means of the INCONTROL Installation and Customization Engine (ICE). For more information on ICE, see the INCONTROL for z/OS Installation Guide.

CTMA86I CTMUDR STARTED

Explanation: This informational message indicates that the initial program invoked by the CTMEMUDL procedure has begun processing.

Corrective Action: No action is required.

CTMA87I CTMUDR ENDED

Explanation: This information message indicates the normal termination of the initial program invoked by the CTMEMUDL procedure.

Corrective Action: No action is required.

CTMAE1I LOADING AUTO-EDIT CACHE USING MEMBER: `memName`

Explanation: This information message indicates the start of Control-M AutoEdit cache initialization. The message is issued on starting the Control-M monitor if the AECACHL parameter is defined, or when the command F CONTROLM,AECACHE=RELOAD... is processed.

In this message, memName identifies the member that contains the list of members that should be loaded into AutoEdit cache.

Corrective Action: No action is required.

CTMAE2I `textLine`

Explanation: This information message displays a non-comment line from the member indicated in message CTMAE1I, as follows:

This message is issued for each line in that member that is processed.
This message is also issued, if an error occurs, to display the line associated with the error. The error can occur in the line itself, or it can occur in the member pointed to by the line.

Corrective Action: No action is required.

CTMAE3E ERROR READING MEMBER `memName` RSN/RC = `rsn rc`

Explanation: An error occurred during the reading of the member referenced by the DD statement identified in message CTMAE2I. The return code (rc) and reason code (rsn) are returned by the IOAMEM utility.

Loading of Auto-Edit cache is terminated.

Corrective Action: Correct the error. Recycling of the Control-M monitor is not necessary; refresh the Auto-Edit cache by entering the operator command F CONTROLM,AECACHE=RELOAD[(memName)].

CTMAE4E INTERNAL ERROR LOADING AUTO-EDIT CACHE. CACHING CANCELLED. RC = `rc`

Explanation: An internal error occurred during the loading of AutoEdit cache. The cause may have been a shortage of storage.

Loading of Auto-Edit cache is terminated.

Corrective Action: Correct the error. Recycling of the Control-M monitor is not necessary; refresh the Auto-Edit cache by entering the operator command F CONTROLM,AECACHE=RELOAD[(memName)].

CTMAE5E SYNTAX ERROR IN MEMBER `memName`. LOADING OF AUTO-EDIT CACHE TERMINATED

Explanation: An AutoEdit syntax error was detected either in the line identified in message CTMAE2I, or in the member referenced by that line.

Loading of Auto-Edit cache is terminated.

Corrective Action: Correct the syntax error. Recycling of the Control-M monitor is not necessary; refresh the Auto-Edit cache by entering the operator command F CONTROLM,AECACHE=RELOAD[(memName)].

CTMAE7E ERROR CODE RETURNED BY IOAGLB. FUNCTION: `func` RC = `rc`

Explanation: An error occurred when trying to access the IOA AutoEdit database.

If the problem occurred during JCL processing during submission, and %%RESOLVE NO was not previously set , job submission is cancelled. Otherwise, the variable remains as is, that is, unresolved.

Corrective Action: The following actions are recommended:

Check if the Control-O or CMEM monitor is up.
Use screen IV to check that the IOAVAR database is defined.
Check that the IOAVAR database is defined in the IOAprefix IOAENV(IOAGLBVL) member.

Messages CTMB00 through CTMBxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMB01S ISPF MESSAGE: `msgText`

Explanation: ISPF generates this message when an ISPF service returns an invalid return code of 12 or higher. The message text describes the specific problem.

The ISPF service is abnormally terminated.

Corrective Action: Check the information provided in the error message. Note that many problems can be resolved by exiting and reentering ISPF.

CTMB03S INTERNAL ERROR `descr`. EXIT ISPF AND RETRY

Explanation: ISPF returned an invalid return code, usually an RC less than 12. This general message may be issued for any ISPF service, such as TBADD, TBPUT, VCOPY, and so on.

The ISPF service is abnormally terminated.

Corrective Action: Many problems can be solved by exiting and reentering ISPF.

CTMB04E LOCATE FAILED FOR - `string`

Explanation: The LOCATE command failed to find the required parameter.

The lines on the screen remain in their original position.

Corrective Action: No action is required.

CTMB05E INVALID COMMAND - `cmd`

Explanation: The command entered is not a valid command.

The command is ignored.

Corrective Action: Correct the command entry. You may use the Help command (PF1) to display a list of the available commands.

CTMB06I CHANGES NOT SAVED DUE TO A CANCEL REQUEST

Explanation: This information message indicates that a CANCEL command was entered. The user requested that all changes made to the current table or plan be ignored.

The changes are not kept in the library.

Corrective Action: No action is required.

CTMB07E VALID OPTIONS: " " (UPDATE) D (DELETE) A/R (ADD) I (INSERT)

Explanation: An invalid value was entered in the OPTION field.

The invalid option is ignored.

Corrective Action: Enter a valid option. Valid options are listed in the error message. Use the Help command (PF1) to display a list and explanation of the available options.

CTMB10E {TABLE | PLAN} {`table|planid`} NOT CREATE. RC=`rc`

Explanation: The facility could not create a new Master Table or Plan. The ISPF service TBADD failed with the return code rc specified in the message.

The table or plan is not created.

Corrective Action: Check the return code of the TBADD service. Many problems are solved by exiting and reentering ISPF.

CTMB11I {TABLE | PLAN} {`table|planid` } CREATED AND PLACED IN `lib`

Explanation: This information message indicates that a new table or plan was added to the library.

Corrective Action: No action is required.

CTMB12E MASTER {TABLE | PLAN} {`table|planid`} ALREADY EXISTS. USE ANOTHER NAME

Explanation: The facility found an existing table or plan with the same name. Each Master Table or Plan must have a unique name in the system.

The Master Table or Plan is not created.

Corrective Action: Assign another name to the table you want to create.

CTMB13E INTERNAL ERROR - MEMORY ALLOCATION FAILED

Explanation: An internal error occurred during the Display Type definition syntax check.

The User Report List is not displayed.

Corrective Action: Contact BMC Customer Support.

CTMB14E MASTER {TABLE | PLAN} {`table|planid` } NOT FOUND. YOU MAY CREATE IT, OR EXIT

Explanation: The facility could not find the specified Master Table or Plan. It can be created now).

Corrective Action: To create a new Master Table or Plan, fill in the required details. To exit and return to the previous menu, press PF03 or PF15.

CTMB20E UPDATING OF MEMBER `memName` FAILED. COMPRESS LIBRARY `lib`

Explanation: The facility cannot update the AutoEdit member in the library because the AutoEdit parameters library is full.

The parameters member will not be created or updated.

Corrective Action: Compress the AutoEdit library.

CTMB21S UNABLE TO ALLOCATE DATASET `dsn` DDNAME `ddName`

Explanation: The facility cannot perform dynamic allocation for the data set. The most probable cause is that the data set is held by another user or job.

The operation is terminated immediately.

Corrective Action: Check what prevented the dynamic allocation. If it was because another user held the data set, try again later.

CTMB22S IOACND ERROR - COND `cond` NOT ADDED. RC=`rc`

Explanation: The facility received an invalid return code from IOACND. The facility tried to add the condition to the IOA Conditions file by using the IOACND program. The operation failed.

The condition is not added.

Corrective Action: Check the messages produced by IOACND and proceed accordingly.

CTMB23I PARM `parm` UPDATED IN MEM `memName` LIBRARY `lib`

Explanation: This information message indicates that the AutoEdit member was updated in the library. The facility updated the parameter in the AutoEdit member.

Corrective Action: No action is required.

CTMB25S UNABLE TO FIND THE LOG FILE. CHECK THE SPECIFIED CONTROL-M PREFIX

Explanation: The facility cannot find the IOA Log file having the specified prefix. The facility uses the IOA Log file, and other files to add a condition to the Conditions file. Only the log file is checked, since all the files have the same prefix.

The operation stops immediately.

Corrective Action: Check the IOA files prefix in the Primary Menu.

CTMB26E TABLE PROMPTB NOT FOUND - DEFINE AT LEAST ONE TABLE IN OPTION 1

Explanation: The facility cannot find any tables in the Master Table List. The PROMPTB Table, which contains the Master Table List, is not found. The reason may be that a user specified Option 2 of the facility before defining at least one Master Table.

The facility returns to the Primary Menu.

Corrective Action: Define at least one Master Table in Option 1.

CTMB27E PLEASE FILL IN A VALID OPTION - "Y" OR "N"

Explanation: You tried to close the Save/Create Window without specifying whether or not to save or create the defined parameters and conditions. When exiting the Define Parameters and Conditions screen in the Parameter Prompting Facility Type 1, the Save/Create Window is opened. Option Y or N must be specified to save or create.

Corrective Action: No action is required.

CTMB28I TABLE `tableName` DELETED

Explanation: This information message confirms that the specified table will be deleted from the table list displayed by the Parameter Prompting facility (PPF) (Type 1) and from the table prompt library, as requested. The system issues this message after the user confirms the delete request.

As soon as the system finishes deleting the table, it redisplays the PPF Table Selection screen.

Corrective Action: No action is required.

CTMB30E PLEASE ENTER: SAVE (SAVE THE CHANGES) OR CANCEL (DO NOT KEEP CHANGES)

Explanation: Changes to the table were not saved or cancelled. After making changes in a table, you must enter SAVE or CANCEL to leave the table. SAVE saves the changes; CANCEL leaves the table unchanged.

Corrective Action: Enter SAVE or CANCEL.

CTMB31E PLEASE {SPECIFY THE PLAN NAME | FILL IN THE TABLE NAME PREFIX}

Explanation: There is no table name prefix or plan name.

Corrective Action: Enter the table name prefix or plan name.

CTMB32E TABLE `tableName` NOT FOUND IN LIB `lib`

Explanation: The facility cannot find the tableName table in the lib library.

Corrective Action: Do one of the following:

For the PROMPT facility, create a new master table with the appropriate table name prefix.
For the End User Job Order interface, ask your INCONTROL administrator to do one of the following:
Modify the @@USRTBL administration member
Create the tableName table in the lib library

CTMB33E THE PARAMETER IS NOT CORRECTLY DEFINED. DEFINE IT IN OPTION 1

Explanation: The parameter name is missing from the Daily or Master Table, so the facility cannot update the parameter.

Corrective Action: Define the parameter using Option 1.

CTMB34E TABLE IN USE BY ANOTHER USER OR UNABLE TO CREATE A NEW TABLE

Explanation: The facility cannot read the existing Daily Table or create a new one. The table is probably in use by another user.

The Daily Table is not displayed.

Corrective Action: Try again later.

CTMB37E `master_table` NOT FOUND IN LIBRARY `lib`

Explanation: The table list contains the name of a Master Table that the facility cannot find in the library.

The facility returns the Master Table List to the user.

Corrective Action: Delete the Master Table name from the Master Table list.

CTMB38E MEMBER `memName` MAY ALREADY EXIST IN `lib`

Explanation: The facility cannot copy the Master Table to Daily Table. When a member cannot be copied from one library to another, it may be because a member with the same name already exists in the target library.

The facility returns the Master Table List to the user.

Corrective Action: Check the Table library.

CTMB41I COND `cond` ODATE `odate` ADDED, AND PARM `parm` UPDATED

Explanation: This information message indicates that the specified parameter was successfully updated, and the specified prerequisite condition was added to the IOA Conditions file.

Corrective Action: No action is required.

CTMB42I PARM UPDATED, BUT COND `cond` ODATE `odate` ALREADY EXISTS

Explanation: This information message indicates that the specified parameter was updated, but the specified prerequisite condition was not added to the IOA Conditions file, because the condition already existed in the file. While the requested parameter change was successful (that is, the facility updated the parameter), it was unnecessary to add the condition to the Conditions file because the parameter had already been updated that day.

Corrective Action: No action is required.

CTMB48S INSUFFICIENT STORAGE. EXIT ISPF AND RETRY

Explanation: The facility cannot get enough virtual storage to create or read an AutoEdit member because the REGION size is too small.

The member is not created or updated.

Corrective Action: Exit ISPF and try to re-enter; or increase the REGION size.

CTMB49E READING AUTOEDIT MEMBER `memName` FAILED. CHECK LIBRARY `lib`

Explanation: The facility can not read the AutoEdit member from the library. There is probably a general system problem with the library file.

The member is not created or updated.

Corrective Action: Check the AutoEdit library file for general systems problems.

CTMB50E `type` - IS AN INVALID TYPE

Explanation: Invalid TYPE specified.

Corrective Action: Correct the TYPE field.

CTMB51E TYPE - `type` - ALREADY IN USE FOR THIS PARAMETER TYPE

Explanation: This type has already been defined for this parameter.

Corrective Action: Enter a correct TYPE combination.

CTMB52E INVALID TYPE COMBINATION - `type`

Explanation: This type conflicts with the previous types in the TYPE definition for the parameter. The combination is invalid.

Corrective Action: Enter a correct TYPE combination.

CTMB53E A VALID NUMBER IS EXPECTED AFTER MINL/MAXL

Explanation: An invalid value was entered after MINL or MAXL, which specifies the length limit. Valid values are number between 1- 99.

Corrective Action: Enter a valid number after MINL or MAXL.

CTMB54E SPECIFIED PARAMETER INVALID FOR TYPE - `type`

Explanation: The parameter does not match the type specified in the message.

Corrective Action: Enter a value which is appropriate to the TYPE.

CTMB60S INTERNAL ERROR - UNABLE TO CALL VALIDATION ROUTINE CTMTVAL

Explanation: The facility cannot call the validation routine CTMTVAL. The CTMTPRP program, which is operated from CTMEXEC, failed to call the CTMTVAL validity check routine.

CTMEXEC terminates abnormally.

Corrective Action: Check the IOA Load library.

CTMB61E DATE FORMAT SHOULD BE `ddmmyy` (INTERNATIONAL) OR `mmddyy` (USA)

Explanation: The date format is invalid. The date field contains data, but the format of the date is not ddmmyy or mmddyy.

The panel is redisplayed with an error message.

Corrective Action: Enter date in the correct format.

CTMB62E UNABLE TO ALLOCATE LIBRARY `lib`

Explanation: The facility cannot allocate the lib library. The facility failed to allocate an existing library, or to create a new Daily library.

The current operation is abnormally terminated.

Corrective Action: If the library already exists, try displaying it. If the library is a new library, check to see if there is sufficient free space on the disk.

CTMB63E SCHEDULING TABLE `tableName` NOT FOUND IN LIBRARY `lib`

Explanation: The facility cannot find the tableName Scheduling Table in the lib library.

The current operation is terminated.

Corrective Action: Add the Scheduling Table to the library.

CTMB69E THE PARAMETER `parm` DOES NOT HAVE A DEFAULT VALUE

Explanation: There is no default value for this parameter. There is a request for the default value of the parameter to be used; however, this parameter does not have a default value.

No value is set for the parameter.

Corrective Action: Enter the value for the parameter.

CTMB70I AUTOEDIT MEMBER `memName` HAS BEEN UPDATED IN THE DAILY LIBRARY

Explanation: This information message indicates the facility updated the AutoEdit member. The facility does not order the jobs of the Daily Plan more than once. However the AutoEdit member is updated with the current value of the parameters in the plan.

Corrective Action: No action is required.

CTMB71I PLAN `planid` CONTAINS PARAMETERS WITHOUT A VALUE. CANNOT BE ORDERED

Explanation: This information message indicates that the plan contains parameters without values. Therefore, the plan cannot be ordered by Control-M. A plan is ordered by Control-M only when all the parameters contain values.

The plan is not ordered.

Corrective Action: Enter values for the parameters.

CTMB72E THE REMAIN OPTION IS BEING USED. TRY AGAIN LATER

Explanation: Another user is probably performing an EXEC using the REMAIN option.

The EXEC phase is not performed.

Corrective Action: Try again later.

CTMB73S CANNOT OPEN PLAN `planid`. EXIT ISPF AND RETRY

Explanation: The facility cannot read the parameters from the plan.

The plan will not be ordered by Control-M, and the AutoEdit member will not be created.

Corrective Action: Exit, and then re-enter, ISPF.

CTMB74I END OF PLAN LIST

Explanation: This informational message indicates that the user specified YES in the REMAIN option of CTMEXEC, and CTMEXEC finished processing all the plans in the Daily library.

Corrective Action: No action is required.

CTMB75E AUTOEDIT MEMBER `memName` ALREADY EXISTS IN `lib`

Explanation: The facility tried to create a new member in the AutoEdit library, but a member with the specified name already exists in the library.

The AutoEdit member is not created and the plan is not ordered by Control-M.

Corrective Action: Check the AutoEdit library.

CTMB77I PLAN `planid` HAS BEEN PLACED ON ACTIVE JOBS FILE

Explanation: This informative message indicates that the plan was ordered by Control-M.

Corrective Action: No action is required.

CTMB78E INDEX TABLE NOT FOUND. EXECUTE CTMFETCH BEFORE CTMEXEC

Explanation: The facility cannot find the Index Table in the Daily library that is created during the FETCH phase. The Index Table, which is created during the FETCH phase, contains information on all the Daily Plans that were fetched for that day.

The EXEC is not performed.

Corrective Action: Perform the FETCH again, and then execute CTMEXEC.

CTMB79S INTERNAL ERROR - PLAN `planid` WAS NOT FETCHED CORRECTLY

Explanation: This is an internal facility error. The FETCH phase was not completed. Due to previous errors during the FETCH, the Daily libraries do not contain all the information required to perform the EXEC.

The EXECUTE phase for the plan is terminated.

Corrective Action: Execute the FETCH for the plan again.

CTMB80I PLAN STATUS WAS CHANGED. SELECT IT AGAIN

Explanation: This information message indicates that the status of the plan was changed while the user was in the Plan Selection screen. The plan was probably executed by another user while the list of plans was displayed.

The list of plans is redisplayed.

Corrective Action: Select the plan again.

CTMB81I PLAN `planid` FETCHED TO THE DAILY LIBRARY

Explanation: This informative message indicates that the facility has successfully performed the FETCH phase for the plan.

Corrective Action: No action is required.

CTMB83E BAD RC FROM CTMMEM. COMPRESS THE SCHEDULING LIBRARY

Explanation: The facility received a non-zero return code when trying to read or update the Scheduling Table. The CTMMEM program returned a non-zero return code when the facility accessed the Scheduling library. The Daily Scheduling library may need to be compressed.

The FETCH phase is not completed.

Corrective Action: Compress the Daily Scheduling library, and perform the FETCH again.

CTMB84E MASTER PLAN `planid` NOT FOUND IN LIBRARY `lib`

Explanation: The facility cannot find the Master Plan in the Master Plan library. During the FETCH phase, the facility copies the Master Plan to the Daily library, but the Master Plan does not exist in the Master Plan library.

The FETCH phase is not completed.

Corrective Action: Create the Master Plan, or correct the name of the Master Plan or library.

CTMB85E DAILY SCHEDULING TABLE DOES NOT CONTAIN JOBS

Explanation: No jobs in this Scheduling Table are scheduled to be run today, according to their scheduling definitions. Therefore, there are no parameters in this plan that require prompting.

The Daily Scheduling Table is not created.

Corrective Action: Check whether or not jobs from this plan should have been fetched today.

CTMB86I ALLOCATING `lib` AS A NEW DAILY LIBRARY

Explanation: This informative message indicates that the facility is allocating a new Daily library. The first time, on a given day, that a user tries to perform a FETCH, the library against which the FETCH is performed is allocated as the Daily library for that day.

Corrective Action: No action is required.

CTMB87E PLEASE SPECIFY "YES" TO OVERRIDE THE DAILY PLAN, OR USE SUFFIX

Explanation: A Daily Plan with the same name was already fetched. Each Daily Plan must have a unique name in the Daily library. If a plan with the same name already exists in the Daily library, override the existing plan, or use a suffix to create a new plan.

The FETCH is not performed.

Corrective Action: Specify YES to override the plan or use a suffix to create a new Daily Plan.

CTMB93E PLAN `planid` NOT FOUND IN LIBRARY `lib`

Explanation: The facility cannot find the plan in the library. The plan should have been created earlier.

Corrective Action: Check to see if there is a physical problem with the library.

CTMB94E PLAN IS BEING UPDATED. TRY AGAIN LATER

Explanation: The plan is probably in use by another user. A plan can be updated by only one user at a time. A second user trying to update the same plan receives this message.

The plan is not displayed.

Corrective Action: Try again later.

CTMB95E PROMPTING MESSAGE IS REQUIRED WHEN SPECIFYING PROMPT IND=Y

Explanation: The user set PROMPT IND to Y, but the MESSAGE field is empty.

Setting PROMPT IND to Y means that the user will be prompted for a value for this parameter during the EXEC phase. In such a case, a prompting message must be displayed at the time the EXEC is performed.

The parameter is not accepted.

Corrective Action: Enter the text of the message, or set PROMPT IND to N.

CTMB96E DEFAULT VALUE IS REQUIRED WHEN SPECIFYING PROMPT IND=N

Explanation: PROMPT IND was set to N, but the DEFAULT field is empty. Setting PROMPT IND to N assigns the value of this parameter in the Master Plan, and prevents it from being modified during the EXEC phase. In this case, the value must be supplied.

Corrective Action: Enter the default value, or set PROMPT IND to Y.

CTMB97E OCCURRENCE NUMBER MUST BE TWO DIGITS (01, 02, 31, ETC.)

Explanation: Invalid format of the OCCUR NO. field. It should be two digits.

Corrective Action: Enter the value in correct format.

CTMBA0E PLEASE FILL IN TABLE NAME

Explanation: In the Control-M Quick Schedule Definition screen, the name of the scheduling table to be created was not entered. It is a required entry.

A prompt asks for a valid table name.

Corrective Action: Enter the name of the scheduling table to be created.

CTMBA1E SKELETON SCHEDULING TABLE `tableName` DOES NOT EXIST IN `lib`

Explanation: In the Control-M Quick Schedule Definition screen, the skeleton scheduling table tableName was not found in library lib.

A prompt requests the name of a skeleton scheduling table.

Corrective Action: Enter the name of a skeleton scheduling table that exists in library lib.

CTMBA2E GROUP NAME REQUIRED FOR THIS OPTION

Explanation: In the Control-M Quick Schedule Definition screen, the group name was not entered.

If the format of the inter-job prerequisite conditions is GROUP-FROMJOB-SUFFIX, the group name is a required entry.

A prompt asks for a group name.

Corrective Action: Enter a group name of 1 to 20 non-blank characters.

CTMBA3E PLEASE FILL IN SKELETON SCHEDULING TABLE NAME

Explanation: In the Control-M Quick Schedule Definition screen, the name of the skeleton scheduling table was not entered.

A prompt asks for the name of a skeleton scheduling table.

Corrective Action: Enter the name of the skeleton scheduling table to be used.

CTMBA4E PREREQUISITE CONDITION PREFIX REQUIRED FOR THIS OPTION

Explanation: In the Control-M Quick Schedule Definition screen, a prerequisite condition prefix was not entered. If the format of the inter-job prerequisite conditions is PREFIX-FROMJOB-TOJOB, the prefix is a required entry.

A prompt asks for a prefix.

Corrective Action: Enter a one or two character prefix.

CTMBA6E PREREQUISITE CONDITION SUFFIX REQUIRED FOR THIS OPTION

Explanation: In the Control-M Quick Schedule Definition screen, a prerequisite condition suffix was not entered. If the format of the inter-job prerequisite conditions is FROMJOB-TOJOB-SUFFIX or GROUP-FROMJOB-SUFFIX, the suffix is a required entry.

A prompt requests a suffix.

Corrective Action: Enter the suffix. For FROMJOB-TOJOB-SUFFIX, the suffix is limited to one or two characters.

CTMBA9E ONE (AND ONLY ONE) OPTION MUST BE MARKED AS "Y"

Explanation: In the Control-M Quick Schedule Definition screen, either none of the options for prerequisite condition format was marked Y, or more than one was marked Y. Only one format for the inter-job prerequisite conditions may be used to create a scheduling table.

A prompt requests entry of valid Y and N values for the three prerequisite condition format options.

Corrective Action: Ensure that one of the three choices is marked Y, and the other two choices are marked N.

CTMBAAE ITEM MUST REFERENCE A MEMBER NAME IN THIS TABLE

Explanation: In the Control-M Quick Schedule Definition Jobs List screen, an entry in the DEPENDS ON field refers to a member that was not found in the table. Entries in the DEPENDS ON field must refer only to members in the table being created. One of the following was found:

A reference was made by member name, and no entry was found in the table with that name.
A reference was made by line number, and the line number was either greater than the last line in the table, or the line referenced has a blank member name.
On the first line of the table, a minus sign (- ) was used to indicate the previous line. There is no previous line.

A prompt requests correction of the DEPENDS ON field.

Corrective Action: Correct the invalid reference, as follows:

For a reference by member name, ensure that the spelling of the member name is correct, or that the referenced member is entered into the table.
For a reference by line number, either enter a member name on the numbered line, or correct the reference so that it points to a line in the table with a non-blank member name.
Remove the minus sign (- ) reference from the first line.

CTMBABE ONLY ONE "MOVE" OR "COPY" OPERATION ALLOWED

Explanation: In the Control-M Quick Schedule Definition Jobs List screen, more than one member has Option C or Option M selected.

Each time the Enter key is pressed, only one member may be moved or copied.

A prompt requests removal of one of the duplicate M or C options.

Corrective Action: Enter the M or C option on one line only.

CTMBACE ONLY ONE "BEFORE" OR "AFTER" ALLOWED

Explanation: In the Control-M Quick Schedule Definition Jobs List screen, more than one member has Option A or Option B selected. The target of a move or copy line operation must be a specific line, indicated with the A or B option.

A prompt requests removal of one of the duplicate A or B options.

Corrective Action: Enter option A or B on one line only.

CTMBADE BEFORE/AFTER IS REQUIRED WITH MOVE/COPY

Explanation: In the Control-M Quick Schedule Definition Job List screen, a Move or Copy operation was requested, but no line was marked with either an A (after) or B (before).

A prompt requests entry of option A or B.

Corrective Action: Enter either the A or B option to define where the data is to be moved or copied, or remove the Move or Copy option.

CTMBAEE MOVE/COPY IS REQUIRED WITH BEFORE/AFTER

Explanation: In the Control-M Quick Schedule Definition Jobs List screen, a Before or After was indicated, but no Move or Copy operation was requested.

A prompt asks for specification of an M or C option.

Corrective Action: Either enter a Move or Copy option, or remove the Before or After option.

CTMBAFE PLEASE ENTER DESCRIPTION

Explanation: In the Control-M Quick Schedule Definition Jobs List screen, the Description for a member was not entered.

A prompt requests a description.

Corrective Action: Enter the member description.

CTMBB0E A MEMBER MAY NOT DEPEND ON ITSELF

Explanation: In the Control-M Quick Schedule Definition Job List screen, a member refers to itself. A reference was found that is either a job name that is identical to the member name, or a line number that is the same as the line number the member is on.

A prompt requests correction of the DEPENDS ON field.

Corrective Action: Correct the reference in error.

CTMBB1E DEPENDENCY CAN BE: MEMNAME, LINE NUMBER, "- " OR *CONDNAME

Explanation: The DEPENDS ON field in the Quick Schedule Definition Job List screen contains data in an invalid format, such as an embedded blank in a member name, or two commas with no data between them. The DEPENDS ON field may consist of any number of subfields separated by commas. Each subfield may be either:

The name of another member in the table
The number of a line on which a member is defined
A minus sign (- ), indicating the previous job in the table
An asterisk (*) followed by a prerequisite condition name

If a prerequisite condition name is used, it must be the last subfield in the DEPENDS ON area. Only one condition name is allowed per line.

A prompt requests correction of the DEPENDS ON field.

Corrective Action: Correct the invalid data in the DEPENDS ON field.

CTMBB2E MEMBER NAME MAY APPEAR ONLY ONCE IN THE TABLE

Explanation: In the Control-M Quick Schedule Definition Job List screen, a member name appears more than once. A member name in a schedule produced by the Quick Schedule Definition must appear only once in the table.

A prompt requests removal of the duplicate members.

Corrective Action: Delete the duplicate entry.

CTMBB3E LINE IS A PREREQUISITE FOR ANOTHER MEMBER - CANNOT BE DELETED

Explanation: In the Control-M Quick Schedule Definition Job List screen, option D (Delete) was entered for a member that is a prerequisite to another member. This line cannot be deleted, since this would cause the member that depends on it to refer to a member that does not exist.

A prompt requests removal of the reference to the line marked for deletion.

Corrective Action: Delete the references to the member to be deleted. Then the deletion will be accepted.

CTMBB4I TABLE `tableName` CREATED IN LIBRARY `lib`

Explanation: This information message indicates that scheduling table tableName has been built successfully and placed in library lib.

Corrective Action: No action is required.

CTMBB5W UPDATE CANCELLED BY USER

Explanation: In the Control-M Quick Schedule Definition Exit Option Window, the user entered N for the Save or Create option.

The scheduling table is not updated.

Corrective Action: No action is required.

CTMBB6I TABLE `tableName` REPLACED IN LIBRARY `lib`

Explanation: This information message indicates that a scheduling table has been successfully built and has replaced table tableName in library lib.

Corrective Action: No action is required.

CTMBB7E MEMBER IS NOT A VALID SKELETON SCHEDULING TABLE

Explanation: In the Control-M Quick Schedule Definition screen, the skeleton scheduling table specified is not a valid skeleton scheduling table, or it contains definitions for more than one job. The skeleton scheduling table must be a valid Control-M scheduling table, and must contain a definition for one and only one job.

The user is prompted to enter the name of a valid scheduling table.

Corrective Action: Either modify the skeleton scheduling table using the Control-M Online Schedule Definition - screen 2, and retry the request to use this skeleton scheduling table, or enter the name of a valid skeleton scheduling table.

CTMBB8E "S" IS THE ONLY OPTION PERMITTED

Explanation: In the End User Job Order Interface (CLIST CTMJBINT), a value other than S (select this job for submission) was specified in the OPTION field. Only S may be specified in the OPTION field, other than leaving the OPTION field blank.

Corrective Action: Ensure that the OPTION field for each job in the list either contains S or is blank, and then press Enter.

CTMBB9E DATE MUST BE IN FORMAT {MMDDYY | DDMMYY | YYMMDD}

Explanation: An invalid date was specified in the End User Job Order Interface (CLIST CTMJBINT). The format shown in the message text depends on the standard in use at the site. The specified date was not valid according to this standard.

Corrective Action: Specify a date that is valid according to the indicated site standard, and press Enter.

CTMBBAS ERROR ALLOCATING LIBRARY. PLEASE CONTACT YOUR IOA ADMINISTRATOR

Explanation: An internal error occurred while allocating the library for the End User Job Order Interface (CLIST CTMJBINT). The system was unable to allocate a required library. Possible causes are:

Control-M was not installed, or was incorrectly installed.
CLIST CTMJBINT was modified to point to a library other than the default library, and the modification is incorrect.
The library indicated by USRLIB is currently allocated to another address space with DISP set to OLD or MOD or NEW.

The CLIST is terminated without any further processing.

Corrective Action: Notify your INCONTROL administrator who, depending on the cause of the error, should perform the appropriate action, as follows:

Examine CLIST CTMJBINT. If the USRLIB parameter contains percent signs (%), there is a problem with the installation of Control-M. Install Control-M correctly.
Ensure that the USRLIB parameter points to a cataloged data set.
Resolve any outstanding allocation conflicts.

CTMBBBS ERROR OPENING LIBRARY. PLEASE CONTACT YOUR IOA ADMINISTRATOR

Explanation: An internal error occurred while opening the library for the End User Job Order Interface (CLIST CTMJBINT). The system cannot open the library indicated in the USRLIB parameter in CLIST CTMJBINT.

The CLIST is terminated without any further processing.

Corrective Action: Notify your IOA administrator. The IOA administrator should determine why the system was not able to open the library. For example, ensure that the library exists, and resides on the volume to which the MVS catalog points.

CTMBBCE THIS FUNCTION HAS NOT BEEN PREPARED FOR USE AT YOUR INSTALLATION

Explanation: The user attempted to use the Control-M End User Job Order Interface (CLIST CTMJBINT), but the End User Job Order Interface has not been implemented at your site.

The CLIST is terminated without any further processing.

Corrective Action: Request that the INCONTROL administrator implement the End User Job Order Interface at your site. Implementation instructions are in the Control-M chapter of the INCONTROL for z/OS Administrator Guide.

CTMBBDE NO JOB LIST DEFINED FOR `usr`. CONTACT YOUR IOA ADMINISTRATOR

Explanation: A user (usr) attempted to use the Control-M End User Job Order Interface (CLIST CTMJBINT), but no job list is defined for that user.

The CLIST is terminated without any further processing.

Corrective Action: Notify your IOA administrator that you are unable to use the End User Job Order Interface. Implementation instructions for the End User Job Order Interface are provided in the chapter that describes JCL and the AutoEdit facility in the Control-M for z/OS User Guide.

CTMBBEE RENAME/DELETE DUPLICATE JOB `jobName` IN SCHEDULING TABLE `tableName`

Explanation: The user requested the M6 Control-M ISPF utility or executed the CLIST CTMJOBRQ command. However, the tableName Control-M Job Scheduling table contains job names that are duplicates.

A list of the job names in the tableName Job Scheduling table is displayed, but this list contains only one entry for each set of duplicated job names.

Corrective Action: Ask your INCONTROL administrator to delete or rename the jobs in the tableName scheduling table that have names that duplicate other job names.

Messages CTMC00 through CTMCxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMC30I Another CMEM/CTO IS ALREADY MONITORING THIS JOB - REQUEST FROM `subsystem-name` IS IGNORED. USED BY `subsystem-name`

Explanation: A job’s ON DSNEVENT and ON STEP events can only be handled by one CMEM or Control-O.

A CMEM or Control-O subsystem is attempting to monitor an ON DSNEVENT or an ON STEP event but is unable to do so because the address space is already monitored by a different CMEM or Control-O subsystem.

Corrective Action: If another subsystem needs to intercept an ON DSNEVENT or an ON STEP event, modify the rule filters of the other subsystem so that the job name is not matched.

CTMC31I `monitor` STARTED MONITORING `jobname` FOR DATA SET AND STEPEND EVENTS

Explanation: The Control-O monitor is currently monitoring the job for ON DSNEVENT and ON STEPEND events.

Corrective Action: No action is required.

CTMC41E JOB TERMINATED BY {CMEM | CONTROL-O} DUE TO STOPJOB REQUEST for "`disposition`" ON:

Explanation: The job was stopped due to a STOPJOB request for a DSNEVENT event. This message is followed by message CTMC42E, which contains additional details about the event.

In this message, disposition is the dataset disposition that triggered the event. Valid values are:

NOT CATLGD x - x is the number from the NOT CATALGD message
DISP= x. Valid values for x are:
C - cataloged
D - deleted
R - retained
S - scratched
U - uncataloged
K - kept

The job is stopped after the current step. All subsequent steps (including steps having COND set to EVEN/ONLY) will not be executed.

Corrective Action: No action is required.

CTMC42E STEP=`stepName` PROCSTEP=`procStep` DSNAME=`dsn`

Explanation: This message follows message CTMC41E when a job is stopped due to an NCT2 (NOT CATLGD 2) event. The NCT2 event occurred for the dsn data set in the stepName step in the procStep procedure step.

Corrective Action: No action is required.

CTMC43E ERROR IN PROCESSING A CMEM EVENT - CODE=`code`. SOME EVENTS MIGHT BE LOST

Explanation: An internal error occurred when CMEM or Control-O tried to process a CMEM event. This message is followed by message CTMC44E with the event that caused the error.

The event is ignored.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMC44E MESSAGE: `text`

Explanation: This message follows message CTMC43E and CTMC4AE when an internal error occurs during event processing.

Corrective Action: No action is required.

CTMC45W CMEM PROCESSING STOPPED AT STEP=`stepName` PROCSTEP=`procStep` DUE TO SUBSYSTEM DEACTIVATION

Explanation: CMEM subsystem functions or Control-O subsystem functions were stopped. Some or all events for the specified stepName procstep might not be processed because the subsystem was stopped.

Corrective Action: Activate the subsystem functions (CMEM or Control-O).

CTMC46I CMEM PROCESSING RESUMED AT STEP=`stepName` PROCSTEP=`procStep`

Explanation: This information message indicates that CMEM or Control-O subsystem functions were reactivated. This message appears when a CMEM subsystem function or Control-O was stopped and restarted during job execution. Message CTMC45W was issued for this job. Events that occurred between these two messages are ignored.

CMEM events for this job from stepName procstep are processed.

Corrective Action: No action is required.

CTMC47E CMEM PROCESSING STOPPED FOR THIS JOB DUE TO AN INTERNAL ABEND:

Explanation: An abend occurred during processing of CMEM events for this job. This message is followed by message CTMC48E with details about the abend.

CMEM event processing stops for this job and a dump is written to a system dump data set.

Corrective Action: Format and save the dump, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMC48E ABEND-CODE=`abCode` MODULE=`modName` LOAD-POINT=`modAddr` OFFSET=`offset`

Explanation: This message follows message CTMC47E when an internal abend occurs in CMEM event processing. It contains details about the abend: subsystem name, abending module name, abending load module load point and offset of the abending instruction in the module.

A system dump is produced. The title of the dump contains this message.

Corrective Action: No action is required.

CTMC49E CMEM PROCESSING STOPPED FOR THIS JOB DUE TO AN INTERNAL ERROR. ERROR CODE = `code`

Explanation: An internal error occurred when CMEM or Control-O tried to process a CMEM event. This message is followed by message CTMC44E, which specifies the event that caused the error.

CMEM event processing stops for this job.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMC4AW CONTROL-O 'ON SYSOUT' PROCESSING STOPPED FOR DD `ddName` DUE TO SUBSYSTEM DEACTIVATION

Explanation: Control-O SYSOUT processing for the SYSOUT allocated to the ddName DD statement was stopped.

Some or all events for this SYSOUT might not be processed because Control-O was stopped.

Corrective Action: Activate Control-O.

CTMC4BI CONTROL-O 'ON SYSOUT' PROCESSING RESUMED FOR DD `ddName`

Explanation: This information message indicates that SYSOUT processing for SYSOUT allocated to the ddName DD statement was reactivated. This message appears when Control-O was stopped and restarted during application SYSOUT processing. Message CTMC4AW was issued for this SYSOUT. Events that occurred between these two messages are ignored.

SYSOUT events for this SYSOUT are processed.

Corrective Action: No action is required.

CTMC4CE CONTROL-O 'ON SYSOUT' PROCESSING STOPPED FOR DD `ddName` DUE TO UNSUPPORTED FALLBACK

Explanation: Control-O fallback to a lower version was performed while processing a SYSOUT allocated to the ddName DD statement. Fallback is not allowed in the following cases:

Fallback to a Control-O version earlier than 6.0.15 or 6.1.15.
Fallback to Control-O version 6.0. xx or 6.1. xx for SYSOUT processed in key other than 8.

Control-O processing stops for the SYSOUT allocated to the ddName DD statement.

Corrective Action: Restart the job to resume SYSOUT processing.

CTMC4DE CMEM PROCESSING STOPPED FOR THIS JOB DUE TO UNSUPPORTED FALLBACK

Explanation: Control-O or CMEM fallback to an earlier version was performed while processing DSNEVENT or STEP events. Fallback is not allowed to Control-O or CMEM versions earlier than 6.0.15 or 6.1.15.

Control-O or CMEM processing stops for the job.

Corrective Action: Restart the job to resume DSNEVENT and STEP events processing.

CTMC4EE SYSOUT PROCESSING STOPPED DUE TO KEY MISMATCH

Explanation: Writing to the SYSOUT file is controlled by a storage key that differs from the one used for the first SYSOUT write. Control-O cannot handle such writes and stops SYSOUT monitoring.

Corrective Action: No action is required.

CTMC50E INSUFFICIENT STORAGE FOR CMEM PROCESSING

Explanation: Highlighted, unrollable message.

Insufficient storage for CMEM processing initialization in the Control-M monitor.

The Control-M monitor stops processing CMEM/Control-O requests.

Corrective Action: Increase the REGION size specified for the Control-M monitor.

CTMC50W CONTROL-M MONITOR CMEM FACILITY IS NOT INSTALLED

Explanation: Control-M has determined that the CMEM facility is not installed.

Communication between CMEM or the Control-O monitor and Control-M is not established, but the Control-M monitor continues processing.

Corrective Action: No action is required.

CTMC51E INSUFFICIENT STORAGE FOR TABLE `tableName` FROM `lib`

Explanation: Insufficient storage for loading table tableName into storage.

This message is followed by the WKJA59E message, which contains more details about the error.

Job order fails. No additional action taken.

Corrective Action: Increase the REGION size specified for the Control-M monitor; or define a smaller table if possible (for example, if only one job is ordered from the table). For further actions, see the WKJA59E message.

CTMC52E DATASET IS NOT A LIBRARY, DSN=`dsn`

Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is not a partitioned data set.

This message is followed by the WKJA59E or WKJC39E message, which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Specify the name of a partitioned data set containing one or more valid scheduling tables.

CTMC53E DATASET IN USE, DSN=`dsn`

Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is currently used by another job.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: Determine which job has allocated the data set with disposition OLD and resolve the conflict.

CTMC54E DATASET IS NOT CATALOGED, DSN=`dsn`

Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is not cataloged.

This message is followed by additional messages which identify the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Make sure that the SCHLIB library specified in the CMEM table entry refers to a cataloged data set.

CTMC55E DYNAMIC ALLOCATION ERROR, DSN=`dsn`

Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a dynamic allocation error.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: Record the problem, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMC56E M2S FILE IS FOR QNAME `qName`. IT DOES NOT MATCH IOA QNAME `qName` DSN=`dsn`

Explanation: Control-M could not allocate the monitor to the Monitor-to-Subsystem (M2S) file of another IOA environment.

During initialization the Control-M monitor compares the QNAME in the IOA environment with the QNAME in the M2S file. They should match.

Message CTM441E is issued.

Corrective Action: Check the IOACPRM member and do one of the following:

If it points to the wrong file, correct the name and start a new monitor.
If there is no problem in the IOACPRM member, the M2S file was created in a different IOA environment. Delete the file and create a new M2S file using the correct IOA environment.

CTMC56S PREVIOUS FORMAT OF ACTIVE JOBS FILE ABENDED

Explanation: The source Active Jobs file is either currently being formatted, or an abend occurred during the previous formatting.

The Active Jobs file is formatted daily as part of the New Day process. It may also be formatted by the CTMCAJF utility.

Copy program terminates with a condition code of 08.

Corrective Action: If the Active Jobs file is currently being formatted, wait until the formatting is completed. If the previous formatting abended, determine the reason. Resubmit the copy job only after successful formatting.

CTMC57E S2M FILE IS FOR SMFID `smfid` QNAME `qName`. IT DOES NOT MATCH IOA QNAME `qName` DSN=`dsn`

Explanation: The Control-M monitor could not allocate the subsystem to the Subsystem-to-Monitor (S2M) file of another IOA environment.

During initialization the Control-M monitor compares the qname in the IOA environment with the qname in the S2M file. They should match.

Message CTM441E is issued.

Corrective Action: Check the IOACPRM member and do one of the following:

If it points to the wrong file, correct the name and start a new monitor.
If there is no problem in the IOACPRM member, the S2M file was created in a different IOA environment. Delete the file and create a new S2M file using the correct IOA environment.

CTMC57S TARGET ACTIVE JOBS FILE IS NOT A NEWLY FORMATTED FILE

Explanation: The target Active Jobs file should not be used before it is formatted by the FORMCKP procedure.

Copy program terminates with a condition code of 08.

Corrective Action: Format the Active Jobs file using the FORMCKP procedure.

CTMC58I M2S FILE FOR IOA QNAME `qName`. DSN=`dsn`

Explanation: This information message identifies the Monitor-to-Subsystem (M2S) file that the Control-M monitor allocated for communication with the Control-O or the CMEM monitor.

qName is defined in the M2S file with the data set name dsn.

Corrective Action: No action is required.

CTMC58S TARGET ACTIVE JOBS FILE IS NOT LARGE ENOUGH

Explanation: Target Active Jobs file is not large enough to contain the source Active Jobs file.

Copy program terminates with a condition code of 08.

Corrective Action: Reallocate and reformat the new Active Jobs file.

CTMC59I `num` JOBS WERE DELETED FROM THE ACTIVE JOBS FILE

Explanation:This is one of two messages with the same ID, but different text.

This information message displays the number of jobs deleted from the Active Jobs file during a run of the CLEANUP function of the CTMCAJF utility. The CLEANUP function of the CTMCAJF utility deletes jobs from the Active Jobs file according to the same criteria as the New Day procedure.

Corrective Action: No action is required.

CTMC59I S2M FILE FOR SMFID `smfid` QNAME `qName` DSN=`dsn`

Explanation:This is one of two messages with the same ID, but different text.

This information message identifies the Subsystem-to-Monitor (S2M) file that the Control-M monitor allocated for communication with the Control-O or the CMEM monitor.

qName is defined in the S2M file with the dsn DSN.

Corrective Action: No action is required.

CTMC5AE SMFID `smfid` NOT FOUND IN M2S DSN=`dsn`

Explanation: The SMFID is not in the Monitor-to-Subsystem (M2S) file.

During initialization the Control-M monitor checks that every SMFID required for CMEM functions is defined in the M2S file.

Control-O issues the CTM441E message and CMEM functions become inactive.

Corrective Action: Add the missing SMFID to the M2S file, and restart the Control-M monitor.

For more information on adding the SMFID to the M2S file, see the section on reformatting communication files for only one SMFID in the INCONTROL for z/OS Installation Guide.

CTMC68E VALUE OF CNDREC# PARAMETER IN IOAPARM IS NOT EQUAL TO ACTUAL FILE SIZE

Explanation: The CNDREC# parameter in the IOAPARM member has been changed, but the IOA Conditions file has not been rebuilt. A difference between the length of the IOA Conditions file and the CNDREC# value specified in the IOAPARM member of the PARM library was detected.

This is usually caused by using the IOAPARM member for the wrong monitor.

The Control-M monitor shuts down.

Corrective Action: Correct the problem and restart the monitor.

CTMC69E UPDATE OF QUANTITATIVE RESOURCE `resourceName` FAILED

Explanation: The action specified in a Control-O DO RESOURCE statement failed, because it would have produced either a negative quantity or a quantity greater than the maximum of 9999. Therefore it was rejected.

The system ignores the illegal statement and continues processing.

Corrective Action: Check and correct, if necessary, the definition of the quantitative resource to be updated and/or the rule defining how to update it.

CTMC69S EXECUTION STOPS DUE TO CONTROL-M MONITOR NOT RUNNING

Explanation: The CLEANUP function of the CTMCAJF utility stops because the Control-M monitor is not running. The CLEANUP function of the CTMCAJF utility should run only when the Control-M monitor is running.

The CTMCAJF utility terminates.

Corrective Action: BMC recommends the following:

If Control-M is down, run the CTMCAJF utility with the COMPRESS function.
If Control-M is up, run the CTMCAJF utility with the CLEANUP function.

CTMC70E PLEASE FILL IN STEPRANGE NAME

Explanation: When you define a STEP RANGE by specifying either FROMSTEP or TOSTEP, the STEP RANGE must have a name.

Corrective Action: Fill in the STEP RANGE field.

CTMC70I PROBABLE LOGMODE DEFINITIONS ERROR

Explanation: This information message indicates that an IOA Gateway attempted to establish a connection with another IOA Gateway. However, the LOGMODE definitions of the partners do not match.

When IOA Gateways try to establish a connection with each other, both send LOGMODE during the bind process. If the LOGMODEs do not match, the connections fail. Message COMG98W, COMG90E or COMG95E precedes this message and explains the error.

The connection between the IOA Gateways fails.

Corrective Action: Check the LOGMODE definitions for each partner in your SYS1.VTAMLIB. Make sure that they are defined according to the recommendations in the IOA installation chapter of the INCONTROL for z/OS Installation Guide.

CTMC70S ACTIVE JOBS FILE (CKP) SIZE - PARM TABLE MISMATCH

Explanation: The value for the CKPSIZE parameter being used by the CTMCAJF utility is different from the CKPSIZE value used to format the Active Jobs file. The parameter is defined in the CTMPARM member in the IOA PARM library. The values used must be identical.

The CTMCAJF utility terminates. The requested action is not performed.

Corrective Action: Ask the INCONTROL administrator to determine the cause of the discrepancy in the CKPSIZE value and correct the error.

CTMC71E PLEASE FILL IN FROMSTEP OR TOSTEP

Explanation: You must fill in either FROMSTEP or TOSTEP or both. To create a STEP RANGE, you must specify either FROMSTEP or TOSTEP or both. STEP RANGE without additional parameters has no meaning.

Corrective Action: Add FROMSTEP or TOSTEP or both.

CTMC71I PROBABLE ALLOCATION FAILURE NO RETRY

Explanation: This information message indicates that when an IOA Gateway attempted to establish a connection with another IOA Gateway, a local IOA gateway made a VTAM LU6.2 allocation request. However, the request failed.

A local IOA Gateway attempted to allocate a session with a partner gateway. The attempt failed. Message COMG98W, COMG90E or COMG95E precedes this message and explains the failure.

Corrective Action: Check that the partner gateway LU is active in VTAM, and that it is defined as explained in IOAGATE installation in the INCONTROL for z/OS Installation Guide.

CTMC72E THIS STEPRANGE IS NOT DEFINED FOR THIS JOB

Explanation: There is a reference to a STEP RANGE that is not defined. ONPGMSTEP refers to a STEPRANGE (*XXXXXXX) that is not defined for this job.

Corrective Action: Specify a STEP RANGE that is defined for this job.

CTMC72I PROBABLE ALLOCATION FAILURE - RETRY

Explanation: This information message indicates that a local IOA Gateway attempted to allocate a partner gateway session. The attempt failed.

The failed request was a VTAM LU6.2 allocation request. Messages COMG98W, COMG90E or COMG95E precede this message and explain the failure.

Connection will be reattempted in 1 minute.

Corrective Action: Make sure that Logical Unit (LU) of the partner gateway is active in VTAM and that it is defined as explained in the IOA installation chapter in the INCONTROL for z/OS Installation Guide.

CTMC73E OPERANDS ">","<", "N" ARE INVALID FOR THIS TYPE OF CODE

Explanation: You cannot specify this operand for this type of code. Some of these operands are not allowed for various types of codes. For example, >Sxxx, <Sxxx are not allowed.

Corrective Action: Use only the valid operands for this type of code.

CTMC73I PROBABLE MISMATCH IN VTAM DEFINITIONS

Explanation: This information message indicates that an IOA Gateway attempted to establish a connection with another IOA Gateway. However, IOA Gateway detected a mismatch in the IOA Gateway LU definitions. The VTAM LU was defined incorrectly.

Messages COMG98W, COMG90E and COMG95E precede this message, and explain the error.

The connection to the partner LU fails, and the IOA Gateway terminates.

Corrective Action: Define the IOA Gateway VTAM LU as explained in the IOA installation chapter of the INCONTROL for z/OS Installation Guide.

CTMC74E CONFLICT BETWEEN "OK", "NOTOK" AND "EXERR" CODES

Explanation: The combination of status codes is not valid. Some combinations are not acceptable. For example, EXERR and NOTOK, because the NOTOK code already covers the EXERR code.

Corrective Action: Check and correct the specification in the CODES field.

CTMC76E SEARCH COUNTER SHOULD BE 00000-32767 OR 99999

Explanation: Invalid SEARCH COUNTER value. The SEARCH COUNTER counts the number of times Control-M looks for a job. When this value equals the maximum number of searches allowed defined by the INCONTROL administrator, the job status changes to DISAPPEARED. You can change the value of the counter manually.

Valid search values:

00000 through 32767
99999 - This value causes a DISAPPEARED status, and stops further searches.

Corrective Action: Correct the SEARCH COUNTER parameter.

CTMC77E "NCT2-PREVENT" IS NOT SUPPORTED FOR A STARTED TASK

Explanation: PREVENT-NCT2 was requested for a started task (STC). PREVENT-NCT2 handling may not be requested for a started task (STC).

Corrective Action: Change the value of PREVENT-NCT2 to N or leave the value blank, or change the task type.

CTMC78I JOB DOCUMENTATION NOT FOUND

Explanation: This information message indicates that a user entered command DOC in the Zoom screen but the job has no documentation.

Corrective Action: No action is required.

CTMC79E INSUFFICIENT STORAGE TO SAVE DOCUMENTATION

Explanation: Insufficient storage to save the documentation lines into the library or member specified in the DOCLIB or DOCMEM fields of the Job Scheduling Definition screen.

Corrective Action: The user can either delete the additional documentation lines and save the Job Scheduling Definition, or cancel the Job Scheduling Definition changes. The user should then log on again using a larger SIZE parameter (under TSO).

CTMC80E INTERNAL ERROR - INVALID INPUT PARAMETERS FOR CTMDOC

Explanation: The Online facility called routine CTMDOC with an invalid parameter list when the DOC command was entered in either the Job Scheduling Definition screen or the Zoom screen.

Corrective Action: Notify the INCONTROL administrator.

CTMC81E INTERNAL ERROR - INVALID FUNCTION FOR CTMDOC

Explanation: The Online facility called routine CTMDOC with an invalid function when the DOC command was entered in the Job Scheduling Definition screen or in the Zoom screen.

Corrective Action: Notify the local INCONTROL administrator.

CTMC82E INTERNAL ERROR - INVALID RETURN CODE FROM CTMDOC

Explanation: The Online facility received an invalid return code from routine CTMDOC.

Corrective Action: Notify the INCONTROL administrator.

CTMC83E CHARACTERS "*" AND "?" ARE NOT ALLOWED FOR DOC MEMBER NAME

Explanation: User entered the * character, or the ? character in the DOCMEM field in the Job Scheduling Definition screen (or in the Zoom screen). These are invalid characters for this field.

Corrective Action: Enter a valid value in the DOCMEM field.

CTMC84E ONLY 8 PERIODIC REQUESTS ARE ALLOWED

Explanation: More than eight requests for a periodic calendar were specified in the DAYS field in the Job Scheduling Definition screen. Only eight requests for a periodic calendar may be kept in a job scheduling definition.

Corrective Action: Decrease the number of periodic calendar requests.

CTMC85E INVALID BOOLEAN EXPRESSION: UNPAIRED PARENTHESES

Explanation: The Boolean expression that is specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains unpaired parentheses.

Corrective Action: Correct the Boolean expression in the IN field.

CTMC86E INVALID BOOLEAN EXPRESSION: EMBEDDED PARENTHESES

Explanation: The Boolean expression that is specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains parentheses within a condition name. IN conditions may be specified as a Boolean expression with parentheses. Use the parentheses only before or after the condition name.

Corrective Action: Correct the Boolean expression in the IN field.

CTMC87E DUPLICATE PIPE NAME IS NOT ALLOWED

Explanation: The job scheduling definition contains duplicate entries with the same pipe name. The names of the pipes in a job must be unique.

The scheduling definition cannot be saved and the job cannot be ordered.

Corrective Action: Change one or more pipe names so that all pipes in the job have a unique name.

CTMC88E NESTING IS NOT ALLOWED FOR BOOLEAN EXPRESSION

Explanation: The Boolean expression that is specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains two or more open or close parentheses in succession. Control-M Online facility does not support nesting for a Boolean expression in the IN field.

Corrective Action: Correct the Boolean expression in the IN field.

CTMC89E NOT MORE THAN 20 CONDITIONS CAN BE CONTAINED IN BOOLEAN EXPRESSION

Explanation: A Boolean expression in the Job Scheduling Definition screen or Job Zoom screen contains more than 20 conditions.

The job scheduling definition cannot be saved.

Corrective Action: Modify the Boolean expression so that it contains not more than 20 conditions.

CTMC8AE REQUESTED RBC DOES NOT EXIST IN THE SMART TABLE DEFINITION OR THE MAXIMUM NUMBER (5000) HAS BEEN EXCEEDED

Explanation: This message is displayed in the following cases:

A rule-based calendar was specified in the job scheduling definition, but it was not defined in the SMART Table Entity definition. A rule-based calendar for a group of jobs must be defined in the SMART Table Entity definition.
A user attempted to define more than 5,000 rule-based calendar definitions in the definition of a SMART Table Entity

Corrective Action: Do one of the following, as appropriate:

Either replace the rule-based calendar with one defined in the SMART Table Entity definition, or define the requested rule-based calendar in the SMART Table Entity definition. To display a list of the defined rule-based calendars, exit the job scheduling definition, and enter the SMART Table Entity definition.
Delete rule-based calendar definitions from the SMART Table Entity definition until the number is less than 5,000.

CTMC8BE "DAYS" AND "GENERATIONS" ARE MUTUALLY EXCLUSIVE

Explanation: There are retention values for both # OF DAYS TO KEEP and # OF GENERATIONS TO KEEP, but these fields are mutually exclusive.

The request is ignored.

Corrective Action: Delete one of the specified values.

CTMC8CE MAXIMUM 255 PIPES IN COLLECTION IS ALLOWED

Explanation: The job has more than 255 pipe definitions in the scheduling table. This message may be issued when editing a job definition with more than 255 pipe definitions. The maximum number of pipes per collection is 255.

The scheduling definition is not saved, and the job is not ordered.

Corrective Action: Reduce the number of pipe entries in the job scheduling definition.

CTMC8EE VALUE 'Y' VALID ONLY WHEN JOB STATUS 'WAIT SCHEDULE'

Explanation: An attempt was made to change the value of the data in a job's WAIT CONFIRMATION field, via screen 3.Z, when the job was not in WAIT SCHEDULE state.

Corrective Action: No action is required.

CTMC8FE A SLASH ('/') IS AN NOT ALLOWED

Explanation: In order to be compatible with the nested containers feature in Control-M/Enterprise Manager, a slash (/) is not allowed in this field.

Corrective Action: Correct the field contents.

CTMC90E INVALID POSITION OF THE BOOLEAN OPERATOR "I"

Explanation: The Boolean expression specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains the operator I in an invalid position. The Boolean operator I may be specified only in the first position of the condition name, or immediately after the open parentheses.

Corrective Action: Correct the Boolean expression in the IN field.

CTMC91E REMOTE FORCEJOB CANCELLED - NOT ENOUGH MEMORY

Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to insufficient storage allocated to the Control-M monitor.

Corrective Action: Increase the region size of the Control-M monitor.

CTMC92E REMOTE FORCEJOB CANCELLED – INTERNAL ERROR

Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to an internal error.

Corrective Action: Contact BMC support.

CTMC93E REMOTE FORCEJOB CANCELLED - INVALID RESPONSE FROM CTWWMF

Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to a problem in accessing the DAM2F file.

Corrective Action: Verify that DAM2F is allocated to a valid file. If it is, contact BMC support.

CTMC94E INVALID VALUE ENTERED. ENTER ONLY `text`

Explanation: Invalid data was specified.

Corrective Action: Change the entry in the field with the help of the text displayed in the message, or with the assistance of the HELP command.

CTMC95I JOB NOT HELD - CHANGES WILL NOT BE SAVED

Explanation: A user entered the Zoom screen (3.Z) of a job from the Control-M Active Environment screen, but the status of the job was not HELD. In such a case, any changes made in the Zoom screen cannot be saved on exit.

Changes made to the current job in the Zoom screen are ignored.

Corrective Action: To change the job, do the following:

Exit from the Zoom screen.
Change the status of the job to HELD.
Redisplay the job in the Zoom screen.
Make the required changes.

CTMC97I REMOTE FORCE JOB REQUEST ISSUED - UNIQUE ID `unique_id`

Explanation: Control-M successfully performed a job’s DO REMFORCE statement. The unique ID can be used to track the remote force request on the remote Control-M.

Corrective Action: No action is required.

CTMC98E VALUES "GENERAL" AND "USER=" ARE INVALID

Explanation: GENERAL or USER was specified in the OVERLIB field in the Job Scheduling Definition screen or in the Job Zoom screen. GENERAL and USER are not permitted in the OVERLIB field.

Corrective Action: Specify a valid value in the OVERLIB field.

CTMC99E PLEASE FILL IN THE REQUIRED FIELD `text`

Explanation: Missing APPLICATION or GROUP name in the Job Scheduling Definition screen or in the Job Zoom screen. The APPLICATION and GROUP fields may be designated as mandatory in the IOA profile. By default they are optional. See the chapter that discusses online facilities in the Control-M for z/OS User Guide for a description of these fields.

Corrective Action: Fill in the requested field with the help of the text in the message, or correct the appropriate variable in the IOA profile.

CTMC9AE VALID OPTIONS ARE "OK" OR "NOTOK" ONLY

Explanation: A value other than OK or NOTOK is specified in a field than can only take either one of these values.

Corrective Action: Specify either OK or NOTOK.

CTMC9BE INVALID ACTION FOR SMART TABLE ENTRY

Explanation: The user entered an action that is invalid for SMART tables.

Corrective Action: Enter an action that is valid for SMART tables.

CTMC9CE "OK" AND "NOTOK" ARE MUTUALLY EXCLUSIVE DO ACTIONS

Explanation: Both OK and NOTOK were entered as a DO action for a SMART table. OK and NOTOK are mutually exclusive DO actions.

Corrective Action: Delete either OK or NOTOK.

CTMC9DE PLEASE FILL IN "DO" ACTION

Explanation: No DO action after an ON PGMSTEP/ON GROUP-END line.

Corrective Action: Fill in at least one DO action.

CTMC9EW ENTRY IN USE BY ANOTHER USER. "BROWSE" FORCED

Explanation: There was an attempt to zoom a job that is currently being zoomed by another user.

The Zoom screen is displayed in the forced browse mode.

Corrective Action: If the job data must be updated, continue trying to zoom the job in Edit mode, until it is released by the other user.

CTMC9FE "SAVE" IS NOT VALID IN "BROWSE" MODE

Explanation: The SAVE was entered in the Zoom screen in the browse mode.

The job is not saved.

Corrective Action: Exit the screen without trying to save the changes.

Messages CTMD00 through CTMDxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMD00I BROWSE MODE IS FORCED FOR DOC LINES

Explanation: This information message indicates that the requested job documentation is displayed in browse mode. Display of job documentation was requested using the DOC command. Normally, when requested, documentation can be edited. However documentation displayed in Browse mode cannot be updated. The documentation is in Browse mode for one of the following reasons:

The data set that contains the job documentation is not an MVS library (PDS).
One of the documentation lines has non-blank characters after column 71, and has therefore been truncated.
One of the documentation lines contains an unprintable character.

Documentation lines are displayed in browse mode.

Corrective Action: No action is required.

CTMD01E Cannot find host `host` in dsHosts table

Explanation: The host host name, referred to by in the –host input parameter, is not defined in the DSHOSTS member, located in the Control-M PARM library.

Corrective Action: Check that that the value of –host parameter is correct, or add a definition of the host host name to DSHOSTS member.

CTMD02E User `mf user id` does not have permission to work with host `host` as user `DS user id`

Explanation: The User mf user id does not have permission to work with host host as user DS user id.

Corrective Action: Ensure that the User mf user id has permission to work with host host as user DS user id.

CTMD03E Cannot get ip of host. Host name = `host`. Error code = `codeError message`

Explanation: The error occurs when the utility tries to get the IP address of the host host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Perform the appropriate action, based on the error code and the error message.

CTMD04E Parameter `param` is not defined.

Explanation: Parameter param is mandatory, but not defined in the input stream of the utility.

Corrective Action:Add the param parameter to the input and rerun the utility.

CTMD05E `request` request ended with error. Error code = `codeError message`

Explanation: Request request ended with an error. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Refer to the Control-M documentation for details.

Corrective Action:Add the param parameter to the input and rerun the utility.

CTMD06E Error creating file '`file name`’ on the remote host. Error code = `code Error message`

Explanation: The utility cannot create the file name file on the remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Refer to the Control-M documentation for details.

CTMD07E Error opening file '`file name`’. Error code = `codeError message`

Explanation: The utility cannot open the file name file. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Perform the appropriate action, based on the error code and the error message.

CTMD08E `build_upload`: Size of data to upload is too large - `number of bytes`

Explanation: Internal error.

Corrective Action:Perform the following:

Update the EXEC statement in the problematic job as follows: EXEC PGM=CTMDSRN,PARM='7'
Rerun the utility.
Call BMC Customer Support and send the full output of the job to support.

CTMD09E Error creating socket. Error code = `codeError message`

Explanation: The error occurred when the utility tried to create a socket. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Perform the appropriate action, based on the error code and the error message.

CTMD10E Cannot connect to remote host. Error code = `codeError message`

Explanation: The error occurred when the utility tried to connect to a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Perform the appropriate action, based on the error code and the error message.

CTMD11E Data transmission failure. Error code = `codeError message`

Explanation: The error occurred when the utility tried to send data to a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Perform the appropriate action, based on the error code and the error message.

CTMD12E %s request to upload file '`file name`' ended with error. Error code = `codeError message`

Explanation: The error occurred when the utility tried to upload the file name file to a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Refer to the Control-M documentation for details. Perform the appropriate action, based on the error code and the error message.

CTMD13E Error deleting file '`file name`' on the remote host. Error code = `codeError message`

Explanation: The error occurred when the utility tried to delete the file name file on a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action:Refer to the Control-M documentation for details. Perform the appropriate action, based on the error code and the error message.

CTMD14E Reception failure. Error code = `codeError message`

Explanation: The error occurred while the utility was receiving data from a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action: Perform the appropriate action, based on the error code and the error message.

CTMD15E Parameter `param` is too long - `length`. Max length is `max_length`

Explanation: The value of the param input parameter is too long. The maximum length of this parameter is max_length bytes.

Corrective Action:Correct the value of this input parameter.

CTMD16E Invalid `param` parameter

Explanation: The value of the param input parameter is incorrect.

Corrective Action:Correct the value of this input parameter.

CTMD17E Unsupported agent version - `ver. num`

Explanation: The utility cannot work with a Control-M Agent of version ver. num.

Corrective Action:Check the value of the –host input parameter. If the host name is correct, contact the Control-M administrator to install the correct version of Control-M agent.

CTMD18E Error during load module CTMX006. Error code = `codeError message`

Explanation: The error occurred while the utility was trying to load user exit CTMX006. Usually this error occurs when the load module CTMX006 does not exist in the STEPLIB libraries. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.

Corrective Action: Perform the appropriate action, based on the error code and the error message.

CTMD19E Invalid `param` parameter. Value = `value`

Explanation: The value of the param input parameter is incorrect.

Corrective Action:Correct the value of this input parameter.

CTMD21E ENHANCED SHIFT EXCEEDS MAXIMUM NUMBER OF WORKDAYS

Explanation: An invalid value was specified for the SHIFT parameter. The enhanced SHIFT algorithm allows the scheduling date to be shifted forward or backward a maximum of 62 working days.

The scheduling definition is not saved.

Corrective Action: Specify a valid value for the SHIFT parameter. For more information, see the CONFCAL parameter in the chapter that describes job production parameters of the Control-M for z/OS User Guide.

CTMD22E INVALID VALUE. "-" , "+" OR BLANKS EXPECTED

Explanation: An incorrect value was specified for the second character of the SHIFT subparameter. The SHIFT subparameter has two fields. The first is a 1-character field that designates the shift direction (< or >). The second is an optional 3-character field that contains a + or - followed by a two digit integer. This field designates how much to move the scheduling date forward (if plus) or backward (if minus).

The scheduling definition is not saved.

CTMD23E INVALID VALUE

Explanation: An invalid value was specified in the last three characters of the SHIFT subparameter. The format of the last three characters of the SHIFT subparameter must be +nn or -nn, where nn is an integer between 01 and 62.

The scheduling definition is not saved.

Corrective Action: Specify a valid value for the SHIFT subparameter. For more information, see the CONFCAL parameter in the chapter that describes job production parameters of the Control-M for z/OS User Guide.

CTMD24E SHIFT VALUE CAN BE BETWEEN 1 AND 62

Explanation: An invalid value was specified in the last two characters of the SHIFT subparameter. The last two characters of the SHIFT subparameter must be an integer between 01 and 62.

The scheduling definition is not saved.

CTMD25E ENTRY IN USE BY ANOTHER USER

Explanation: This information message is displayed if a user performs a HOLD of a job on the Active Environment screen (Screen 3) or the Active Environment Zoom screen (Screen 3.Z), and a second user then attempts to delete or free that job.

Corrective Action: No action is required.

CTMD27E INVALID VALUE. USE <, >, -, +, @, D, I, N, P, OR BLANK

Explanation: An invalid character was specified in the SHIFT field of the job scheduling definition.

Corrective Action: Specify a valid value.

CTMD30E IOASINIT CANNOT BE USED TO START CMEM ANYMORE. CMEM SHOULD BE STARTED USING CTMCMEM

Explanation: There was an attempt to start CMEM using the IOASINIT procedure. CMEM is now started using the CTMCMEM procedure.

IOASINIT terminates. CMEM initialization fails.

Corrective Action: Start CMEM using the S CTMCMEM command.

CTMD31E IOA SUBSYSTEM `subsys` IS ACTIVE FOR ENVIRONMENT (IOA QNAME)

Explanation: The subsys subsystem is already active for another IOA environment. The same subsystem name cannot be used for two IOA environments in parallel.

IOA subsystem initialization fails for the subsys subsystem.

Corrective Action: Either choose another subsystem name for the current environments of the IOA products, or deactivate the IOA online monitor and all the subsystem components of the old IOA environment and restart the subsystem.

CTMD32E LOAD OF SUBSYSTEM EXECUTOR `name` FAILED

Explanation: Subsystem initialization process failed while trying to load the subsystem executor program specified in the message.

IOA subsystem initialization fails.

Corrective Action: Verify the module name exists in the STEPLIB library.

CTMD33E `funcName` IS ACTIVE. BRING IT DOWN BEFORE RUNNING THIS PROCEDURE AGAIN

Explanation: An attempt was made to start CMEM when Control-O was up, or vice versa. CMEM and Control-O procedures cannot work concurrently. If one already started, the other must be down.

Control-O performs all the functions of CMEM.

The requested CMEM or Control-O initialization fails.

Corrective Action: If you want to run the initialization procedure, first stop the Control-O or CMEM monitor identified in the message text.

CTMD34E NOT ENOUGH STORAGE IN (EXTENDED) CSA. CANNOT LOAD TABLES FOR IOA SUBSYSTEM `subsys`

Explanation: Insufficient storage in ECSA or CSA for the subsystem tables and modules.

Subsystem initialization fails.

Corrective Action: If the storage defined for ECSA or CSA is not large enough, increase the size of ECSA or CSA.

CTMD35E INVALID SUBSYSTEM NAME IN "DISCONNECT SUBSYSTEM" REQUEST

Explanation: Length of the subsystem name specified for the disconnect subsystem request is incorrect. It is either less than, or greater than four characters.

The disconnect subsystem function is not performed.

Corrective Action: Restart the disconnect subsystem function using a valid, four-character subsystem name.

CTMD36I SUBSYSTEM `subsys` DISCONNECT STARTED

Explanation: This information message indicates that subsys subsystem is being disconnected.

Corrective Action: No action is required.

CTMD37I SUBSYSTEM `subsys` DISCONNECT COMPLETED SUCCESSFULLY

Explanation: This information message indicates that subsys subsystem is inactive and no longer used by Control-O.

Corrective Action: No action is required.

CTMD38E IOA ONLINE MONITOR IS ACTIVE WITH SSNAME "`subsys`" FOR ANOTHER ENVIRONMENT (IOA QNAME)

Explanation: The subsys subsystem is already active for the IOA Online monitor of another IOA environment. The same subsystem cannot be specified for two IOA environments in parallel.

IOA subsystem initialization fails for the subsys subsystem.

Corrective Action: Either choose another subsystem name for the current environment of the IOA products, or deactivate the IOA online monitor and all the subsystem components of the old IOA environment and restart the subsystem.

CTMD3AE ERROR IN INITIALIZATION CONTROL-D SUBSYSTEM "`xxxx`"

Explanation: Initialization of the CDAM subsystem failed. Additional system messages are issued before this message.

The job or STC terminated with a return code other than zero.

Corrective Action: Correct the error and try again.

CTMD41E MISSING OBLIGATORY KEYWORD `keyName` IN ORDER REQUEST

Explanation: The keyName keyword was not given in the order request. Some keywords are obligatory in each order request. Failing to specify one produces this message.

The CTMJOB program ends with errors.

Corrective Action: Supply the missing keyword.

CTMD45E AT LEAST ONE VALID COND MUST BE SPECIFIED IN THE ISCPARM MEMBER

Explanation: No conditions to be passed to the other CPU were specified in the ISCPARM member allocated to one of the Control-M monitors. The DAISCPRM DD name should point to a library containing the ISCPARM member. This member should contain at least one COND parameter, set to cond, where cond is a condition name up to 20 characters. Masking characters * and ? are allowed. Only these conditions are passed to the other CPU.

CTMISR routine returns a return code of 24 to the calling IOA Exit 7. No conditions are passed to the other CPU.

Corrective Action: Add at least one COND=cond statement in the ISCPARM member and then shut down and restart the monitor. COND=* is valid for passing all the conditions.

CTMD46S CTMBLT ENDED WITH ERRORS

Explanation: The CTMBLT utility ended due to errors. CTMBLT creates Control-M scheduling tables. If CTMBLT ended with errors, messages in the Error Messages file DAPRINT DD statement explain the reasons. The Error Table Definitions file DATABERR DD statement contains the input definition statements that have the errors.

The utility ends with a non-zero return code.

Corrective Action: Correct all problems, and rerun the job.

CTMD48I CTMBLT ENDED OK

Explanation: This information message indicates that the CTMBLT utility ended normally. The CTMBLT utility creates Control-M scheduling tables.

Corrective Action: No action is required.

CTMD50S READING JOB DATA BY `subsystem_request` FAILED `nnnn` TIMES. LAST RC `rc fileName jobName/jobId`

Explanation: This message is issued after the number of unsuccessful attempts to read job data by subsystem request reaches the defined maximum. After searching for the job data the maximum number of times, Control-M changes the job status to DISAPPEARED and stops searching.

The job status changes to DISAPPEARED.

Corrective Action: For the appropriate action, refer to the section on the Control-M monitor and JES in the INCONTROL for z/OS Administrator Guide.

CTMD51S NO MORE SPACE FOR SYSOUT ARCHIVING (SB37)

Explanation: No space is available on the designated volumes to archive SYSDATA sysouts.

Archiving of SYSDATA is not completed due to lack of the space on the volumes designated for allocation of the Archived Sysout data sets.

Control-M issues additional messages describing the nature of the problem and terminates.

Corrective Action: Please do the following before attempting to restart the Control-M monitor:

Make sure that there is sufficient free space on the volumes defined by the AMVOL parameter of the CTRPARM member.
If it is not possible to provide enough space on the volumes defined by the AMVOL parameter of the CTRPARM member, please add another volume to the list of volumes designated for allocation of the Archived Sysout Data Sets.
If it is not possible to add more volumes to the AMVOL parameter of the CTRPARM member, remove all of them. Then the Archived Sysout Data Sets will be allocated only according to the AMUNIT parameter of the CTRPARM member.
Start the Control-M monitor.
If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

CTMD53S UNABLE TO ALLOCATE COMPRESSED DATASET FOR SYSDATA SYSOUT ARCHIVING. LAST RC=`rc`

Explanation: Dynamic allocation of an Archived Sysout Dataset has failed.

This message will be preceded by other messages detailing the nature of the problem, DD name, RC and reason code.

The Archived Sysout Dataset is not allocated. The job is processed and an ENDED NOTOK message is displayed, with the status FAILED REASON UNKNOWN.

Corrective Action: Record all relevant messages, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMD55S SYSOUT ARCHIVING FAILED

Explanation:Highlighted, unrollable message.

The Control-M monitor failed to archive SYSDATA for the job. This message is preceded by other messages detailing the nature of the error.

The job is processed and an ENDED NOTOK message is displayed, with the status FAILED REASON UNKNOWN.

Corrective Action: Do the following:

Examine the preceding messages, and follow the steps recommended in the description of those messages.
Start the Control-M monitor again. If the problem persists, report it to your INCONTROL administrator, who should prepare the Control-M monitor full output and contact BMC Customer Support.

CTMD60E FILL IN THE NEW PASSWORD TWICE

Explanation: A normal prompt of the IOA Entry Panel. The user is asked to write the value of the new password twice (to confirm the user choice).

Corrective Action: Enter the same value of the new password in the two provided fields.

CTMD67S ORDERING CHECKPOINT RECORD IS INVALID FOR THIS DAILY

Explanation: The Ordering Checkpoint Record contains recovery information which is invalid for this Daily run.

The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains data specifying recovery for the CTMJOB program, but these data are incorrect for the jobs that were ordered in this run of CTMJOB.

The CTMJOB program ends with errors.

Corrective Action: Either run CTMJOB with the same data (ordered jobs) as were in the last (abending) run, or blank out the values of the keywords in the Ordering Checkpoint Record, and run CTMJOB without recovery.

CTMD68S STRUCTURE OF ORDERING CHECKPOINT RECORD IS INVALID

Explanation: The Ordering Checkpoint Record contains invalid keywords, or valid keywords in invalid offsets. The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains keywords in an unexpected structure.

The CTMJOB program ends with errors.

Corrective Action: Either correct the Ordering Checkpoint Record, or delete the Ordering Checkpoint Record, and run CTMJOB without recovery.

CTMD69I NO JOBS WERE SCHEDULED DURING SCHEDULING REQUEST

Explanation: This information message indicates that no jobs matched the ordering criteria during a scheduling request. This message is issued after the scheduling request has been processed, and no jobs were ordered.

Corrective Action: If you think a job should have been ordered in this scheduling request, check and correct the scheduling parameters as required, and rerun the scheduling request.

CTMD6AI RETRO SCHEDULING BYPASSED FOR JOBS WITHIN GROUP

Explanation: This information message indicates that Y was specified in the RETRO field in a group entity or in one of the group jobs. RETRO processing is not supported in GROUPS. Setting RETRO to Y in a group can cause jobs to be scheduled on inappropriate ODATES.

The RETRO field is ignored in group processing.

Corrective Action: Set the RETRO field to N and retry.

CTMD6BI NUMBER OF JOBS ORDERED - `numJobs`

Explanation: This information message indicates the number of jobs ordered by the present invocation of CTMJOB.

Corrective Action: No action is required.

CTMD70E OPTION IS VALID UNDER ISPF ONLY

Explanation: ISPF environment is missing. This option can be used only under ISPF.

Corrective Action: To use the option, invoke Control-M under ISPF.

CTMD71E EDIT NOT PERFORMED. MEMLIB IS EITHER DUMMY OR CONTAINS "USER="

Explanation: Editing was attempted when the MEMLIB or OVERLIB field contained either DUMMY or USER. When the MEMLIB or OVERLIB field contains DUMMY or USER, editing cannot be performed.

Corrective Action: No action is required.

CTMD72E ONLY JOBS MAY BE EDITED (NOT STARTED TASKS OR GROUP ENTITIES)

Explanation: An attempt was made to edit a group entity or the JCL of a started task. Only the JCL of regular jobs can be edited.

Corrective Action: No action is required.

CTMD73E ISPF/EDIT FAILED FOR `text`

Explanation: Execution of the ISPF EDIT command failed.

If the variable text is of the form lib (memname), then ISPF was unable to edit the library or member specified in MEMLIB and MEMNAME of the job. The ISPF profile or the directory in which the profile is contained may be full or the library (specified in the MEMLIB field) does not exist.

If the variable text is of the form DDNAME= xxx, then ensure that Control-M exit CTMX014G is installed, which provides support for online editing of members specified via the MEMLIB DDNAME= xxx format. See the explanation of the MEMLIB parameter in the Control-M for z/OS User Guide for further details.

If the variable text is of the form EDIT DENIED BY [USER EXIT]- moduleName, then the edit command was failed by the IOA Editor or by the specified user exit.

Corrective Action: Check the parameters specified in MEMLIB and MEMNAME of the job. If the reason that ISPF could not edit the library or member is not obvious, then invoke the ISPF EDIT DATASET library or member to clarify the problem.

CTMD74E MEMLIB AUTOEDIT RESOLUTION FAILED. ENDED WITH RC=`rc`

Explanation: The MEMLIB field contained AutoEdit variables which could not be resolved.

Corrective Action: Correct the problematic AutoEdit variable.

CTMD75E EDIT NOT PERFORMED SINCE MEMNAME CONTAINS EITHER "*" OR "?"

Explanation: MEMNAME contains an invalid parameter for the EDIT option. When the MEMNAME field contains either * or ?, editing cannot be performed.

Corrective Action: Correct the parameter in the MEMNAME field.

CTMD78I JCL VERIFICATION CAN ONLY BE DONE FOR JOBS

Explanation:The message explains the error.

Corrective Action:No action is required.

>CTMD79I JCL VERIFICATION CAN'T BE DONE FOR ON-SPOOL JOBS

Explanation:Control-M JCL Verify cannot verify on-spool jobs.

Corrective Action:No action is required.

CTMD7AI JCL VERIFY OK, RERUN OF`job_name`=TABLE`table_name`ODATE`odate`PERFORMED

Explanation:JCL verification was performed while rerunning a job. The JCL verification finished OK, and the rerun was successful.

Corrective Action:No action is required.

CTMD7BI JOB NOT RERUN DUE TO JCL VERIFICATION FAILURE

Explanation:JCL verification was performed before rerunning a job. The JCL did not successfully pass the verification, and therefore the job was not rerun.

Corrective Action:No action is required.

CTMD7CI JCL VERIFICATION CAN'T BE DONE FOR DUMMY JOBS

Explanation:Control-M JCL Verify cannot verify dummy jobs.

Corrective Action:No action is required.

CTMD7EI JCL VERIFICATION CAN'T BE DONE FOR WARNING JOBS

Explanation:Control-M JCL Verify cannot verify warning jobs.

Corrective Action:No action is required.

CTMD7FW Control-M JCL Verify IS NOT INSTALLED

Explanation:Control-M JCL Verify is not installed.

Corrective Action:No action is required.

CTMD7GI JOB HAS CHANGED. INVOKE JVER AFTER RE-ENTERING THIS SCREEN

Explanation:This message is issued in screen 2 and screen 3. If the job scheduling definition is changed, and then the JVER command is issued, this message is displayed.

Corrective Action:Exit screen 2 or screen 3, and re-enter.

CTMD90E RECOVERY RECORD INCOMPATIBLE WITH DATE RECORD

Explanation: The Date Control Record indicates that recovery is not necessary, but the recovery record, that is, the second record of the Date Control Record member used for Enhanced Daily Checkpointing, indicates that recovery is needed.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. In the Date Control Record, date-2 (columns 18-23) is equal to date-3 (columns 25-30) and date-4 (columns 43-48) is equal to date-5 (columns 50-55). However, the recovery record contains non-blank values for the recovery parameters.

For more details, please see the description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.

The program terminates with a condition code of 08.

Corrective Action: If recovery is required, set date-3 to the day before date-2, and date-5 to the day before date-4. If recovery is not required, replace the values in the recovery record with blanks.

CTMD91E INVALID PREVIOUS MONTHLY SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 25-30)

Explanation: Invalid previous monthly scheduling date in the User Daily Date Control Record date-3 (columns 25-30). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Valid formats for the date are:

ddmmyy
mmddyy
yymmdd

Possible causes are:

The previous run of the CTMJOB program did not complete successfully.
The contents of the User Daily Date Control Record (the DACHK DD statement) have been incorrectly modified manually.

For more details, please see the description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.

The program terminates with a condition code of 08.

Corrective Action: Correct the Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTMD92S FILE ALLOCATED TO DDNAME "DACKPT" IS NOT THE EXPECTED ACTIVE JOBS FILE

Explanation:Highlighted, unrollable message.

The Active Jobs file specified for the Control-M monitor is not the correct Active Jobs file for this monitor. The QNAME specified in CTMPARM does not match the QNAME specified in Record 0 of the Active Jobs file.

The Control-M monitor shuts down.

Corrective Action: Correct the data set name referenced by the DD name DACKPT, or format the Active Jobs file using the same IOA Load library used by the Control-M monitor.

CTMD93S BUILD OF RESOURCE FILE ENDED WITH ERRORS

Explanation: The procedure that builds a new Control-M Resources file encountered an error. The next message describes the error.

The system stops without building the Control-M Resources file, and issues a return code of 12.

Corrective Action: Correct the error described in the next message and try again.

CTMD94S RECORD 0 CONTAINS ILLEGAL CONTROL OR QUANTITATIVE COUNTERS

Explanation: The counters in record 0 have illegal values. Record 0 of the Control-M Resources file contains counters and parameters that define the file. The maximum value of each counter is 100.

The system stops and issues a return code of 12.

Corrective Action: Ensure that there are no more than 100 Quantitative resource records and no more than 100 Control resource records.

CTMD95S NUMBER OF BASE SLOTS TO BE DEFINED IN THE NEW RESOURCE FILE BUILD PROGRAM EXCEEDS MAXIMUM

Explanation: You tried to define too many base slots in the new Control-M Resources file. The new Control-M Resources file build program can define a maximum of 1160 base slots.

The system stops without defining any base slots, and issues a return code of 12.

Corrective Action: Change the value of the RESBQNT parameter to a value that is less than 1160. For more information, see the section on MVS procedures and configuration in the Control-M chapter of the INCONTROL for z/OS Installation Guide.

CTMD96S COPY OF RESOURCES OR CONDITIONS FILE ENDED WITH AN ERROR

Explanation: An error interrupted copying of the Control-M Resources file or the IOA Conditions file. The next message describes the cause of the error.

The system stops without copying the file, and issues return code 12.

Corrective Action: Correct the error described in the next message and try again.

CTMD97S NEW RES FILE IS TOO SMALL FOR MIGRATION OF RESOURCES

Explanation: Copying failed because the new Control-M Resources file is not big enough to contain all of the resource data, whether relating to quantitative or control resources or both, in the old Control-M Resources file.

The system stops without copying the file, and issues a return code of 12.

Corrective Action: Try again with a larger new Control-M Resources file.

CTMD98E FAILED TO UPDATE RESOURCE FILE WITH THESE JOB RESOURCES. JOB=`jobName` OID=`orderId`

Explanation: The program that builds the new Control-M Resources file could not update it from the Active Jobs File (AJF). The program detected new jobs data in the AJF that should be updated in the Control-M Resources file, but it could not do the update.

The system continues building the Control-M Resources file, without adding the new data.

Corrective Action: Check and correct the definitions of the AJF, the Control-M Resources file, and the data, as necessary, and try again. If necessary, update the Control-M Resources file manually.

CTMD9AS RESBQNT# (FOR NEW RES FILE) IS SMALLER THAN VALUE IN THE OLD RES FILE.

Explanation: This message is issued if the RESBQNT# parameter in the new resource file is less than the value of RESBQNT# in the old file.

Corrective Action: Refer to the Control-M Utilities guide, utility CTMCRES, section "Copy or Resize the Control-M Resources File". Part of the procedure involves changing parameter RESBQNT#, which is the maximum number of Quantitative resources to be defined in the Control-M Resources file.

CTMD9BE TABLE CONTAINS A MIX OF M/F AND DISTRIBUTED JOBS

Explanation: During the execution of the CTMTLB utility, a scheduling table was encountered which contained a combination of both mainframe and distributed job definitions. This is not supported by the utility.

The program terminates with a return code of 8.

Corrective Action: To overcome this situation, the CTMTLB utility must be executed twice, once using the EXCLUDE MF control statement and once using the EXCLUDE NONMF control statement so that two separate XMLs are created, one for the mainframe datacenter and one for the distributed datacenter. The DATACENTER control statement for each execution must be appropriately changed.

CTMD9DW CURRENT TABLE IS EMPTY. THE TABLE IS IGNORED

Explanation: During the execution of the CTMTLB utility, an empty scheduling table was encountered.

The program ignores the empty table, continues processing and terminates with a return code of 4.

Corrective Action: No action is required.

Messages CTME00 through CTMExx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTME01I type BASED JOB TRACKING INITIALIZED SUCCESSFULLY

Explanation: The type variable indicates the type of job tracking method used, either ENF or JES.

ENF based tracking. The most efficient job tracking method available for Control-M beginning with version 8.0.00. It is based on ‘Job Status Change’ events, which is supplied by z/OS Events Notification Facility (ENF) for JES2 (since z/OS 1.11) and for JES3 (since z/OS 1.13). The ENF based job tracking is the default method used by Control-M, unless ENF is unavailable or deactivated by setting the ENFENA installation parameter to N (in which case the CTME06W message is also issued). In a SYSPLEX environment Control-M uses this method only when the z/OS level for all SYSPLEX members is z/OS 1.11 or later.
JES based tracking. This is the only method available in versions of Control-M earlier than 8.0.00. The jobs tracking handled by Control-M is based on periodical issuing the JES ‘STATUS’ Subsystem Request.

Corrective Action: No action is required.

CTME02E ERROR IN ESTABLISHING LISTENER FOR JOB STATE CHANGES. REASONerror reason CODEerror code

Explanation: An internal error occurred while Control-M attempted to initialize the ENF based job tracking method. Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME03E ERROR IN RESUME LISTENING FOR JOB STATE CHANGES. REASONerror reason CODEerror code

Explanation: An internal error occurred while Control-M attempted to resume the ENF based job tracking method after it was temporary disabled. Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME04E LISTENING FOR JOB STATE CHANGES ENDED ABNORMALLY AND TERMINATED. LAST POINT `internal name of last check point passed`

Explanation: Control-M monitor detected the abnormal termination of the ENF ‘Job Status Change’ events listening exit (established by Control-M for ENF Based Job Tracking). The ENF based job tracking is disabled because of the abnormal termination, but Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME05E INTERNAL QUEUE ERROR IN LISTENING FOR JOB STATE CHANGES. REQUEST `internal queue request` CODE `error code`

Explanation: An internal queue error occurred while processing the ENF ‘Job Status Change’ events passed to Control-M monitor from the events listening exit (established by Control-M for ENF Based Job Tracking). The ENF based job tracking is disabled because of the abnormal termination, but Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME06W ENF BASED JOB TRACKING IS DISABLED BY INSTALLATION PARAMETER

Explanation: The ENFENA Control-M installation parameter is set to N, specifying JES based job tracking instead of ENF based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: No action is required.

CTME07W UNKNOWN LEVEL OF NON-ACTIVE SYSPLEX MEMBER `system_name`

Explanation: Control-M did not recognize the z/OS level of the SYSPLEX member. As a result, Control-M does not activate the ENF based jobs tracking, but uses JES based jobs tracking instead. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: If the ENF based job tracking method is required, and the actual z/OS levels of the SYSPLEX members displayed in the message are not lower than z/OS 1.11, do the following: Locate the ENFENA installation parameter in the 'Monitor Parameters' section of the CTMPARM installation member and set it to F.

CTME80S STATEMENT PARSING ERROR. RC= `rc`. EXECUTION WILL TERMINATE

Explanation:Highlighted, unrollable message.

An internal error occurred while building the online environment.

The online environment is not started.

Corrective Action: Try to reenter the online environment after logging out and reconnecting. If this is unsuccessful, record the message and contact BMC Customer Support.

Messages CTMF00 through CTMFxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMF0DI POLICIES ARE EDITED BY USER:`userName` SYSTEM:`systemName`, BROWSE ENFORCED

Explanation: Another user is currently editing Workload Policies. The Workload Policies List screen is displayed in Browse mode.

Corrective Action: Try again later, in coordination with the specified user.

CTMF0GE WORKLOAD POLICIES CANNOT BE SAVED DUE TO ERRORS.

Explanation: The Workload Policy could not be saved. This may be due to a variety of reasons.

Corrective Action: Try exiting the Workload Policy and re-entering. If the problem persists, contact BMC Customer Support.

CTMF0OE ABEND `abCode` ENCOUNTERED WHILE SAVING WORKLOAD POLICIES - POLICIES NOT SAVED

Explanation: The Workload Policy could not be saved. An abend code gives more information regarding the reason for this problem.

Corrective Action: Try exiting the Workload Policy and re-entering. If the problem persists, contact BMC Customer Support.

CTMF0PE SAVING WORKLOAD POLICIES FAILED WITH RC `rc` AND REASON `rsn` - POLICIES NOT APPLIED

Explanation: The Workload Policy could not be saved. The return code and reason code give more information about the problem.

Corrective Action: Try exiting the Workload Policy and re-entering. If the problem persists, contact BMC Customer Support.

CTMF0QE SAVE/APPLY FAILED - CHECK CTMF0OE/CTMF0PE IN IOA LOG

Explanation: The Workload Policy could not be saved. This may be due to a variety of reasons.

Corrective Action: Try exiting the Workload Policy and re-entering. Check the log for further information in the additional messages. If the problem persists, contact BMC Customer Support.

CTMF0RE WORKLOAD POLICY SAVED, APPLY OF WORKLOAD POLICIES FAILED

Explanation: The Workload Policy was saved but changes were not applied to the active environment and have not taken effect. This may be due to a variety of reasons.

Corrective Action: Try applying the Workload Policy using the WLREFRESH command, which enables you to recalculate and rebuild all Workload Policies and refresh all their definitions. You can also use the WLLIST command to see the status of Workload Policies. For more information about the WLREFRESH and WLLIST commands, refer to the INCONTROL for z/OS Administrator Guide.

If the problem persists and changes do not take effect, contact BMC Customer Support.

CTMF51I LOC SNDR `loc_sendr` INIT SESSION WITH RMT RCVR `rmt_recvr`

Explanation: The loc_sendr local sender is trying to initiate a session with the rmt_rcvr remote receiver.

A session starts when the remote Gateway comes up.

Corrective Action: No action is required.

CTMF52I LOC RCVR `loc_recvr` AWAITING SESSION WITH RMT SNDR `rmt_sendr`

Explanation: The loc_recvr local receiver is waiting for a session to be initiated with the rmt_sendr remote sender.

A session starts when the remote Gateway comes up.

Corrective Action: No action is required.

CTMF53I LOC SNDR `loc_sendr` NOW IN SESSION WITH RMT RCVR `rmt_recvr`

Explanation: The loc_sendr local sender is now in a session with the rmt_recvr remote receiver.

Communication is established.

Corrective Action: No action is required.

CTMF54I LOC RCVR `loc_recvr` INIT SESSION WITH RMT SNDR `rmt_sendr`

Explanation: The loc_recvr local receiver is now in a session with the rmt_sendr remote sender.

Communication is established.

Corrective Action: No action is required.

CTMF55E SERVER TYPE `x` FAILED IN `yyy`. RC=`rc`

Explanation: An Application Server of type x has failed to perform service yyy.

The variables in this message are:

x - the type of Application Server
yyy - the problematical service Valid values are:
- PUT
- GET
rc - the return code A value of 28 indicates communication recovery and is allowed.All other return codes are indicative of internal errors.

Corrective Action: If the value of rc is not 28, consult your INCONTROL administrator.

CTMF90S OPEN OF DDCARD `ddName` FAILED

Explanation: Open for the specified DD statement pointing to password member failed.

Possible causes are:

The ddName DD statement is missing.
The file allocated to the ddName DD statement is not a sequential file nor a member in a PDS.

Authorization to access the product is denied.

Corrective Action: Correct the JCL statement for the procedure or the allocations for the CLIST.

CTMF91S PASSWORD MEMBER TOO LARGE (DD `ddName`)

Explanation: Password member (or sequential data set) has too many lines.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Remove unnecessary lines from the member.

CTMF92S SYNTAX ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A syntax error was found in the password member. When this message is issued by the monitor, it is generally followed by message CTMF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTMF93S VALUE ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A field in the password member contains invalid data. When this message is issued by the monitor, it is generally followed by message CTMF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTMF94S PASSWORD INVALID, PLEASE RECHECK PASSWORD MEMBER (DD `ddName`)

Explanation: Data in the password member was not consistent with the specified password.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from BMC Customer Support. If it checks, contact the representative.

CTMF95S PASSWORD FOR CONTROL-`x` IS ABOUT TO EXPIRE IN `n` DAYS

Explanation:Highlighted, unrollable message.

Password expiration period is about to end.

An expiration date is specified in the password member for the product.

Corrective Action: Contact BMC Customer Support for a new password.

CTMF96S PASSWORD FOR CONTROL-`x` HAS EXPIRED

Explanation:Highlighted, unrollable message.

Password expiration period has ended.

An expiration date is specified in the password member for the product.

Authorization to access the product is denied.

Corrective Action: Contact BMC Customer Support for a new password.

CTMF97S INTERNAL ERROR OCCURRED ON DD `ddName`, PLEASE NOTIFY THE IOA ADMINISTRATOR

Explanation: An internal error has occurred while analyzing the password member pointed to by the ddName DD statement.

Authorization to access the product is denied.

Corrective Action: Notify the IOA administrator.

CTMF98S OBLIGATORY FIELD MISSING FROM PASSWORD MEMBER (DD `ddName`)

Explanation: An obligatory field is missing from a password member.

The ddName DD statement points to the password member. The PROD, START, CPUID, PASS, and TYPE fields should appear at least once in a password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from your INCONTROL administrator.

CTMF9AS PASSWORD FOR CONTROL-`x` NOT DEFINED IN MEMBER (DD `ddName`)

Explanation: The member pointed to by the ddName DD statement does not contain the password for the appropriate product.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this product.

CTMF9BS AUTHORIZATION PERIOD HAS NOT STARTED YET (DD `ddName`)

Explanation: The start date of the password has not yet arrived.

In this message, ddName is the identity of the DD statement that points to the password member. The START field contains the starting date of the password.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this period.

CTMF9CS CPUID/MODEL NOT FOUND IN AUTHORIZED CPU LIST (DD `ddName`)

Explanation: The current CPU is not defined in the CPU list.

In this message, ddName is the identity of the DD statement that points to the password member. Each entry in the CPU list in the password member contains the CPUID of the CPU and its model.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this CPU.

CTMF9DS CARD = `text`

Explanation: This message supplies additional information for a previous error message.

This message may appear after message CTMF92S or CTMF93S which indicates an error has occurred in one of the lines of the password member. Message CTMF9DS displays the erroneous line.

Corrective Action: See messages CTMF92S or CTMF93S.

CTMF9ES PASSWORD DDCARD `ddName` POINTS TO A NON EXISTING MEMBER (ABEND S013-18)

Explanation: The ddNameDD statement is allocated to a nonexisting member in a PDS file.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the name of the member in the DD statement or create a member with the specified name.

CTMF9FS PASSWORD FOR CONTROL-`x` EXPIRED, TEMPORARY AUTHORIZATION GRANTED

Explanation: The password for Control-x has expired. Nonetheless, Control-x can be run on the current date.

Despite password expiration, Control-x can be run on the 28th, 29th, 30th, 31st, 1st, 2nd, and 3rd days of each month for special purposes.

Control-x processing continues.

Corrective Action: Contact BMC Customer Support to obtain password renewal.

CTMFB0S PARAMETER `parm` NOT RECOGNIZED

Explanation: The parameter specified for the IOATEST utility is invalid.

IOATEST terminates with a condition code of 08.

Corrective Action: Correct the syntax of the parameters to IOATEST.

CTMFB1S PARAMETER SHOULD BE NUMERIC (`parm`)

Explanation: The value of a parameter that should be numeric is nonnumeric.

The IOATEST utility terminates with a condition code of 08.

Corrective Action: Make sure the value of the parameter is numeric.

CTMFB2S NUMERIC PARAMETER OUT OF RANGE (`parm`)

Explanation: Numeric parameter is not within the defined range.

The utility terminates with a condition code of 08.

Corrective Action: Make sure the value of the parameter is within the defined range.

CTMFB3S A MAXIMUM OF TEN MINOR LINES ARE ALLOWED FOR A MULTI-LINE MESSAGE

Explanation: More than 10 minor lines were specified for a multi-line message; 10 is the maximum allowed.

The IOATEST utility terminates with a condition code of 08.

Corrective Action: Make sure that no more than 10 minor lines are specified.

Messages CTMG00 through CTMGxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMG00I ENTERPRISE/CS MAINFRAME GATEWAY STARTED

Explanation: This information message indicates a normal start of MVS Gateway for Enterprise Controlstation.

Corrective Action: No action is required.

CTMG01I ENTERPRISE/CS MAINFRAME GATEWAY TRACE LEVEL IS SET TO `debugLevel`

Explanation: This information message indicates that the Enterprise Controlstation Mainframe Gateway DEBUG level was set by an operator modify command (F).

The TRACE level is set to a new level. Each TRACE level activates the trace option on different components of the Enterprise Controlstation Mainframe Gateway.

Corrective Action: No action is required.

CTMG02E ENTERPRISE/CS MAINFRAME GATEWAY NOT APF-AUTHORIZED

Explanation: The Enterprise Controlstation Mainframe Gateway is not APF-authorized. The CTWGTW module is not in an APF-authorized library or does not have the AC attribute set to 1.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Either add the library name in which CTWGTW resides to the IEAAPF00 member in SYS1.PARMLIB, or relink the module with the AC attribute set to 1.

CTMG03E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

Explanation: An operator modify command (F) passed an erroneous parameter to the Enterprise Controlstation Mainframe Gateway. One or more GTWG25I messages are displayed on the operator console after this message, each containing a valid modify parameter.

The modify command is rejected.

Corrective Action: Enter a valid modify parameter.

CTMG04E BLDL/ATTACH FAILED FOR TASK `modName`

Explanation: Initialization of an IOA Gateway internal task failed. The system code indicating the exact reason can be found in the system log. Possible causes are:

The modName module is not in the IOA Gateway Load library.
Insufficient storage is available for the IOA Gateway.

The IOA Gateway shuts down.

Corrective Action: Call your system programmer for assistance. If necessary, increase the IOA Gateway REGION size.

CTMG05E UNRECOVERABLE ERROR ENCOUNTERED

Explanation: An unrecoverable error occurred in the operation of the Enterprise Controlstation Mainframe Gateway. The IOA Log, or the Enterprise Controlstation Mainframe Gateway JES messages file or SYSPRINT file, should contain a message with more details about the error. See also, CTWA01W.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

CTMG07I SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message confirms that an operator command (P) was issued, requesting shutdown of MVS Gateway for Enterprise Controlstation. This message is followed by message GTWG20I, indicating completion of the shutdown.

MVS Gateway for Enterprise Controlstation starts to shut down.

Corrective Action: No action is required.

CTMG10E TRACE LEVEL MUST BE A NUMBER BETWEEN 0 AND 255

Explanation: An invalid TRACE level was entered, either in the operator modify command (F) or in the operator start command (S). When activating the Enterprise Controlstation trace facilities, specify a number from 0 through 255, inclusive, for the TRACE level. 0 specifies no tracing.

Corrective Action: Issue the command again with the correct TRACE level. The required TRACE level should be supplied by BMC Customer Support.

CTMG11I SERVICE ID "`id`" IS {ENABLED | DISABLED}

Explanation: This information message confirms the current enable or disable status of service ID, after the operator has issued an operator modify command (F) that enables or disables it.

Corrective Action: No action is required.

CTMG24E INTERVAL MUST BE A TWO-DIGIT NUMBER BETWEEN 03 AND 99 SECONDS

Explanation: Invalid Enterprise Controlstation Mainframe Gateway sleeping interval specified in an operator modify command (F). The Enterprise Controlstation Mainframe Gateway sleeping interval must be a two-digit number from 03 to 99 seconds.

The modify command is rejected.

Corrective Action: Enter a valid sleeping interval.

CTMG51E COMM GATEWAY INTERNAL ERROR. RC=`rc`

Explanation: An internal error occurred. A call to internal routine ECAPUT failed with return code rc.

The IOA Gateway shuts down.

Corrective Action: Contact your INCONTROL administrator.

CTMG52E INTERNAL ERROR: ASID=`asid` NOT FOUND

Explanation: An internal error occurred.

In this message, asid is the internal sequence number assigned to the server address space in which the error occurred.

The IOA Gateway shuts down.

Corrective Action: Contact your INCONTROL administrator.

CTMG53E OPEN OF DDNAME `ddName` FAILED

Explanation: An attempt to open a data set failed. The data set allocated by the specified DD name does not exist.

IOA Gateway shuts down.

Corrective Action: Determine why the data set allocated by the DD name in the startup procedure does not exist, fix the problem, and restart IOA Gateway.

CTMG63I DEALLOCATE SENT TO WORKSTATION GATEWAY ID=`id` APPLID=`applId` LU=`luName`

Explanation: This information message is issued during IOA Gateway shutdown or communication recycling. The deallocation was issued by the IOA Gateway APPLID applId. The corresponding partner or client LU is luName.

Corrective Action: No action is required.

CTMG65I DEALLOCATE RECEIVED FROM WORKSTATION GATEWAY ID=`id` APPLID=`applId` LU=`luName`

Explanation: This information message indicates that deallocation was issued by partner or client LU luName during communication re-cycling or shutdown initiated by the IOA Gateway. The corresponding IOA Gateway APPLID is applId.

Corrective Action: No action is required.

CTMG66W TPEND EXIT INVOKED. WORKSTATION GATEWAY ID=`id` APPLID=`applId` LU=`luName` REASON=`rsn`

Explanation: The connection between IOA Gateway APPLID applId and partner or client LU luName is being taken down by the VTAM operator.

Exit TPEND is invoked with a reason code of rsn. An attempt is made to recycle communication.

Corrective Action: See the VTAM programming manual for an explanation of TPEND reason codes. Take appropriate action based on the reason code.

CTMG67W ATTN LOSS EXIT INVOKED. WORKSTATION GATEWAY ID=`id` APPLID=`applId` LU=`luName`

Explanation: The connection between partner or client LU luName and IOA Gateway APPLID applId was lost. This message is followed by message COMG68I containing VTAM information.

The IOA Gateway attempts to restart communication.

Corrective Action: With message COMG68I, determine the cause of the connection disruption. Correct it, if possible. If necessary, call your VTAM system programmer for assistance.

CTMG68I RPL6SNSI=`snsi` RPL6RC=`rc` RPL6DETP=`dept` RPLSONCD=`soncd`

Explanation: This information message follows message COMG67I. It indicates that the connection between IOA Gateway and the partner/client was lost.

This message provides VTAM information for the VTAM system programmer. RPL6 fields are documented in the VTAM Programming for LU 6.2 manual, as follows:

RPL6SNSI snsi - the section on VTAM sense codesSee also the VTAM messages and codes manual.
RPL6RC rc - the appendix on return codes
RPL6DEPT dept - at the end of ISTRPL6X DSECT (VTAM 3.3 and up)
RPLSONCD soncd - the UNBIND Type Code, documented in the VTAM programming manual under the SCIP exit routine

Corrective Action: Determine the cause of the connection disruption and correct it.

CTMG71I PROBABLE VTAM IS HALTING

Explanation: This information message follows a message which indicates that a request from VTAM, such as an APPC command or an OPEN ACB command, failed. This message indicates that the probable reason for the failure is that VTAM is going down.

This message is followed by message COMG81I, COMG84I or COMG85I, which indicates the action that will be taken by IOA Gateway.

Corrective Action: No action is required.

CTMG72I PROBABLE APPLID NOT DEFINED

Explanation: This information message indicates that the probable reason for a VTAM request failure is that the APPLID specified in the OPEN ACB command is unknown to VTAM. It follows message COMG91W, which indicates that an OPEN ACB command has failed.

Possible causes are:

The Major Node where the APPLID is defined was not activated.
The APPLID defined to VTAM does not match the APPLID defined to IOA Gateway in the ECAPARM member.

This message is followed by message COMG83E, which indicates the action that will be taken by IOA Gateway.

Corrective Action: Activate the Major Node or correct the APPLID specification.

CTMG73I PROBABLE APPLID NOT DEFINED PROPERLY

Explanation: This information message indicates that the probable reason for the VTAM request failure is that the APPLID specified in the OPEN ACB is not a valid application definition, although it is known to VTAM. This could happen, for instance, if the APPLID defined to the IOA Gateway in the ECAPARM member is incorrect, but happens to match the name of another resource known to VTAM.

This message follows message COMG91W, which indicates that an OPEN ACB command has failed. It is followed by message COMG83E, which indicates the action that will be taken by the IOA Gateway.

Corrective Action: Correct the definition of the APPLID in the ECAPARM member.

CTMG74I PROBABLE ACB HAS ALREADY BEEN OPENED

Explanation: This information message indicates that the probable reason for the VTAM request failure is that the APPLID specified in the OPEN ACB command is already open and in use by another application.

Possible causes are:

Another IOA Gateway with the same APPLID is already up.
The APPLID defined to the IOA Gateway in the ECAPARM member is incorrect, but matches another APPLID definition.

This message follows message COMG91W, which indicates that an OPEN ACB command has failed. It is followed by message COMG85I, which indicates the action that will be taken by the IOA Gateway.

Corrective Action: Correct the definition of the APPLID in the ECAPARM member, or take down one of the address spaces with the same APPLID.

CTMG75I PROBABLE APPLID DEACTIVATED

Explanation: This information message indicates that the probable reason for a VTAM request failure is that the APPLID was deactivated by a VARY NET,INACT command.

This message follows a message that indicates that a request from VTAM, such as an APPC command or an OPEN ACB command, failed. This message is followed by message COMG81I, which indicates the action that will be taken by the IOA Gateway.

Corrective Action: Activate the APPLID.

CTMG76I PROBABLE VTAM IS NOT ACTIVE

Explanation: This information message indicates that the probable reason for a VTAM request failure is that VTAM is down.

This message follows message COMG91W, which indicates that an OPEN ACB command failed. It is followed by message COMG85I, which indicates the action that will be taken by the IOA Gateway.

Corrective Action: No action is required.

CTMG77I PROBABLE PARTNER DISCONNECTED

Explanation: This information message indicates that the probable reason for a VTAM request failure is that the conversation was lost due to abend or disconnection of the partner or client.

This message follows message COMG90E, which indicates that an APPC command has failed. It is followed by message COMG81I, which indicates the action that will be taken by the IOA Gateway.

Corrective Action: Check the message issued by the partner or client and proceed accordingly.

CTMG78I PROBABLE CONNECTION LOST

Explanation: This information message indicates that the probable reason for a VTAM request failure is a communication disruption. This may be due to a resource failure on the route to the partner or client.

This message follows message COMG90E, which indicates that an APPC command has failed. It is followed by message COMG81I, which indicates the action that will be taken by the IOA Gateway.

Corrective Action: Try to determine the cause of the communication disruption and correct it.

CTMG79I PROBABLE SESSION TERMINATED

Explanation: This information message indicates that the probable reason for a VTAM request failure is that a VTAM session termination occurred.

This message follows message COMG90E, which indicates that an APPC command has failed. It is followed by message COMG81I, which indicates the action that will be taken by the IOA Gateway.

Corrective Action: Contact your INCONTROL administrator.

CTMG81I RE-START COMMUNICATION WILL BE ATTEMPTED

Explanation: This information message indicates that an attempt will be made to restart communication. Restarting communication involves preparing to receive a conversation allocation request from the partner or client LU, including opening the ACB if it is not already open.

This message follows other messages that provide details about an error that occurred.

The IOA Gateway attempts to restart communication.

Corrective Action: No action is required.

CTMG82I RE-CYCLE COMMUNICATION WILL BE ATTEMPTED

Explanation: This information message indicates that an attempt will be made to recycle communication. Communication is recycled when VTAM is going down or when the retry limit is exceeded. Recycling communication involves deallocating the conversation (if there is any), closing and then reopening the ACB, and preparing to receive a conversation allocation request from the partner or client LU.

This message follows other messages that provide details about an error that occurred.

The IOA Gateway attempts to recycle communication.

Corrective Action: No action is required.

CTMG83E THE COMM GATEWAY WILL BE SHUT DOWN

Explanation: This message indicates that the IOA Gateway will shut down. This message follows other messages that provide details about an error that occurred.

The IOA Gateway shuts down.

Corrective Action: If the shutdown is due to an error in the IOA Gateway, contact your INCONTROL administrator.

CTMG85I OPERATION WILL BE RE-ATTEMPTED AFTER ONE MINUTE

Explanation: This information message indicates that a failed operation will be retried until the retry limit is reached. This message follows other messages that provide details about an error that occurred.

The failed operation is retried. When the retry limit is exceeded, an attempt is made to recycle communication.

Corrective Action: No action is required.

CTMG90E APPCCMD `appccmd` FAILED. APPLID=`applId` R15=`r15` R0=`r0` RPL6RC=`rc` PARTNER LU=`partner_lu`

Explanation: An APPC command failed.

This message is followed by a message indicating the action that will be taken by the IOA Gateway. This message may be preceded by another message that provides more information about the error that occurred.

The following information in this message is for the VTAM system programmer:

appccmd - Command that failed
applId - APPLID that issued the failing command
r15 - Register 15 returned by VTAM
r0 - Register 0 returned by VTAM
rc - RPL6RC returned by VTAM

The following fields are documented in the VTAM Programming for LU 6.2 Guide:

APPCCMD - in the section on LU 6.2 macro instruction syntax and operands.
RPL6RC - in the appendix on return codes.
R0 and R15 - in the section on handling errors.

Corrective Action: If a second message gives a probable cause for the error, proceed according to the recommended User Response in that message. Otherwise, contact your VTAM system programmer.

CTMG91W OPEN ACB FAILED. APPLID=`applId` ACBERFLG=`erflg`

Explanation: An OPEN ACB command failed.

The following information in this message is for the VTAM system programmer:

applId - APPLID that issued the failing command
erflg - ACBERFLG returned by VTAM

ACBERFLG is documented in OPEN - Open One or More ACBs, ERROR Field, in the VTAM programming manual.

This message is followed by a message which indicates the action that will be taken by the IOA Gateway. This message may be preceded by another message which provides additional information about the error that occurred.

Corrective Action: If a second message gives a probable cause for the error, proceed according to the recommended user action for that message. Otherwise, contact your VTAM system programmer.

CTMG93W CLOSE ACB FAILED. APPLID=`applId` ACBERFLG=`erflg`

Explanation: A CLOSE ACB command has failed.

The following information in this message is for the VTAM system programmer:

applId - APPLID that issued the failing command
erflg - ACBERFLG returned by VTAM

CBERFLG is documented in "CLOSE - Close One or More ACBs, ERROR Field", in the VTAM programming manual.

This message is followed by a message that indicates the action taken by the IOA Gateway.

Corrective Action: Determine the cause of the failure from ACBERFLG. If necessary, contact your VTAM system programmer.

CTMG94W SETLOGON FAILED. APPLID=`applId` R15=`r15` R0=`r0` RPLRTNCD=`rtncd` RPLFDBK2=`fdbk2`

Explanation: A SETLOGON command failed.

The following information in this message is for the VTAM system programmer:

applId - APPLID that issued the failing command.
r15 - Register 15 returned by VTAM.
r0 - Register 0 returned by VTAM.
rtncd - RPLRTNCD returned by VTAM.
fdbk2 - RPLFDBK2 returned by VTAM.

The following fields are documented in the VTAM programming manual:

RPLRTNCD
RPLFDBK2
R0, R15 - Chapter on handling errors and special conditions.

This message is followed by a message which indicates the action that will be taken by the IOA Gateway.

Corrective Action: Determine the cause of the failure from RPLRTNCD and RPLFDBK2. If necessary, contact your VTAM system programmer.

CTMG95E APPCCMD `appc_cmd` FAILED AFTER `nn` RETRIES. APPLID=`applId` PARTNER LU=`partner_lu`

Explanation: An APPC command failed after nn retries.

The following information in this message is for the VTAM system programmer:

appc_cmd - Command that failed.
applId - APPLID that issued the failing command.

This message is followed by a message which indicates the action that will be taken by IOA Gateway. This message may be preceded by another message providing additional information about the error that occurred.

The IOA Gateway attempts to recycle communications.

Corrective Action: If a second message gives a probable cause for the error, proceed according to the user action in that message. Otherwise, contact your VTAM system programmer.

CTMG96E APPCCMD SEND NOT COMPLETED WITHIN `num` MINUTES. APPLID=`applId` PARTNER LU=`partner_lu`

Explanation: A SEND operation was not completed within the specified number of minutes.

The IOA Gateway attempts to recycle communication.

Corrective Action: Contact BMC Customer Support.

CTMG97E GENCB FAILED. APPLID=`applId` R15=`r15` R0=`r0` RPLRTNCD=`rplrc` RPLFDBK2=`fdbk2`

Explanation: The IOA Gateway issued a GENCB macro to generate a control block, but the operation failed.

The following information in this message is for the VTAM system programmer:

applId - APPLID that issued the failing command
r15 - Register 15 returned by VTAM
r0 - Register 0 returned by VTAM
rtncd - RPLRTNCD returned by VTAM
fdbk2 - RPLFDBK2 returned by VTAM

The following fields are documented in the VTAM Programming manual:

RPLRTNCD
RPLFDBK2
R0, R15 - Chapter on handling errors and special conditions

The IOA Gateway shuts down.

Corrective Action: Use the diagnostic information in the message to determine the cause of the failure. Correct the problem accordingly.

Messages CTMH00 through CTMHxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMH01I CONTROL-M HEALTH CHECKER TASK STARTED

Explanation: This information message indicates that the Health Checker task has begun.

Corrective Action: No action is required.

CTMH02I CONTROL-M HEALTH CHECKER TASK DISABLED IN CTMPARM

Explanation: This information message indicates that the Control-M parameter Use Health Checker (HCHEKER) is set to N.

Corrective Action: Enable the Health Checker task by setting the Control-M parameter Use Health Checker (HCHEKER) to Y.

CTMH03E HEALTH CHECKER IS NOT SUPPORTED IN CURRENT ZOS VERSION

Explanation: This error message indicates that the operating system does not support the IBM Health Checker component.

Corrective Action: No action is required.

CTMH04E CONTROL-M SUBTASK `subtask` HANGING

Explanation: This error message indicates that one or more Control-M subtasks has been processing the job (displayed as part of the preceding CTMH05I message) for an unreasonably long period of time. Refer to the preceding CTMH05I message lists for additional information pertaining to the job.

The Control-M Monitor continues processing as usual. The subtask continues processing the job. The delay, however, may indicate a more severe problem.

Corrective Action: Review the system log for additional messages related to the job. Then report the problem to the Control-M administrator.

If the reason for the problem is unclear, take the following actions:

Take a system (SVC) dump of the Control-M monitor’s address space, using the DUMP console command. Specify the parameter SDATA=(CSA,GRSQ,SUM,RGN,TRT).
Prepare the Control-M monitor full output and contact BMC Customer Support.

If the reason for the problem is outside of Control-M, holding the job being processed and restarting the Control-M monitor may have only a temporary effect.

CTMH05I CONTROL-M SUBTASK STATUSES

Explanation: This information message indicates the start of the status information displayed by the Health Checker task. This message is followed by additional information on subtasks being monitored and either CTMH06I or CTMH04E.

Corrective Action: No action is required.

CTMH06I CURRENT STATUS OF CONTROL-M MONITOR IS OK

Explanation: This information message indicates that all tasks being monitored are processing normally. This message is preceded by CTMH05I.

Corrective Action: No action is required.

CTMH07I CONTROL-M AJF FILE CONDITION

Explanation: This information message indicates that what follows is the current status of the Active Jobs File (AJF). The following information on the AJF is listed:

Number of entries - maximum number of entries permitted in the AJF
Size in Bytes - the amount of space used by the AJF
Free entries - the number of additional entries permitted in the AJF
Percentage used - the number of entries currently in use, expressed as a percentage of the maximum number of entries
Threshold - the Control-M monitor starts to notify the operator about AJF utilization when the number of used entries reaches this percentage of the maximum allowed

Corrective Action: No action is required.

CTMH08A HEALTH CHECKER INTERFACE IS DEACTIVATED AS RESULT OF A FAILURE. REPLY CONTINUE OR RETRY

Explanation: This message indicates that the Health Checker task has encounter a problem and has stopped processing.

The Health Checker task stops processing and waits for a reply.

Corrective Action: Enter one of the following responses:

CONTINUE - disable communication between the Health Checker interface and Control-M monitor, allowing the Control-M monitor to continue processing.
RETRY - retry the failed Health Checker task

CTMH09E CONTROL-M ACTIVE JOBS FILE UTILIZATION THRESHOLD IS REACHED

Explanation: This information message indicates that the use of the Active Jobs File (AJF) has reached the threshold. This message is preceded by CTMH07I, which lists information on the size of the AJF. For more information, see the Explanation of message CTMH07I.

When the number of entries used in the AJF reaches the threshold percentage Control-M could stop ordering jobs. The threshold percentage is specified in the Control-M parameter AJFTHRSH.

Control-M could stop ordering jobs but all other functions (such as, job submission and post-processing) continue normally.

Corrective Action: Contract your INCONTROL administrator. It may be necessary to compress the Active Jobs file or to increase its size.

CTMH0AI CURRENT STATUS OF CONTROL-M AJF FILE IS OK

Explanation: This information message indicates that the use of the Active Jobs File (AJF) has not reached the threshold. This message is preceded by CTMH07I, which lists information on the size of the AJF. For more information, see the Explanation of message CTMH07I.

Corrective Action: No action is required.

CTMH0BI THE CONTROL-M MONITOR RUNNING WITH CURRENT SET OF PARAMETERS

Explanation: This message indicates there are no differences between the parameter settings currently in use and those in the CTMPARM member.

Corrective Action: No action is required.

CTMH0BE REMOTE FORCEJOB PROCESSED WITH ERRORS ON REMOTE CTM, ID: `remote_Control-M_ID`

Explanation: Indicates that a remote FORCEJOB request that was sent to the remote Control-M failed (the remote Control-M could not force that job). It is followed by a sequence of CTMVH0EI messages detailing the response from the remote Control-M.

Corrective Action: Correct the problem indicated by the messages and then re-attempt to force the job.

CTMH0CE FOUND SOME DIFFERENCES IN CURRENT PARAMETERS SET AND CTMPARM

Explanation: This message indicates that one or more Control-M parameters, in the CTMPARM member, are not equal to the parameter setting in the running Control-M Monitor. This message precedes CTMH0DI.

The running Control-M Monitor continues processing, however, the inconsistency between the Control-M parameters could cause unpredictable results.

Corrective Action: Review the output of the message CTMH0DI and check for unexpected parameter changes.

If the differences in the parameter settings are known, perhaps as a result of using the MODIFY command, you can ignore this exception. However, if the differences are not expected, you may need to restart the Control-M monitor or refresh the Control-M parameter settings using the following command:

F CTM_monitor,NEWPARM

CTMH0DI CTMPARM COMPARATION DETAIL REPORT

Explanation: This message precedes the listing of the Control-M parameters where differences were found between the current settings and those saved in the CTMPARM member. The listing includes the following columns:

CTM parameter - the name of the Control-M parameter
Current value - parameter setting in the running Control-M monitor
CTMPARM value - parameter setting saved in the CTMPARM member

Corrective Action: No action is required.

CTMH0EI GSR:ERROR Cancel in GSR. Authorization failure, user: `user_ID` rc: `return_code`

Explanation: Follows a CTMH0BE message, providing details from the remote Control-M of why the remote Control-M could not force that job.

Corrective Action: Correct the problem indicated by the messages and then re-attempt to force the job.

CTMH11W IBM HEALTH CHECKER TERMINATED

Explanation: This message indicates that the Health Checker for z/OS (HZSPROC) is not active. As a result, the Control-M Health Checker interface suspends operations.

Corrective Action: To resume operations of the Control-M Health Checker interface, activate the Health Checker for z/OS.

CTMH18I CONTROL-M MONITOR MEMORY USAGE CHECK

Explanation: This information message indicates that the Health Checker has begun checking memory usage (Control-M Monitor Virtual Storage Consumption).

Corrective Action: No action is required.

CTMH1BI IOALOG INDEX FILE CONDITION

Explanation: This information message indicates that the Health Checker has begun checking the condition of the IOALOG INDEX file.

Corrective Action: No action is required.

CTMH1CI CURRENT STATUS OF IOALOG INDEX IS "OK"

Explanation: This information message notifies you that the health checker has completed checking the IOALOG INDEX file, and its status is OK.

Corrective Action: No action is required.

CTMH1DE CURRENT STATUS OF IOALOG INDEX IS "NOT ACTIVE"

Explanation: Use of the IOA LOG Index file is optional, but an inactive INDEX file can slow down the process of viewing IOA log messages using ORDERID.

Corrective Action: The LOG index file can be activated dynamically using the IOALOGXC utility.

CTMH1EE CURRENT STATUS OF IOALOG INDEX IS BELOW THRESHOLD OF `xx`%

Explanation: The current IOALOG Index file does not fully correspond to information contained in the IOA Log file. This can slow down the process of viewing IOA log messages using ORDERID.

Corrective Action: The LOG index file can be rebuilt dynamically by using the IOALOGI utility.

CTMH1FE AVAILABLE MEMORY {ABOVE | BELOW} 16MB IS LESS THAN THRESHOLD OF `xxx`

Explanation: The Control-M monitor is running under a memory shortage condition. This can lead the monitor to fail.

Corrective Action: Please inform the Control-M administrator.

CTMH1GE ABEND DURING UPLOAD OF TABLE tableName

Explanation: The specified table could not be uploaded from Control-M/EM to Control-M for z/OS, due to invalid data which caused the Control-M Application Server to abend.

Corrective Action: Find and correct the errors in the table in Control-M/EM, and then re-upload it to Control-M for z/OS.

CTMH30E HEALTH CHECKER REQUEST FAILED: IBM HEALTH CHECKER IS NOT ACTIVE

Explanation: This error message indicates that the Health Checker task could not be processed because the IBM Health Checker component is not running.

Corrective Action: No action is required.

CTMH31W IBM HEALTH CHECKER TERMINATED

Explanation: This warning message indicates that the IBM Health Checker was stopped or ended abnormally.

Corrective Action: No action is required.

CTMH32E IBM HEALTH CHECKER REMOTE CHECK `checkName` FAILED; REASON=`nn`

Explanation: This error message indicates that one of the following remote checks, identified by checkName in the message string, failed to process correctly.

CTMHCKPR - check for job processing delays
CTMHCKTR - report on the status of the Active Jobs File
CTMHCKMR - report on comparison of current session parameters and the parameters in CTMPARM.

The cause of the failure can be identified by the reason code, represented by nn in the message string. The following table shows possible values for nn:

Reason	Explanation
01	OPSTART failed
02	OPCOMPLETE failed
03	ADD CHECK failed
04	Obtain PAUSE
05	Pause Request failed
06	Failed to load CTMPARM

Corrective Action: No action is required.

Messages CTMI00 through CTMIxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMI01S `pgm` UNABLE TO OPEN FILE `ddName`

Explanation: The pgm program is unable to open the ddName file referenced by the specified DD name.

The ddName file may be missing. This message is accompanied by a system message explaining the cause of the problem.

The program terminates.

Corrective Action: Supply the required DD name if it is missing. Otherwise, see the accompanying system message and take appropriate action.

CTMI02S `pgm` UNABLE TO LOAD `modName`

Explanation: The pgm program is unable to load the modName module.

The modName module is probably missing from the IOA Load library.

The program is terminated.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMI03I AJF/CONDITIONS JOURNAL INITIALIZED: BLOCKSIZE `num`

Explanation: This information message indicates that the Control-M Journal file was successfully initialized during New Day processing.

The first record of the Journal file contains information relevant to the Control-M current working day.

In this message, num is the blocksize of the Journal file.

Corrective Action: No action is required.

Messages CTMJ00 through CTMJxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMJ02E `ddName` BEING FORMATTED. TRY AGAIN LATER

Explanation: The ddName file is currently being formatted.

This error message may be issued as part of the New Day procedure, or some other component that formats the file. It is also possible that a component attempted to format the file, but failed, leaving the file unusable (in status “FORMAT”).

Corrective Action: Try again later. If no component is currently formatting the file, the file must be reformatted before it can be used.

CTMJ03E `ddName` - PARM QNAME `qName1` DIFFERENT THAN IN FILE `qName2`

Explanation: QNAME qName1 defined in CTMPARM differs from QNAME qName2 specified in the file pointed to by the ddNameDD statement. The QNAMEs of the files must be identical to the QNAME specified in CTMPARM.

Processing of the current command stops with a return code of 8.

Corrective Action: Reformat the file pointed to by the ddNameDD statement, using the proper installation procedures.

CTMJ81I UTILITY IOADDR STARTED

Explanation: This information messages indicates that the IOADDR utility started.

Corrective Action: No action is required.

CTMJ82I UTILITY IOADDR ENDED

Explanation: This information message indicates that the IOADDR utility ended.

Corrective Action: No action is required.

CTMJ83S INVALID PARAMETER SPECIFICATION

Explanation: The parameter passed to the IOADDR utility was either invalid or missing.

The IOADDR utility terminates.

Corrective Action: Verify that a valid DSNAME was passed as a parameter to the IOADDR utility.

CTMJ84S OPEN OF FILE "SYSPRINT" FAILED

Explanation: Opening of the print file failed. Possible causes are:

The SYSPRINT DD statement is missing from the step.
The file allocated to the SYSPRINT DD statement is not a valid print file.

The IOADDR utility terminates.

Corrective Action: Correct the JCL for the IOADDR utility so that it contains a valid SYSPRINT DD statement.

CTMJ85S OPEN OF CONTROL-FILE FAILED. DDNAME "`ddName`"

Explanation: The IOADDR utility failed to open one of its control files.

The IOADDR utility terminates.

Corrective Action: Correct the JCL for the IOADDR utility so that it has a correct control member allocated to it.

CTMJ86S ALLOCATION FOR MEMBER `memName` LIBRARY `lib` FAILED

Explanation: Allocation of the specified member failed because the member does not exist in the specified library or is inaccessible.

The IOADDR utility terminates.

Corrective Action: Verify that the @IDCNTL control member contains a valid library and member name for each user.

CTMJ87S ALLOCATION FOR TABLE FAILED

Explanation: Allocation of one of the IOADDR members failed, because one of the members pointed to by @IDCNTL does not exist or is inaccessible.

The missing member is skipped. Processing continues for the following members.

Corrective Action: Verify that the @IDCNTL control member contains a valid library and member name for each user.

CTMJ88S BAD OP-CODE "`op_code`"

Explanation: A user table contained an invalid operation code.

The event definition with the bad OP-CODE is skipped. Processing continues with the following entries.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMJ89S LOAD FAILED FOR MEMBER "`memName`"

Explanation: Load of one the IOA modules failed.

The IOADDR utility terminates.

Corrective Action: Verify that your STEPLIB DD statement points to the IOA LOAD library.

CTMJ90S ACCESS RC=`rc` FOR LIBRARY `lib` MEMBER `memName`

Explanation: An error occurred in the IOADDR utility when reading a member from a PDS library. The return code describes the reason for the error.

Valid values for the return code (rc) are:

rc	Explanation
4	Premature end of file.
8	Storage allocation error.
12	Member not found.
16	The data set name is not the name of a PDS library.
20	The data set is not a fixed format data set.
24	Logical record length of the file is not 80.
28	The data set in use.
32	Internal error.
36	The data set is not cataloged.
40	The data set allocation failed.
44	Invalid request.
48	Internal error.
52	Error accessing the directory.

The entry that caused the error is skipped.

Corrective Action: Correct the cause of the error, and retry the operation. In case of an internal error, supply BMC Customer Support with a copy of the input file and the parameters specified for the IOADDR utility.

CTMJ91S INSUFFICIENT STORAGE FOR PROCESS

Explanation: The IOADDR utility failed to allocate storage for its operation.

The IOADDR utility terminates.

Corrective Action: Increase the REGION size.

CTMJ92S JOB `jobName` NOT FOUND IN TABLE `tableName` OF LIB `lib`

Explanation: A request to order a job could not be fulfilled because the job did not exist in the scheduling table.

The event definition pointing to the missing job is skipped. Processing continues with the subsequent entries.

Corrective Action: Add the missing definition to the specified scheduling table.

CTMJ93S BAD DATE `date` SPECIFIED

Explanation: The order date specified in the event definition is invalid.

The event definition with the bad date is skipped. Processing continues with the subsequent entries.

Corrective Action: Correct the date in the event definition.

CTMJ94I USER: `userId` TABLE: `tableName` LIBRARY: `lib`

Explanation: This information message completes a preceding message stating the reason for the error.

Corrective Action: Use this information to locate the cause of the error.

CTMJ9CE QNAME TABLE ENTRY ERROR. FLAG=`num` STC=`stcName` STR=`structName` LSN=`logStreamName` HLQ=`hiLevelQualifier`

Explanation: The IOADDC program found an invalid entry in the QNAME table for the QNAME specified by the IOADDC request.

The variables in this message are:

num - a hexadecimal number representing the communication method used to transfer the IOADDC input trigger to Control-M Possible values are:
40 - use the MVS system logger
20 - call the IOADDR routine directly
stcName - the name of the started task
structName - the name of the CF structure
logStreamName - the name of the log stream
hiLevelQualifier - the high-level qualifier of the log stream file

The IOADDC request is aborted.

Corrective Action: Rerun the IOADDI job for the specified IOA installation, and verify that it was successful.

CTMJ9DE `cbName` CONTROL BLOCK NOT FOUND - DATA SET TRIGGERING REQUEST ABORTED

Explanation: The IOADDC program was unable to find the cbName system-wide control block.

The IOADDC request is aborted.

Corrective Action: Run the IOADDI job for each IOA installation that requires it.

CTMJ9EE `qName` QNAME TABLE ENTRY NOT FOUND - DATA SET TRIGGERING REQUEST ABORTED

Explanation: The IOADDC program was unable to find an entry in the QNAME table that matched the qName QNAME.

The IOADDC request is aborted.

Corrective Action: Rerun the IOADDI job for the specified IOA installation, and verify that it was successful.

CTMJA1I IOADDS: `dsn`

Explanation: This information message indicates that the IOADDC utility was activated in an environment with no authorization to issue modify commands to the IOADDS started task. It can be used to issue a MODIFY command to IOADDS by a console automation product, for example, Control-O.

Execution continues.

Corrective Action: If you have already defined this message to your console automation software, no intervention is required. Otherwise, make sure that either IOADDC is activated in an APF-authorized environment, or that measures have been taken to handle this message.

CTMJA2S IOADDS FUNCTIONAL SERVER IS NOT OPERATIONAL. DATASET TRIGGERING REQUESTS MAY BE LOST

Explanation: The IOADDS started task was not operational during an IOADDC-related data set event. The IOADDC utility attempted to start the IOADDS started task automatically, but IOADDS was not initialized.

The event that triggered this action is not processed.

Corrective Action: Check the output of the IOADDS utility. It should point to the problem which prevented the initialization. Proceed accordingly.

CTMJA3I AJF IS BEING FORMATTED. IOADDS WILL WAIT TILL FORMAT FINISHES.

Explanation: The CONNECT DIRECT interface module has attempted to order a job as a result of a user request but the Active Jobs file is currently being formatted.

The interface module waits until the formatting has been completed, then retries the request.

Corrective Action: No action is required.

CTMJA4S SYSPLEX TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTED

Explanation: The CONNECT DIRECT interface module has attempted to read the Sysplex table and failed.

Possible causes are:

the Sysplex table is not present in the PARM library
the internal format of the table is invalid

The interface module aborts the request.

Corrective Action: Check why the Sysplex table is not in the PARM library, or why its internal format is invalid. Correct the problem and retry the request.

CTMJA5S CMMPLEX TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTED

Explanation: The CONNECT DIRECT interface module has attempted to read the CMMPLEX table and failed.

Possible causes are:

The CMMPLEX table is not present in the PARM library.
The internal format of the table is invalid.

The interface module aborts the request.

Corrective Action: Check why the CMMPLEX table is not in the PARM library, or why its internal format is invalid. Correct the problem and retry the request.

CTMJA6S SYSTEM LOGGER REQUEST `xxxxxx` FAILED: R15=`rc15` RETURN=`rcx` REASON=`rsn`

Explanation: One of the following System Logger requests failed:

DEFCFS, IXGINVNT (define coupling facility structure)
DEFLGS, IXGINVNT (define log stream)
CONLGS, IXGCONN (connect to log stream)
WRITEL, IXGWRITE (write a log stream log block)
DISLGS, IXGCONN (disconnect from log stream)
DELLGS, IXGINVNT (delete log stream)
DELCFS, IXGINVNT (delete coupling facility structure)

rc15 is the return code in Register 15 that identifies the error, and is one of the following:

Return Code	Explanation
08	Minor System Logger request error.
12	Intermediate System Logger request error.
16	Major System Logger request error.
20	Permanent System Logger request error.
28	Operating system does not support System Logger interface.

The return code rcx and reason code rsn are documented in the IBM manual MVS Programming: Assembler Services Reference, which contains the relevant system action. Each of the System Logger requests identified by the return code rc15 is in a separate section of that publication, which also contains the possible values for the return code rcx and the reason code rsn for that System Logger request.

Corrective Action: If you have any difficulty interpreting the IBM publication, contact your INCONTROL administrator.

CTMJA7E NAME/TOKEN SERVICES REQUEST `xxxxxxxx` FAILED: R15=`rc`

Explanation: One of the following MVS name/token services requests failed:

CREATE, IEANTCR (name/token create)
RETRIEVE, IEANTRT (name/token retrieve)
DELETE, IEANTDL (name/token delete)

The return code rc is documented in the IBM manual MVS Programming: Assembler Services Reference, which contains the relevant system action. Each of the name/token services requests xxxxxxxx is in a separate section of the publication, which also contains the possible values for the return code rc for that request.

Corrective Action: If you have any difficulty interpreting the IBM publication, contact your INCONTROL administrator.

CTMJA8E PARAMETER (DATA SET NAME) LENGTH ERROR - DATA SET TRIGGERING REQUEST ABORTED

Explanation: The data set name used as a CONNECT DIRECT interface trigger was not specified, or was longer than 44 characters.

The interface module aborts the request.

Corrective Action: Specify an appropriate data set name trigger, then retry the request.

CTMJA9S IOACPRM TABLE MISSING - DATA SET TRIGGERING REQUEST ABORTED

Explanation: The CONNECT DIRECT interface module attempted to read the IOACPRM table, and failed.

Possible causes are:

the IOACPRM table is not present in the PARM library
the internal format of the table is invalid

The interface module aborts the request.

Corrective Action: Check why the IOACPRM table is not in the PARM library, or why its internal format is invalid. Correct the problem and retry the request.

CTMJAAS SYSTEM LOGGER INTERFACE NOT ENABLED BY USER - DATA SET TRIGGERING REQUEST ABORTED

Explanation: The system logger interface in the IOACPRM table was not enabled.

The interface module aborts the request.

Corrective Action: Change the value of SYSTLOGR in the IOACPRM table to Y.

CTMJABW SYSTEM LOGGER INTERFACE NOT OPERATIVE - DATA SET TRIGGERING REQUEST PROCESSED BY IOADDR

Explanation: The System Logger interface is not enabled (SYSTLOGR parameter value in the IOACPRM parameters member is set to 'N') so IOADDC cannot pass the data set name argument to Control-M by the System Logger.

Instead of passing the data set name argument to Control-M using the System Logger, IOADDC directly calls to IOADDR to trigger the corresponding data set event. For more information, see the Control-M chapter in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If required, set up the System Logger interface. For information on setting up the System Logger, see the Control-M chapter in the INCONTROL for z/OS Installation Guide.

CTMJACI `qName` QNAME TABLE ENTRY SUCCESSFULLY REGISTERED

Explanation: The IOADDI job successfully registered the qName QNAME table entry.

Corrective Action: No action is required.

CTMJADE `cbName` CONTROL BLOCK CREATION ERROR - REGISTRATION ABORTED

Explanation: The IOADDI job was unable to build the cbName system-wide control block.

The IOADDI job does not register the required IOA installation.

Corrective Action: Rerun the IOADDI job for the required IOA installation, and verify that it was successful.

CTMJAEE NO AVAILABLE ENTRIES IN QNAME TABLE - REGISTRATION ABORTED

Explanation: The IOADDI job was unable to register the required IOA installation because no remaining QNAME table entries are available.

The IOADDI job does not register the required IOA installation.

Corrective Action: Delete any entries in the QNAME table that are no longer required. If all existing entries are required, prepare the Control-M monitor full output and contact BMC Customer Support.

Messages CTMK00 through CTMKxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMK40I PRIORITY PROPAGATION PROCESS STARTED

Explanation: This information message indicates that the Priority Propagation process has been started by the Control-M monitor.

Corrective Action: No action is required.

CTMK41I PRIORITY PROPAGATION PROCESS ENDED

Explanation: This information message indicates that the Priority Propagation process has ended.

Corrective Action: No action is required.

CTMK41S FILE ALLOCATED TO DDNAME "DAG2M" IS NOT YOUR CONTROL-M COMMUNICATION FILE

Explanation: The data set described by the DAG2M DD statement is not the communication file of this IOA installation. The file allocated to the DAG2M DD statement contains a different queue name from the one specified by IOA Installation Parameters.

Sysout transmission is suspended.

Corrective Action: Correct the problem and restart the job.

CTMK42E INSUFFICIENT STORAGE FOR CALCULATION

Explanation: The Control-M monitor did not have enough storage for either the Deadline Scheduling Calculation process or for the Priority Propagation process.

The process is aborted.

Corrective Action: Increase the storage for the Control-M monitor.

CTMK43W WAITING FOR DEPENDENCIES FILE. DDNAME "`ddName`"

Explanation: The Control-M monitor cannot access a file because it is being used by another component. The monitor requires exclusive access to the file.

The monitor waits for the file to be released.

Corrective Action: Check who is holding the file and have it released.

CTMK44E CANNOT ISSUE ENQ FOR COMMUNICATION FILE. DDNAME "DAG2M"

Explanation: ENQ for the remote sysout tracking communication file failed. The communication file allocated to this DD name is allocated to another tracker, or another IOA installation uses the same qname.

Sysout tracking is suspended.

Corrective Action: Correct the problem, and restart the task again.

CTMK44S QNAME MISMATCH IN DEPENDENCIES FILE

Explanation: The Dependencies file allocated to the Control-M monitor does not belong to the current installation.

The process is aborted.

Corrective Action: Verify that the correct Dependencies file is allocated to the Control-M monitor through the DAGRAPH DD statement.

CTMK45I `numRecd` JOBS RECEIVED HIGHER PRIORITY. `numHeld` JOBS HELD

Explanation:This is one of two messages with the same ID, but different text.

This information message is issued when the Priority Propagation process ends. The message indicates the number of jobs that received higher priority, and the number of jobs whose priority was not changed, that is, were held.

Corrective Action: No action is required.

CTMK46I DEADLINE SCHEDULING PROCESS STARTED

Explanation: This information message indicates that a request to resolve all deadline scheduling requests was received either from a modify command, or from a user entering command REFRESH in the Jobs Dependencies screen.

The Control-M monitor resolves all deadline scheduling definitions.

Corrective Action: Wait for message JDLK47I or CTMK47I, to signal the end of the process.

CTMK47E INVALID RC FROM CTMG2M, FUNCTION=`func` RC=`rc`

Explanation: Invalid return code from the CTMG2M internal module. The return code was not one typically expected after the particular routine.

The variables in this message are:

func - the function in which the error occurred
rc - the return code from CTMG2M

Sysout transmission is suspended.

Corrective Action: Notify your INCONTROL administrator.

CTMK47I DEADLINE SCHEDULING PROCESS ENDED

Explanation: This information message indicates that the Control-M monitor successfully finished resolving all deadline scheduling definitions. This message is accompanied by message JDLK48I or CTMK48I which displays the number of updated jobs.

Corrective Action: No action is required.

CTMK48I num1 JOBS DUE OUT TIME UPDATED. `num2` JOBS HELD/FINISHED

Explanation: This information message indicates that the Control-M monitor successfully finished resolving all deadline scheduling definitions.

The variables in the message are:

num1 - the number of jobs with DUE OUT times that were updated
num2 - the number of jobs that were not updated, because
- the job was held
- the job ended
- the job record was not available for change

This message follows the CTMK47I message.

Corrective Action: No action is required.

CTMK48S LOADING OF CTMCSI FAILED

Explanation: Loading of the CTMCSI module failed. Possible causes are:

The IOA LOAD library is not in the load modules search list.
Insufficient memory is available to load the CTMCSI member.
The CTMCSI module does not exist in the LOAD library.

Sysout transmission is suspended.

Corrective Action: Correct the problem and restart the job.

CTMK49E DEADLINE SCHEDULING FACILITY IS DISABLED. PROCESSING STOPPED

Explanation:This is one of two messages with the same ID, but different text.

A request has been made to resolve deadline scheduling, but the Deadline Scheduling Facility has not been enabled in the Control-M defaults member.

Deadline scheduling is not performed.

Corrective Action: Ask your INCONTROL administrator to enable the Deadline Scheduling Facility in the Control-M default parameters member.

CTMK50I INITIALIZATION OF DEPENDENCIES FILE COMPLETED

Explanation: This information message indicates that the Dependencies file was successfully formatted and is ready for use. The current dependencies between jobs can be viewed after entering the REFRESH command from the appropriate screen.

Corrective Action: No action is required.

CTMK50S CONTROL-M COMMUNICATION FILE WAS NOT BUILT

Explanation: Control-M communication file could not be created.

The job terminates with errors.

Corrective Action: Look for a earlier error message that describes the cause of the error.

CTMK51I BUILDING OF CONTROL-M COMMUNICATION FILE ENDED

Explanation: This information message is the normal termination message issued after formatting the Control-M communication file.

Corrective Action: No action is required.

CTMK52E OPEN OF CONTROL-M COMMUNICATION FILE FAILED. DDNAME "DAG2M"

Explanation: Open of data set referenced by the DAG2M DD statement failed. The data set described by the DAG2M DD statement is the communication file between the Receiver and Control-M monitor.

If the message occurred under the Receiver address-space, the sysout transmission is suspended. If the message occurred under Control-M monitor, the monitor shuts down.

Corrective Action: Correct the problem, and restart the job.

CTMK53E I/O ERROR IN CONTROL-M COMMUNICATION FILE. DDNAME "DAG2M"

Explanation: I/O error occurred while working with the Control-M communication file. The data set described by the DAG2M DD statement is the communication file between the Receiver and Control-M monitor. This error is issued when an error occurred during a read or write operation.

If the message occurred under the Receiver address space, the sysout transmission is suspended. If the message occurred under the Control-M monitor, the monitor shuts down.

Corrective Action: Verify that the JCL for the data set is referred to by the DAG2M DD statement. If so, format the data set. To build the FORMG2M job, use the TAILOR JOB option, available from ICE by selecting Maintain your Environment => ICE refresh=> OPTION 3.

CTMK53S TOO MANY INTERJOB CONNECTIONS

Explanation: The number of prerequisite conditions for dependency calculations exceeds the maximum number supported. The maximum number of conditions is ten times the maximum number of records in the Active Jobs file.

The dependency calculation process is aborted.

Corrective Action: Increase the size of the Active Jobs file.

CTMK55W DEADLINE SCHEDULING INTERNAL ERROR - DIAGNOSTIC DUMP PRODUCED

Explanation: The Control-M monitor encountered an internal error during REFRESH processing in the Control-M Active Environment screen.

The system produces a diagnostic dump, and continues processing.

Corrective Action: Ask your system programmer to record the error message, the diagnostic dump, and the Control-M monitor full output; and contact BMC Customer Support.

CTMK56E "DACOMPRM" CONTAIN INVALID CARD `sequential_num` DATA=`data`

Explanation: The $GTWMPRM member in the IOA COMMCNTL library, which was referenced by the DACOMPRM DD statement, contains an invalid statement. This member contains SYSDATA sysout tracking and transfer parameters.

The variables in this message are:

sequential_num - the relative number of the invalid statement in the member
data - the contents of the invalid statement

Sysout transmit is suspended.

Corrective Action: Correct the invalid statement, and restart the job.

CTMK56S INVALID INPUT TO SHIFT. DATA SHOULD BE +NNN/-NNN

Explanation: The user specified invalid parameters for operator command SDOUT.

The operator command is ignored.

Corrective Action: Specify valid parameters for operator command SDOUT. See the Control-M chapter of the INCONTROL for z/OS Administrator Guide for a details about this operator command.

CTMK57E "DACOMPRM" CONTAINS DUPLICATE CARD `sequential_num` DATA= `data`

Explanation: The $GTWMPRM member in the IOA COMMCNTL library, which was referenced by the DACOMPRM DD statement, contains a duplicate statement. This member contains SYSDATA sysout tracking and transfer parameters.

The variables in this message are:

sequential_num - the relative number of the duplicate statement in the member
data - the contents of the duplicate statement in the member

Sysout transmit is suspended.

Corrective Action: Correct the problem, and restart the job.

CTMK57I `shiftnum` JOBS DUE-OUT TIME SHIFTED. `heldnum` JOBS HELD

Explanation: This information message is issued after successful execution of operator command SDOUT.

The variables in this message are:

shiftnum - the number of jobs for which the DUE OUT time was shifted the requested number of minutes
heldnum - the number of jobs that are currently in HELD status and were therefore not shifted

Corrective Action: No action is required.

CTMK58E UNABLE TO OPEN PARAMETER FILE. DDNAME "DACOMPRM"

Explanation: Unable to open the $GTWMPRM member in the IOA COMMCNTL library, which was referenced by the DACOMPRM DD statement. This member contains SYSDATA sysout tracking and transfer parameters.

Sysout transmit is suspended.

Corrective Action: Correct the problem, and restart the job.

CTMK59E PARAMETER FILE IS EMPTY. DDNAME "DACOMPRM"

Explanation: The $GTWMPRM member in the IOA COMMCNTL library, which was referenced by the DACOMPRM DD statement, is empty. This member should contain SYSDATA sysout tracking and transfer parameters.

Sysout transmit is suspended.

Corrective Action: Correct the problem, and restart the job.

CTMK60E PARAMETER `parm` DOES NOT EXISTS IN "DACOMPRM" FILE

Explanation: The parm mandatory parameter does not exist in the $GTWMPRM member in the IOA COMMCNTL library, which was referenced by the DACOMPRM DD statement. This member contains SYSDATA sysout tracking and transfer parameters. The parm parameter is mandatory.

Sysout transmission is suspended.

Corrective Action: Add the missing parameter to the $GTWMPRM member in IOA COMMCNTL library, and restart the job.

Messages CTML00 through CTMLxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTML00I CONTROL-M MONITOR `monName` PROCESSING SUSPENDED

Explanation: This information message indicates that the Control-M monitor has stopped processing jobs temporarily to allow the New Day procedure to begin execution.

Control-M suspends processing at the time specified in CTMPARM to allow the New Day procedure to run.

The Control-M monitor remains suspended until the New Day procedure ends. At the successful completion of the New Day procedure, the monitor resumes normal execution.

Corrective Action: No action is required.

CTML01I CONTROL-M MONITOR `monName` PROCESSING RESUMED

Explanation: In general, this message indicates that the Control-M monitor resumed processing jobs after the New Day procedure completed successfully. However, under the Control-M monitor operator command /F CTMTROLM,NEWDAY=NOW,ORDERONLY, this message can appear before the Newday procedure ends.

Corrective Action: No action is required.

CTML02I CONTROL-M MONITOR `monName` NEW DAY PROCEDURE COMPLETE

Explanation: This message indicates that all phases of New Day Processing for the specified monitor ended successfully. However, under the Control-M monitor operator command /F CTMTROLM,NEWDAY=NOW,ORDERONLY, this message can appear before the Newday procedure ends.

The Control-M monitor resumes execution.

Corrective Action: No action is required.

CTML03W START OF NEW DAY PROCEDURE NOT DETECTED

Explanation:Highlighted, unrollable message.

The Control-M monitor received no indication that the New Day procedure began processing.

The Control-M monitor requests the start of the New Day procedure, and periodically checks the progress of the procedure. This message is issued when the monitor does not receive any indication that the New Day procedure started executing.

A common cause for this message is that the CTMCHK program, which runs at the beginning of the New Day procedure, has detected that the New Day procedure has already been run.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: No action is required.

CTML04W NEW DAY END OF AJF FORMATTING NOT DETECTED

Explanation:Highlighted, unrollable message.

The Control-M monitor detected that the formatting of the Active Jobs file (AJF) did not complete successfully within a specified time interval.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: No action is required.

CTML05W NEW DAY PROCEDURE ERROR - PHASE `phase_num`

Explanation:Highlighted, unrollable message.

During follow-up of the New Day procedure, the Control-M monitor detected an abnormal condition.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: Reply R for retry. If the message is reissued, note the phase number and reply E to terminate the monitor. To reactivate the monitor, run the Control-M New Day procedure, and when it completes successfully, restart the monitor. Give BMC Customer Support the phase number specified in this message and the Control-M monitor full output.

CTML06W REPLY "R" FOR RETRY OR "E" FOR END

Explanation:Highlighted, unrollable message.

While checking the progress of the New Day procedure execution, the Control-M monitor detected an error.

This message is accompanied by a message explaining the cause of the problem.

The Control-M monitor waits for a reply to this message.

Corrective Action: Type R or E and press Enter, with the following results:

R - the Control-M monitor waits an additional intervalIssue this reply after all problems with the New Day procedure are resolved so that the monitor will resume normal execution.
E - the Control-M monitor stops execution

CTML07W CONTROL-M MONITOR `monName` WAITING FOR NEW DAY PROCEDURE

Explanation: Normal message of Control-M monitor when it stops processing jobs temporarily to allow the New Day procedure to begin execution.

Control-M suspends processing at the time specified in CTMPARM to allow the New Day procedure to run.

The Control-M monitor remains suspended until the New Day procedure is successfully completed. Upon successful completion of the New Day procedure, the monitor resumes normal execution.

Corrective Action: No action is required.

CTML08W END OF NEW DAY PROCEDURE NOT DETECTED

Explanation:Highlighted, unrollable message.

Control-M monitor found no indication that New Day procedure completed execution.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: No action is required.

CTML09E DUAL FILES ALLOCATION ERROR. PROCESSING CONTINUES DUE TO SYSTEM PARAMETERS

Explanation:Highlighted, unrollable message.

Allocation of the dual IOA Conditions file or the dual Active Jobs file (AJF) failed, but processing continues because system parameters have indicated that this condition should be ignored.

Wish WM1944 in the IOADFLTS member of the DOC library was activated to allow an allocation error for dual files to be ignored. (If the wish has not been applied when an allocation error occurs, Control-M terminates execution.)

The Control-M monitor continues normal execution.

Corrective Action: If you require dual file processing:

Bring down the Control-M monitor;
Determine the cause of the allocation error and correct it;
Bring up and reactivate the Control-M monitor.

CTML0AI RUNL0AI NEWDAY PARAMETERS SET: `expression`

Explanation: This message is issued in response to the following operator command:

F CONTROLM,NEWDAY=expression

Special NEWDAY processing is performed as specified in expression. For more information, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Corrective Action: No response required.

CTML0BI NEWDAY PROCESS SCHEDULED FOR `hh:mm` WILL BE BYPASSED

Explanation: In response to the F CONTROLM,NEWDAY=SKIP operator command, Newday processing is skipped.

NEWDAY processing normally scheduled to begin at hh:mm is bypassed due to the special NEWDAY command. For more information regarding the special NEWDAY commands, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Corrective Action: No response required.

CTML0CI NEWDAY PROCESS HAS BEEN BYPASSED

Explanation: This informational message is issued at the time scheduled for Newday processing (according to the DAYTIME parameter in CTMPARM). Newday processing is skipped as a result of one of the following commands:

F CONTROLM,NEWDAY=SKIP
S CONTROLM,NEWDAY=SKIP

Newday processing is skipped. For more information regarding the special NEWDAY commands, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Corrective Action: No response required.

CTML0DE NEWDAY COMMAND NOT 'SKIP' - IGNORED

Explanation: The S CONTROLM,NEWDAY=expression command was entered with an invalid value of expression. In this command, the only valid value for expression is SKIP. For more information, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

The command is ignored

Corrective Action: Correct and re-enter the NEWDAY command.

CTML10I RESUME REQUEST ACCEPTED

Explanation: This information message indicates that the RESUME request submitted by the user has been accepted.

Corrective Action: No action is required.

CTML11W AJF/CONDITION JOURNALING DISABLED

Explanation: The Control-M monitor stopped journaling updates to the Active Jobs file due to a detected error.

The error which caused journaling to be terminated is described in earlier messages.

WTOR message CTML12W is displayed, enabling the user to continue without the Journal facility or to shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

CTML12W REPLY ‘C’ CONTINUE WITHOUT JOURNALING, ‘I’ INITIALIZE, OR ‘E’ END

Explanation: This WTOR message is displayed when the Control-M Journaling facility is shut down.

This message may be preceded by messages explaining the reason for Journaling facility shutdown. This message also appears after running the restoration utility successfully to provide an opportunity to reset the journal file. The user can run the restoration utility repeatedly (perhaps to different endtimes) before initializing the journal file.

Responses to this WTOR message allow the user to continue Control-M without journaling, or to shut down Control-M so that a problem can be fixed.

The Control-M monitor waits for a reply to this message.

Corrective Action: See preceding messages for information describing why journaling was stopped.

Specify one of the following values as a response to this message:

C - Continue normal execution without updating the Journal file. Restoration of the Active Jobs file will not include updates made after Journaling was stopped.
I - Re-initialize the journal file. The Control-M monitor continues normal processing, including journaling.
E - Stop execution of the Control-M monitor.

CTML13I CONTROL-M MONITOR CONTINUING WITHOUT JOURNALING

Explanation: This information message is issued when the user specified C in response to WTOR message CTML12W.

The Control-M monitor continues normal execution. The Journal file is no longer updated.

Corrective Action: No action is required.

CTML14E JOURNAL FILE IS NOT SYNCHRONIZED WITH NEWDAY PROCESSING

Explanation: During Control-M monitor startup, the Control-M monitor found records in the journal file that have no corresponding data in the Active Jobs file.

The Control-M monitor stops journaling, and displays message CTML12W to enable continuation without the Journaling facility, shut down of the Control-M monitor, or re-initialization of the journal file.

Corrective Action: Reply to message CTML12W. If the error persists after the Control-M monitor is restarted, contact your INCONTROL administrator.

CTML15E OID=`orderId` BAD MIJ POINTER. MIJ RBA: `rba` ERROR: `errCode`

Explanation: The pointer to the sysout information for a job is incorrect. This is probably caused by corrupt data on the Active Jobs File (AJF).

The incorrect pointer is cleared.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTML16E COMMAND IGNORED - CURRENT `fileName` STATUS: `fileStatus`

Explanation: The user attempted to enable/disable the Control-M Journal or History allocation for space reuse functions. However, the current fileStatus status of this facility already complies with the user request.

The command is ignored.

Corrective Action: No action is required.

CTML16I FOLLOWING BYPASS OPTIONS SET FOR THIS JOB: `bypassOptions`

Explanation: This information message indicates that the job's Bypass options have been changed by an online user, and lists the Bypass options that are currently set for this job (or NONE if no Bypass options are currently set).

Corrective Action: No action is required.

CTML17I CURRENT ACTIVE JOBS FILE UTILIZATION: `nn`%

Explanation: This information message is issued in conjunction with message CTM863W, which indicates that the Active Jobs file (AJF) is nearly full. Both messages are issued when the threshold value specified by the AJFTHRSH CTMPARM parameter is reached.

Corrective Action: Increase the size of the AJF using the CTMCAJF utility.

CTML18I COMMAND RECEIVED: `cmd`

Explanation: This information message displays the MODIFY command entered for the Control-M monitor.

Corrective Action: No action is required.

CTML19I QUIESTIME IS SET: `yyyy`

Explanation: This information message displays the current value of QUIESTIME (the Control-M monitor planned shutdown time), where yyyy is one of the following values:

hhmm - the planned shutdown time (based on a 24-hour clock) set by the QUIESTIME command
NOW - the submission of any job has been stopped
OFF - all QUIESTIME requests have been cancelled

This message is added to the IOA Log.

Corrective Action: No action is required.

CTML1CW TASK CTMWOT PROCESSING NOT SUSPENDED FOR MORE THAN 01 MINUTES

Explanation: The Control-M monitor shutdown was not successful and the New Day procedure could not start because the CTMWOT task has been busy processing jobs for some time.

Corrective Action: If the New Day procedure is delayed for a long time, try restarting the monitor. If the problem persists, contact BMC Support.

CTML31E NO SPACE FOR QUANTITATIVE RESOURCE `resourceName`. NOTIFY YOUR IOA ADMINISTRATOR

Explanation: A resource (resourceName) could not be acquired because the Quantitative Resource List is full.

Resource acquisition is delayed until enough space is regained in the Quantitative Resource List in the Control-M Resources file. This message is not issued more often than once a minute.

Corrective Action: Ask your INCONTROL administrator to increase the logical record length of the Control-M Resources file. If the logical record length is already set to the maximum length allowed, wait until previously acquired quantitative resource entries are freed when jobs end. A third alternative is to have the INCONTROL administrator make more room available by deleting unused quantitative resource definitions.

CTML32E INVALID "SNRSDRNG" PROFILE VALUE. DEFAULT USED"

Explanation: The value of profile variable SNRSDRNG is invalid. Profile variable SNRSDRNG is used to establish a different date range in the Manual Conditions file.

The default value for the variable is used.

Corrective Action: Correct the value of this variable to ALL, MONTH, or ddd, where ddd is a number of days.

CTML33E INVALID "SRESDRNG" PROFILE VALUE. DEFAULT USED"

Explanation: The value of profile variable SRESDRNG is invalid. Profile variable SRESDRNG establishes a different date range in the IOA Conditions file.

The default value for the variable is used.

Corrective Action: Correct the value of this variable to ALL, MONTH, or ddd, where ddd is a number of days.

CTML38S ERROR READING MEMBER `tbl_mem` FROM DATASET `lib`. RC=`rc`.

Explanation: Reading the tbl_mem table member failed.

The order request could not be done either because the library did not exist, or could not be allocated, or the table member was not found.

The CTMJOB program ends with errors.

Corrective Action: Check that the order request is given to an existing 80-bytes record length library, and the member can be accessed. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

CTML39E INVALID DATE `date` IN ORDER REQUEST

Explanation: The date specified in the order request is not a valid date.

The CTMJOB program ends with errors.

Corrective Action: Check that the specified date is specified correctly according to your installation standards.

CTML40E JOB `jobName` NOT FOUND IN TABLE `tbl_mem` DSN `lib`

Explanation: The jobName job was not found in the member specified in the order request.

The keyword job causes a selective order to be made for one job from the table member. This message is issued if the specified job cannot be found.

The CTMJOB program ends with errors.

Corrective Action: Check that the specified job exist inside the table member.

CTML41E MISSING OBLIGATORY PARAMETER `keyName` IN ORDER REQUEST

Explanation: The specified parameter was not given in the order request.

Some parameters are obligatory in each order request. Failing to specify one of them results in this message being issued.

The CTMJOB program ends with errors.

Corrective Action: Supply the missing parameter.

CTML42E MUTUALLY EXCLUSIVE KEYWORDS SPECIFIED IN ORDER REQUEST

Explanation: Two keywords which are mutually exclusive where given in the same order request.

Certain keywords, such as DSNAME and DDNAME, cannot appear together on the same order request.

The CTMJOB program ends with errors.

Corrective Action: Specify one of the keywords.

CTML43I NEW DAY PROCEDURE COMPLETED SUCCESSFULLY

Explanation: This information message indicates that the New Day procedure ended successfully. The CTMEDA program is executed as the last step in the New Day procedure to inform the Control-M monitor that the procedure ended successfully.

The Control-M monitor resumes execution.

Corrective Action: No action is required.

CTML43W DASTAT DD CARD MISSING

Explanation: The DASTAT DD statement is missing from the file allocation of the job step.

This warning message is issued by the CTMJOB program.

The Automatic Tape Adjustment facility is skipped. Jobs are ordered, but required resource quantities are not computed for these jobs.

Corrective Action: Add the DASTAT DD statement for future runs.

CTML44E NEW DAY PROCEDURE ENDED WITH ERRORS

Explanation:Highlighted, unrollable message.

The last phase in the New Day procedure, the CTMEDA program, ended with errors. This message follows a message that describes the specific cause of the error.

The Control-M monitor remains in a suspended state.

Corrective Action: Correct the error according to the description in the previous message and rerun the New Day procedure to invoke the CTMEDA program.

CTML44W AUTO TAPE DRIVE RESOURCE ADJUSTMENT IS BYPASSED DUE TO PREVIOUS MESSAGE

Explanation: This warning message indicates that the Automatic Tape facility cannot adjust resources for jobs currently being processed.

This is a summary message. It is preceded by a message that describes the reason for the error.

The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the quantity of required resources.

Corrective Action: View the error message that precedes this message and correct the problem described there.

CTML45E ERROR ANALYZING PARM MEMBER "UNITDEF" AT LINE `lineNum`

Explanation: An invalid definition was found in the UNITDEF parameter member.

The UNITDEF parameter member associates logical names to physical resources.

In this message, lineNum is the line number in the UNITDEF parameter member where the error occurred.

Resource definition example in the UNITDEF file:

CARTRIDGE=(0480-0483,0440-0445,0300-031F,0552-0553,0556-0557),DESC=3490 RANGE

The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the required amount of resources.

Corrective Action: Correct the error at the specified line. View the description in the UNITDEF file supplied during the installation.

CTML46W DAUNITDF DD CARD MISSING

Explanation: The UNITDEF DD statement is missing.

This warning message is issued by the CTMJOB program.

The Automatic Tape Adjustment facility is skipped. Jobs are ordered without computing the required amount of resources.

Corrective Action: Add the UNITDEF DD statement to the JCL stream.

CTML47S GETMAIN FAILED IN CTMATD AUTO TAPE PROCESSING

Explanation: The Control-M Daily Subsystem stopped due to insufficient memory.

The Daily job stops execution.

Corrective Action: Increase the region size defined in the Daily job and rerun the job.

CTML49W NOT ALL CONDITIONS IN JOB COULD BE ADJUSTED

Explanation: The requirement for prerequisite conditions for a job which is part of a group were not deleted.

This message accompanies message JOBL48W.

The job is ordered prerequisite condition requirement intact.

Corrective Action: Determine if the condition prevents the job from running. If so, add the required condition manually in screen 4 or erase the requirement for the condition from the job in zoom screen 3.Z.

CTML4XE YOU ARE NOT AUTHORIZED TO USE THIS OPTION

Explanation: An option was requested for which there is no authorization. The INCONTROL administrator can authorize or deny use of certain options for certain users.

Corrective Action: To get authorization to use the option specified, contact your INCONTROL administrator.

CTML50E DYNAMIC ORDER FAILED

Explanation: A request to dynamically insert a job into a Group Entity that is already on the Active Jobs file has failed. The reason for the failure is detailed in an accompanying message.

Dynamic ordering of the job was not performed.

Corrective Action: Check the accompanying message to determine the cause of the failure, and respond accordingly.

CTML53E SMART TABLE `table_name` RBA `rba` IS FULL. NO MORE JOBS CAN BE DYNAMICALLY INSERTED

Explanation: A request to dynamically insert a job into a SMART Table in the AJF failed, because the SMART Table already contains the maximum number of jobs allowable.

The job is not ordered.

Corrective Action: No action is required.

CTML56E SPECIFY EITHER JCL LIBRARY OR SCHEDULE LIBRARY INFORMATION

Explanation: Parameters were specified for both the JCL library mode and the scheduling library mode. Only one mode can be used at a time. The AutoEdit simulation program processes only one mode per invocation. The mode is determined by the first type of input parameter encountered.

Corrective Action: Delete all parameters pertaining to the mode to be ignored.

CTML61E COPY TO HISTORY FILE FAILED: `rsn` REASON CODE: `rc`

Explanation: An error occurred while copying records from the Active Jobs file to the History Jobs file.

The variables in this message are:

rsn - the cause of the error.
rc - the reason code, containing additional information in certain cases

The Control-M New Day procedure terminates.

Corrective Action: Correct the cause of the error and rerun the Control-M New Day procedure. The enhanced checkpoint record can be used to continue the New Day procedure processing from the point at which the error occurred.

CTML63E HISTORY FILE PROCESSING MODULE NOT FOUND

Explanation: The attempt to load the CTMHCP or CTMFRH module failed. The name of the module that was not loaded appears in a previous error message. The load may have failed because the module does not exist in the IOA Load library.

The Control-M New Day procedure terminates.

Corrective Action: If History Jobs file processing is specified in the CTMPARM member, verify that the IOA Load library contains the required module.

CTML64I CTMFRM IS RUNNING IN HISTORY FILE CLEANUP MODE

Explanation: This information message indicates that the CTMFRM utility is currently cleaning the History Jobs file.

Corrective Action: No action is required.

CTML65W HISTORY FILE FREESPACE THRESHOLD REACHED

Explanation: This message is issued during New Day processing when the free space that remains in the History file (HST) will not be enough to accommodate the entire Active Jobs file (AJF) during execution on the next new day. In other words, the free space in the HST file is not enough to support a case where all the jobs in the AJF need to be moved to the HST during execution on the next new day.

When the HST is full, New Day processing stops. Therefore, it is highly recommended that you prepare enough free space prior to tomorrow's New Day processing.

Corrective Action: Perform the following actions:

Use the CTMHCLN utility with specific SELECT statements to remove records that are no longer required (for example, based on date).
If the error message is still displayed, use the CTMHCOP utility to increase the size of the History file.

CTML66S OPEN OF CONTROL-M HISTORY FILE FAILED. DDNAME "DAHIST"

Explanation: The Control-M History Jobs file (HST) defined in the DAHIST DD statement could not be opened. The New Day procedure calls the program that issues this message.

A possible cause of this message is that the DAHIST DD statement is missing.

Program execution stops with a condition code of 08.

Corrective Action: Add the statement KEY=DAHIST to the ALCMDAS member in the IOA ENV library, and rerun the DELARCH step of the New Day procedure.

CTML67S INTERNAL ERROR - ARCHIVED SYSOUT POINTER IS INVALID. ORDERID: `jobId`

Explanation: During the New Day procedure, the Control-M Active Jobs file (AJF) was found to be corrupt, due to an internal error. The archived sysout of a job cannot be read.

In this message, jobId is the identity of the job that produced the archived sysout that cannot be read.

The New Day procedure does not delete the archived sysout for the jobId job.

Corrective Action: No action is required.

CTML71E INVALID RECORD FOUND ON AJF - FILE USAGE VERIFICATION SKIPPED

Explanation: The CDAM file deletion utility detected an invalid record type when verifying the CDAM records in the Active Jobs file (AJF). Before deleting a CDAM file, the CDAM file deletion utility verifies that the file names in the JOBLIST file are not referenced by any jobs in the AJF.

Verification of the AJF is aborted, and deletion of CDAM files proceeds based on previous checks of the AJF.

Corrective Action: Check the integrity of the AJF with the IOAVERFY utility.

CTML81E INVALID OPTION, SPECIFY "U" (UTIL),"4" (4HRA),"E" (EXTERNAL), "M" (MVA)

Explanation: You entered an invalid type for the Load-Index.

Corrective Action: Enter one of the valid types listed in the message.

CTML82E INVALID OPTION, SPECIFY 'ACCUM','MAXLPAR','MINLPAR', 'MAXCPC','MINCPC'

Explanation: You entered an invalid value in the Based On field. This field specifies the source of data for setting thresholds.

Corrective Action: Enter one of the valid values listed in the message.

CTML83E LOAD-INDEX WITH THE SAME NAME ALREADY EXISTS.

Explanation: You entered a Load-Index name that is already in use by a previously defined Load-index.

Corrective Action: Correct the Load-Index name.

CTML84I LOAD-INDEX `Load-Index_name` DELETED

Explanation: The Load-Index was deleted successfully, as requested.

Corrective Action: No action is required.

CTML86E INVALID LOAD-INDEX NAME.

Explanation: You entered a Load-Index name that is longer than the maximum allowed 20 characters (for most types) or 16 characters (for type M).

Corrective Action: Correct the Load-Index name.

CTML87E INVALID THRESHOLD.

Explanation: The minimum threshold of a load level must be higher than the threshold of any lower load level.

Corrective Action: Correct the invalid threshold.

CTML88E INVALID OPTION (USE "Y" OR BLANK)

Explanation: You entered invalid text in the Home line of the >Include section in Load-Index definitions. In the Home line, you can set the scope of LPARs that are associated with Control-M's Global Monitor (the GSM).

Corrective Action: For each of the items displayed in the Home line, either enter a Y or leave the field blank.

CTML89I LOAD-INDEXES WERE SUCCESSFULLY SAVED.

Explanation: Changes in the definitions of Load-Indexes were successfully saved. The changes take effect only after Load-Indexes are applied (using the APPLY command or Exit Option 3) or after Control-M monitor is recycled.

Corrective Action: No action is required.

CTML8AI LOAD-INDEXES WERE SUCCESSFULLY SAVED AND APPLIED.

Explanation: Changes in the definitions of Load-Indexes were successfully saved. The changes will take effect immediately.

Corrective Action: No action is required.

CTML8CE INVALID LEVEL, SPECIFY "CRITICAL","V-HIGH","HIGH","MEDIUM","LOW"

Explanation: The threshold load level that you entered for the Load-Index is invalid.

Corrective Action: Enter one of the valid levels listed in the message.

CTML8DE INVALID LEVEL, SPECIFY "CRITICAL","V-HIGH","HIGH","MEDIUM","LOW","IDLE"

Explanation: The Override action could not be performed on the Load-Index, because you entered an invalid load level.

Corrective Action: Enter one of the valid levels listed in the message.

CTML8FE INVALID SORT COMMAND, SPECIFY "NAME","TYPE","SETAT","LEVEL"

Explanation: You entered an invalid column name in the SORT command on the Load-Indexes Status screen

Corrective Action: In the SORT command, enter one of the valid values listed in the message.

CTML8GI NAME=`Load-Index_name` TYPE=`type` DESC=`description`

Explanation: First line of detailed information provided by CTMAPI for the listed Load-Index.

Corrective Action: No action is required.

CTML8MI `Load-Index_details`

Explanation: Third line of detailed information provided by CTMAPI for the listed Load-Index.

Corrective Action: No action is required.

CTML8NI LEVEL=`level` OVERRIDDEN=[Y|N] SET AT=`timestamp` BY=`initiator` NOTE=`note`

Explanation: Second line of detailed information provided by CTMAPI for the listed Load-Index.

Corrective Action: No action is required.

CTML8OW LOAD-INDEXES ARE EDITED BY USER:`userName` SYSTEM:`systemName`, BROWSE ENFORCED.

Explanation:Another user is currently editing Load-Indexes. The Load-Indexes Definition screen is displayed in Browse mode.

Corrective Action: Try again later, in coordination with the specified user.

CTML8PE INVALID LOAD-INDEX NAME, NAME LIMITED TO 16 CHARS FOR MAINVIEW ALARM

Explanation: The name that you entered for the new Load-Index is too long. MVA-type Load-Index names are limited to 16 characters.

Corrective Action: Modify the name of the Load-Index.

CTML8QW MAINVIEW ALARM LOAD-INDEX DEFINED BUT COLLECTION DISABLED

Explanation: The new MVA-type Load-Index that you defined was saved successfully. However, data will not be collected for this type of Load-Index because the OPTMVLID parameter was set to N.

Corrective Action: If you want load levels set for MVA-type Load-Indexes, set parameter OPTMVLID to Y.

CTML8RW MAINVIEW ALARM LOAD-INDEX FOUND BUT COLLECTION DISABLED

Explanation: The list of Load-Indexes contains MVA-type Load-Indexes. Data will not be collected for this type of Load-Index because the OPTMVLID parameter was set to N.

Corrective Action: If you want load levels set for MVA-type Load-Indexes, set parameter OPTMVLID to Y.

Messages CTMM00 through CTMMxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMM01W AJF/CONDITIONS JOURNALING TERMINATED - RESTORATION BEYOND THIS TIME NOT POSSIBLE

Explanation: Logging to the journal file was terminated due to a detected error.

This message is preceded by a message indicating the cause of the error.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W, which asks the operator how the monitor should proceed.

Corrective Action: Respond to message CTML12W.

CTMM02I AJF/CONDITIONS JOURNALING STARTED

Explanation: This information message indicates that Control-M started logging updates to the Journal file.

Changes made to the Active Jobs file and to prerequisite conditions in the IOA Conditions file are recorded in the Journal file.

Corrective Action: No action is required.

CTMM03E `text`

Explanation: This message is produced if an abend occurs while Control-M is writing to the Journal file.

The Control-M monitor displays data about the abend. (meaning the text in this message).

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

CTMM04I AJF/CONDITIONS JOURNALING CLOSED NORMALLY

Explanation: This information message indicates that Control-M Journaling ended normally.

The Journaling facility was terminated in response to an operator command, or as part of Control-M shutdown.

Corrective Action: No action is required.

CTMM05S AJF/CONDITIONS JOURNALING INITIALIZATION FAILURE

Explanation: The Control-M journaling facility could not be started because the Journal file or another file required for journaling could not be opened.

The above message describes the reason for the problem.

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W, which asks the operator whether to continue without journaling or shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

CTMM06S JOURNAL FILE RECORD 0 FORMAT ERROR

Explanation: The record length of the Control-M journal file was incorrect.

This message is preceded by a message describing the specific cause of the problem.

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W, which asks the operator whether to continue without journaling or to shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

CTMM07S JOURNAL/AJF MISMATCH: FIELD=`fldname`

Explanation: The Control-M Journaling facility could not be started because the specified journal file does not match the Active Jobs file used by the Control-M monitor.

In this message, fldname is the name of the field in the Active Jobs file that does not match the corresponding field in the Journal file.

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

CTMM08S GETMAIN FAILURE IN PROGRAM `progname`

Explanation: Sufficient storage could not be obtained for Journal file processing.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W. CTML12W asks the operator to either continue without journaling or shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

CTMM09S BUFFER OVERFLOW ERROR

Explanation: An internal error was detected during Journal file processing.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W. Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMM10S LUW RECORD GENERATION ERROR

Explanation: A error occurred while writing the LUW syncpoint record to the Journal file.

The LUW syncpoint record is the last synchronization point in the Journal file and verifies the completion of all records previously recorded in the Journal file. Without the LUW syncpoint record, records in the Journal file cannot be verified as complete.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

CTMM12E JOURNAL FILE DCB ABEND EXIT INVOKED: SYSTEM CC=X‘`sys`’, RC=`rc`

Explanation: An abend occurred while writing to the Journal file.

In this message, sys and rc are the system codes and return codes which describe the abend.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

CTMM15I AJF/CONDITIONS JOURNALING ACTIVITY SUSPENDED

Explanation: This information message indicates that journaling has been suspended due to New Day processing.

During New Day processing, Control-M always suspends writing to the Journal file.

Journaling is automatically resumed after completion of New Day processing.

Corrective Action: No action is required.

CTMM16I AJF/CONDITIONS JOURNALING ACTIVITY RESTORED

Explanation: This information message indicates that Control-M resumed writing to the Journal file after completing New Day processing.

Corrective Action: No action is required.

CTMM16S INSUFFICIENT MEMORY FOR IOA FUNCTIONAL MONITOR

Explanation: The available storage is insufficient for execution of the Functional monitor.

The Functional monitor shuts down.

Corrective Action: Increase the region size and restart the Functional monitor.

CTMM17S AJF/CONDITIONS JOURNAL SEARCH FAILURE

Explanation: An error was encountered during a search of the Control-M Journal file.

During Control-M monitor startup, the journal file is searched for data that may have been added to the Active Jobs File while the Control-M monitor was down.

The Control-M monitor stops journaling and displays WTOR message CTML12W.

Corrective Action: Reply to message CTML12W, which follows.

CTMM20S INTERNAL ERROR IN FUNCTIONAL MONITOR. RC=`rc`

Explanation: The Functional monitor encountered a severe internal error.

The Functional monitor shuts down.

Corrective Action: Have your system programmer contact BMC Customer Support.

Messages CTMO00 through CTMOxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMO01E ERROR IN SENDING COMMAND TO CONTROL-M MONITOR. REASON '`rsn`' CODES `text1, text2 / text3`

Explanation: The Control-M Local monitor or Control-M Application Server did not successfully issue an operator command to another Control-M monitor.

The command is not processed by the target Control-M monitor.

Corrective Action: Keep the REASON and CODES displayed by the message and contact BMC technical support for assistance. The required operator command may be usually issued manually for the target Control-M monitor.

Messages CTMR00 through CTMRxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMR01W Control-M AJF SPACE REUSE FACILITY WILL BE ACTIVATED AFTER NEWDAY, AJF FORMAT OR COMPRESS

Explanation: The AJF Space Reuse Facility was enabled by the user, but the AJF has not yet been formatted to include the special index records required to manage the AJF Space Reuse Facility.

The AJF Space Reuse Facility will be activated automatically by Control-M after the upcoming New Day process.

Corrective Action: No action is required.

CTMR02E CONTROL-M AJF SPACE REUSE FACILITY DISABLED. REASON `rsn`

Explanation: Internal facility-wide errors were encountered in the AJF Space Reuse Facility.

The possible values of rsn are explained in the following table:

rsn	Explanation
WRONG MIF	Invalid index record detected
MIF ERROR	Invalid index record structure detected
NO MEMORY	GETMAIN failure
CTMMIF	Error encountered in module CTMMIF
READTGT	Error encountered in READTGT routine
WRITTGT	Error encountered in WRITTGT routine
GETMAIN	GETMAIN failure
FREEMAIN	FREEMAIN failure

The AJF Space Reuse Facility is disabled.

Corrective Action: Do the following:

Contact BMC Customer Support.
To reactivate the AJF Space Reuse Facility, format or compress the AJF and recycle the Control-M monitor.

CTMR03I JOB `jobName` ORDERID `orderId` PERMANENTLY DELETED FROM AJF

Explanation: This information message indicates that the AJF Space Reuse Facility is active and, as expected, deleted an entry from the AJF.

Corrective Action: No action is required.

CTMR04E INTERNAL ERROR IN AJF SPACE REUSE PROCESSING FOR JOB `jobName`/`orderId` CODE `rsn`

Explanation: Internal errors were encountered in the AJF Space Reuse Facility for this job.

The possible values of rsn are explained in the following table:

rsn	Explanation
GROUP JOB	error in removing a job from a group
END TIME	error in extracting the job's end time

The indicated job will not be deleted from the AJF.

Corrective Action: No action is required.

CTMR05E AJF SPACE REUSE FACILITY IS NOT ACTIVATED BECAUSE AJF IS FULL

Explanation: The user formatted or compressed the AJF, but there is no room for the special index records required to manage the AJF Space Reuse Facility.

The AJF Space Reuse Facility is not activated.

Corrective Action: To reactivate the AJF Space Reuse Facility, format a larger AJF and recycle the Control-M monitor.

CTMR06E ATTEMPTING TO REUSE ACTIVE AJF ENTRY. AJF SPACE REUSE FACILITY DISABLED.

Explanation: When Control-M attempted to reuse an unused job entry in the AJF, a last-moment check indicated that the job entry slot in the AJF was an active entry. This is an unexpected internal error.

The AJF Space Reuse Facility is disabled.

Corrective Action: Do the following:

Contact BMC Customer Support.
To reactivate the AJF Space Reuse Facility, format a larger AJF and recycle the Control-M monitor

CTMR07E `activeJobEntrySlot`

Explanation: This message displays the first 65 characters of the active job entry slot referenced by message CTMR06E.

Corrective Action: No action is required.

CTMR09E `userExit` CANNOT BE RELOADED BY THE RELOAD COMMAND (`reason`)

Explanation: The RELOAD= userExit operator command was issued by the user, but it aborted because of one of these reasons:

reason	Explanation
NOT 123415	The user attempted to reload a module which is not CTMX001, CTMX002, CTMX003, CTMX004, or CTMX015
LINK-EDITED	The user attempted to reload CTMX001 but it has been link-edited by the user into CTMJOB, or the user attempted to reload CTMX002 but it has been link-edited by the user into CTMSUB
NOT FOUND	The user attempted to reload a user exit but it was not found in the STEPLIB concatenation

The RELOAD command is aborted.

Corrective Action: No action is required.

CTMR0AI `userExit` RELOADED. OLD=`mm/dd/yy-hh.mm` NEW=`mm/dd/yy-hh.mm`

Explanation: This information message indicates that the userExit user exit was successfully reloaded as a result of the RELOAD= userExit operator command. The date and time of the 'old' and 'new' user exits are only accurate when the IOAEXNM userExit macro is used to provide standard entry linkage in the user exit.

Corrective Action: No action is required.

CTMR0BW `taskname` INT. ERR, MAYBE DELETE: `grpnameapplorder_idodate`

Explanation: This warning message indicates that there was an internal error in taskname during the New Day procedure. As a result of this error, grpname might be deleted from the Active Jobs file.

The variables in this message are:

grpname--the group entity name
appl--the application to which the group entity belongs
order_id--the order ID of the group entity
odate--the ODATE of the group entity

Corrective Action: Send the Control-M Backup Active Jobs file and the output of the New Day procedure to technical support.

CTMR0CE 'DO REMEDY' ERROR: `error`

Explanation: Control-M encountered an error when attempting to execute a DO REMEDY request.

The possible values of error that can appear are explained in the following table:

error	Explanation
INIT FUNCTION FAILED RC = `rc`	The initialization function failed with a return code of `rc`.
SEND FUNCTION FAILED RC = `rc`	The send function failed with a return code of `rc`.
FEATURE DISABLED	The feature has previously been disabled.
TICKET ALREADY OPEN FOR JOB	A REMEDY problem ticket has already been opened for this job.
SUMMARY LINE TRUNCATED	The summary line was too large and was truncated.
DESCRIPTION LINE TRUNCATED	The description line was too large and was truncated.
ERROR IN DO REMEDY CODES	An internal error was encountered in the schedule definition.

Corrective Action: The following table has valid return code (rc) values for the error SEND FUNCTION FAILED, together with their explanations and the appropriate corrective action.

Return Code	Explanation	Corrective Action
64	Can not load IOAMAIL.	Contact BMC Customer Support.
68	Can not load IOAMEM.	Contact BMC Customer Support.
72	At REMTMPLx one of the variables which are surround by double %% are not defined, a valid variables are: SUMM DESC URGENCY USER	Check REMTMPLx for invalid variable.
76	REMCONF or REMTMPLx member at IOA.PARM does not exist.	Check the existence of REMCONF member or REMTMPLx at IOA.PARM library or the filed REMTMPLS at REMCONF to suits one of the REMTMPLx.
80	REMCONF member at IOA.PARM is corrupted.	Check REMCONF member for missing single quotes or undefined fields.

The DO REMEDY request is aborted (or sent truncated if the summary or description was too large).

Contact BMC Customer Support.

CTMR0DE 'DO REMEDY' FEATURE IS DISABLED

Explanation: Control-M encountered an error during the initialization or send function of a DO REMEDY request.

All DO REMEDY requests are aborted until Control-M is recycled.

Corrective Action: Contact BMC Customer Support.

CTMR0FW INT. ERR, JOB HLD: `tasknamegrpnameapplorder_idodate`

Explanation: This warning message indicates that there was an internal error in taskname during the New Day procedure.

The variables in this message are:

grpname--the group entity name
appl--the application to which the group entity belongs
order_id--the order ID of the group entity
odate--the ODATE of the group entity

As a result of this error, the job is put on hold and the job is longer part of group grpname.

Corrective Action: Send the Control-M Backup Active Jobs file and the output of the New Day procedure to technical support.

CTMR11I JOB/GROUP `name` ORDERID `orderId` COPIED TO HISTORY AJF

Explanation: This information message indicates that job name, whose order ID is orderId, was successfully copied to the History AJF. The job records are now available for space reuse.

Corrective Action: No action is required.

CTMR12E COPY TO HISTORY FILE FAILED: `rsn` REASON CODE: `rc`

Explanation: An error occurred while copying records from the AJF to the History AJF.

The variables in this message are:

rsn - the cause of the error
rc - the reason code, which may contain additional information

History processing for space reuse jobs is disabled. Jobs having a retention period will no longer be eligible for space reuse.

Corrective Action: No action is required.

CTMR13E JOB/GROUP `name` ORDERID `orderId`

Explanation: This message accompanies message CTMR12E and indicates that job name, whose order ID is orderId, was being processed when the error occurred.

Corrective Action: No action is required.

CTMR14E ALLOCATION OF FILE `fileName` FAILED RC `rc`

Explanation: The Control-M Monitor failed to allocate the fileName file. The reason for the failure is described by a return code value of rc.

The Control-M monitor continues normal processing. Since the History file is not allocated to the Control-M monitor, jobs having a retention period will no longer be eligible for space reuse.

Corrective Action: Use the return code (rc) to determine the cause of the allocation error and use the modify command HISTALOC=ENABLE to try and allocate the History file again.

CTMR15E DEALLOCATION OF FILE `fileName` FAILED RC `rc`

Explanation: The Control-M Monitor failed to deallocate the fileName file. The reason for the failure is described by a return code of rc.

The Control-M monitor continues normal processing.

Corrective Action: Use the return code (rc) to determine the cause of the allocation error and use the modify command HISTALOC=DISABLE to try and deallocate the History file.

CTMR16E VALUE MUST BE C(DEFAULT), V(VARYING), OR S(RUN AT SPECIFIC TIMES)

Explanation: An invalid option has been entered in the CYCLIC type field. The valid values are:

C - A cyclic job can be submitted only at fixed intervals (such as every 5 minutes or every hour).
V - Varying intervals when a cyclic job can be submitted (such as every 30 minutes, and every hour, and every 3 days).
S - Specific times when a cyclic job can be submitted (such as at 9 AM, or at 2 PM).

Corrective Action: Specify C or V or S, or leave the field blank (same as entering a value of C ).

CTMR21I CTMRSMF STARTED

Explanation: This information message indicates that the CTMRSMF utility has begun.

Corrective Action: No action is required.

CTMR22I CTMRSMF ENDED

Explanation: This information message indicates that the CTMRSMF utility has ended normally.

The utility terminates normally with a return code of zero.

Corrective Action: No action is required.

CTMR23S UNABLE TO OPEN SMF INPUT FILE

Explanation: The CTMRSMF utility was unable to open the input SMF file.

The utility terminates with a return code other then zero.

Corrective Action: Check the JCL to ensure that the dd statement DASMF is pointing to a valid SMF file.

CTMR24S UNABLE TO OPEN CSV OUTPUT FILE

Explanation: The CTMRSMF utility was unable to open the output .CSV file.

Processing terminates with non-zero return code

Corrective Action: Check the JCL to ensure that the dd statement DACSV is present pointing to a valid CSV file.

CTMR25S INVALID SMF RECORD - SEE SNAP

Explanation: During execution of the CTMRSMF utility, an invalid SMF record was encountered in the DASMF file.

The utility terminates with a return code other then zero.

Corrective Action: Send all the output from the CTMRSMF job to BMC technical support.

CTMR27E UNABLE TO OPEN PRINT FILE, DDNAME "DAREPORT"

Explanation: The CTMEVRT utility was unable to open the output DD DAREPORT.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMR28E UNABLE TO OPEN THE `ddname` DD

Explanation: The CTMEVRT utility was unable to open the input or output DD specified.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMR29E INCLTIME NOT SPECIFIED

Explanation: The period of time DSNEVENTs were not handled by CMEM must be specified for the CTMEVRT utility.

The utility terminates with a return code of 8.

Corrective Action: Specify the recovery time range using the INCLTIME parameter.

CTMR2AE SYSID OR SYSTEM NOT SPECIFIED

Explanation: The system identification must be specified for the CTMEVRT utility.

The utility terminates with a return code of 8.

Corrective Action: Specify the LPAR for which the events must be recovered, by using either the SYSID or SYSTEM parameters.

CTMR2BE INVALID STATEMENT SPECIFIED

Explanation: An invalid statement was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Correct the SYSIN statement.

CTMR2CE DUPLICATE STATEMENTS SPECIFIED

Explanation: Duplicate statements were specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Remove one of the duplicate SYSIN statements.

CTMR2DE INVALID VALUE SPECIFIED

Explanation: An invalid value was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid value.

CTMR2EE INVALID TIME SPECIFIED: `time`

Explanation: An invalid time was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid time, in the range from 00:00 to 23:59, using the hh:mm format.

CTMR2FE INVALID DATE SPECIFIED: `date`

Explanation: An invalid date was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid date, using the yyyy/mm/dd format.

CTMR2GE INVALID TIME RANGE SPECIFIED

Explanation: An invalid time range was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid time range, ensuring that end of the range is after the beginning of the range.

CTMR2HE INVALID STATEMENT SPECIFIED IN DSNEVEXL: `statement`

Explanation: An invalid statement was specified in the CTMEVRT utility DSNEVEXL PARM member.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the invalid statement. Valid statements are: EXCLDSN= and EXCLJOB=. Specify a valid job name or data set name mask.

CTMR2IE TOO MANY STATEMENTS SPECIFIED IN DSNEVEXL: `statement`

Explanation: Too many statements were specified in the CTMEVRT utility DSNEVEXL PARM member.

The utility terminates with a return code of 8.

Corrective Action: Contact BMC technical support.

CTMR2JE ERROR LOADING THE SORT MODULE

Explanation: The SORT module cannot be loaded.

The utility terminates with a return code of 8.

Corrective Action: Check the job log for additional messages related to the problem. If you still cannot resolve the issue, contact BMC technical support.

CTMR2KE SORT INVOCATION ERROR, RC=`rc`

Explanation: The invocation of the SORT module ended with errors.

The utility terminates with a return code of 8.

Corrective Action: For more details, check the SYSOUT DD SORT error messages. If you still cannot resolve the issue, contact BMC technical support.

CTMR2LE NONE OF THE SMF RECORDS SATISFIED THE INCLTIME AND SYSID OR SYSTEM CRITERIA

Explanation: The CTMEVRT utility did not find any SMF records matching the time period and/or the system identification specified in the SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement.

CTMR2ME THE REQUIRED SMF TYPES WERE NOT PROVIDED FOR THE INCLUDED PERIOD OF TIME

Explanation: The CTMEVRT utility did not find any of the mandatory SMF types in the SMF input. The mandatory SMF types are 14, 15, 17, 30, 61, 64, and 65.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement that contains the SMF record types.

CTMR2NW NO CMEM/CTO EVENTS WERE FOUND IN INPUT SMF - DSNEVENTS LIST NOT GENERATED

Explanation: The CTMEVRT utility did not find any DSNEVENTs in the SMF data that would have been caught by CMEM or Control-O during the time period specified.

The utility terminates with a return code of 4.

Corrective Action: No action is required.

CTMR2OE MANDATORY SMF TYPE `SMF_type` NOT FOUND IN INPUT

Explanation: The CTMEVRT utility did not find this mandatory SMF record type in the SMF input. The mandatory SMF types are 14, 15, 17, 30, 61, 64, and 65.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement.

CTMR2PE DSNEVENTS LIST MAY BE PARTIAL BECAUSE OF MISSING DISP INFORMATION IN THE SMF INPUT

Explanation: Data sets for which the CTMEVRT utility did not find any matching SMF records are excluded from the event list generated. See message CTMR2ZE for more details.

The event list is generated but the utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement that contains the SMF record types missing. If all SMF types were provided to the utility, provide the DASMF records to BMC Support.

CTMR2QW SMF TYPE 119-70 (FTP SERVER) NOT FOUND IN INPUT, INCOMING FTP DSNEVENTS COULD NOT BE GENERATED

Explanation: The CTMEVRT utility did not find any SMF record type 119, subtype 70, in the SMF input. As a result, the utility cannot find and list DSNEVENTs triggered by FTP transfers originating in remote systems.

The utility continues to execute.

Corrective Action: If SMF 119 is collected at the site, specify the correct SMF data set(s) in the DASMF DD JCL statement and re-run the utility.

CTMR2RE INTERNAL ERROR - `error_description`

Explanation: An internal error has occurred during the execution of the CTMEVRT utility.

The utility terminates with a return code of 8.

Corrective Action: Send all the output from the CTMEVRT job to BMC technical support.

CTMR2SW INVALID SMF RECORD(S) ENCOUNTERED - SEE SNAP

Explanation: During execution of the CTMEVRT utility, one or more invalid SMF records were encountered in the DASMF file.

The utility continues to execute.

Corrective Action: Send all the output from the CTMEVRT job to BMC technical support.

CTMR2TE CMEM/CTO EVENTS COULD NOT BE FOUND DUE TO AN ERROR WHILE LOADING RULES

Explanation: The CTMEVRT utility was unable to read CMEM or Control-O rules from the DACTMLST DD. No rules defining DSNEVENTs were found.

The utility terminates with a return code of 8.

Corrective Action: Check DAREPORT for additional messages related to the problem.

CTMR2VW RULE `cmem_rule` TABLE `table` IS CHECKING ON THE UNSUPPORTED DISP NCT2

Explanation: The selection criteria in the CMEM rule specifies DSNEVENTs with a disposition of NOT CATLG 2 (NCT2). The CTMEVRT utility cannot detect such events, therefore this rule will not be found and listed by this utility. The rule/event cannot be recovered; the rule cannot be triggered and the DSNEVENT cannot be restored.

The utility continues to execute.

Corrective Action: No action is required.

CTMR2WE SMF RECORDS NOT FOUND IN THE INPUT DD "DASMF"

Explanation: The CTMEVRT utility did not find any SMF record in the DASMF input DD.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement.

CTMR2XI EVENTS WILL BE EXCLUDED FROM OUTPUT DUE TO DSNEVEXL SETTINGS:

Explanation: The CTM PARM member DSNEVEXL contains the listed exclude statement(s). The events triggered by these data sets and/or jobs will be excluded from the DAEVENTS list.

Corrective Action: No action is required.

CTMR2YE TOO MANY STATEMENTS SPECIFIED

Explanation: An input statement has been specified more than the allowed number of times.

The utility terminates with a return code of 8.

Corrective Action: Remove the redundant statement(s).

CTMR2ZE CANNOT DETERMINE DISP FOR FTP-ED DATA SET `data-set-name`

Explanation: The CTMEVRT utility did not find matching SMF types 14, 15, 17, 30, 61, 64, and 65 to the FTP records it read.

The event list is generated but the utility terminates with a return code of 8.

Corrective Action: Perform the following actions:

Specify the correct SMF data set(s) in the DASMF DD JCL statement that contains the SMF record types missing.
If all SMF types were provided to the utility, adjust the _BPX_JOB parameter, as necessary.
If the issue is not yet resolved, provide the DASMF records to BMC Support.

CTMR31E UNABLE TO OPEN THE "DACTMLST" DD

Explanation: The CTMEVRT utility was unable to open the CMEM rule order list DD DACTMLST.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMR32E DACTMLST IS EMPTY

Explanation: The CTMEVRT utility found no rule tables defined in the CMEM rule order list DD DACTMLST.

The utility terminates with a return code of 8.

Corrective Action: Check and correct DACTMLST.

CTMR33E GETMAIN FAILED FOR DACTMLST ENTRIES

Explanation: There is not enough memory to load the CMEM rule order list. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR34E GETMAIN OF 1M FOR RULES FAILED

Explanation: There is not enough memory to load the CMEM rule order list. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR35E GETMAIN FOR DIRECTORY AREA FAILED

Explanation: There is not enough memory to load the CMEM rule order list. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR36E IOAMEM DIRECTORY FAILED. RC=`rc` RS=`rsn` LIB=`library`

Explanation: The CTMEVRT utility was unable to read CMEM rules from the library library because IOAMEM failed to read its directory.

The utility terminates with a return code of 8.

rc is the return code and rsn is the reason code returned by IOAMEM with the DIRECTORY function call. For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If rc and rsn descriptions are not sufficient to solve the problem then prepare the full CTMEVRT output, and contact BMC Customer Support.

CTMR37W EMPTY LIBRARY=`library`

Explanation: The CTMEVRT utility was unable to find any members in the library library.

The utility continues to read DACTMLST entries.

Corrective Action: Check the library name and if it is correct but empty, remove its entry from the DACTMLST rule list.

CTMR38W IOAMEM DIRECTORY FAILED. RC=`rc` RS=`rsn` MEM=`member` LIB=`library`

Explanation: The CTMEVRT utility was unable to read CMEM rules from the library library because IOAMEM failed to read the member member. The return code=rc and reason code=rsn were issued.

The utility continues to read DACTMLST entries.

For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If rc and rsn descriptions are not sufficient to solve the problem then prepare the full CTMEVRT output, and contact BMC Customer Support.

CTMR39E GETMAIN FOR DIRECTORY AREA FAILED

Explanation: There is not enough memory to load the CMEM rules member member from the library library because a GETMAIN of size size for it failed. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR3AE NO ELIGIBLE RULES FOUND IN DACTMLST

Explanation: The CTMEVRT utility was unable to find any eligible CMEM rules among the DACTMLST entries.Eligible rules are DSNEVENT CMEM rules performing either DO FORCEJOB, DO COND, or both.

The utility terminates with RC=08.

Corrective Action: Ensure there are eligible rules in the DACTMLST rule list.

CTMR3BW NO RECORDS IN MEM=`member` LIB=`library`

Explanation: The CTMEVRT utility was unable to find any CMEM rule records in the member member in the library library.

The utility continues to read DACTMLST entries.

Corrective Action: If rules in the library member can be skipped, remove its entry from the DACTMLST rule list.

CTMR3CW INVALID FIRST RECORD IN RULE. MEM=`member` LIB=`library`

Explanation: The first record that the CTMEVRT utility encountered in the member CMEM rules member in the library library is invalid.

The utility continues to read DACTMLST entries.

Corrective Action: Check the validity of the rule by viewing it in the IOA screen C and possibly by ordering it, then correct it or remove it from DACTMLST.

CTMR3DI DACTMLST `entry sequence number: dactmlst_entry`

Explanation: The CTMEVRT utility prints the DACTMLST entry dactmlst_entry, which is being handled, and its assigned sequence number.

Corrective Action: No action is required.

CTMR3EW MASK=`mask` DOES NOT MATCH ANY MEMBER IN LIB=`library`

Explanation: The CTMEVRT utility was unable to find any member in the library library matching the mask member mask specified in the current DACTMLST entry.

The utility continues to read DACTMLST entries.

Corrective Action: If rules in the library member can be skipped, remove its entry from the DACTMLST rule list.

CTMR3FE GETMAIN OF 4K FAILED

Explanation: There is not enough memory to convert the CMEM rules order list to an internal representation. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR3GW TRUNCATED RULE=`rule` MEM=`member` LIB=`library`

Explanation: The CTMEVRT utility encountered an invalid truncated CMEM rule rule in the member member in the library library.

The utility continues to read the next rule in the member.

rule is the name of the rule as it appears in the IOA screen C.

Corrective Action: Check the validity of the rule by viewing it in the IOA screen C and possibly by ordering it, then correct it or remove it from the rules table.

CTMR3HW INVALID RECORD IN RULE=`rule` MEM=`member` LIB=`library`

Explanation: The CTMEVRT utility encountered an invalid record CMEM rule rule in the member member in the library library.

The utility continues to read the next rule in the member.

rule is the name of the rule as it appears in the IOA screen C.

This message is followed by message CTMR3II.

Corrective Action: Check the validity of the rule by viewing it in the IOA screen C and possibly by ordering it, then correct it or remove it from the rules table.

CTMR3II INVALID RECORD=`record`

Explanation: This message displays the invalid record referred to in the previous message CTMR3HW.

Corrective Action: See the CTMR3HW message.

CTMR3JW MEM=`member` NOT FOUND IN LIB=`library`

Explanation: The CTMEVRT utility did not find the member member in the library CMEM rules library.

The utility continues to read DACTMLST entries.

Corrective Action: Correct the member name or add it to the CMEM rules library or remove its entry from the DACTMLST rule list.

CTMR3SE UNABLE TO READ DD "DAEVENTS". RC=`rc`

Explanation: The CTMEVRT utility failed to read the DAEVENTS DD using the REXX EXECIO command.

The utility terminates with a return code of 8.

Corrective Action: Check the job sysout for related messages. Also check the JCL to ensure that the DAEVENTS DD statement exists and is pointing to a valid DAEVENTS file.

CTMR3TE ERROR WHILE READING IOAPARM. RC=`rc`

Explanation: The CTMEVRT utility failed to read the IOAPARM and CTMPARM members using the REXX EXECIO command.

The utility terminates with a return code of 8.

Corrective Action: Check the job sysout for related messages. Also check the JCL to ensure that the DAPARM DD statement exists and is pointing to a valid IOA parameter library.

CTMR3UE ALLOCATION OF DD "`ddname`" FAILED. RC=`rc`

Explanation: The CTMEVRT utility failed to dynamically allocate DD ddname.

The utility terminates with a return code of 8.

Corrective Action: Check the DAPRINT DD for additional messages related to the problem. If you still cannot resolve the issue, contact BMC technical support.

CTMR3VI CTMPARM DAYTIMEM (`time`) AND NOT CTOPARM DAYTIMEO (`time`) IS USED TO DETERMINE ODAT

Explanation: During the startup of the CTMEVEX, the value of the DAYTIMEO Control-O parameter was not identical with the value of the DAYTIMEM Control-M parameter.

The DAYTIMEO Control-O parameter sets the start of the work day for Control-O. The DAYTIMEM Control-M parameter sets the start of the work day for Control-M. Any discrepancy between these two parameters might result in the same time being interpreted differently by Control-O and Control-M.

CTMEVEX uses DAYTIMEM to set the work day (ODATE) for a DSNEVENT action.

Corrective Action: Contact your INCONTROL administrator.

CTMR3WE INVALID RECORD FOUND IN "DAEVENTS" DD:`record`

Explanation: The CTMEVEX utility found a record in an unexpected format in the DAEVENTS DD. The only supported format for DAEVENTS is as it is written by the CTMEVRT utility. If the record was added as a comment, prefix it with an asterisk (*).

The utility terminates with a return code of 8.

Corrective Action: Check the JCL to ensure that the DAEVENTS DD statement is pointing to the DAEVENTS output dataset created by the CTMEVRT utility. If events were added to DAEVENTS, make sure that they are in the same format as the CTMEVRT-written events, or comments.

CTMR3XE MEMBER `member` NOT FOUND IN DAPARM LIBRARY=`library`

Explanation: The CTMEVRT utility could not find the IOAPARM or CTMPARM member in the library allocated as DAPARM.

The utility terminates with a return code of 8.

Corrective Action: Check the JCL to ensure that the DAPARM DD statement exists and is pointing to the IOA parameter library.

CTMR3YE UNABLE TO OPEN THE "`ddname`" DD

Explanation: The CTMEVRT utility was unable to open the required output DD.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMRS0E SECURITY, FAILED TO UPDATE RESOURCE FILE

Explanation: An unauthorized attempt to update the resource file failed.

Corrective Action: Ensure that the user has sufficient authorization.

CTMRS1E SECURITY, FAIL TO `action resourceType` RESOURCE `resourceName`

Explanation: An unauthorized attempt to add/delete/update a resource.

Corrective Action: Ensure that the user has sufficient authorization.

CTMRS3E INTERNAL ERROR, RESOURCE FILE NOT FREE

Explanation: Failed to use the resource file because the file is being used.

Corrective Action: Wait to the file to be released. Retry the process.

CTMRS4E INTERNAL ERROR, INVALID `resourceType` RESOURCE RECORDS IN FILE HEADER

Explanation: The resource file header contains an invalid number of resource type slots.

Corrective Action: This is an internal error. Retry the process and if the problem reoccurs, call BMC Customer Support.

CTMRS5E ERROR, QUANTITY SLOTS NUMBER GREATER THAN FILE

Explanation: The actual number of quantity base slots is greater than the counter in the resource file header.

Corrective Action: This is an internal error. Retry the process and if the problem reoccurs, call BMC Customer Support.

CTMRS7E FAIL TO ADD QUANTITY BASE RESOURCE `resourceName, reason`

Explanation: Failed while adding the base resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRS8E FAIL TO DELETE QUANTITY BASE RESOURCE `resourceName, reason`

Explanation: Failed while deleting the base resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRS9E FAIL TO UPDATE QUANTITY BASE RESOURCE `resourceName, reason`

Explanation: Failed while updating the base resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRSBE FAIL TO OBTAIN `resourceType` RESOURCE `resourceName, reason`

Explanation: Failed while trying to obtain the resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRSCE FAIL TO RELEASE `resourceType` RESOURCE `resourceName, reason`

Explanation: Failed while trying to release the resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRSDE FAIL TO OBTAIN `resourceType` RESOURCE, ALL SLOTS IN USE

Explanation: Failed while trying to obtain the resource because all slots for this resource type are being used.

Corrective Action: Increase the file size and retry the process.

Messages CTMS00 through CTMSxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMS001 INVALID DATE

Explanation: N was specified for the CURRENT AJF option, but no alternative date was specified for the creation of a new Active Jobs file (AJF). An alternative date must be specified when the date of the current AJF is not utilized.

Corrective Action: Specify a valid alternate date for the generation of a simulation AJF.

CTMS001 SIMULATION PARAMETERS ARE IGNORED WHEN "RUN SIMULATION=N"

Explanation: N was specified for the RUN SIMULATION option but simulation parameters were specified. If N is specified for the simulation option, parameters specified for this option are ignored.

Corrective Action: If you want to generate a simulation file, select the RUN SIMULATION option.

CTMS002 INVALID FROM-DATE. SHOULD BE `YYMMDDHHMM`

Explanation: The user specified a date in the FROM-DATE field that was not valid or not in the format yymmddhhmm.

Corrective Action: Enter a valid date in the format indicated.

CTMS003 INVALID UNTIL-DATE. SHOULD BE `YYMMDDHHMM`

Explanation: The user specified a date in the UNTIL-DATE field that was not valid or not in the format yymmddhhmm.

Corrective Action: Enter a valid date in the format indicated.

CTMS004 UNTIL-DATE IS EARLIER THAN FROM-DATE

Explanation: The date specified in the UNTIL-DATE field precedes the date specified in the FROM-DATE field.

Corrective Action: Specify a valid date range.

CTMS005 "ANOTHER DAY" IS VALID ONLY WHEN "N" IS SPECIFIED FOR CURRENT AJF

Explanation: A date was specified in the ANOTHER DAY field when Y was specified for the current AJF. Either the current AJF may be used for the simulation run, or a simulation AJF may be generated for another working day. Either option may be chosen, but not both.

Corrective Action: Specify N in the CURRENT AJF field, or delete the date in ANOTHER DAY field.

CTMS006 SKELETON `skelName` IS NOT FOUND IN THE LIBRARY ALLOCATED TO DD "ISPSLIB"

Explanation: The skeleton libraries referenced by the ISPSLIB DD statement does not contain the skelName member.

Corrective Action: The skelName skeleton name should have been placed in the ISPSLIB concatenation during the IOA ISPF installation process. Review the installation procedure and correct accordingly.

CTMS007 SKELETON `skelName` IS ALREADY IN USE BY ANOTHER USER

Explanation: Skeleton skelName is currently being used by another user to generate simulation JCL.

Corrective Action: Wait until the other user has generated the JCL and try again.

CTMS008 "ORDER DAILY JOBS" AND "NEW AJF" ARE VALID ONLY WHEN "CURRENT AJF=N"

Explanation: The ORDER DAILY JOBS and CREATE NEW AJF fields are mutually exclusive with the CURRENT AJF field. Either the current AJF can be used for the simulation run, or options can be specified for a new AJF to be generated.

Corrective Action: Specify N in the CURRENT AJF field or specify N in the other two fields identified in the message.

CTMS009 INVALID COMBINATION OF PARAMETERS IN JOBSCAN SECTION

Explanation: The combination of options for JOBSCAN processing is not valid. Certain JOBSCAN options are mutually exclusive, and may not be used together. For example, JCL Listing lists the JCL along with the errors, while JCL-Listing-Errors lists only the errors.

Corrective Action: Enter a valid combination of options.

CTMS010 JOBS LEFT REPORT REQUIRE THAT "Y" BE SPECIFIED FOR "KEEP OUTPUT AJK"

Explanation: User requested the Jobs Left KSL report, but did not specify Y in the KEEP OUTPUT AJF field. When requesting the Jobs Left report from the Control-M Simulation Facility (CLIST CTMCSIM), the Active Jobs file that is output from the simulation (SIMOAJF) must be kept to run the report.

Corrective Action: Specify Y in the KEEP OUTPUT AJF field, or specify N in the JOBS LEFT field.

Messages CTMT00 through CTMTxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMT01E TIME ZONE DEFINITION MEMBER NOT FOUND. TIME ZONES ARE NOT AVAILABLE.

Explanation: No Time Zone definition member can be found in the IOA PARM library.

If this message is displayed during job or group definition, the program waits for the Time Zone field to be cleared. If this message is displayed during job or group scheduling, the job is not scheduled.

Corrective Action: Do the following:

Define a Time Zone member.
Log off TSO.
Log on to TSO again.
Enter the NEWPARM monitor command.
Reschedule the job.

CTMT02E THE FOLLOWING INVALID TIME ZONE DEFINITIONS ARE IGNORED:

Explanation: The Time Zone specified is not defined in the Time Zone definition member in the IOA PARM library.

This message is followed by the CTMT03E message, which identifies the Time Zones that were found to be undefined.

The job is not scheduled.

Corrective Action: No action is required.

CTMT03E `text`

Explanation: This information message follows the CTMT02E message.

In this message, text lists the individual Time Zones that were specified in the job scheduling definition but were found not to be defined in the Time Zone definition member in the IOA PARM library.

Corrective Action: No action is required.

CTMT04E THE TIME ZONE SPECIFIED IS INVALID

Explanation: The Time Zone specified in the job or group definition is not defined in the Time Zone member in the IOA PARM library.

The program waits for the Time Zone specification to be corrected or deleted.

Corrective Action: Correct or delete the Time Zone specification. If you modify the Time Zone member, you must also do the following:

Log off TSO.
Log on to TSO again.
Enter the NEWPARM monitor command.

CTMT05E JOB NOT SUBMITTED DUE TO TIME ZONE PROCESSING INACTIVE

Explanation: The job contains a Time Zone specification, but no Time Zone definition member can be found in the IOA PARM library.

The job is not submitted.

Corrective Action: Do the following:

Define a Time Zone member.
Log off TSO.
Log on to TSO again.
Enter the NEWPARM monitor command.
Reschedule the job.

CTMT06E JOB NOT SUBMITTED DUE TO INVALID TIME ZONE `timeZone`

Explanation: The job contains a Time Zone specification, but the specified Time Zone is not defined in the Time Zone definition member in the IOA PARM library.

The job is not submitted.

Corrective Action: Do the following:

Modify the Time Zone member.
Log off TSO.
Log on to TSO again.
Enter the NEWPARM monitor command.
Reschedule the job.

CTMT07E JOB NOT SUBMITTED DUE TO TIME ZONE PROCESSING FAILURE

Explanation: An internal error occurred while the Time Zone specification was being processed.

The job is not submitted.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMT02E THE FOLLOWING INVALID TIME ZONE DEFINITIONS ARE IGNORED:

Explanation: The Time Zone specified is not defined in the Time Zone definition member in the IOA PARM library.

This message is followed by the CTMT03E message, which identifies the Time Zones that were found to be undefined.

The job is not scheduled.

Corrective Action: No action is required.

CTMT08I TIME HAS CHANGED IN ACCORDANCE TO THE DST SETTING IN TIMEZONE `xxx`

Explanation: This informational message indicates that Control-M has detected a change in the Daylight Saving Time setting in timezone xxx.

Corrective Action: No action is required.

CTMT09I CTM HAS DETECTED A DYNAMIC MODIFICATION IN THE SYSTEM TIME.

Explanation: This informational message indicates that Control-M has detected a change in a local time performed by an operator command.

Corrective Action: No action is required.

Messages CTMU00 through CTMUxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMU01I AJF/CONDITIONS RESTORATION STARTED

Explanation: This information message indicates that the CTMRSTR restoration utility has begun processing.

Corrective Action: No action is required.

CTMU02I AJF/CONDITIONS RESTORATION ENDED

Explanation: This information message indicates that the CTMRSTR restoration utility has completed processing.

Corrective Action: No action is required.

CTMU22W AJF/CONDITIONS RESTORATION UTILITY WAITING FOR ACTIVE JOBS FILE

Explanation: The restore utility could not access the Active Jobs File because it was being used by another job.

The restoration utility waits until the file is accessible.

Corrective Action: No action is required.

Messages CTMW00 through CTMWxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMW00E INVALID PARAMETER PASSED TO CTMWLM; WLM SRVCLASS REQUEST ABORTED

Explanation: CTMWLM, the Control-M workload management service class processing module, received an incomplete or incorrect parameter list.

The specific service class request is aborted.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMW01E IOAMEM GETMEM ERROR. RETURN=`rc` REASON=`rsn`

Explanation: CTMWLM, the Control-M workload management service class processing module, was unable to read the WLMSCTBL table in the CTM PARM library.

The specific service class request is aborted.

Corrective Action: Note the values of rc and rsn, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMW02E GETMAIN FOR INTERNAL TABLE FAILED. LEN=`len` R15=`r15`

Explanation: CTMWLM, the Control-M workload management service class processing module, was unable to acquire enough storage to build the internal table which represents the WLMSCTBL table in the CTM PARM library.

The specific service class request is aborted.

Corrective Action: Note the values of len and r15, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMW03E FREEMAIN OF OLD INTERNAL TABLE FAILED. LEN=`len` PTR=`ptr`

Explanation: CTMWLM, the Control-M workload management service class processing module, was unable to free previously-acquired storage.

Corrective Action: Note the values of len and ptr, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTMW04I WLM SRVCLASS TABLE {LOADED | RELOADED} SUCCESSFULLY WITH `num` ENTRIES

Explanation: CTMWLM, the Control-M workload management service class processing module, successfully loaded or reloaded the WLMSCTBL table from the CTM PARM library.

Corrective Action: No action is required.

CTMW05W INTERNAL WLM SRVCLASS TABLE HAS NO VALID ENTRIES

Explanation: CTMWLM, the Control-M workload management service class processing module, successfully loaded or reloaded the WLMSCTBL table from the CTM PARM library but found no valid entries.

All subsequent service class requests are effectively ignored.

Corrective Action: Correct or add entries to the WLMSCTBL table in the CTM PARM library.

CTMW06E ENTRY `rec` PARSING ERROR: `jobNameapplNamefromTimetoTime`

Explanation: CTMWLM, the Control-M workload management service class processing module, detected a parsing error in this entry in the WLMSCTBL table in the CTM PARM library.

The variables in this message are:

rec - the record number
jobName - the name of the job in the WLMSCTBL table entry
applName - the name of the application in the WLMSCTBL table entry
fromTime - the start time of the range
toTime - the end time of the range

The table entry is ignored.

Corrective Action: Correct the entry in the WLMSCTBL table in the CTM PARM library.

CTMW07I {COMMAND | MACRO} ISSUED TO RESET JOB TO SRVCLASS `servClass`

Explanation: CTMWLM, the Control-M workload management service class processing module, attempted to reset the service class of the job to servClass.

Corrective Action: No action is required.

CTMW08E IWMRESET MACRO ERROR. SRVCLASS=`servClass` RETURN=`rc` REASON=`rsn`

Explanation: CTMWLM, the Control-M workload management service class processing module, attempted to reset the service class of the job to servClass but failed.

The specific service class request is unsuccessful.

Corrective Action: For information about the return and reason codes, see the explanation of IWMRESET in the IBM manual MVS Programming: Workload Management Services.

CTMW10W RULE IGNORED - LOAD-INDEX LEVEL IS COVERED BY PREVIOUS RULES

Explanation: The Workload Policy contains two or more rules that are almost identical — associated with the same Load-Index, but differing in the defined limit (of jobs or resources) and threshold load level. The defined threshold level in the first rule is lower than in the latter rule(s), and logically covers the scope of levels defined by any higher threshold level in a latter rule. The rule with the higher threshold is ignored.

Corrective Action: Review the rules in the Workload Policy and adjust their definitions or change their order in the Workload Policy.

CTMW11E UNABLE TO OBTAIN STORAGE FOR CALLING RMF MON III SERVICE ERB3XDRS

Explanation: Control-M Workload Optimization was unable to call the RMF Monitor III Sysplex Data Service ERB3XDRS because not enough storage was available.

Corrective Action: Increase the region size available to the Control-M monitor. If the problem persists, contact BMC Customer Support.

CTMW12W RMF MON III SERVICE ERB3XDRS FOR SYSTEM `system` FAILED WITH RC=`rc` REASON=`reason`

Explanation: Control-M Workload Optimization tried to call the RMF Monitor III Sysplex Data Service ERB3XDRS, but was unsuccessful. As a result, RMF data for the specified system is not available to Control-M.

Corrective Action: For more information about ERB3XDRS return codes and reason codes, review the material about return codes and reason codes for RMF sysplex data services in IBM’s z/OS RMF Programmer's Guide.

CTMW13E RMF MON III SERVICE ERB3XDRS FOR SYSTEM `system` RETURNED INCOMPLETE DATA

Explanation: Control-M Workload Optimization tried to call the RMF Monitor III Sysplex Data Service ERB3XDRS, but it returned incomplete data. As a result, RMF data for the specified system is not available to Control-M.

Note that systems running as a z/VM guest cannot produce the required RMF data and thus cannot be monitored by the Control-M Workload Optimization feature.

Corrective Action: Check the RMF Monitor III in the relevant system for errors.

CTMW14E UNABLE TO `function` THE WLI REPOSITORY - RC=`rc` REASON=`reason`

Explanation: Control-M Workload Optimization was unable to either initialize/terminate or write to the Workload Load-Indexes repository.

Corrective Action: Contact BMC Customer Support.

CTMW16E UNABLE TO `function` THE WLI REPOSITORY - RC=`rc` REASON=`reason`

Explanation: Control-M Workload Optimization was unable to either initialize/terminate, lock/unlock, read or clear from the Workload Load-Indexes repository.

Corrective Action: Contact BMC Customer Support.

CTMW17E UNABLE TO OBTAIN STORAGE FOR CALCULATING LOAD-INDEXES LEVELS

Explanation: Control-M Workload Optimization tried to obtain storage but was unsuccessful. As a result, Load-Index level calculations are inactive.

Corrective Action: Increase the region size available to the Control-M monitor. If the problem persists, contact BMC Customer Support.

CTMW18E PROGRAM program ENDED WITH RC=`rc`, CALCULATION INACTIVE

Explanation: Control-M Workload Optimization program has failed. As a result, Load-Index calculations are inactive.

Corrective Action: Contact BMC Customer Support.

CTMW19E UNABLE TO PROCESS `system` RMF DATA - INSUFFICIENT STORAGE

Explanation: Control-M Workload Optimization tried to call the RMF Monitor III Sysplex Data Service ERB3XDRS but it returned incomplete data. As a result, RMF data for the specified system is not available to Control-M.

Corrective Action: Increase the region size available to the Control-M monitor. If the problem persists, contact BMC Customer Support.

CTMW1AE INTERNAL ERROR LOADING LOAD-INDEX RULES. RC=`rc`

Explanation: Control-M Workload Optimization failed to load Load-Index definitions. As a result, Load-Index calculations are inactive.

Corrective Action: Fix the problem and restart Control-M.

CTMW1BI `number` LOAD-INDEXES SUCCESSFULLY LOADED

Explanation: The specified number of Load-Indexes were successfully loaded to memory.

Corrective Action: No action is required.

CTMW1DE INTERNAL ERROR CALC MEASURED . RC=`rc`

Explanation: Control-M Workload Optimization failed during Load-Index level calculation. As a result, Load-Index calculations are inactive.

Corrective Action: Contact BMC Customer Support.

CTMW1FI WLI FILE DOES NOT EXIST OR INVALID

Explanation: The Control-M Workload Load-Indexes repository file is missing or invalid, Control-M will continue without the Workload Optimization feature.

Corrective Action: Allocate and initiate the Workload Load-Indexes repository file. For more information, see the section about the CTMWLI utility in the INCONTROL for z/OS Utilities Guide.

CTMW1GI WLI FILE WAS REFRESHED

Explanation: The Control-M Workload Optimization Load-Indexes repository was updated with the latest Load-Index definitions.

Corrective Action: No action is required.

CTMW1HE RMF MON III SERVICE ERB3XDRS FOR SYSTEM `system` IS NOT AVAILABLE

Explanation: Control-M Workload Optimization tried to call the RMF Monitor III Sysplex Data Service ERB3XDRS, but RMF is not active in that system. As a result, RMF data for the specified system is not available to Control-M.

Corrective Action: Start RMF Monitor III in the relevant system.

CTMW1JW MAINVIEW ALARM LOAD-INDEX LOADED BUT COLLECTION DISABLED

Explanation: An MVA-type Load-Index was found and loaded, but data will not be collected for this type of Load-Index because the OPTMVLID parameter was set to N.

Corrective Action: If you want load levels set for MVA-type Load-Indexes, set parameter OPTMVLID to Y.

CTMW20I LOAD-INDEXES CALCULATION RESUMED

Explanation: Control-M Workload Optimization has resumed Load-Index calculations after temporarily inactivating calculations, as indicated by previous message CTMW18E.

Corrective Action: No action is required.

CTMW21I LOAD-INDEX DEFINITIONS DO NOT EXIST

Explanation: Control-M Workload Optimization tried to load Load-Index definitions, but the CTMINDX member does not exist.

Corrective Action: Use Screen W.ID to define Load-Indexes.

CTMW22I WORKLOAD POLICY `policyName` SET TO `status` STATUS

Explanation: Workload Policy status changed to active or inactive.

Corrective Action: No action is required.

CTMW23I WORKLOAD POLICY `policyName` ALREADY IN ACTIVE STATUS

Explanation: The Workload Policy that you tried to activate is already in Active status. The action is ignored.

Corrective Action: No action is required.

CTMW25I WORKLOAD POLICY `policyName` ALREADY IN INACTIVE STATUS

Explanation: The Workload Policy that you tried to inactivate is already in Inactive status. The action is ignored.

Corrective Action: No action is required.

CTMW26E OPTION INVALID UNDER BROWSE

Explanation: The Action is not allowed in Browse mode.

Corrective Action: Enter Edit mode and perform the action again.

CTMW27E OPTION INVALID UNDER BROWSE

Explanation: Cannot save nor apply Workload definitions in Browse mode.

Corrective Action: Enter Edit mode and perform the action again.

CTMW28I IS COMMAND CANNOT BE PERFORMED WHILE WLI IS BEING FORMATTED

Explanation: Load-Index status is not available when rebuild of the WLI file is in progress.

Corrective Action: Wait until the rebuild ends and try again.

CTMW2DE RMF MON III DID NOT RETURN ANY DATA - INTERNAL LOAD-INDEXES CALCULATION IS SUSPENDED

Explanation: Control-M Workload Optimization tried to call the RMF Monitor III Sysplex Data Service ERB3XDRS, but failed to obtain the required information. Load-Index calculation is suspended.

Corrective Action: Contact your system programmer to solve the issue.

CTMW2EI GLOBAL MONITOR HAS SUSPENDED INTERNAL LOAD-INDEXES CALCULATION

Explanation: Control-M Workload Optimization stopped calculating the Load-Index value.

Corrective Action: No action is required. Optimization is disabled.

CTMWL1I CONTROL-M STARTED REBUILDING WORKLOAD DATA

Explanation: Control-M uploaded the new workload definitions from Control-M/Enterprise Manager and has started updating the workload data for the jobs. For each job that is associated with at least one workload, a CTMWL9I message is issued, followed by a set of CTMWLAI messages - one for each workload that is associated with the job. Alternatively, in response to the WLREFRESH command, this message is followed by the CTMWLBI message.

Corrective Action: No action is required.

CTMWL2I CONTROL-M FINISHED REBUILDING WORKLOAD DATA. `nnnnn` JOBS UPDATED

Explanation: Control-M has completed rebuilding the workload data of the jobs; the data for nnnnn jobs were changed.

Note that if the number of jobs that were changed is 0 ("00000 JOBS"), this does not mean that Control-M has failed to rebuild the workload data of the jobs, but rather it means that none of the currently existing jobs in the AJF were affected by the old or new data provided by the workloads. This might be the result of inactive workloads or due to a mismatch between the jobs that the workloads aim to limit (via the filters) and the actual jobs that currently reside in the AJF.

Corrective Action: No action is required.

CTMWL3E ERROR WHEN TRYING TO ADD A NEW WORKLOAD TO THE JOB WITH ORDERID `order_id`

Explanation: The available memory in the job record for the order_id job is insufficient for the new workload data. The job record is not partially updated, but instead the workload data for the job remains unchanged, as it was before.

Corrective Action: To avoid this problem in the future, increase the memory for job records by increasing the value specified for the FREESPAC parameter in the CTMPARM member.

CTMWL4I WORKLOAD NAME RULE NAME OF LIMIT UTIL WAITING

Explanation: This message is issued in response to the WLLIST Control-M monitor operator command. It is the first message of a series, forming a resource utilization report, which lists the active Workload Policies and provides details on how the rules in these Workload Policies impact job execution.

This message is the first line in the header. It is always followed by CTMWLDI (the second line of the header), then CTMWLEI (a separation line), and finally CTMWLTI (Workload Policy summary) and CTMWL5I (statistics for rules).

Corrective Action: No action is required.

CTMWL5I `rule_type` JOB|`resource_name` `limit` `utilization` `jobsWaiting`

Explanation: This message is part of a series of messages, issued by the WLLIST Control-M monitor operator command. The messages form a resource utilization report, which lists the active Workload Policies and provides details on how the rules in these Workload Policies impact job execution.

If a Workload Policy is not currently active (based on its scheduling or due to Load-Index values), N/A is displayed and statistics are not provided.

CTMWL5I messages are preceded by the CTMWLTI message (Workload Policy summary).

Corrective Action: No action is required.

CTMWL6W WORKLOAD POLICY DEFINITIONS DO NOT EXIST

Explanation: A member containing the workload definitions has not been defined. Control-M will run without the workload facility.

Corrective Action: Determine if workload policies are required. If so, apply the workload policies. For more information, see the Workload Management topic in Chapter 1 of the Control-M for z/OS User Guide.

CTMWL7E INVALID DATA IN WORKLOAD POLICY DEFINITIONS

Explanation: The member with the workload policies contains a technical error. If there were previously defined valid workload policies, the CTMWL8W message is issued after this message. If no previously defined valid workload policies existed, the CTMWL8W message is not issued, and Control-M continues to run without the workload facility.

Corrective Action: Correct the error in the workload policies definitions.

CTMWL8W PREVIOUS WORKLOAD POLICY DEFINITIONS WILL BE USED

Explanation: This message is issued only after the CTMWL7E error message. Since there is an error, the workload policy is not redefined. Instead, the previous workload policy remains active.

Corrective Action: Determine if the previous workload policy is still valid. If not, redefine the workload policy.

CTMWL9I JOB `job_name` ORDERID `order_id` WORKLOADS CHANGED DUE TO `reason`

Explanation: This message is displayed for each job (indicated by job_name and order_id) that satisfies a workload policy. The cause that initiates the workload data change is indicated by reason, which can be one of the following:

JOB ORDER - a workload was assigned to the newly ordered job while the Control-M monitor is active.
MONITOR INIT - a workload was assigned or changed for the job during the start of the Control-M monitor or its resume after NEWDAY processing.
FREE - a workload policy that affects a job was changed while the job was in Held status. As soon as the job is freed, the workload data is updated according to the new policy.
FREE TABLE - a workload policy that affects a SMART Table was changed while the SMART Table was in Held status. As soon as the SMART Table is freed, the workload data is updated according to the new policy.
REBUILD - the workload policy was changed, requiring the workload data to be updated.

Corrective Action: No action is required.

CTMWLAI JOB `job_name` ORDERID `order_id` IS NOW IN WORKLOAD `work_load_name`

Explanation: The work_load_name workload is assigned to the job_name job, with order ID order_id. This message is displayed for each workload that is assigned to the job. A set of one or more of CTMWLAI messages is preceded by the CTMWL9I message.

Corrective Action: No action is required.

CTMWLBI `number` {LOCAL|GLOBAL} WORKLOAD POLICIES LOADED

Explanation: This information message indicates how many Workload Policies of the specified type (Local or Global) were successfully loaded.

Corrective Action: No action is required.

CTMWLCI EMAIL WAS SENT TO emailRecipient

Explanation: This information message notifies you that job attributes were successfully sent to the specified email recipient.

Corrective Action: No action is required.

CTMWLDI TYPE RESOURCE/SEP WKLD JOBS

Explanation: This message is the second line in the header of the resource utilitzation report issued by the WLLIST Control-M monitor operator command. It is always preceded by CTMWL4I (the first line of the header), and followed by CTMWLEI (a separation line) and then CTMWLTI (Workload Policy summary) and CTMWL5I (statistics for rules).

Corrective Action: No action is required.

CTMWLEI ---------------------------------------------

Explanation: This message is a separation line within the resource utilitzation report issued by the WLLIST Control-M monitor operator command. This message is preceded by the CTMWL4I and CTMWLDI header messages, and followed by CTMWLTI (Workload Policy summary) and CTMWL5I (statistics for rules) messages.

Corrective Action: No action is required.

CTMWLFE INTERNAL ERROR IN [LOCAL|GLOBAL] WORKLOAD POLICY MEMBER, MEMBER NOT LOADED CODE rc

Explanation: An internal error occurred. The Workload Policy member could not be accessed.

Corrective Action: Contact BMC Customer Support.

CTMWLGE ERROR IN PERIOD TYPE 6 IN WORKLOAD POLICY workloadPolicyName, LIMIT OF RULE WILL BE IGNORED

Explanation: Errors were found in the advanced scheduling parameters (that is, in a time period of Type 6) in one of the rules defined in this Workload Policy. The rule is ignored.

Corrective Action: Correct the scheduling parameters in the relevant rule.

CTMWLHI LOCAL WORKLOADS MEMBER IS EMPTY OR DOES NOT EXIST

Explanation: No definitions of Local Workload Policies were found in the member that stores these definitions (member CTMWKLDT).

Corrective Action: If you want, define Workload Policies.

CTMWLII GLOBAL WORKLOADS MEMBER IS EMPTY OR DOES NOT EXIST

Explanation: No definitions of Global Workload Policies were found in the member that stores these definitions (member CTMWKLDS).

Corrective Action: If you want, define Workload Policies.

CTMWLJE ERROR READING [LOCAL|GLOBAL] WORKLOAD POLICY, RETURN CODE `rc` REASON CODE `rn`

Explanation: Problem detected in reading the member that stores definitions of Workload Policies.

Corrective Action: Contact BMC Customer Support.

CTMWLKE GETMAIN ERROR, WORKLOAD POLICIES WERE NOT LOADED

Explanation: Workload Policies cannot be loaded due to a memory issue in your environment.

Corrective Action: Troubleshoot your environment for memory issues.

CTMWLLE UNRECOGNIZED VERSION IN WORKLOAD POLICY `policyName`, POLICY WAS NOT LOADED

Explanation: Control-M monitor did not recognize the version of the Workload Policy. The Workload Policy was not loaded.

Corrective Action: Contact BMC Customer Support.

CTMWLMI [WLLIST|WLSTAT] - ACTIVE WORKLOAD POLICIES REPORT

Explanation: This message is the header of a resource utilitzation report issued by either the WLLIST or WLSTAT Control-M monitor operator command. The report lists the active Workload Policies and provides details on how the rules in these Workload Policies impact job execution. The report issued by WLLIST is in tabular format, and the report issued by WLSTAT is in textual format.

Corrective Action: No action is required.

CTMWLNI ---------------------------------------------

Explanation: This message is a separation line within the resource utilitzation report issued by the WLSTAT Control-M monitor operator command. This message is preceded by the CTMWLSI message, which presents a summary for an active Workload Policy, and is followed by a series of messages with statistics for rules within the Workload Policy.

Corrective Action: No action is required.

CTMWLOI JOB LIMIT `job_limit` EXECUTING `number_executing` JOBS, WAITING `number_waiting` JOBS

Explanation: This message presents the impact of a JOB-type rule in a report issued by the WLSTAT Control-M monitor operator command. This rule is associated with the Workload Policy presented in the preceding CTMWLSI message. Statistics in this message include the job limit defined in the rule (that is, the maximum number of jobs that are allowed to run), the number of jobs executing, and the number of jobs waiting to execute.

Corrective Action: No action is required.

CTMWLPI RESOURCE `resource_name` LIMIT `limit` UTIL `utilization` WAITING `number_waiting`

Explanation: This message presents the impact of a RESOURCE-type rule in a report issued by the WLSTAT Control-M monitor operator command. This rule is associated with the Workload Policy presented in the preceding CTMWLSI message. Statistics in this message include the resource limit defined in the rule (that is, the maximum number of this resource that can be used), the number of jobs executing, and the number of jobs waiting to execute.

Corrective Action: No action is required.

CTMWLQI SEPARATE EXECUTION - CURRENTLY WAITING FOR `number_waiting` JOBS

Explanation: This message presents the impact of a SEPARATE EXECUTION rule in a report issued by the WLSTAT Control-M monitor operator command. This rule is associated with the Workload Policy presented in the preceding CTMWLSI message.

Corrective Action: No action is required.

CTMWLRI [LOCAL|GLOBAL] WORKLOAD `workloadPolicyName` WITH `number_executing` JOBS EXECUTING

Explanation: This message presents information about one of the Workload Policies that was specified in the SEPARATE EXECUTION rule (of the preceding CTMWLQI message) and may be blocking jobs from running (jobs associated with the Workload Policy presented in the preceding CTMWLSI message).

Corrective Action: No action is required.

CTMWLSI [LOCAL|GLOBAL] `workloadPolicyName`, UTILIZIATION `utilization`

Explanation: This message presents an active Workload Policy and summarizes its utilization (that is, the total number of associated jobs executed) in a resource utilitzation report issued by the WLSTAT Control-M monitor operator command. This message is followed by a series of messages that provide statistics for rules within the Workload Policy.

Corrective Action: No action is required.

CTMWLTI [L|G]-`workloadPolicyName` `utilization`

Explanation: This message presents an active Workload Policy and summarizes its utilization (that is, the total number of associated jobs executed) in a resource utilitzation report issued by the WLLIST Control-M monitor operator command. This message is followed by a series of CTMWL5I messages, which present statistics for rules within the Workload Policy.

Corrective Action: No action is required.

CTMWLZI `(Blank separation line)`

Explanation: This message is a blank separation line within the resource utilitzation report issued by the WLSTAT Control-M monitor operator command. This message ends a series of messages with statistics for rules within a Workload Policy and is usually followed by a CTMWLSI message, which presents the next active Workload Policy.

Corrective Action: No action is required.

Messages CTMX00 through CTMXxx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTMX01I CONTROL-M GLOBAL SYSPLEX MONITOR STARTED ON SYSTEM `systemId`

Explanation: This information message indicates that the Control-M monitor that was started on system systemId will operate as the global Sysplex monitor. This monitor is the first Control-M monitor started in the CTMPLEX environment.

Corrective Action: No action is required.

CTMX02I CONTROL-M LOCAL SYSPLEX MONITOR STARTED ON SYSTEM `systemId`

Explanation: This information message indicates that the monitor started on system systemId operates as a local Sysplex monitor. All monitors in the CTMPLEX environment, except the first monitor, which acts as the global Sysplex monitor, are local monitors.

Corrective Action: No action is required.

CTMX03I SHUT DOWN REQUEST RECEIVED BY CONTROL-M LOCAL MONITOR ON SYSTEM `systemId`

Explanation: This information message indicates that the global monitor issued a shut down request to the local monitor on system systemId. The shutdown is in response to a STOP CONTROLM command that was issued to the global monitor. The entire CTMPLEX is stopped. All local monitors are shut down.

Shutdown of the Control-M local monitor begins.

Corrective Action: No action is required.

CTMX04I SUSPEND REQUEST RECEIVED BY CONTROL-M LOCAL MONITOR ON SYSTEM `systemId`

Explanation: This information message indicates that activity of the local monitor on system systemId is suspended until the end of New Day Processing as a result of a SUSPEND request issued before the New Day procedure began.

The Control-M local monitor stops its activity till end of New Day processing.

Corrective Action: No action is required.

CTMX05E GLOBAL MONITOR FAILED. THE LOCAL IS SWITCHING TO GLOBAL ON SYSTEM `systemId`

Explanation: In response to the global monitor failing or being stopped by operator command, the local monitor on system systemId is now the global monitor. In a CTMPLEX environment, there must always be a global monitor.

The local monitor switches to Global mode.

Corrective Action: If the global monitor failed, prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX06I NEW LOCAL MONITOR CONNECTED TO CONTROL-M SYSPLEX

Explanation: This information message indicates that the global monitor detected a new local monitor connected to CTMPLEX.

Corrective Action: No action is required.

CTMX07I LOCAL MONITOR DISCONNECTED FROM CONTROL-M SYSPLEX

Explanation: This information message indicates that the global monitor detected that a local monitor is disconnected from CTMPLEX.

CTMPLEX continues running, and no jobs are lost. Jobs that were being processed by the disconnected local monitor are passed to the global monitor, and from there to other local monitors.

Corrective Action: A new local monitor can be started on the system where the local monitor disconnected, or on any other system that has no Control-M monitor.

CTMX08E ERROR IN COUPLING FACILITY REQUEST

Explanation: An error occurred during access of the CTMPLEX coupling facility. This message is generally accompanied by other messages that explain the exact type of error and system actions.

The system action depends on the type of error. If the error is an environmental error, Control-M switches from CTMPLEX to regular mode. All local monitors shut down, and the global monitor continues working in regular, not CTMPLEX, mode. If the error is an internal or program error in handling the Coupling facility request, the whole CTMPLEX shuts down.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support. In case of environmental errors, Control-M can be switched back to CTMPLEX mode by STARTPLEX operator command.

CTMX09E THERE IS ANOTHER CONTROL-M MONITOR ON THE SYSTEM `systemId`

Explanation: System systemId has more than one Control-M monitor. Only one Control-M monitor, either global or local, may run on any SYSPLEX member.

Only the first Control-M monitor on system systemId continues to operate. The other monitors on the system shut down.

Corrective Action: Ensure that only one Control-M monitor runs on any system in the CTMPLEX. If desired, use LISTPLEX operator command to display the current CTMPLEX environment.

CTMX0AE SYSTEM `systemId` NOT FOUND IN CTMPLEX PARAMETERS TABLE

Explanation: An attempt was made to start a Control-M monitor in system systemId, which is not defined in a CTMPLEX parameter member. For the monitor to be started in the system, the system must be defined in the CTMPLEX parameter member.

The Control-M monitor is not started in system systemId.

Corrective Action: Ensure that all systems that should be available for Control-M monitors are identified in the CTMPLEX parameter member.

CTMX0BE INTERNAL ERROR IN CTMPLEX PROCESSING. `error`

Explanation: An internal error occurred in CTMPLEX processing.

CTMPLEX shuts down.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX0DE NO LOCAL MONITOR FOUND FOR PROCESSING OF A JOB

Explanation: As a result of an internal error in CTMPLEX processing, no local Control-M monitor was found for processing a job.

The job is processed by the global monitor.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX0EE STRUCTURE NAME `structName` IS ALREADY IN USE BY ANOTHER CTMPLEX

Explanation: The same Coupling facility structure name is being used by another CTMPLEX environment. The structure name of the Coupling facility must be unique to the CTMPLEX environment.

CTMPLEX does not start.

Corrective Action: Specify another name for the Coupling Facility structure in the CTMPLEX parameter member.

CTMX11E ERROR IN `reqType` REQUEST FOR CTMPLEX COUPLING FACILITY. RC `rc` REASON `rsn`

Explanation: An error occurred while accessing the CTMPLEX coupling facility. This message is usually accompanied by other messages that explain system actions.

The system action depends on the type of error in the Coupling Facility. For environmental errors, Control-M switches from CTMPLEX to regular mode. All local monitors shut down and the global monitor continues working in regular, not CTMPLEX, mode. For internal or program errors, the entire CTMPLEX shuts down.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support. For environmental errors, Control-M can be switched back to CTMPLEX mode by STARTPLEX operator command.

CTMX12I THE COMMAND IS ROUTED TO BE HANDLED BY GLOBAL MONITOR

Explanation: This information message indicates that the Local monitor received an operator command that may only be processed by the Global monitor. In this situation the Local monitor routes the command to the Global monitor.

Corrective Action: No action is required.

CTMX13E MAXIMUM NUMBER OF CTMPLEX LOCAL MONITORS EXCEEDED

Explanation: An attempt was made to start more than the allowable number of Control-M monitors. A maximum of 32 Control-M monitors, one global and the rest local, are allowed in the CTMPLEX environment

Additional monitors beyond the first allowed maximum of 32 are not started.

Corrective Action: To add additional monitors, stop an active local monitor for each new monitor to be added. Use the LISTPLEX operator command to display a current CTMPLEX environment.

CTMX14I THE COMMAND IS NOT VALID FOR A LOCAL MONITOR

Explanation: This information message indicates that a local monitor received an operator command that is valid for a global monitor only.

The operator command is ignored.

Corrective Action: Issue the operator command to the global monitor only. Operator command WHOGLOBAL, which is valid for each monitor, can be used to display information about the global monitor.

CTMX15I WORK BALANCING MODE ACTIVATED ON CTMPLEX ENVIRONMENT

Explanation: This information message indicates that Work Balancing mode was activated by the operator command F CONTROLM,BALANCE=YES.

CTMPLEX works in Work Balancing mode.

Corrective Action: No action is required.

CTMX16I WORK BALANCING MODE DEACTIVATED ON CTMPLEX ENVIRONMENT

Explanation: This information message indicates that Work Balancing mode was deactivated by the operator command F CONTROLM,BALANCE=NO.

CTMPLEX stops working in Work Balancing mode.

Corrective Action: No action is required.

CTMX17I CTMPLEX COMMANDS ARE NOT AVAILABLE WHEN CTMPLEX=N IN CTMPARM

Explanation: This information message indicates that a CTMPLEX operator command was issued while the CTMPLEX facility is not available. The facility is not available because the CTMPLEX parameter is set to N in the CTMPARM member in the IOA PARM library.

CTMPLEX operator commands are ignored

Corrective Action: To activate the CTMPLEX facility, set the CTMPLEX parameter to Y in the CTMPARM member, and restart the Control-M monitor.

CTMX18I GLOBAL CTMPLEX MONITOR IS WAITING FOR THE LOCAL MONITORS TO SHUT DOWN

Explanation: This information message indicates that as part of CTMPLEX shut down, the global monitor passed STOP requests to all local monitors, and is waiting for them to shut down.

The global monitor waits for the local monitors to shut down. When all local monitors are shut down, the global monitor updates the Active Jobs file with the last changes, and shuts down.

Corrective Action: No action is required.

CTMX19E NO ACTIVE LOCAL MONITOR FOUND ON SYSTEM `systemId`

Explanation: CTMPLEX operator command F CONTROLM,STOPGSM,systemId was issued to stop the global monitor, and to pass global functions to the local monitor on system systemId, but, no active local monitor was found on system systemId.

The command is ignored.

Corrective Action: Ensure that the correct system identifier is specified in the operator command. Operator command LISTPLEX can be issued to display a current CTMPLEX configuration.

CTMX1AI `mon_type` - `jobName_of_mon.stepName_of_mon` ON SYSTEM `systemId`. ACTIVE JOBS `numActiveJobs`, CAPACITY `systemCapacity`

Explanation: This information message displays the current CTMPLEX configuration in response to a LISTPLEX operator command. This message is issued for each monitor in the CTMPLEX.

The list of Control-M global and local monitors is displayed.

Corrective Action: No action is required.

CTMX1BI JOB WAS HANDLED BY LOCAL MONITOR ON SYSTEM `systemId`

Explanation: This information message is a statistics message issued to IOA log any time a job is handled by a local monitor. It indicates the system on which the job was handled.

Corrective Action: No action is required.

CTMX1CI SUCCESSFUL RECOVERY AFTER LOCAL MONITOR DISCONNECTED

Explanation: This information message indicates that the global monitor successfully finished a recovery after a local monitor disconnected.

CTMPLEX continues working. All jobs processed by disconnected local monitor were passed to the global or other local monitors.

Corrective Action: An additional local monitor can be activated on any suitable SYSPLEX member where no such monitor runs.

CTMX1DE UNSUCCESSFUL RECOVERY AFTER LOCAL MONITOR DISCONNECTED

Explanation: Errors occurred in during recovery by the global monitor following a local monitor disconnect.

CTMPLEX continues working, but some jobs from the disconnected local monitor may be not passed to the global or other local monitors, and therefore may remain unprocessed.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX1EI SUCCESSFUL COMPLETION OF LOCAL-TO-GLOBAL SWITCHING

Explanation: This information message indicates that a local monitor was successfully switched to Global mode. The switch to Global mode is generally performed if the global monitor fails, or stops in response to a STOPGSM operator command.

CTMPLEX continues working; the local monitor is now the global monitor.

Corrective Action: If the global monitor failed, prepare the Control-M monitor full output and contact BMC Customer Support. An additional local monitor can be activated on any suitable SYSPLEX member where no such monitor runs. Operator command LISTPLEX can be issued to display a current CTMPLEX configuration.

CTMX1FE ERRORS ENCOUNTERED DURING LOCAL-TO-GLOBAL SWITCHING

Explanation: Errors occurred in the local monitor during switching to Global mode. The switch to Global mode is generally performed if the global monitor fails, or stops in response to a STOPGSM operator command.

The local monitor shuts down.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX1GE LOCAL MONITOR TERMINATING DUE TO CTMPLEX COUPLING FACILITY FAILURE

Explanation: The local monitor is shutting down due to CTMPLEX Coupling Facility environmental failures, or internal or program errors in the CTMPLEX facility. This message is usually accompanied by other messages explaining the reason for the failure.

The local monitor shuts down. Its jobs are passed to the global monitor and other local monitors. CTMPLEX continues working.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX21E ERROR IN PROPAGATING OPERATOR COMMAND TO LOCAL MONITORS. THE COMMAND IS IGNORED

Explanation: The global monitor failed to propagate an operator command to the local monitors. This message is usually accompanied by other messages explaining a reason of failure.

The operator command is ignored.

Corrective Action: Try to repeat the operator command. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX22E PREVIOUS COMMAND WAS NOT PROCESSED BY A LOCAL MONITOR. RETRY THE CURRENT COMMAND LATER

Explanation: The previous operator command was not yet extracted and/or processed by all of the local monitors. In the CTMPLEX environment, a new operator command can be processed only after a previous command was processed by all active local monitors.

The operator command is ignored.

Corrective Action: Try to repeat the operator command. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX23I GLOBAL CTMPLEX MONITOR IS `jobName.stepName` ON SYSTEM `systemId`

Explanation: This information message displays information about the current global monitor in response to the WHOGLOBAL operator command.

Corrective Action: No action is required.

CTMX24E CONTROL-M CONTINUES WORKING IN STAND-ALONE MODE BECAUSE OF COUPLING FACILITY FAILURE

Explanation: Control-M switched from CTMPLEX mode to regular Standalone mode because the global monitor detected an environmental error while accessing the CTMPLEX Coupling Facility structure. The message is accompanied by a message supplying additional information about the Coupling Facility failure.

All local monitors shut down. The global monitor continues working in regular Standalone mofe, not CTMPLEX mode.

Corrective Action: Fixing the problem caused by the Coupling Facility environmental error. Then, return to CTMPLEX mode by issuing the STARTPLEX operator command.

CTMX25E LOCAL CTMPLEX MONITOR SHUTS DOWN ON SYSTEM `systemId` BECAUSE OF COUPLING FACILITY FAILURE

Explanation: The local monitor shut down because an environmental error in accessing the CTMPLEX Coupling Facility structure was detected either by the global monitor or by the local monitor.

If a failure in accessing the Coupling Facility is detected by the global monitor, then all local monitors shut down, and the global monitor continues working in Standalone mode, not CTMPLEX mode. If a failure in accessing Coupling Facility is detected by a local monitor, then only this monitor shuts down.

Corrective Action: Search the job log of the global and local monitors for a message supplying additional information about the Coupling Facility failure. Fixing the problem caused by the Coupling Facility environmental error. Then return to CTMPLEX mode by issuing a STARTPLEX operator command. Additional local monitors can then be activated.

CTMX26I CONTROL-M IS CURRENTLY IN STAND-ALONE MODE DUE TO COUPLING FACILITY FAILURE

Explanation: This information message indicates that a requested CTMPLEX operator command could not be processed, or a local monitor could not be started, because Control-M is running in Standalone mode due to Coupling Facility failure.

While Control-M works in Standalone mode, it ignores the CTMPLEX operator command, and no local monitors can be activated.

Corrective Action: Fix the problem caused by the Coupling Facility environmental error. Then return to CTMPLEX mode by issuing a STARTPLEX operator command.

CTMX27I USE 'STARTPLEX' COMMAND TO REACTIVATE CTMPLEX PROCESSING

Explanation: This information message indicates that CTMPLEX processing can be reactivated by issuing a STARTPLEX operator command. This message is usually issued following a CTMPLEX operator command request, or an attempt to start a local monitor while Control-M runs in Stand-alone mode due to a Coupling Facility failure.

Corrective Action: No action is required.

CTMX28I CTMPLEX IS ALREADY ACTIVE

Explanation: This information message indicates that a STARTPLEX operator command was issued while Control-M already works in CTMPLEX mode. Command STARTPLEX is used to place Control-M in CTMPLEX mode. Since CTMPLEX mode is already active, the STARTPLEX command is unnecessary.

The STARTPLEX operator command is ignored.

Corrective Action: No action is required.

CTMX29E CTMPLEX COUPLING FACILITY STRUCTURE IS FULL

Explanation: The CTMPLEX Coupling Facility structure is full.

CTMPLEX continues running. New active jobs are processed by the global monitor, but the jobs are not passed to local monitors. Control-M waits until some active jobs have finish and the Coupling facility shortage is relieved.

Corrective Action: Increase the value of the MAXENTRY parameter in the CTMPLEX parameter member, and restart CTMPLEX.

CTMX2AE THE MONITOR RUNNING ON SYSTEM `systemId` IS ALREADY A GLOBAL

Explanation: The system specified in operator command STOPGSM sys is the system in which the global monitor is already running. This is not allowed because this command is used to stop the global monitor and pass global function to the monitor running on the specified system (systemId).

The STOPGSM operator command is ignored.

Corrective Action: Reissue the STOPGSM command, but ensure that the system specified in the command is not the system with the current global monitor. Operator command. LISTPLEX can be issued to display the current CTMPLEX environment.

CTMX2BW MAXIMUM JOBS NUMBER `num` SET FOR LOCAL ON SYSTEM `systemId`

Explanation: There is a conflict in the MAXCAP (maximum capacity) and RELCAP (relative capacity) definitions for the indicated system in the CTMPLEX parameter table. MAXCAP is, but should not be, less than RELCAP.

The value for MAXCAP is set equal to the RELCAP value for the system entry.

Corrective Action: If these values should not be equal increase the MAXCAP value, or decrease the RELCAP value for the system, in the CTMPLEX parameter member. Then stop and restart CTMPLEX.

CTMX2CW WARNING: COUPLING FACILITY STRUCTURE IS `num`% FULL

Explanation: The CTMPLEX Coupling facility structure is nearly full.

CTMPLEX continues running, and will continue to run even after the Coupling facility becomes full. However, once the Coupling facility becomes full, new active jobs are processed by the global monitor, but are not passed to local monitors. After the Coupling facility shortage is relieved, Control-M continues sending jobs to local monitors.

Corrective Action: Increase the value of the MAXENTRY parameter in CTMPLEX parameter member, and restart CTMPLEX.

CTMX2DI COUPLING FACILITY SPACE PROBLEM ALLEVIATED

Explanation: This information message indicates that the CTMPLEX Coupling Facility structure space problem was alleviated. This message is issued after message CTMX2CW is reissued.

CTMPLEX once again sends new active jobs to local monitors.

Corrective Action: No action is required.

CTMX2EI COUPLING FACILITY STRUCTURE IS `num`% FULL

Explanation: This information message is a part of the CTMPLEX response to a LISTPLEX operator command.

Corrective Action: No action is required.

CTMX31W NO ACTIVE LOCAL MONITORS FOUND IN CTMPLEX

Explanation: The user issued a STOPGSM command to stop the Control-M global monitor and pass global functions to one of local monitors, but there are no active local monitors.

The STOPGSM command is ignored.

Corrective Action: Use the STOP command to stop the global monitor, or activate a local monitor and then issue the STOPGSM command.

CTMX32W STOP COMMAND RECEIVED BY GLOBAL MONITOR. WOULD YOU LIKE TO STOP ENTIRE CTMPLEX?

Explanation: The user issued a STOP command to the Control-M global monitor while there are still active local monitors.

Message CTMX33W is issued after this message.

Corrective Action: Respond to message CTMX33W.

CTMX33W ANSWER Y(YES)-STOP CTMPLEX, N(NO)-IGNORE, G(GSM)-STOP GLOBAL ONLY

Explanation: The user issued a STOP command to the Control-M global monitor while there are still active local monitors. This message appears after message CTMX32W.

The system action depends on the user response.

Corrective Action: Select one of the available responses:

YES - the whole CTMPLEX is stopped (that is, all monitors are stopped)
NO - the STOP command is ignored
GSM - only the global monitor is stopped

CTMX34I STOP COMMAND IS IGNORED

Explanation: The user issued a STOP command for the Control-M global monitor while there are still active local monitors, and answered NO to message CTMX33W.

The STOP command is ignored.

Corrective Action: Repeat the STOP command to stop the global monitor, or activate a local monitor and then issue the STOPGSM command.

CTMX35I GLOBAL MONITOR SHUTS DOWN UPON REQUEST FROM OPERATOR

Explanation: The user issued a STOPGSM command, or a STOP command for the Control-M global monitor while there are still active local monitors. After messages CTMX32W and CTMX33W were issued, the user answered GSM to message CTMX33W.

The global monitor shuts down and one of active local monitors switches to global mode.

Corrective Action: No action is required.

CTMX36W STRUCTURE SIZE `size` WAS USED INSTEAD OF MAXENTRY SIZE

Explanation: This message may be displayed during Control-M CTMPLEX environment initialization. If the MAXENTRY parameter value in the CTMPLEX PARM member or the SIZE/INITSIZE parameter value in the CFRM policy is too small for CTMPLEX requirements, Control-M attempts to automatically recover from this 'invalid structure size' error by using the minimum required structure size, size. The value of size, which is displayed in the message, is equal to the minimum required number of 4K blocks.

If this retry attempt is successful, Control-M displays this message with the structure size used instead of the user-specified MAXENTRY value.

Corrective Action: No action is required.

CTMX37I ALL LOCAL MONITORS STOPPED. CONTROL-M WILL OPERATE IN STAND-ALONE MODE

Explanation: The user issued a STOPPLEX command, or the CTMPLEX mode changed to the regular standalone (no- CTMPLEX) mode as a result of a Coupling Facility failure.

As a result of the STOPPLEX command or a Coupling Facility failure, all local monitors are stopped. The global monitor disconnects from the Coupling Facility, releases all CTMPLEX resources and continue running as a regular Control-M monitor.

Corrective Action: Issue the STARTPLEX command to return to CTMPLEX mode.

CTMX38I CONTROL-M IS CURRENTLY IN STAND-ALONE MODE DUE TO STOPPLEX REQUEST

Explanation: The operator issued a command valid only in the CTMPLEX environment, while Control-M is currently in regular standalone mode (that is, not CTMPLEX) due to a STOPPLEX request or a Coupling Facility failure.

Any CTMPLEX operator command is ignored if Control-M is not currently in CTMPLEX mode.

Corrective Action: Issue the STARTPLEX command to return to CTMPLEX mode.

CTMX39E GLOBAL MONITOR NOT FOUND. LOCAL MONITOR TERMINATES ON THE SYSTEM `sysName`

Explanation: The local monitor detected that the global monitor terminated while the Control-M New Day procedure was running.

The local monitor shuts down.

Corrective Action: Check the reason for the global monitor termination, and restart Control-M.

CTMX3AI GLOBAL MONITOR WAITS UNTIL ALL LOCAL MONITORS ARE SUSPENDED BEFORE STARTING NEWDAY

Explanation: The global monitor intends to invoke the Control-M New Day procedure. Before doing this, the global monitor sends SUSPEND requests to all active local monitors, and waits until they confirm their suspension.

The global monitor waits for the local monitors to suspend their processing before invoking the New Day procedure.

Corrective Action: No action is required.

CTMX3BW LOCAL MONITOR IS WAITING FOR THE GLOBAL CTMPLEX MONITOR TO SHUT DOWN

Explanation: The global monitor is in the process of terminating. The local monitor should switch to the global mode, but waits until the global monitor completely terminates.

The local monitor waits until the global monitor completely terminates.

Corrective Action: Check the reason for termination of the global monitor, and check whether the global monitor is hanging during this termination. If it hangs, then cancel the Global monitor with the dump, prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX3CE SYSTEM `sysname` ALREADY REGISTERED IN CTMPLEX

Explanation: This is an internal CTMPLEX error. The local monitor starts on a particular system, but detects that another local monitor on the same system is already registered in the CTMPLEX environment.

The local monitor shuts down.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTMX3DE RESOURCE SERIALIZATION INACTIVE

Explanation: The local monitor detects that global resources serialization is not active in the SYSPLEX environment.

The local monitor shuts down.

Corrective Action: Check the status of global resources serialization. It should be active in order to use CTMPLEX in the SYSPLEX environment.

CTMX3FE MINIMUM STRUCTURE SIZE IS `size`; INCREASE CFRM POLICY VALUES ACCORDINGLY

Explanation: This message may be displayed during Control-M CTMPLEX environment initialization. If the MAXENTRY parameter value in the CTMPLEX PARM member or the SIZE/INITSIZE parameter value in the CFRM policy is too small for CTMPLEX requirements, Control-M will attempt to automatically recover from this 'invalid structure size' error by using the minimum required structure size, size. The value of size, which is displayed in the message, is equal to the minimum required number of 4K blocks.

If this retry attempt is successful, Control-M displays message CTMX36W. However, if the retry attempt is unsuccessful because the structure size is too small, Control-M displays this message with the minimum required structure size.

Control-M is activated in stand-alone mode (not in CTMPLEX mode).

Corrective Action: Contact your system programming group and have them increase the structure size in the CFRM policy to the minimum required structure size specified in the message. When increasing the size in the CFRM policy, ensure that the size is specified in Kilobytes (not to be confused with the value of size in the message text, which indicates the number of 4K blocks.)

CTMX41I LOCAL MONITOR SUSPENDED AWAITING RECONNECT TO CTMPLEX. ONLY STOP COMMAND AVAILABLE

Explanation: The Local Monitor is in SUSPEND mode due to Coupling facility failure. In this mode, the Local Monitor does not receive any operator commands except for STOP.

The operator command is ignored.

Corrective Action: Issue the operator command to the Global Monitor or wait until the Coupling Facility recovers, and resumes CTMPLEX processing.

CTMX42W LOCAL CTMPLEX MONITOR (SYSTEM `sysName`) PROCESSING SUSPENDED DUE TO COUPLING FACILITY FAILURE

Explanation: The Local Monitor is in SUSPEND mode due to Coupling Facility failure detected by the Global Monitor. The Local Monitor waits for the recovery of the Coupling Facility and the request of Global Monitor to reconnect to CTMPLEX, and resumes processing.

Automatic CTMPLEX recovery is controlled by two CTMPLEX installation parameters:

RECOVERT - Frequency of attempts to recover CTMPLEX after Coupling Facility failures
RECOVERM - Maximum number of attempts to recover CTMPLEX after Coupling Facility failures.

The Local Monitor does not handle any jobs. It only waits for the request of Global Monitor to reconnect to CTMPLEX, and resumes processing.

Corrective Action: Check the system log and job logs of Control-M Monitors, and try to find the reason for the Coupling Facility failure.

CTMX43I LOCAL MONITOR (SYSTEM `sysName`) ATTEMPTING TO RECONNECT CTMPLEX

Explanation: The Local Monitor received the request from the Global Monitor to reconnect to CTMPLEX, and resumes the processing. Before this, the Local Monitor was in SUSPEND mode due to Coupling facility failure detected by the Global Monitor.

The Local Monitor attempts to reconnect to CTMPLEX and to start processing the jobs. If the Local Monitor does not succeed in reconnecting, it stops immediately.

Corrective Action: No action is required.

CTMX44I LOCAL MONITOR (SYSTEM `sysName`) RECONNECTED TO CTMPLEX. PROCESSING RESUMED

Explanation: The Local Monitor reconnected to CTMPLEX after it was in SUSPEND mode due to Coupling facility failure detected by the Global Monitor.

The Local Monitor resumes processing the jobs.

Corrective Action: No action is required.

CTMX45I GLOBAL MONITOR WILL ATTEMPT TO RESUME CTMPLEX PROCESSING LATER

Explanation: The Global Monitor stopped the CTMPLEX facility and switched to Standalone mode due to Coupling Facility failure. During some time interval, the Global Monitor will attempt to recover the CTMPLEX facility, that is, it will try to reconnect to the Coupling Facility and resume CTMPLEX processing.

Automatic CTMPLEX recovery is controlled by two CTMPLEX installation parameters:

RECOVERT - Frequency of attempts to recover CTMPLEX after Coupling Facility failures
RECOVERM - Maximum number of attempts to recover CTMPLEX after Coupling Facility failures.

The Global Monitor continues working in Standalone mode. After some time interval (the number of seconds specified by the RECOVERT installation parameter of CTMPLEX), the Global Monitor will attempt to recover the CTMPLEX facility, that is, it will try to reconnect to the Coupling Facility and resume CTMPLEX processing.

Corrective Action: Check the system log and job logs of Control-M Monitors, and try to find the reason for the Coupling Facility failure.

CTMX46I GLOBAL MONITOR ATTEMPTING TO RESUME CTMPLEX PROCESSING

Explanation: The Global Monitor tries to reconnect to the Coupling Facility and resume CTMPLEX processing. Before this, the Global Monitor was working in Standalone mode due to Coupling Facility failure.

If the Global Monitor succeeds in reconnecting to the Coupling Facility, it sends the request to reconnect to the Coupling Facility and resume processing to Local monitors (which are in SUSPEND mode).

If the Global Monitor does not succeed in reconnecting to the Coupling Facility (the Global monitor fails again), then after some time interval (the number of seconds specified by the CTMPLEX installation parameter RECOVERT), the Global Monitor performs another attempt to recover CTMPLEX. The maximum number of attempts is defined in the CTMPLEX installation parameter RECOVERM.

Corrective Action: No action is required.

CTMX47I GLOBAL MONITOR SUCCESSFULY RECONNECTED TO COUPLING FACILITY. LOCAL MONITORS WILL RESUME PROCESSING

Explanation: The Global Monitor successfully reconnected to the Coupling Facility and resumed CTMPLEX processing. Before this, the Global Monitor was working in Standalone mode due to Coupling Facility failure.

After the Global Monitor successfully reconnects to the Coupling Facility and resumes CTMPLEX processing, it sends to Local Monitors the request to reconnect to the Coupling Facility and resume processing the jobs (before this the Local Monitors were in SUSPEND mode due to Coupling Facility failure.

Corrective Action: No action is required.

CTMX48E CONTROL-M OPERATING IN STAND-ALONE MODE DUE TO CTMPLEX INITIALIZATION FAILURE

Explanation: The Control-M monitor did not successfully activate the CTMPLEX facility.

The Control-M monitor continues working in Standalone (regular) mode.

Corrective Action: Investigate the job log of the Control-M monitor and clarify the reason for the CTMPLEX initialization failure. After fixing the problem, the CTMPLEX facility may be activated with the STARTPLEX operator command.

CTMX49E MAXIMUM NUMBER OF ATTEMPTS TO REACTIVATE CTMPLEX EXCEEDED. ALL LOCAL MONITORS WILL TERMINATE.

Explanation: The Global Monitor did not successfully reconnect to the Coupling facility and recover CTMPLEX. The maximum number of attempts to recover CTMPLEX (CTMPLEX installation parameter RECOVERM) was exhausted.

The Global monitor stops all Local monitors and continues working in Standalone (regular) mode.

Corrective Action: Investigate the job log of the Control-M monitor and clarify the reason for the CTMPLEX recovery failures. After fixing the problem, the CTMPLEX facility may be activated with the STARTPLEX operator command.

CTMX4AE LOCAL MONITOR TERMINATED DUE TO FAILURE OF THE GLOBAL MONITOR TO REACTIVATE CTMPLEX

Explanation: The Local monitor received a termination request from the Global monitor, because the Global monitor could not successfully reconnect to the Coupling facility and recover CTMPLEX. The maximum number of attempts to recover CTMPLEX (CTMPLEX installation parameter RECOVERM) was exhausted by the Global monitor.

Local monitors terminate and the Global monitor continues working in Standalone (regular) mode.

Corrective Action: Investigate the job log of the Control-M Global monitors and clarify the reason for the CTMPLEX recovery failures. After fixing the problem, the CTMPLEX facility may be activated with the STARTPLEX operator command.

CTMX4BI * START OF GLOBAL RESPONSE TO ROUTED OPERATOR COMMANDS *

Explanation: The Local monitor received an operator command that may only be processed by the Global monitor. In this situation the Local monitor routes the command to the Global monitor. This message indicates the start of the Global monitor’s response to the routed operator command.

The Global monitor’s response records to the operator command are issued after this message.

Corrective Action: No action is required.

CTMX4CI * END OF GLOBAL RESPONSE TO ROUTED OPERATOR COMMANDS *

Explanation: The Local monitor received an operator command that may only be processed by the Global monitor. In this situation the Local monitor routes the command to the Global monitor. This message indicates the end of the Global monitor’s response to the routed operator command.

The Global monitor’s response records to the operator command are issued before this message.

Corrective Action: No action is required.

CTMX51I LOCAL CTMPLEX MONITOR (SYSTEM `system_name`) SWITCHES TO GLOBAL BECAUSE IT HAS THE HIGHEST PRIORITY

Explanation:The Local Monitor switches to Global because it has the highest PRIORITY (in the CTMPLEX parameters member) among all active Control-M monitors.

Corrective Action:No action is required.

CTMX52I GLOBAL CTMPLEX MONITOR (SYSTEM `system_name`) SWITCHES TO LOCAL BECAUSE IT FOUND A MONITOR WITH A HIGHER PRIORITY

Explanation:The Global Monitor switches to Local because it detected that the active Local monitor has a higher PRIORITY (in the CTMPLEX parameters member) than the Global Monitor.

Corrective Action:No action is required.

CTMX53I SUCCESSFUL FINISH OF GLOBAL - LOCAL SWITCH

Explanation:The Global Monitor successfully switched to Local. The Global Monitor made the switch because it detected that the active Local monitor has a higher PRIORITY (in the CTMPLEX parameters member) than the Global Monitor.

Corrective Action:No action is required.

CTMX54I Control-M MONITOR STARTED ON SYSTEM `system_name` WAITING TILL ANY LOCAL SWITCHES TO GLOBAL

Explanation:The Global Monitor was restarted a very short time after it was stopped or terminated, before any Local Control-M monitor could detect the termination of the Global Monitor and switch to Global status. The restarted monitor delays until any Local monitor successfully switches to Global status, after which the restarted monitor continues initialization as a Local monitor.

Corrective Action:No action is required.

CTMX55I GLOBAL MONITOR STOPPED BY OPERATOR. THE LOCAL IS SWITCHING TO GLOBAL ON SYSTEM `system_name`

Explanation: The Local Monitor is switching to Global status because the previously active Global Monitor was stopped by the operator.

Corrective Action:No action is required.

CTMX61W ERROR IN NEWDAY - MONITOR CROSS MEMORY TRANSFER OF AJF. REASON `'rsn'`.

Explanation: Control-M encountered errors when trying to implement the New Day in Memory facility (activated by the NEWDAYIM=Y installation parameter). This facility uses synchronous cross-memory to copy the AJF between the New Day procedure and Control-M monitor address spaces.

The New Day in Memory facility is deactivated. The AJF is always read from DASD by the New Day procedure and by the Control-M monitor.

Corrective Action: Investigate the cause of the error according to reason code rsn. If necessary, contact Control-M technical support for assistance. To reactivate the New Day in Memory facility, stop and then restart the Control-M monitor.

CTMX62W NEWDAY - MONITOR CROSS MEMORY TRANFER OF AJF NOT AVAILABLE

Explanation: The Control-M New Day procedure failed to implement the New Day in Memory facility (activated by the NEWDAYIM=Y installation parameter). This facility uses synchronous cross-memory to copy the AJF between the New Day procedure and Control-M monitor address spaces. This message is issued if the New Day procedure detects that the cross-memory environment (to be set by the Control-M monitor) is unavailable.

Possible causes are:

not running the Control-M monitor on the same system where the New Day procedure runs
the Control-M monitor failed to establish the cross-memory environment.

The New Day in Memory facility is deactivated. The AJF is read from DASD by the New Day procedure and by the Control-M monitor.

Corrective Action: Check if Control-M runs on the same system as the New Day procedure. If so, look at the Control-M monitor’s system log to find the reason for not establishing the cross-memory environment. If necessary, contact Control-M technical support for assistance.

CTMX63W MONITOR FAILED DURING NEWDAY AJF COMPRESS

Explanation: The Control-M New Day procedure failed to implement the New Day in Memory facility (activated by the NEWDAYIM=Y installation parameter). This facility uses synchronous cross-memory to copy the AJF between the New Day procedure and the Control-M monitor address spaces. The message is issued when the New Day procedure should be copying the compressed AJF to the Control-M monitor’s memory, but detects that the monitor is inactive.

The New Day procedure continues its processing. When the Control-M monitor restarts, it reads the AJF from DASD.

Corrective Action: No action is required.

CTMX64I AJF COPIED FROM MONITOR MEMORY

Explanation: This information message indicates that the Control-M New Day procedure copied the AJF from the Control-M monitor’s memory. The New Day does this to implement the New Day in Memory facility (activated by the NEWDAYIM=Y installation parameter). This facility uses synchronous cross-memory to copy the AJF between the New Day procedure and Control-M monitor address spaces.

The New Day procedure continues its processing. The compressed AJF is copied back to the Control-M monitor’s memory.

Corrective Action: No action is required.

CTMX65I COMPRESSED AJF RETURNED TO MONITOR

Explanation: This information message indicates that the Control-M New Day procedure copied the compressed AJF back to the Control-M monitor’s memory. The New Day procedure does this to implement the New Day in Memory facility (activated by the NEWDAYIM=Y installation parameter). This facility uses synchronous cross-memory to copy the AJF between the New Day procedure and Control-M monitor address spaces.

When Control-M resumes processing after completing the New Day procedure, it uses the AJF that was copied from the New Day procedure, and does not need to read the compressed AJF from DASD.

Corrective Action: No action is required.

CTMX66I CROSS MEMORY ENVIRONMENT SET TO EXPEDITE NEWDAY PROCESSING

Explanation: This information message indicates that the Control-M monitor established the cross-memory environment used by the New Day in Memory facility (activated by the NEWDAYIM=Y installation parameter). This facility uses synchronous cross-memory to copy the AJF between the New Day procedure and Control-M monitor address spaces. The New Day procedure extracts the AJF from the Control-M monitor memory. After compressing the AJF, the New Day procedure copies the compressed AJF back to the Control-M monitor’s memory.

The New Day in Memory facility is activated.

Corrective Action: No action is required.

CTMX67I COMPRESSED AJF RECEIVED BY MONITOR

Explanation: This information message indicates that the Control-M monitor received AJF that was compressed by the New Day procedure. This is done by New Day in Memory facility (activated by the NEWDAYIM=Y installation parameter), which uses synchronous cross-memory to copy the AJF between the New Day procedure and Control-M monitor address spaces. The New Day procedure extracts the AJF from the Control-M monitor’s memory. After compressing the AJF, the New Day procedure copies the compressed AJF back to the Control-M monitor’s memory.

When Control-M resumes processing after completing the New Day procedure, it uses the AJF that was copied from the New Day procedure, and does not need to read the compressed AJF from DASD.

Corrective Action: No action is required.

CTI–CTM

CTI Messages

Messages CTI600 through CTI6xx

CTI650E STORAGE OBTAIN FAILED WITH RETURN CODE rc

CTI651E OPEN FAILED FOR DDNAME OBJFILE

CTI652S INTERNAL OBJECT TABLE MUST BE ENLARGED

CTI653E ALESERV ADD FAILED FOR addr-spc WITH RETURN CODE rc

CTI654I ADDRESS SPACE addr-spc IS SWAPPED OUT AND WILL BE SKIPPED

CTI655E ALESERV DELETE FAILED FOR addr-spc WITH RETURN CODE rc

CTI656I STARTED TASK taskName WILL BE ADDED TO THE DATABASE

CTI657I OBJECT_NAME/DESC CLASS_NAME/DESCR ADDRSPAC STATUS _J

CTI658I text

CTI659I objectName className addrSpace status j

CTJ messages

Messages CTJ000 through CTJ0xx

CTJ000I Control-M JCL Verify is starting. Levelapar_id

CTJ001I Control-M JCL Verify is ended RC=return_code

CTJ002I Start processing MEMBER member_nameDSNAME=dataset_name

CTJ003I Processing ended RC=return_codeREASONreason_code MEMBERmember_nameSNAME dataset_name

CTJ004I Processednumbermembers from lib_name

CTJ005E MEMBERmember_namenot found in lib_name

CTJ006ECould not find LIBRARY=lib_name

CTJ007W Empty MEMBER member_name in library lib_name

CTJ008I Start verifying JOBjob_name MEMBER member_name

CTJ009I Processing ended RC=return_code for JOB job_name MEMBER member_name

CTJ00AE Control-M JCL Verify is not APF-authorized

CTJ00BE Reading library's directory using maskmaskfailed DSNAME=dataset_name

CTJ00CI Runtime parameters: FA=fa FV=fv JES=jes ME=me ML=ml CTM=ctm STDR=stdr UT=ut ENV=envUSER=user

CTJ00DS CAN NOT DISPLAY HUGE REPORT WITHnumber_of _records OF RECORDS

CTJ00FI Jobs Dependency Flow is Active

CTJ00II Job ID jobid in Jobs Dependency Flow.

CTJ00JI Start processing MEMBERmem_nameDSNAME=dataset_name

CTJ00MI Start processing MEMBER mem_nameDSNAME=dataset_name

CTJ00NI Start verifying JOBjob_nameMEMBERmem_name

CTJ00PW PACKED MEMBERmember_namein library lib_name

CTJ00QE File/Member referenced in DDNAME ddname could not be opened

CTJ00RE Internal error while opening file/member referenced in DDNAME ddname

CTJ00SE jcl_statement_number RULE-ERR: text

CTJ00SI jcl_statement_number RULE-INFO: text

CTJ00SW jcl_statement_number RULE-WARN: text

CTJ00TIjcl_statement_number REXX-INFO:message text

CTJ00TW jcl_statement_number REXX-WARN:message text

CTJ00TEjcl_statement_number REXX-ERR:message text

CTJ00UI Processing ended RC=return_code REASON=reason_code file/member referenced in DD ddname

CTJ00VE Empty file/member referenced in DDNAME ddname

CTJ00WW Packed file/member referenced in DDNAME ddname

CTJ00XI Start verifying file/member referenced in DDNAME=ddname

CTJ00YI Processing ended RC=rc for JOB job_name referenced in DDNAME ddname

Messages CTJ100 through CTJ1xx

CTJ105I //SYSIN DD * GENERATED BY CTJVER

Messages CTJ200 through CTJ2xx

CTJ200I Function function_nameis Starting Level level_idAPAR:apar_id

CTJ201E ERROR string tables were not initiated

CTJ202I Shared INFO does not exist. Issue Modify command 'REFRESH,SCOPE=ALL' for CTJ monitor.

CTJ203E ERROR: Storage not available Return Code:return_code, Reason:reason_code

CTJ204E ERROR: JES sub-system is not available

CTJ205E ERROR: string tables cannot be accessed. Return Code: return_code

CTJ206E ERROR: Sub-System internal error

CTJ207E ERROR: Sub-System failure. Return Codes:return_code - reason_code

CTJ208E ERROR: Function function_name input parameters invalid. RC=return_code

CTJ209E ERROR: STEPLIB dataset is not a library, DSN=dataset_name

CTJ20AI CTJ monitor Function function_name Scope string ended - RC=return_code

CTJ20BI Control-M JCL Verify Data Pool was created successfully

CTJ20CE Data Pools were not created

CTJ20DW Data Pool is in use and was not removed. SCOPE=string

CTJ20EW JES search table string not recognized

CTJ20FE Control-M JCL Verify system anchor was not created. RC=return_code

CTJ20GE ERROR: string library info cannot be obtained for library_name

CTJ20HE Number of tasks exceeds

CTJ20IE internal error: Shared Memory Object was not found

CTJ20JE CTJSHRM - Not Enough Memory. STORAGE RC=return_code

CTJ20KE PDS pds_name cannot be accessed due to authorization issue

CTJ20LW WARNING: Library volumevolume_idcannot be accessed DSN=dataset_name

CTJ20ME Syntax error during CTJPRC parsing. Line:line_number

CTJ20NE Unrecognized System Variable Name:variable _name

CTJ20OI Procedure Library was not Found. Library:library

CTJ20PE No JES Procedure libraries provided with string DD name

CTJ20QI INFORMATION: LLA Library is not authorized for reading

CTJ20RE CTJ monitor utility is already running. Execution aborted.

CTJ20SE Rule List member member_name is empty

CTI650E STORAGE OBTAIN FAILED WITH RETURN CODE `rc`

CTI653E ALESERV ADD FAILED FOR `addr-spc` WITH RETURN CODE `rc`

CTI654I ADDRESS SPACE `addr-spc` IS SWAPPED OUT AND WILL BE SKIPPED

CTI655E ALESERV DELETE FAILED FOR `addr-spc` WITH RETURN CODE `rc`

CTI656I STARTED TASK `taskName` WILL BE ADDED TO THE DATABASE

CTI658I `text`

CTI659I `objectName className addrSpace status j`

CTJ000I Control-M JCL Verify is starting. Level`apar_id`

CTJ001I Control-M JCL Verify is ended RC=`return_code`

CTJ002I Start processing MEMBER `member_name`DSNAME=`dataset_name`

CTJ003I Processing ended RC=`return_code`REASON`reason_code` MEMBER`member_name`SNAME `dataset_name`

CTJ004I Processed`number`members from `lib_name`

CTJ005E MEMBER`member_name`not found in `lib_name`

CTJ006ECould not find LIBRARY=`lib_name`

CTJ007W Empty MEMBER `member_name` in library `lib_name`

CTJ008I Start verifying JOB`job_name` MEMBER `member_name`

CTJ009I Processing ended RC=`return_code` for JOB `job_name` MEMBER `member_name`

CTJ00BE Reading library's directory using mask`mask`failed DSNAME=`dataset_name`

CTJ00CI Runtime parameters: FA=`fa` FV=fv JES=`jes` ME=`me` ML=`ml` CTM=`ctm` STDR=`stdr` UT=`ut` ENV=`env`USER=`user`

CTJ00DS CAN NOT DISPLAY HUGE REPORT WITH`number_of _records` OF RECORDS

CTJ00II Job ID `jobid` in Jobs Dependency Flow.

CTJ00JI Start processing MEMBER`mem_name`DSNAME=`dataset_name`

CTJ00MI Start processing MEMBER `mem_name`DSNAME=`dataset_name`

CTJ00NI Start verifying JOB`job_name`MEMBER`mem_name`

CTJ00PW PACKED MEMBER`member_name`in library `lib_name`

CTJ00SE `jcl_statement_number` RULE-ERR: `text`

CTJ00SI `jcl_statement_number` RULE-INFO: `text`

CTJ00SW `jcl_statement_number` RULE-WARN: `text`

CTJ00TI`jcl_statement_number` REXX-INFO:`message text`

CTJ00TW `jcl_statement_number` REXX-WARN:`message text`

CTJ00TE`jcl_statement_number` REXX-ERR:`message text`

CTJ200I Function `function_name`is Starting Level `level_id`APAR:`apar_id`

CTJ201E ERROR `string` tables were not initiated

CTJ203E ERROR: Storage not available Return Code:`return_code`, Reason:`reason_code`

CTJ20AI CTJ monitor Function `function_name` Scope `string` ended - RC=`return_code`

CTJ20KE PDS `pds_name` cannot be accessed due to authorization issue

CTJ20LW WARNING: Library volume`volume_id`cannot be accessed DSN=`dataset_name`

CTJ20PE No JES Procedure libraries provided with `string` DD name

CTJ20ZE JES DESTID`destid`NOT FOUND

CTJ40CI Rule Loading. Member:`member_name`, Rule:`rule_name`

CTJ40EE Abend S0`abend_code` at offset:`offset` in `program` code. Run `string`

CTJ50PWSYMBOL `symbol` WAS NOT RESOLVED

CTJD01W `jcl_statement_number` WARNING: VOLUMES list and VOLUMES in catalog are not matched. DSN=`dataset_name`

CTJD02W `jcl_statement_number` WARNING: DSN with DISP=NEW, already exists. DSN=`dataset_name`

CTJD03S `jcl_statement_number` ERROR: CTJDSC GETMAIN `error`

CTJD04S `jcl_statement_number` ERROR: The DSN block was not found

CTJD05W `jcl_statement_number` WARNING: DSN with DISP=`disp` not found. DSN=`dataset_name`

CTJD06W `jcl_statement_number` WARNING: DSN with DISP=DELETE not found. DSN=`dataset_name`

CTJD07W `jcl_statement_number` WARNING: invalid DSN=`dataset_name`

CTJD09W `jcl_statement_number` WARNING: file was already cataloged on a previous statement. DSN=`dataset_name`