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:

1. Using the documentation provided as part of the IOA Monthly Maintenance Upgrade system, transfer the JCL job stream from the diskette to the mainframe.
2. Modify the JCL as specified in the documentation.
3. Submit the job.

Note:

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.

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.

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.

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.

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.

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.

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.

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 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:

For information about the return code, see message SMF047S.

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: 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:
  • CONVERT STARTED - The conversion has begun.
  • ENDED “OK” - The conversion ended and was successful,
  • ENDED “NOT OK” - The conversion ended and was unsuccessful.
• tableName - the name of the table
• 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.