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.

Corrective Action: Recommended actions depend on where the calendar was specified:

• Calendar specified in job order or mission:

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

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