|
|
|
|
|
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: This information message indicates that the requested job documentation is displayed in browse mode. Display of job documentation was requested using the DOC command. Normally, when requested, documentation can be edited. However documentation displayed in Browse mode cannot be updated. The documentation is in Browse mode for one of the following reasons:
Documentation lines are displayed in browse mode.
Corrective Action: No action is required.
Explanation: The host host name, referred to by in the –host input parameter, is not defined in the DSHOSTS member, located in the Control-M PARM library.
Corrective Action: Check that that the value of –host parameter is correct, or add a definition of the host host name to DSHOSTS member.
Explanation: The User mf user id does not have permission to work with host host as user DS user id.
Corrective Action: Ensure that the User mf user id has permission to work with host host as user DS user id.
Explanation: The error occurs when the utility tries to get the IP address of the host host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Perform the appropriate action, based on the error code and the error message.
Explanation: Parameter param is mandatory, but not defined in the input stream of the utility.
Corrective Action: Add the param parameter to the input and rerun the utility.
Explanation: Request request ended with an error. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Refer to the Control-M documentation for details.
Corrective Action: Add the param parameter to the input and rerun the utility.
Explanation: The utility cannot create the file name file on the remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Refer to the Control-M documentation for details.
Explanation: The utility cannot open the file name file. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Perform the appropriate action, based on the error code and the error message.
Explanation: Internal error.
Corrective Action: Perform the following:
Explanation: The error occurred when the utility tried to create a socket. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Perform the appropriate action, based on the error code and the error message.
Explanation: The error occurred when the utility tried to connect to a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Perform the appropriate action, based on the error code and the error message.
Explanation: The error occurred when the utility tried to send data to a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Perform the appropriate action, based on the error code and the error message.
Explanation: The error occurred when the utility tried to upload the file name file to a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Refer to the Control-M documentation for details. Perform the appropriate action, based on the error code and the error message.
Explanation: The error occurred when the utility tried to delete the file name file on a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Refer to the Control-M documentation for details. Perform the appropriate action, based on the error code and the error message.
Explanation: The error occurred while the utility was receiving data from a remote host. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Perform the appropriate action, based on the error code and the error message.
Explanation: The value of the param input parameter is too long. The maximum length of this parameter is max_length bytes.
Corrective Action: Correct the value of this input parameter.
Explanation: The value of the param input parameter is incorrect.
Corrective Action: Correct the value of this input parameter.
Explanation: The utility cannot work with a Control-M Agent of version ver. num.
Corrective Action: Check the value of the –host input parameter. If the host name is correct, contact the Control-M administrator to install the correct version of Control-M agent.
Explanation: The error occurred while the utility was trying to load user exit CTMX006. Usually this error occurs when the load module CTMX006 does not exist in the STEPLIB libraries. The error message and the error code are described in the following IBM documents: XL C/C++ Run-Time Messages, z/OS Language Environment Run-Time Messages, and XL C/C++ Run-Time Library Reference.
Corrective Action: Perform the appropriate action, based on the error code and the error message.
Explanation: The value of the param input parameter is incorrect.
Corrective Action: Correct the value of this input parameter.
Explanation: An invalid value was specified for the SHIFT parameter. The enhanced SHIFT algorithm allows the scheduling date to be shifted forward or backward a maximum of 62 working days.
The scheduling definition is not saved.
Corrective Action: Specify a valid value for the SHIFT parameter. For more information, see the CONFCAL parameter in the chapter that describes job production parameters of the Control-M for z/OS User Guide.
Explanation: An incorrect value was specified for the second character of the SHIFT subparameter. The SHIFT subparameter has two fields. The first is a 1-character field that designates the shift direction (< or >). The second is an optional 3-character field that contains a + or - followed by a two digit integer. This field designates how much to move the scheduling date forward (if plus) or backward (if minus).
The scheduling definition is not saved.
Corrective Action: Specify a valid value for the SHIFT parameter. For more information, see the CONFCAL parameter in the chapter that describes job production parameters of the Control-M for z/OS User Guide.
Explanation: An invalid value was specified in the last three characters of the SHIFT subparameter. The format of the last three characters of the SHIFT subparameter must be +nn or -nn, where nn is an integer between 01 and 62.
The scheduling definition is not saved.
Corrective Action: Specify a valid value for the SHIFT subparameter. For more information, see the CONFCAL parameter in the chapter that describes job production parameters of the Control-M for z/OS User Guide.
Explanation: An invalid value was specified in the last two characters of the SHIFT subparameter. The last two characters of the SHIFT subparameter must be an integer between 01 and 62.
The scheduling definition is not saved.
Corrective Action: Specify a valid value for the SHIFT subparameter. For more information, see the CONFCAL parameter in the chapter that describes job production parameters of the Control-M for z/OS User Guide.
Explanation: This information message is displayed if a user performs a HOLD of a job on the Active Environment screen (Screen 3) or the Active Environment Zoom screen (Screen 3.Z), and a second user then attempts to delete or free that job.
Corrective Action: No action is required.
Explanation: There was an attempt to start CMEM using the IOASINIT procedure. CMEM is now started using the CTMCMEM procedure.
IOASINIT terminates. CMEM initialization fails.
Corrective Action: Start CMEM using the S CTMCMEM command.
Explanation: The subsys subsystem is already active for another IOA environment. The same subsystem name cannot be used for two IOA environments in parallel.
IOA subsystem initialization fails for the subsys subsystem.
Corrective Action: Either choose another subsystem name for the current environments of the IOA products, or deactivate the IOA online monitor and all the subsystem components of the old IOA environment and restart the subsystem.
Explanation: Subsystem initialization process failed while trying to load the subsystem executor program specified in the message.
IOA subsystem initialization fails.
Corrective Action: Verify the module name exists in the STEPLIB library.
Explanation: An attempt was made to start CMEM when Control-O was up, or vice versa. CMEM and Control-O procedures cannot work concurrently. If one already started, the other must be down.
Note:
Control-O performs all the functions of CMEM.
The requested CMEM or Control-O initialization fails.
Corrective Action: If you want to run the initialization procedure, first stop the Control-O or CMEM monitor identified in the message text.
Explanation: Insufficient storage in ECSA or CSA for the subsystem tables and modules.
Subsystem initialization fails.
Corrective Action: If the storage defined for ECSA or CSA is not large enough, increase the size of ECSA or CSA.
Explanation: Length of the subsystem name specified for the disconnect subsystem request is incorrect. It is either less than, or greater than four characters.
The disconnect subsystem function is not performed.
Corrective Action: Restart the disconnect subsystem function using a valid, four-character subsystem name.
Explanation: This information message indicates that subsys subsystem is being disconnected.
Corrective Action: No action is required.
Explanation: This information message indicates that subsys subsystem is inactive and no longer used by Control-O.
Corrective Action: No action is required.
Explanation: The subsys subsystem is already active for the IOA Online monitor of another IOA environment. The same subsystem cannot be specified for two IOA environments in parallel.
IOA subsystem initialization fails for the subsys subsystem.
Corrective Action: Either choose another subsystem name for the current environment of the IOA products, or deactivate the IOA online monitor and all the subsystem components of the old IOA environment and restart the subsystem.
Explanation: Initialization of the CDAM subsystem failed. Additional system messages are issued before this message.
The job or STC terminated with a return code other than zero.
Corrective Action: Correct the error and try again.
Explanation: The keyName keyword was not given in the order request. Some keywords are obligatory in each order request. Failing to specify one produces this message.
The CTMJOB program ends with errors.
Corrective Action: Supply the missing keyword.
Explanation: No conditions to be passed to the other CPU were specified in the ISCPARM member allocated to one of the Control-M monitors. The DAISCPRM DD name should point to a library containing the ISCPARM member. This member should contain at least one COND parameter, set to cond, where cond is a condition name up to 20 characters. Masking characters * and ? are allowed. Only these conditions are passed to the other CPU.
CTMISR routine returns a return code of 24 to the calling IOA Exit 7. No conditions are passed to the other CPU.
Corrective Action: Add at least one COND=cond statement in the ISCPARM member and then shut down and restart the monitor. COND=* is valid for passing all the conditions.
Explanation: The CTMBLT utility ended due to errors. CTMBLT creates Control-M scheduling tables. If CTMBLT ended with errors, messages in the Error Messages file DAPRINT DD statement explain the reasons. The Error Table Definitions file DATABERR DD statement contains the input definition statements that have the errors.
The utility ends with a non-zero return code.
Corrective Action: Correct all problems, and rerun the job.
Explanation: This information message indicates that the CTMBLT utility ended normally. The CTMBLT utility creates Control-M scheduling tables.
Corrective Action: No action is required.
Explanation: This message is issued after the number of unsuccessful attempts to read job data by subsystem request reaches the defined maximum. After searching for the job data the maximum number of times, Control-M changes the job status to DISAPPEARED and stops searching.
The job status changes to DISAPPEARED.
Corrective Action: For the appropriate action, refer to the section on the Control-M monitor and JES in the INCONTROL for z/OS Administrator Guide.
Explanation: No space is available on the designated volumes to archive SYSDATA sysouts.
Archiving of SYSDATA is not completed due to lack of the space on the volumes designated for allocation of the Archived Sysout data sets.
Control-M issues additional messages describing the nature of the problem and terminates.
Corrective Action: Please do the following before attempting to restart the Control-M monitor:
Explanation: Dynamic allocation of an Archived Sysout Dataset has failed.
This message will be preceded by other messages detailing the nature of the problem, DD name, RC and reason code.
The Archived Sysout Dataset is not allocated. The job is processed and an ENDED NOTOK message is displayed, with the status FAILED REASON UNKNOWN.
Corrective Action: Record all relevant messages, prepare the Control-M monitor full output, and contact BMC Customer Support.
Explanation: Highlighted, unrollable message.
The Control-M monitor failed to archive SYSDATA for the job. This message is preceded by other messages detailing the nature of the error.
The job is processed and an ENDED NOTOK message is displayed, with the status FAILED REASON UNKNOWN.
Corrective Action: Do the following:
Explanation: A normal prompt of the IOA Entry Panel. The user is asked to write the value of the new password twice (to confirm the user choice).
Corrective Action: Enter the same value of the new password in the two provided fields.
Explanation: The Ordering Checkpoint Record contains recovery information which is invalid for this Daily run.
The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains data specifying recovery for the CTMJOB program, but these data are incorrect for the jobs that were ordered in this run of CTMJOB.
The CTMJOB program ends with errors.
Corrective Action: Either run CTMJOB with the same data (ordered jobs) as were in the last (abending) run, or blank out the values of the keywords in the Ordering Checkpoint Record, and run CTMJOB without recovery.
Explanation: The Ordering Checkpoint Record contains invalid keywords, or valid keywords in invalid offsets. The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains keywords in an unexpected structure.
The CTMJOB program ends with errors.
Corrective Action: Either correct the Ordering Checkpoint Record, or delete the Ordering Checkpoint Record, and run CTMJOB without recovery.
Explanation: This information message indicates that no jobs matched the ordering criteria during a scheduling request. This message is issued after the scheduling request has been processed, and no jobs were ordered.
Corrective Action: If you think a job should have been ordered in this scheduling request, check and correct the scheduling parameters as required, and rerun the scheduling request.
Explanation: This information message indicates that Y was specified in the RETRO field in a group entity or in one of the group jobs. RETRO processing is not supported in GROUPS. Setting RETRO to Y in a group can cause jobs to be scheduled on inappropriate ODATES.
The RETRO field is ignored in group processing.
Corrective Action: Set the RETRO field to N and retry.
Explanation: This information message indicates the number of jobs ordered by the present invocation of CTMJOB.
Corrective Action: No action is required.
Explanation: ISPF environment is missing. This option can be used only under ISPF.
Corrective Action: To use the option, invoke Control-M under ISPF.
Explanation: Editing was attempted when the MEMLIB or OVERLIB field contained either DUMMY or USER. When the MEMLIB or OVERLIB field contains DUMMY or USER, editing cannot be performed.
Corrective Action: No action is required.
Explanation: An attempt was made to edit a group entity or the JCL of a started task. Only the JCL of regular jobs can be edited.
Corrective Action: No action is required.
Explanation: Execution of the ISPF EDIT command failed.
If the variable text is of the form lib (memname), then ISPF was unable to edit the library or member specified in MEMLIB and MEMNAME of the job. The ISPF profile or the directory in which the profile is contained may be full or the library (specified in the MEMLIB field) does not exist.
If the variable text is of the form DDNAME= xxx, then ensure that Control-M exit CTMX014G is installed, which provides support for online editing of members specified via the MEMLIB DDNAME= xxx format. See the explanation of the MEMLIB parameter in the Control-M for z/OS User Guide for further details.
If the variable text is of the form EDIT DENIED BY [USER EXIT]- moduleName, then the edit command was failed by the IOA Editor or by the specified user exit.
Corrective Action: Check the parameters specified in MEMLIB and MEMNAME of the job. If the reason that ISPF could not edit the library or member is not obvious, then invoke the ISPF EDIT DATASET library or member to clarify the problem.
Explanation: The MEMLIB field contained AutoEdit variables which could not be resolved.
Corrective Action: Correct the problematic AutoEdit variable.
Explanation: MEMNAME contains an invalid parameter for the EDIT option. When the MEMNAME field contains either * or ?, editing cannot be performed.
Corrective Action: Correct the parameter in the MEMNAME field.
Explanation: The message explains the error.
Corrective Action: No action is required.
Explanation: Control-M/JCL Verify cannot verify on-spool jobs.
Corrective Action: No action is required.
Explanation: JCL verification was performed while rerunning a job. The JCL verification finished OK, and the rerun was successful.
Corrective Action: No action is required.
Explanation: JCL verification was performed before rerunning a job. The JCL did not successfully pass the verification, and therefore the job was not rerun.
Corrective Action: No action is required.
Explanation: Control-M/JCL Verify cannot verify dummy jobs.
Corrective Action: No action is required.
Explanation: Control-M/JCL Verify cannot verify warning jobs.
Corrective Action: No action is required.
Explanation: Control-M/JCL Verify is not installed.
Corrective Action: No action is required.
Explanation: This message is issued in screen 2 and screen 3. If the job scheduling definition is changed, and then the JVER command is issued, this message is displayed.
Corrective Action: Exit screen 2 or screen 3, and re-enter.
Explanation: The Date Control Record indicates that recovery is not necessary, but the recovery record, that is, the second record of the Date Control Record member used for Enhanced Daily Checkpointing, indicates that recovery is needed.
This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. In the Date Control Record, date-2 (columns 18-23) is equal to date-3 (columns 25-30) and date-4 (columns 43-48) is equal to date-5 (columns 50-55). However, the recovery record contains non-blank values for the recovery parameters.
For more details, please see the description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.
The program terminates with a condition code of 08.
Corrective Action: If recovery is required, set date-3 to the day before date-2, and date-5 to the day before date-4. If recovery is not required, replace the values in the recovery record with blanks.
Explanation: Invalid previous monthly scheduling date in the User Daily Date Control Record date-3 (columns 25-30). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.
Valid formats for the date are:
Possible causes are:
For more details, please see the description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.
The program terminates with a condition code of 08.
Corrective Action: Correct the Date Control Record (the DACHK DD statement) and rerun the New Day procedure.
Explanation: Highlighted, unrollable message.
The Active Jobs file specified for the Control-M monitor is not the correct Active Jobs file for this monitor. The QNAME specified in CTMPARM does not match the QNAME specified in Record 0 of the Active Jobs file.
The Control-M monitor shuts down.
Corrective Action: Correct the data set name referenced by the DD name DACKPT, or format the Active Jobs file using the same IOA Load library used by the Control-M monitor.
Explanation: The procedure that builds a new Control-M Resources file encountered an error. The next message describes the error.
The system stops without building the Control-M Resources file, and issues a return code of 12.
Corrective Action: Correct the error described in the next message and try again.
Explanation: The counters in record 0 have illegal values. Record 0 of the Control-M Resources file contains counters and parameters that define the file. The maximum value of each counter is 100.
The system stops and issues a return code of 12.
Corrective Action: Ensure that there are no more than 100 Quantitative resource records and no more than 100 Control resource records.
Explanation: You tried to define too many base slots in the new Control-M Resources file. The new Control-M Resources file build program can define a maximum of 1160 base slots.
The system stops without defining any base slots, and issues a return code of 12.
Corrective Action: Change the value of the RESBQNT parameter to a value that is less than 1160. For more information, see the section on MVS procedures and configuration in the Control-M chapter of the INCONTROL for z/OS Installation Guide.
Explanation: An error interrupted copying of the Control-M Resources file or the IOA Conditions file. The next message describes the cause of the error.
The system stops without copying the file, and issues return code 12.
Corrective Action: Correct the error described in the next message and try again.
Explanation: Copying failed because the new Control-M Resources file is not big enough to contain all of the resource data, whether relating to quantitative or control resources or both, in the old Control-M Resources file.
The system stops without copying the file, and issues a return code of 12.
Corrective Action: Try again with a larger new Control-M Resources file.
Explanation: The program that builds the new Control-M Resources file could not update it from the Active Jobs File (AJF). The program detected new jobs data in the AJF that should be updated in the Control-M Resources file, but it could not do the update.
The system continues building the Control-M Resources file, without adding the new data.
Corrective Action: Check and correct the definitions of the AJF, the Control-M Resources file, and the data, as necessary, and try again. If necessary, update the Control-M Resources file manually.
Explanation: This message is issued if the RESBQNT# parameter in the new resource file is less than the value of RESBQNT# in the old file.
Corrective Action: Refer to the Control-M Utilities guide, utility CTMCRES, section "Copy or Resize the Control-M Resources File". Part of the procedure involves changing parameter RESBQNT#, which is the maximum number of Quantitative resources to be defined in the Control-M Resources file.
Explanation: During the execution of the CTMTLB utility, a scheduling table was encountered which contained a combination of both mainframe and distributed job definitions. This is not supported by the utility.
The program terminates with a return code of 8.
Corrective Action: To overcome this situation, the CTMTLB utility must be executed twice, once using the EXCLUDE MF control statement and once using the EXCLUDE NONMF control statement so that two separate XMLs are created, one for the mainframe datacenter and one for the distributed datacenter. The DATACENTER control statement for each execution must be appropriately changed.
Explanation: During the execution of the CTMTLB utility, an empty scheduling table was encountered.
The program ignores the empty table, continues processing and terminates with a return code of 4.
Corrective Action: No action is required.
Parent Topic |