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:

1. Activate debug level 75.
2. Restart the Control-M monitor.
3. Recreate the error.
4. 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:

1. 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.
2. Add the failing condition manually, to maintain production flow.
3. 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.

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

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.