|
|
|
|
|
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.
Explanation: A job’s ON DSNEVENT and ON STEP events can only be handled by one CMEM or Control-O.
A CMEM or Control-O subsystem is attempting to monitor an ON DSNEVENT or an ON STEP event but is unable to do so because the address space is already monitored by a different CMEM or Control-O subsystem.
Corrective Action: If another subsystem needs to intercept an ON DSNEVENT or an ON STEP event, modify the rule filters of the other subsystem so that the job name is not matched.
Explanation: The Control-O monitor is currently monitoring the job for ON DSNEVENT and ON STEPEND events.
Corrective Action: No action is required.
Explanation: The job was stopped due to a STOPJOB request for a DSNEVENT event. This message is followed by message CTMC42E, which contains additional details about the event.
In this message, disposition is the dataset disposition that triggered the event. Valid values are:
The job is stopped after the current step. All subsequent steps (including steps having COND set to EVEN/ONLY) will not be executed.
Corrective Action: No action is required.
Explanation: This message follows message CTMC41E when a job is stopped due to an NCT2 (NOT CATLGD 2) event. The NCT2 event occurred for the dsn data set in the stepName step in the procStep procedure step.
Corrective Action: No action is required.
Explanation: An internal error occurred when CMEM or Control-O tried to process a CMEM event. This message is followed by message CTMC44E with the event that caused the error.
The event is ignored.
Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.
Explanation: This message follows message CTMC43E and CTMC4AE when an internal error occurs during event processing.
Corrective Action: No action is required.
Explanation: CMEM subsystem functions or Control-O subsystem functions were stopped. Some or all events for the specified stepName procstep might not be processed because the subsystem was stopped.
Corrective Action: Activate the subsystem functions (CMEM or Control-O).
Explanation: This information message indicates that CMEM or Control-O subsystem functions were reactivated. This message appears when a CMEM subsystem function or Control-O was stopped and restarted during job execution. Message CTMC45W was issued for this job. Events that occurred between these two messages are ignored.
CMEM events for this job from stepName procstep are processed.
Corrective Action: No action is required.
Explanation: An abend occurred during processing of CMEM events for this job. This message is followed by message CTMC48E with details about the abend.
CMEM event processing stops for this job and a dump is written to a system dump data set.
Corrective Action: Format and save the dump, prepare the Control-M monitor full output, and contact BMC Customer Support.
Explanation: This message follows message CTMC47E when an internal abend occurs in CMEM event processing. It contains details about the abend: subsystem name, abending module name, abending load module load point and offset of the abending instruction in the module.
A system dump is produced. The title of the dump contains this message.
Corrective Action: No action is required.
Explanation: An internal error occurred when CMEM or Control-O tried to process a CMEM event. This message is followed by message CTMC44E, which specifies the event that caused the error.
CMEM event processing stops for this job.
Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.
Explanation: Control-O SYSOUT processing for the SYSOUT allocated to the ddName DD statement was stopped.
Some or all events for this SYSOUT might not be processed because Control-O was stopped.
Corrective Action: Activate Control-O.
Explanation: This information message indicates that SYSOUT processing for SYSOUT allocated to the ddName DD statement was reactivated. This message appears when Control-O was stopped and restarted during application SYSOUT processing. Message CTMC4AW was issued for this SYSOUT. Events that occurred between these two messages are ignored.
SYSOUT events for this SYSOUT are processed.
Corrective Action: No action is required.
Explanation: Control-O fallback to a lower version was performed while processing a SYSOUT allocated to the ddName DD statement. Fallback is not allowed in the following cases:
Control-O processing stops for the SYSOUT allocated to the ddName DD statement.
Corrective Action: Restart the job to resume SYSOUT processing.
Explanation: Control-O or CMEM fallback to an earlier version was performed while processing DSNEVENT or STEP events. Fallback is not allowed to Control-O or CMEM versions earlier than 6.0.15 or 6.1.15.
Control-O or CMEM processing stops for the job.
Corrective Action: Restart the job to resume DSNEVENT and STEP events processing.
Explanation: Highlighted, unrollable message.
Insufficient storage for CMEM processing initialization in the Control-M monitor.
The Control-M monitor stops processing CMEM/Control-O requests.
Corrective Action: Increase the REGION size specified for the Control-M monitor.
Explanation: Control-M has determined that the CMEM facility is not installed.
Communication between CMEM or the Control-O monitor and Control-M is not established, but the Control-M monitor continues processing.
Corrective Action: No action is required.
Explanation: Insufficient storage for loading table tableName into storage.
This message is followed by the WKJA59E message, which contains more details about the error.
Job order fails. No additional action taken.
Corrective Action: Increase the REGION size specified for the Control-M monitor; or define a smaller table if possible (for example, if only one job is ordered from the table). For further actions, see the WKJA59E message.
Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is not a partitioned data set.
This message is followed by the WKJA59E or WKJC39E message, which identifies the failed action.
No additional action will be taken for the failed job or table order.
Corrective Action: Specify the name of a partitioned data set containing one or more valid scheduling tables.
Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is currently used by another job.
This message is followed by message WKJA59E which identifies the failed action.
No additional action will be taken for the failed job/table order.
Corrective Action: Determine which job has allocated the data set with disposition OLD and resolve the conflict.
Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is not cataloged.
This message is followed by additional messages which identify the failed action.
No additional action will be taken for the failed job or table order.
Corrective Action: Make sure that the SCHLIB library specified in the CMEM table entry refers to a cataloged data set.
Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a dynamic allocation error.
This message is followed by message WKJA59E which identifies the failed action.
No additional action will be taken for the failed job/table order.
Corrective Action: Record the problem, prepare the Control-M monitor full output, and contact BMC Customer Support.
Explanation: Control-M could not allocate the monitor to the Monitor-to-Subsystem (M2S) file of another IOA environment.
During initialization the Control-M monitor compares the QNAME in the IOA environment with the QNAME in the M2S file. They should match.
Message CTM441E is issued.
Corrective Action: Check the IOACPRM member and do one of the following:
Explanation: The source Active Jobs file is either currently being formatted, or an abend occurred during the previous formatting.
The Active Jobs file is formatted daily as part of the New Day process. It may also be formatted by the CTMCAJF utility.
Copy program terminates with a condition code of 08.
Corrective Action: If the Active Jobs file is currently being formatted, wait until the formatting is completed. If the previous formatting abended, determine the reason. Resubmit the copy job only after successful formatting.
Explanation: The Control-M monitor could not allocate the subsystem to the Subsystem-to-Monitor (S2M) file of another IOA environment.
During initialization the Control-M monitor compares the qname in the IOA environment with the qname in the S2M file. They should match.
Message CTM441E is issued.
Corrective Action: Check the IOACPRM member and do one of the following:
Explanation: The target Active Jobs file should not be used before it is formatted by the FORMCKP procedure.
Copy program terminates with a condition code of 08.
Corrective Action: Format the Active Jobs file using the FORMCKP procedure.
Explanation: This information message identifies the Monitor-to-Subsystem (M2S) file that the Control-M monitor allocated for communication with the Control-O or the CMEM monitor.
qName is defined in the M2S file with the data set name dsn.
Corrective Action: No action is required.
Explanation: Target Active Jobs file is not large enough to contain the source Active Jobs file.
Copy program terminates with a condition code of 08.
Corrective Action: Reallocate and reformat the new Active Jobs file.
Explanation: This is one of two messages with the same ID, but different text.
This information message displays the number of jobs deleted from the Active Jobs file during a run of the CLEANUP function of the CTMCAJF utility. The CLEANUP function of the CTMCAJF utility deletes jobs from the Active Jobs file according to the same criteria as the New Day procedure.
Corrective Action: No action is required.
Explanation: This is one of two messages with the same ID, but different text.
This information message identifies the Subsystem-to-Monitor (S2M) file that the Control-M monitor allocated for communication with the Control-O or the CMEM monitor.
qName is defined in the S2M file with the dsn DSN.
Corrective Action: No action is required.
Explanation: The SMFID is not in the Monitor-to-Subsystem (M2S) file.
During initialization the Control-M monitor checks that every SMFID required for CMEM functions is defined in the M2S file.
Control-O issues the CTM441E message and CMEM functions become inactive.
Corrective Action: Add the missing SMFID to the M2S file, and restart the Control-M monitor.
For more information on adding the SMFID to the M2S file, see the section on reformatting communication files for only one SMFID in the INCONTROL for z/OS Installation Guide.
Explanation: The CNDREC# parameter in the IOAPARM member has been changed, but the IOA Conditions file has not been rebuilt. A difference between the length of the IOA Conditions file and the CNDREC# value specified in the IOAPARM member of the PARM library was detected.
This is usually caused by using the IOAPARM member for the wrong monitor.
The Control-M monitor shuts down.
Corrective Action: Correct the problem and restart the monitor.
Explanation: The action specified in a Control-O DO RESOURCE statement failed, because it would have produced either a negative quantity or a quantity greater than the maximum of 9999. Therefore it was rejected.
The system ignores the illegal statement and continues processing.
Corrective Action: Check and correct, if necessary, the definition of the quantitative resource to be updated and/or the rule defining how to update it.
Explanation: The CLEANUP function of the CTMCAJF utility stops because the Control-M monitor is not running. The CLEANUP function of the CTMCAJF utility should run only when the Control-M monitor is running.
The CTMCAJF utility terminates.
Corrective Action: BMC recommends the following:
Explanation: When you define a STEP RANGE by specifying either FROMSTEP or TOSTEP, the STEP RANGE must have a name.
Corrective Action: Fill in the STEP RANGE field.
Explanation: This information message indicates that an IOA Gateway attempted to establish a connection with another IOA Gateway. However, the LOGMODE definitions of the partners do not match.
When IOA Gateways try to establish a connection with each other, both send LOGMODE during the bind process. If the LOGMODEs do not match, the connections fail. Message COMG98W, COMG90E or COMG95E precedes this message and explains the error.
The connection between the IOA Gateways fails.
Corrective Action: Check the LOGMODE definitions for each partner in your SYS1.VTAMLIB. Make sure that they are defined according to the recommendations in the IOA installation chapter of the INCONTROL for z/OS Installation Guide.
Explanation: The value for the CKPSIZE parameter being used by the CTMCAJF utility is different from the CKPSIZE value used to format the Active Jobs file. The parameter is defined in the CTMPARM member in the IOA PARM library. The values used must be identical.
The CTMCAJF utility terminates. The requested action is not performed.
Corrective Action: Ask the INCONTROL administrator to determine the cause of the discrepancy in the CKPSIZE value and correct the error.
Explanation: You must fill in either FROMSTEP or TOSTEP or both. To create a STEP RANGE, you must specify either FROMSTEP or TOSTEP or both. STEP RANGE without additional parameters has no meaning.
Corrective Action: Add FROMSTEP or TOSTEP or both.
Explanation: This information message indicates that when an IOA Gateway attempted to establish a connection with another IOA Gateway, a local IOA gateway made a VTAM LU6.2 allocation request. However, the request failed.
A local IOA Gateway attempted to allocate a session with a partner gateway. The attempt failed. Message COMG98W, COMG90E or COMG95E precedes this message and explains the failure.
Corrective Action: Check that the partner gateway LU is active in VTAM, and that it is defined as explained in IOAGATE installation in the INCONTROL for z/OS Installation Guide.
Explanation: There is a reference to a STEP RANGE that is not defined. ONPGMSTEP refers to a STEPRANGE (*XXXXXXX) that is not defined for this job.
Corrective Action: Specify a STEP RANGE that is defined for this job.
Explanation: This information message indicates that a local IOA Gateway attempted to allocate a partner gateway session. The attempt failed.
The failed request was a VTAM LU6.2 allocation request. Messages COMG98W, COMG90E or COMG95E precede this message and explain the failure.
Connection will be reattempted in 1 minute.
Corrective Action: Make sure that Logical Unit (LU) of the partner gateway is active in VTAM and that it is defined as explained in the IOA installation chapter in the INCONTROL for z/OS Installation Guide.
Explanation: You cannot specify this operand for this type of code. Some of these operands are not allowed for various types of codes. For example, >Sxxx, <Sxxx are not allowed.
Corrective Action: Use only the valid operands for this type of code.
Explanation: This information message indicates that an IOA Gateway attempted to establish a connection with another IOA Gateway. However, IOA Gateway detected a mismatch in the IOA Gateway LU definitions. The VTAM LU was defined incorrectly.
Messages COMG98W, COMG90E and COMG95E precede this message, and explain the error.
The connection to the partner LU fails, and the IOA Gateway terminates.
Corrective Action: Define the IOA Gateway VTAM LU as explained in the IOA installation chapter of the INCONTROL for z/OS Installation Guide.
Explanation: The combination of status codes is not valid. Some combinations are not acceptable. For example, EXERR and NOTOK, because the NOTOK code already covers the EXERR code.
Corrective Action: Check and correct the specification in the CODES field.
Explanation: Invalid SEARCH COUNTER value. The SEARCH COUNTER counts the number of times Control-M looks for a job. When this value equals the maximum number of searches allowed defined by the INCONTROL administrator, the job status changes to DISAPPEARED. You can change the value of the counter manually.
Valid search values:
Corrective Action: Correct the SEARCH COUNTER parameter.
Explanation: PREVENT-NCT2 was requested for a started task (STC). PREVENT-NCT2 handling may not be requested for a started task (STC).
Corrective Action: Change the value of PREVENT-NCT2 to N or leave the value blank, or change the task type.
Explanation: This information message indicates that a user entered command DOC in the Zoom screen but the job has no documentation.
Corrective Action: No action is required.
Explanation: Insufficient storage to save the documentation lines into the library or member specified in the DOCLIB or DOCMEM fields of the Job Scheduling Definition screen.
Corrective Action: The user can either delete the additional documentation lines and save the Job Scheduling Definition, or cancel the Job Scheduling Definition changes. The user should then log on again using a larger SIZE parameter (under TSO).
Explanation: The Online facility called routine CTMDOC with an invalid parameter list when the DOC command was entered in either the Job Scheduling Definition screen or the Zoom screen.
Corrective Action: Notify the INCONTROL administrator.
Explanation: The Online facility called routine CTMDOC with an invalid function when the DOC command was entered in the Job Scheduling Definition screen or in the Zoom screen.
Corrective Action: Notify the local INCONTROL administrator.
Explanation: The Online facility received an invalid return code from routine CTMDOC.
Corrective Action: Notify the INCONTROL administrator.
Explanation: User entered the * character, or the ? character in the DOCMEM field in the Job Scheduling Definition screen (or in the Zoom screen). These are invalid characters for this field.
Corrective Action: Enter a valid value in the DOCMEM field.
Explanation: More than eight requests for a periodic calendar were specified in the DAYS field in the Job Scheduling Definition screen. Only eight requests for a periodic calendar may be kept in a job scheduling definition.
Corrective Action: Decrease the number of periodic calendar requests.
Explanation: The Boolean expression that is specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains unpaired parentheses.
Corrective Action: Correct the Boolean expression in the IN field.
Explanation: The Boolean expression that is specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains parentheses within a condition name. IN conditions may be specified as a Boolean expression with parentheses. Use the parentheses only before or after the condition name.
Corrective Action: Correct the Boolean expression in the IN field.
Explanation: The job scheduling definition contains duplicate entries with the same pipe name. The names of the pipes in a job must be unique.
The scheduling definition cannot be saved and the job cannot be ordered.
Corrective Action: Change one or more pipe names so that all pipes in the job have a unique name.
Explanation: The Boolean expression that is specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains two or more open or close parentheses in succession. Control-M Online facility does not support nesting for a Boolean expression in the IN field.
Corrective Action: Correct the Boolean expression in the IN field.
Explanation: A Boolean expression in the Job Scheduling Definition screen or Job Zoom screen contains more than 20 conditions.
The job scheduling definition cannot be saved.
Corrective Action: Modify the Boolean expression so that it contains not more than 20 conditions.
Explanation: This message is displayed in the following cases:
Corrective Action: Do one of the following, as appropriate:
Explanation: There are retention values for both # OF DAYS TO KEEP and # OF GENERATIONS TO KEEP, but these fields are mutually exclusive.
The request is ignored.
Corrective Action: Delete one of the specified values.
Explanation: The job has more than 255 pipe definitions in the scheduling table. This message may be issued when editing a job definition with more than 255 pipe definitions. The maximum number of pipes per collection is 255.
The scheduling definition is not saved, and the job is not ordered.
Corrective Action: Reduce the number of pipe entries in the job scheduling definition.
Explanation: An attempt was made to change the value of the data in a job's WAIT CONFIRMATION field, via screen 3.Z, when the job was not in WAIT SCHEDULE state.
Corrective Action: No action is required.
Explanation: In order to be compatible with the nested containers feature in Control-M/Enterprise Manager, a slash (/) is not allowed in this field.
Corrective Action: Correct the field contents.
Explanation: The Boolean expression specified in the IN field in the Job Scheduling Definition screen or in the Job Zoom screen contains the operator I in an invalid position. The Boolean operator I may be specified only in the first position of the condition name, or immediately after the open parentheses.
Corrective Action: Correct the Boolean expression in the IN field.
Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to insufficient storage allocated to the Control-M monitor.
Corrective Action: Increase the region size of the Control-M monitor.
Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to an internal error.
Corrective Action: Contact BMC support.
Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to a problem in accessing the DAM2F file.
Corrective Action: Verify that DAM2F is allocated to a valid file. If it is, contact BMC support.
Explanation: Invalid data was specified.
Corrective Action: Change the entry in the field with the help of the text displayed in the message, or with the assistance of the HELP command.
Explanation: A user entered the Zoom screen (3.Z) of a job from the Control-M Active Environment screen, but the status of the job was not HELD. In such a case, any changes made in the Zoom screen cannot be saved on exit.
Changes made to the current job in the Zoom screen are ignored.
Corrective Action: To change the job, do the following:
Explanation: Control-M successfully performed a job’s DO REMFORCE statement. The unique ID can be used to track the remote force request on the remote Control-M.
Corrective Action: No action is required.
Explanation: GENERAL or USER was specified in the OVERLIB field in the Job Scheduling Definition screen or in the Job Zoom screen. GENERAL and USER are not permitted in the OVERLIB field.
Corrective Action: Specify a valid value in the OVERLIB field.
Explanation: Missing APPLICATION or GROUP name in the Job Scheduling Definition screen or in the Job Zoom screen. The APPLICATION and GROUP fields may be designated as mandatory in the IOA profile. By default they are optional. See the chapter that discusses online facilities in the Control-M for z/OS User Guide for a description of these fields.
Corrective Action: Fill in the requested field with the help of the text in the message, or correct the appropriate variable in the IOA profile.
Explanation: A value other than OK or NOTOK is specified in a field than can only take either one of these values.
Corrective Action: Specify either OK or NOTOK.
Explanation: The user entered an action that is invalid for SMART tables.
Corrective Action: Enter an action that is valid for SMART tables.
Explanation: Both OK and NOTOK were entered as a DO action for a SMART table. OK and NOTOK are mutually exclusive DO actions.
Corrective Action: Delete either OK or NOTOK.
Explanation: No DO action after an ON PGMSTEP/ON GROUP-END line.
Corrective Action: Fill in at least one DO action.
Explanation: There was an attempt to zoom a job that is currently being zoomed by another user.
The Zoom screen is displayed in the forced browse mode.
Corrective Action: If the job data must be updated, continue trying to zoom the job in Edit mode, until it is released by the other user.
Explanation: The SAVE was entered in the Zoom screen in the browse mode.
The job is not saved.
Corrective Action: Exit the screen without trying to save the changes.
Parent Topic |