A–CTA

This group includes messages for the Control-D (including Control-D/Image and Control-D/Page on Demand), Control-M for z/OS (including Control-M/Assist, Control-M/Links for z/OS Control-M/Restart), Control-M/Analyzer, Control-O, and IOA (infrastructure) products.

ACI MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages ACIF00 through ACIFxxLink copied to clipboard

This group includes messages for the Control-O product.

ACIF40I ACIF PRINTING INTERFACE STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-D ACIF Interface Facility has started for a report being processed by the Printing Mission that issued the message.

A report destined for PC file transfer that was decollated with the ACIF CDAM parameter set to YES will be converted by ACIF into AFP Category 5 data stream format.

The Printing Mission begins initialization of the ACIF Interface Facility.

Corrective Action: No action is required.

ACIF41I ACIF PRINTING INTERFACE COMPLETED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the Control-D ACIF Interface Facility has successfully converted a report being processed by the Printing Mission that issued the message.

A report destined for PC file transfer that was decollated with the CDAM ACIF parameter set to YES was converted by ACIF into AFP Category 5 data stream format.

The Printing Mission terminates processing of the ACIF Interface Facility and completes processing of the report.

Corrective Action: No action is required.

ACIF42E ACIF PRINTING INTERFACE ENDED IN ERRORLink copied to clipboard

Explanation: The Control-D ACIF Interface Facility encountered an error condition while attempting to convert a report being processed by the Printing Mission that issued the message.

This message is followed by the ACIF43E and ACIF44E messages that describe the cause of the error.

The Printing Mission terminates processing of the ACIF Interface Facility and ends in error.

Corrective Action: Examine the ACIF43E and ACIF44E messages to determine why the Control-D ACIF Interface Facility ended in error and correct the problem accordingly.

ACIF43E CODE= `err_cod`, R15= `reg_15`, R0= `reg_0`, R1= `reg_1`Link copied to clipboard

Explanation: The Control-D ACIF Interface Facility encountered an error condition while attempting to convert a report being processed by the Printing Mission that issued the message. This message displays the Control-D internal error code and the contents of registers 15, 0, and 1 at the time of error.

The variables in this message are:

err_cod - the Control-D internal error code
reg_15 - the contents of register 15
reg_0 - the contents of register 0
reg_1 - the contents of register 1

The Control-D ACIF Interface Facility issues this message in combination with the ACIF44E message to describe the error and to assist in diagnosing its cause.

The Control-D ACIF Interface Facility terminates processing of the report. The Printing Mission ends in error.

Corrective Action: Examine the ACIF44E message for a description of the problem encountered.

ACIF44E descrLink copied to clipboard

The Control-D ACIF Interface Facility issues this message in combination with the ACIF43E or ACIF4BE message to describe the error and to assist in diagnosing its cause.

The Control-D ACIF Interface Facility terminates processing of the report. The Printing Mission ends in error.

Corrective Action: Use the information displayed in this message and in the ACIF43E or ACIF4BE message to determine the cause of the error and correct the problem. If the problem persists, contact your INCONTROL administrator.

ACIF45I MAXIMUM CONCURRENT ACIF/CCIF PRINTING MISSIONS ALREADY EXECUTINGLink copied to clipboard

Explanation: This information message indicates that the Control-D ACIF Interface Facility is temporarily unavailable because, within a Print monitor address space, the maximum number of Printing Missions that can concurrently use the facility has been reached.

The Control-D ACIF Interface Facility limits the total number of ACIF subtasks that can execute at the same time. This limit is defined using customization setting WD2375. The wait interval is defined using customization setting WD2377.

When the time specified in the wait interval has elapsed, the Printing Mission again tries to access the Control-D ACIF Interface Facility.

Corrective Action: No action is required.

ACIF46I WAITING FOR AN EXECUTING ACIF/CCIF PRINTING MISSION TO COMPLETELink copied to clipboard

Explanation: This information message indicates that the Printing Mission detected that the maximum number of ACIF subtasks permitted to execute simultaneously has been reached.

The Control-D ACIF Interface Facility limits the total number of ACIF subtasks that can execute at the same time. This limit is defined by means of customization setting WD2375. The wait interval is defined by means of customization setting WD2377.

When the time specified in the wait interval has elapsed, the Printing Mission again tries to access the Control-D ACIF Interface Facility.

Corrective Action: No action is required.

ACIF47E MAXIMUM RETRIES LIMIT TO START AN ACIF/CCIF PRINTING MISSION REACHEDLink copied to clipboard

Explanation: The Printing Mission failed to access the Control-D ACIF Interface Facility after making the maximum number of attempts allowed.

The Control-D ACIF Interface Facility was being used by the maximum number of ACIF subtasks allowed to execute concurrently. The Printing Mission tried to access the Control-D ACIF Interface Facility without success more than the maximum retry value specified using customization setting WD2378.

Corrective Action: Increase the maximum retry value specified using customization setting WD2378 and/or increase the wait interval value specified using customization setting WD2377. Reorder the Printing Mission. If the problem persists, contact your INCONTROL administrator.

ACIF48W ACIFPARM MEMBER `memName` NOT FOUND - SEARCHING FOR MEMBER $$$$DFLTLink copied to clipboard

Explanation: No matching member was found in the Control-D ACIFPARM library for the report being processed by the Control-D ACIF Interface Facility.

Control-D failed to find an ACIFPARM library member memName with a name matching either the job, Printing Mission or Recipient name of the job. The member name search convention used is determined by the setting of optional wish WD2376. The default is J for job name.

Control-D will attempt to obtain default ACIF execution parameters from the ACIFPARM member $$$$DFLT.

Corrective Action: Check the setting for optional wish WD2376. Add a member to the ACIFPARM library with the appropriate name or verify that the default ACIF execution parameters in ACIFPARM member $$$$DFLT are appropriate for the report.

ACIF49W ACIF ISSUED WARNING MESSAGES - PROCESSING CONTINUESLink copied to clipboard

Explanation: The Control-D ACIF Interface Facility has detected that ACIF completed processing with a noncritical return code of 4.

The Control-D ACIF Interface Facility has successfully completed converting the report to AFP Category 5 data stream format. However, a warning condition was detected by ACIF that may affect the contents of the data stream.

Corrective Action: Inspect the ACIF message output to determine the cause of the warning and whether or not its effect on the report data stream can be ignored.

ACIF4BE CTVINDEX STATEMENT SYNTAX ERRORLink copied to clipboard

Explanation: The Control-D ACIF Interface Facility encountered syntax that is invalid for the CTVINDEX parameter in ACIFPARM library member.

The Control-D ACIF Interface Facility issues this message together with the ACIF44E message, which describes the error.

The Printing Mission terminates processing of the ACIF Interface Facility and ends in error.

Corrective Action: Examine the ACIF44E message for a description of the problem.

AES MessagesLink copied to clipboard

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.

Messages AES100 through AES1xxLink copied to clipboard

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.

AES171S BLDL/LOAD FAILED FOR MODULE "CTMLIB"Link copied to clipboard

Explanation: The CTMLIB module cannot be loaded.

This error message is issued by the CTMAES or CTMJDS utility, which performs an AutoEdit simulation that is used to test the syntax of the AutoEdit control statements. This error message is due to one of the following:

The module does not appear in the load module search list.
There is insufficient memory to load the program.

Submission simulation stops.

Corrective Action: Do one of the following:

Verify whether CTMLIB appears in the IOA Load library or any other concatenated load module library of the CTMAES or CTMJDS utility.
Increase the region size of the CTMAES or CTMJDS utility.

AES172S OPEN OF INPUT CARDS FILE FAILED. DDNAME "DASIM"Link copied to clipboard

Explanation: Open of control statements file failed (the DD statement DASIM).

DD statement DASIM is missing.
The data set described by DD statement DASIM does not exist, or cannot be opened for sequential read, or the record length is not 80.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job (or the CLIST) and run it again.

AES173S BLDL/ATTACH FOR MODULE "CTMSUB" FAILEDLink copied to clipboard

Explanation: The Control-M submission simulation utility (CTMAES or CTMJDS) failed while loading the CTMSUB module.

The CTMSUB (Control-M submitter) module is activated as part of the simulation. The failure could be due to one of the following:

There is insufficient memory.
The module is not in the STEPLIB/Linklist libraries.

Program execution stops with a condition code of 08.

Corrective Action: Look for system messages on the job log related to the problem. Verify whether CTMSUB appears in the IOA Load library, and that the library is defined in the STEPLIB of the CTMAES or CTMJDS utility.

AES174S CTMSUB ABENDED CODE= `abCode` MEMBER `memName` LIBRARY `lib`Link copied to clipboard

Explanation: The Control-M submitter module (CTMSUB) abended with the abend code abCode while trying to submit the memName member from the lib library.

CTMSUB was called by the Control-M CTMAES or CTMJDS utility.

Submission simulation stops with a condition code of 08.

Corrective Action: Check the JOBLOG for additional system messages related to the problem. If you can resolve the problem by responding to previous messages, do so. If the problem is not resolved, or seems to be with the Control-M AutoEdit submit simulation, call your INCONTROL administrator.

AES175I JOB SUBMISSION SIMULATION STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-M submission simulator has started. The Control-M CTMAES or CTMJDS utility produces this message.

Corrective Action: No action is required.

AES176I JOB SUBMISSION SIMULATION ENDEDLink copied to clipboard

Explanation: This information message indicates that the Control-M submission simulator has ended normally. The Control-M CTMAES or CTMJDS utility produces this message.

Corrective Action: No action is required.

AES177I SUBMISSION SIMULATION OF MEMBER `memName` LIBRARY `lib` STARTEDLink copied to clipboard

Explanation: This information message indicates that the submission simulation of the memName member in the lib library has started. The Control-M CTMAES or CTMJDS utility produces this message.

Corrective Action: No action is required.

AES178I SUBMISSION SIMULATION OF MEMBER `memName` LIBRARY `lib` ENDEDLink copied to clipboard

Explanation: This information message indicates that the submission simulation of the memName member in the lib library has ended normally. The Control-M CTMAES or CTMJDS utility produces this message.

Corrective Action: No action is required.

AES179E MISSING PARAMETER DURING MEMBER `memName`Link copied to clipboard

Explanation: A missing parameter for member submission simulation. The Control-M CTMAES or CTMJDS utility produces this message.

Submission simulation stops with a condition code of 08.

Corrective Action: Correct the parameters and try again.

AES180E INVALID COMMANDLink copied to clipboard

Explanation: An invalid command or parameter was supplied to the Control-M CTMAES or CTMJDS utility.

The invalid line appears before this message. This message precedes the AES181I message, which presents the valid commands.

The command is ignored, and processing continues.

Corrective Action: Use one of the valid commands specified in the AES181I message.

AES181I COMMANDS ARE: `cmds`Link copied to clipboard

Explanation: This information message indicates valid commands for the Control-M CTMAES or CTMJDS utility.

Corrective Action: Reissue one of the valid commands specified in the message.

AES182E INVALID SUB-COMMAND VALUELink copied to clipboard

Explanation: Invalid subcommand value in an AutoEdit simulation control statement.

This error message is issued by the CTMAES or CTMJDS utility that is used to test the syntax of the AutoEdit control statements. For more details regarding command syntax, see the Control-M for z/OS User Guide.

The command is ignored, and processing continues.

Corrective Action: Correct the subcommand or command parameter.

AES183I TEN (10) INTERVAL UNITS PASSEDLink copied to clipboard

Explanation: This information message indicates that the AutoEdit simulation submitter task did not return control for over 10 seconds.

The AutoEdit simulation works as two tasks. As it can also be used to check the Control-M submission user exit (CTMX002), there is a chance of getting suspended if there is a bug in the exit.

Corrective Action: If the message continually appears, the CTMSUB task is likely to be either suspended or in a loop. You should cancel the job with a DUMP.

AES184E REDUNDANT INFORMATION IN LINE `lin`Link copied to clipboard

Explanation: There is irrelevant data in the parameters line of the CTMAES or CTMJDS utility.

The redundant data is ignored and processing continues.

Corrective Action: Correct the lin line, usually columns 73 through 80, to prevent the messages from appearing.

AES187E INTERNAL ERROR PROCESSING MASKS FOR MASK `mask` FOR MEMBER `memName`Link copied to clipboard

Explanation: The Control-M CTMAES or CTMJDS utility failed to process a member name memName containing mask characters, due to an internal error.

The CTMAES or CTMJDS utility does not perform a simulation for the requested member or members, and processing continues with the next simulation request.

Corrective Action: Contact your INCONTROL administrator.

AES188E MEMBER CONTROL CARD WAS NOT SPECIFIEDLink copied to clipboard

Explanation: No member name was specified in the input for the Control-M CTMAES or CTMJDS utility. The MEMBER statement is obligatory.

The CTMAES or CTMJDS utility does not perform a simulation for the requested member or members, and processing continues with the next simulation request.

Corrective Action: Correct the input and rerun the job.

AES189E JOB `jobName` NOT FOUND IN SCHEDULING TABLE `tableName`Link copied to clipboard

Explanation: The jobName job that was specified in the input parameters as belonging to the tablename scheduling table was not found in that table.

The program terminates the current simulation request and proceeds to the next input statement.

Corrective Action: Correct the job name or specify a different table name.

AES190I jobName RETRIEVED FROM TABLE `tableName` IN SCHEDULING LIBRARY `lib`Link copied to clipboard

Explanation: This information message indicates that the jobName job that was specified in the input parameters as belonging to the tableName table in the lib scheduling library was successfully retrieved from the table, and will be processed by the AutoEdit Simulation utility.

Corrective Action: No action is required.

Messages AESL00 through AESLxxLink copied to clipboard

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.

AESL45S DD STATEMENT "DASIM" IS EMPTY. UTILITY TERMINATED.Link copied to clipboard

Explanation: There are no input parameters when running the CTMJDS or CTMAESIM utilities. The utility terminates.

Corrective Action: Correct the input parameters and rerun the utility.

AESL46S MANDATORY "SUBMIT" PARAMETER IS MISSING. UTILITY TERMINATED.Link copied to clipboard

Explanation: The SUBMIT parameter is missing when running the CTMJDS utility. The utility terminates.

Corrective Action: Correct the input parameters and rerun the utility.

AESL47I `'cmd'` Control-STATEMENT FOUND - {JCL | SCHEDULING} LIBRARY MODE USEDLink copied to clipboard

Explanation: This information message indicates that the program found the cmd control statement, and based the processing mode on its type, as follows:

If a SCHEDLIB control statement is found, the AutoEdit Simulation program uses Scheduling Library Mode, in which the statements SCHEDLIB, TABLE, and JOB are valid.
If a LIBRARY or MEMBER control statement is found, the AutoEdit Simulation program uses JCL Library Mode, in which the statements LIBRARY and MEMBER are valid.
The two modes cannot be mixed in the same input stream.

Corrective Action: No action is required.

AESL48E Control-STATEMENT INVALID FOR CURRENT MODE. STATEMENT IGNOREDLink copied to clipboard

Explanation: The program found a control statement which did not match the processing mode currently used.

Valid statements are:

in Scheduling Library Mode, SCHEDLIB, TABLE, and JOB statements
in JCL Library Mode, LIBRARY and MEMBER statements

The two modes cannot be mixed in the same input stream.

The program terminates the current simulation request and proceeds to the next input statement.

Corrective Action: Correct the control statement and rerun the job.

AESL49E SCHEDLIB Control-STATEMENT NOT SPECIFIED OR INVALIDLink copied to clipboard

Explanation: A SCHEDLIB control statement was not specified in Scheduling Library Mode, or the control statement specified was rejected because of an error. In Scheduling Library Mode, the SCHEDLIB, TABLE, and JOB statements are required.

The program terminates the current simulation request and proceeds to the next input statement.

Corrective Action: Add the missing control statement and rerun the job.

AESL50E TABLE Control-STATEMENT NOT SPECIFIED OR INVALIDLink copied to clipboard

Explanation: A TABLE control statement was not specified in Scheduling Library Mode, or the control statement specified was rejected because of an error. In Scheduling Library Mode, the SCHEDLIB, TABLE, and JOB statements are required.

The program terminates the current simulation request and proceeds to the next input statement.

Corrective Action: Add the missing control statement and rerun the job.

AESL51E JOB Control-STATEMENT NOT SPECIFIED OR INVALIDLink copied to clipboard

Explanation: A JOB control statement was not specified in Scheduling Library Mode, or the control statement specified was rejected because of an error. In Scheduling Library Mode, the SCHEDLIB, TABLE, and JOB statements are required.

The program terminates the current simulation request and proceeds to the next input statement.

Corrective Action: Add the missing control statement and rerun the job.

AESL52I jobName NOT FOUND IN OVERLIB LIBRARY - MEMLIB LIBRARY WILL BE USEDLink copied to clipboard

Explanation: This information message indicates that the jobName job that was designated by the user was not found in the library specified in the OVERLIB job scheduling definition field.

The library specified in the MEMLIB field is accessed instead.

Corrective Action: No action is required.

AESL53I jobName RETRIEVED FROM MEMLIB/OVERLIB LIBRARY `lib`Link copied to clipboard

Explanation: This information message indicates that the library that contained the job that was to be processed by the AutoEdit Simulation utility was retrieved.

The variables in this message are:

jobName - the job that was to be processed by the AutoEdit simulation utility
lib - the library that contained the jobName job

Corrective Action: No action is required.

AESL54I OWNER `owner` RETRIEVED FROM JOB SCHEDULING DEFINITION `jobName`Link copied to clipboard

Explanation: This information message indicates that the owner ID to be used by the AutoEdit Simulation utility was retrieved from the job scheduling definition.

The variables in this message are:

owner - the owner ID to be used by the AutoEdit simulation utility
jobName - the identity of the job scheduling definition from which owner was retrieved.

Corrective Action: No action is required.

AESL55I APPLICATION `applId` RETRIEVED FROM SCHEDULE DEFINITION `jobName`Link copied to clipboard

Explanation: This information message indicates the application ID to be used by the AutoEdit Simulation utility was retrieved from the schedule definition.

The variables in this message are:

applId - the identity of the application to be used by the AutoEdit simulation utility
jobName - the identity of the job scheduling definition from which applId was retrieved.

Corrective Action: No action is required.

ALI MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages ALI300 through ALI3xxLink copied to clipboard

This group includes messages for the Control-O product.

ALI360S AUTOMATION LOG DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

Explanation: SVC 99 failed during allocation or deallocation of the Automation Log file. The CTOALI program uses SVC 99 to dynamically allocate and deallocate the Automation Log file.

For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTOALI program ends with a return code of 08.

Corrective Action: No action is required.

ALI361S ERROR WHILE LOADING MODULE IDCAMSLink copied to clipboard

Explanation: Loading of the IDCAMS module failed. The CTOALI program failed to link to IDCAMS to define a VSAM linear data set.

The CTOALI program ends with a return code of 08.

Corrective Action: Determine why the IDCAMS module cannot be loaded from STEPLIB or LINKLST, correct the problem, and resubmit the job.

ALI362S INVALID PARAMETERS PASSED TO THE PROGRAMLink copied to clipboard

Explanation: The CTOALI program was called with invalid parameters, either using the PARM parameter in the JCL, or using the program that called the CTOALI program.

The CTOALI program ends with a return code of 08.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact your INCONTROL administrator.

ALI363S NO PARAMETERS PASSED TO THE PROGRAMLink copied to clipboard

Explanation: The CTOALI program was called with null parameters, either using the PARM parameter in the JCL, or using the program that called the CTOALI program.

The CTOALI program ends with a return code of 08.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact your INCONTROL administrator.

ALI364S ERRORS IN IDCAMS PROCESSINGLink copied to clipboard

Explanation: The IDCAMS module ended with a non-zero return code. The CTOALI program links to IDCAMS to define VSAM linear data sets.

The CTOALI program ends with a return code of 08.

Corrective Action: Check the job printout to see why IDCAMS did not end successfully. It may be necessary to edit the DIVSKEL member in the INSTWORK library to change the MODELM statements of the IDCAMS SYSIN. Correct and resubmit the job.

ALI365S VOLUME PARAMETER MUST BE SPECIFIED FOR DIV DATASETSLink copied to clipboard

Explanation: The volume was not specified for a VSAM linear data set.

The CTOALI program ends with a return code of 08.

Corrective Action: Specify a volume and resubmit the job.

ALO MessagesLink copied to clipboard

This group includes messages for the Control-O CMEM product.

Messages ALO200 through ALO2xxLink copied to clipboard

This group includes messages for the Control-O CMEM product.

ALO290I {CONTROL-O | CTMCMEM} AUTOMATION LOG STARTEDLink copied to clipboard

Explanation: This information message indicates that the Automation Log subtask began.

Corrective Action: No action is required.

ALO291E AUTOMATION LOG ERROR WHILE PROCESSING REQUESTSLink copied to clipboard

Explanation: The Automation Log subtask detected an error while processing requests.

The subtask and the Control-O or CMEM monitor shut down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.

Corrective Action: Contact your INCONTROL administrator.

ALO292S {CONTROL-O | CTMCMEM} AUTOMATION LOG TERMINATION ERRORLink copied to clipboard

Explanation: The Automation Log subtask terminated after an error was detected.

Corrective Action: Contact your INCONTROL administrator.

ALO293I CONTROL-O AUTOMATION LOG ENDEDLink copied to clipboard

Explanation: This information message indicates that the Automation Log subtask terminated successfully.

The subtask and the monitor shut down.

Corrective Action: No action is required.

ALO294E OPEN OF AUTOMATION LOG FAILED. LOG SWAPPEDLink copied to clipboard

Explanation: The Automation Log subtask attempted to open the Automation Log file but failed.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Do the following:

Check the CTOPARM member in the Control-O installation library.
Check to see if the Automation Log file exists for this CPU.

ALO295S OPEN OF DAACTLOG FAILEDLink copied to clipboard

Explanation: The Automation Log subtask failed to open the file referenced by the DAACTLOG DD statement.

Corrective Action: Check the JCL of your Control-O or CMEM starting procedure to verify that the DD statement DAACTLOG exists. If the problem is not resolved, contact your INCONTROL administrator.

ALO296E ERROR DETECTED DURING ADDF. LOG SWAPPEDLink copied to clipboard

Explanation: The Automation Log subtask was unable to write to the Automation Log file.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.

ALO297I AUTOMATION LOG STATUS CHANGE COMPLETEDLink copied to clipboard

Explanation: This information message indicates that the Automation Log subtask completed the change of Automation Log status.

This message is displayed in response to the operator command F CONTROLO,AUTOLOG=YES/NO.

The Automation Log subtask writes to the new destination.

Corrective Action: No action is required.

ALO298E ERROR DETECTED DURING ENQ. LOG SWAPPEDLink copied to clipboard

Explanation: The Automation Log subtask detected an error while trying to ENQUEUE the Automation Log file.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.

ALO299E ERROR DETECTED DURING DEQ. LOG SWAPPEDLink copied to clipboard

Explanation: The Automation Log subtask detected an error while trying to dequeue the Automation Log file.

Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.

Messages ALO300 through ALO3xxLink copied to clipboard

This group includes messages for the Control-O CMEM product.

ALO303S {CONTROL-O | CTMCMEM} AUTOMATION LOG INITIALIZATION ERRORLink copied to clipboard

Explanation: The Automation Log subtask detected an error while initializing.

The subtask and the Control-O or CMEM monitor shuts down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.

Corrective Action: Contact your INCONTROL administrator.

ALO304S CONTROL-O AUTOMATION LOG SWAPPING ERRORLink copied to clipboard

Explanation: The Automation Log subtask detected a problem when swapping the log.

If the subtask handled the problem, Control-O continues to work as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

If the subtask could not handle the problem, the subtask and the monitor may shut down. Before shutting down, the Control-O monitor attempts to start a new Control-O monitor to replace itself. If it does not succeed after a few attempts, Control-O ceases trying.

Corrective Action: Contact your INCONTROL administrator.

ALO305S {CONTROL-O | CTMCMEM} AUTOM. LOG SEVERE ERROR ID= `err`Link copied to clipboard

Explanation: The Automation Log subtask detected an internal logic problem.

In this message, err is the identifying number of the error.

Corrective Action: Report the value of err to your INCONTROL administrator.

ALO306S ERROR DETECTED DURING LOGGINGLink copied to clipboard

Explanation: The Automation Log subtask detected an internal error while logging a record.

The subtask continues to work, but some records may be lost from the Automation Log.

Corrective Action: Contact your INCONTROL administrator.

ALO307E PROBLEMS WITH WRITEF. LOG SWAPPEDLink copied to clipboard

Explanation: The Automation Log subtask detected a problem while trying to commit changes in the Automation Log file.

Control-O continues to work as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.

ALO308E AUTOMATION LOG I/O ERROR. RC = `rc`Link copied to clipboard

Explanation: The Automation Log subtask detected an I/O error while trying to perform an operation on the Automation Log file.

In this message, rc is the return code generated by the error.

If the subtask cannot handle the problem, the subtask and the monitor may shut down. Before shutting down, the Control-O monitor attempts to start a new Control-O monitor to replace itself. If it does not succeed after a few attempts, Control-O ceases trying.

Corrective Action: Check operating system messages detailing the return code (rc) and the cause of the error, for example, disk failure, incorrect data set, or incorrect name or allocation parameters. Correct the cause of the error accordingly.

ALU MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages ALU300 through ALU3xxLink copied to clipboard

This group includes messages for the Control-O product.

ALU370I COPY OF CONTROL-O AUTOMATION LOG STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTOALOCP utility has begun copying the Automation Log file.

Corrective Action: No action is required.

ALU371I COPY OF CONTROL-O AUTOMATION LOG ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTOALOCP utility has successfully completed copying the Automation Log file.

Corrective Action: No action is required.

ALU372S COPY OF CONTROL-O LOG ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTOALOCP utility abended. This message follows a message describing the cause of the error detected.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: The previous message identifies the cause of the error. Correct the problem, and resubmit the job.

ALU373S ERROR OPENING SOURCE FILELink copied to clipboard

Explanation: The CTOALOCP utility was unable to open the source Automation Log file.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Check and correct the JCL. If the source file is a sequential file, ensure that the DASOURCE DD name is specified.

ALU374S ERROR OPENING TARGET FILELink copied to clipboard

Explanation: The CTOALOCP utility was unable to open the target Automation Log file because it received a non-zero return code while opening the target file.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Check and correct the JCL. If the target file is a sequential file, ensure that the DATARGET DD name was specified.

ALU375S NON-ZERO RETURN CODE RECEIVED: "`pgm`"Link copied to clipboard

Explanation: The CTOALOCP utility received a non-zero return code from the program whose name (pgm) appears in the text of the message. The CTOALOCP utility calls other programs to perform various tasks.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Check and correct the JCL. Check the job printouts for relevant messages about the problem.

ALU376S INVALID TIMELink copied to clipboard

Explanation: An invalid TIME parameter was specified for CTOALOCP utility.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Check and correct the STARTTIME and ENDTIME parameters. Resubmit the job.

ALU377S INVALID DATASET NAMELink copied to clipboard

Explanation: An invalid data set name was specified for the CTOALOCP utility.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Check and correct the FROMDSN and TODSN parameters. Resubmit the job.

ALU378S INVALID FILE TYPELink copied to clipboard

Explanation: An invalid data set type was specified for the CTOALOCP utility.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Check and correct the FROMTYPE and TOTYPE parameters. Resubmit the job.

ALU379S INVALID VOLUMELink copied to clipboard

Explanation: An invalid volume was specified for the CTOALOCP utility.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Correct the TOVOLUME parameter and resubmit the job.

ALU380S INVALID UNITLink copied to clipboard

Explanation: An invalid unit was specified for the CTOALOCP utility.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify a valid value for the TOUNIT parameter and resubmit the job.

ALU381S SOURCE AND TARGET CANNOT BOTH BE SEQUENTIALLink copied to clipboard

Explanation: Type S (Sequential) files were specified for both the source and the target Automation Log files.

At least one of the files must be nonsequential.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify a nonsequential file for the source file, or the target file, or both. Resubmit the job.

ALU382S VOLUME IS REQUIRED WHEN DIV LOG IS USEDLink copied to clipboard

Explanation: No value was specified for the TOVOLUME parameter.

This parameter must be specified for a VSAM linear data set definition.

The CTOALI program ends with a return code of 08.

Corrective Action: Specify a valid value for the TOVOLUME parameter and resubmit the job.

ALU383S INVALID NUMBER OF RECORDSLink copied to clipboard

Explanation: An invalid number of records was specified in the TORECNUM parameter.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify a valid number of records for the TORECNUMV parameter and resubmit the job.

ALU384S AUTOM. LOG SEQ. DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

Explanation: Dynamic allocation (SVC 99) of a sequential Automation Log file failed. The CTOALOCP utility uses SVC 99 to dynamically allocate and deallocate the dsn file, which is a sequential source or target Automation Log file.

For explanations of the return code (rc) and reason code (rsn) displayed as part of this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Examine the return and reason codes and take appropriate corrective action.

ALU385S ERROR READING RECORD 0 FROM SOURCE FILELink copied to clipboard

Explanation: The CTOALOCP utility detected an internal error while reading record 0 from the source Automation Log file. The CTOALOCP utility reads source file attributes (for example, number of records) from source data set record 0.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

ALU386S MINIMAL IS NOT ALLOWED WITH SEQUENTIAL FILELink copied to clipboard

Explanation: The MINIMAL parameter was specified for a copy operation using sequential files. The MINIMAL parameter is only allowed when source and target files are both nonsequential.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Do one of the following:

Remove the MINIMAL parameter.
Designate nonsequential source and target files.

ALU387S TARGET DATASET NAME IS MANDATORYLink copied to clipboard

Explanation: No data set name was specified for the target Automation Log file. The data set name must be specified when copying a file to a nonsequential data set.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify a valid value for the TODSN parameter and resubmit the job.

ALU388S ERROR READING THE SOURCE FILELink copied to clipboard

Explanation: The CTOALOCP utility detected an internal error while reading the source Automation Log file.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

ALU389S ERROR WRITING THE TARGET FILELink copied to clipboard

Explanation: The CTOALU program detected an internal error while writing the target Automation Log file.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

Messages ALU400 through ALU4xxLink copied to clipboard

This group includes messages for the Control-O product.

ALU401S ERROR DURING WRITEFLink copied to clipboard

Explanation: The CTOALOCP utility detected an internal error while writing the target Automation Log file.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Contact your INCONTROL administrator.

ALU402S SOURCE AND TARGET DSN CANNOT BE THE SAMELink copied to clipboard

Explanation: The same data set name was specified for both the source and the target Automation Log files. Source and target files must have different data set names.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify valid data set names and resubmit the job.

ALU403S MINIMAL ALLOCATION REQUIRES DATE/TIME LIMITLink copied to clipboard

Explanation: The MINIMAL parameter was specified without a DATE/TIME limit. Values must be specified for at least the STARTDATE and ENDDATE parameters. The format for these parameters is yymmdd.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify valid values for the STARTDATE and ENDDATE parameters and resubmit the job.

ALU404S FROM TIME LIMIT REQUIRES FROM DATE LIMITLink copied to clipboard

Explanation: A DATE limit was not specified. When a copy operation is set to start at a specific time, the date must also be specified.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify a valid DATE limit and resubmit the job.

ALU405S TO TIME LIMIT REQUIRES TO DATE LIMITLink copied to clipboard

Explanation: A TODATE limit was not specified. When a copy operation is set to end at a specific time, the date must also be specified.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Specify a valid value for the TODATE parameter and resubmit the job.

ALU406S NO RECORDS FOUND BETWEEN DATE/TIME LIMITSLink copied to clipboard

Explanation: No records were found within the specified DATE or TIME limits (or both) set for the copy operation.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Check the DATE and TIME limits specified in the JCL. Correct them and resubmit the job if necessary.

ALU407S DATE LIMITS ARE EQUAL. TIME IS INCORRECTLink copied to clipboard

Explanation: The specified TIME limits are incompatible with the specified DATE limits. When you specify a copy operation starting and ending on the same day, the ending time must be later than the starting time.

The CTOALOCP utility ends with a return code of 08.

Corrective Action: Correct the values for the STARTDATE, STARTTIME, ENDDATE, and ENDTIME parameters. Resubmit the job.

APA MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages APAF00 through APAFxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

APAF20I COPYING APAPARM LIBRARY TO LIBRARY WITH RECFM VARIABLE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDCNVAP utility started copying the APAPARM library to a library with variable RECFM.

Corrective Action: No action is required.

APAF21I COPYING APAPARM LIBRARY TO LIBRARY WITH RECFM VARIABLE ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDCNVAP utility successfully finished copying the APAPARM library to a library with variable RECFM.

Corrective Action: No action is required.

APAF22S COPYING APAPARM LIBRARY TO LIBRARY WITH RECFM VARIABLE ENDED WITH ERRORSLink copied to clipboard

Explanation: When attempting to copy the APAPARM library to a library with variable RECFM, the CTDCNVAP utility ended with errors.

Corrective Action: Notify your INCONTROL administrator.

APAF23I MEMBER `memName` IS TRANSFERRED TO VARIABLE BLOCKED LIBRARYLink copied to clipboard

Explanation: This information message indicates that the CTDCNVAP utility copied the memName member from the APAPARM library to a library with variable RECFM.

Corrective Action: No action is required.

APAF24S UNABLE TO READ DIRECTORY. INSUFFICIENT STORAGELink copied to clipboard

Explanation: The CTDCNVAP utility could not copy the APAPARM library to a library with variable RECFM because of insufficient storage.

Corrective Action: Notify your INCONTROL administrator.

APAF26S UNABLE TO READ A MEMBER FROM THE APAPARM LIBRARYLink copied to clipboard

Explanation: Due to an internal error while attempting a read operation, the CTDCNVAP utility could not copy a member from the APAPARM library to a library with variable RECFM.

Corrective Action: Notify your INCONTROL administrator.

APAF27S UNABLE TO PUT A MEMBER TO THE NEW APAPARM LIBRARYLink copied to clipboard

Explanation: Due to an internal error while attempting a write operation, the CTDCNVAP utility could not copy a member from the APAPARM library to a library with variable RECFM.

Corrective Action: Notify your INCONTROL administrator.

APAF28S INPUT APAPARM LIBRARY IS EMPTYLink copied to clipboard

Explanation: The CTDCNVAP utility could not copy a member from the APAPARM library to a library with variable RECFM because the input library is empty.

Corrective Action: Notify your INCONTROL administrator.

API MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages API0 through API0xxLink copied to clipboard

This group includes messages for the Control-O product.

API000E PRINT FILE OPEN FAILEDLink copied to clipboard

Explanation: The print file cannot be opened. IOAAPI continues to run, but no messages are printed.

Corrective Action: Find and correct the error. Usually, a DD statement is missing.

API001I IOA API STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOAAPI program has started.

Corrective Action: No action is required.

API002I IOA API ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOAAPI program has ended.

Corrective Action: No action is required.

API003I REQ= `requestText`Link copied to clipboard

Explanation: This information message shows the text of the request (requestText) as passed to IOAAPI.

The message will be processed.

Corrective Action: No action is required.

API004I RC= `rc`Link copied to clipboard

Explanation: This information message shows the return code (rc) issued on processing the request.

Corrective Action: No action is required.

API005E STOPPED ON ERRORLink copied to clipboard

Explanation: The IOAAPI program stopped running because a return code was issued indicating an error. The error code is shown in the API004I message.

Corrective Action: Correct the error and run IOAAPI again.

API006I CONDITION IS {TRUE | FALSE}Link copied to clipboard

Explanation: This message is issued after the THEN or ELSE part of an IF statement. It shows whether the condition value is TRUE, in which case the requests are honored, or FALSE, in which case the requests are ignored.

Corrective Action: No action is required.

API007E ERROR IN "IF" STATEMENTLink copied to clipboard

Explanation: There is an error in an IF statement. The IOAAPI program stopped.

Corrective Action: Correct the error and run IOAAPI again.

API008E SERVICE_TYPE NOT RECOGNISED `serviceType`Link copied to clipboard

Explanation: The service type requested is not recognized. The recognized service types are COND, MAIL and LOG.

In this message, serviceType is the unrecognized service type.

Corrective Action: Correct the error and run IOAAPI again.

API010E xxxx SERVICE IS NOT SUPPORTED AS xxxx

Explanation: The MAIL and LOG services can only be used in batch or API runs.

Corrective Action: Correct the error and run IOAAPI again.

Messages API500 through API5xxLink copied to clipboard

This group includes messages for the Control-O product.

API560I ENVIRONMENT INITIALIZATION COMPLETELink copied to clipboard

Explanation: This information message is issued when the Control-O API first connects with the Control-O or CMEM monitor and completes the initialization process.

Corrective Action: No user action is required.

API561E REQUESTED FUNCTION NOT SUPPORTEDLink copied to clipboard

Explanation: The requested function is not in the list of supported Control-O API functions.

The Control-O API returns a return code of 08 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Check the syntax and spelling of the requested function. If necessary, contact your INCONTROL administrator.

API563E IOA SUBSYSTEM `subsys` INACTIVE. INTERFACE CANNOT BE USEDLink copied to clipboard

Explanation: A request has been received through the Control-O API that needs the Control-O or CMEM monitor, but Control-O or CMEM is not active.

The requested activity is aborted.

Corrective Action: Check why Control-O or CMEM is not active. Once the Control-O or CMEM monitor is active again, re-issue the request.

API565E SETOLOC/SETOGLB ERROR CODE= `rc` REASON= `rsn`, TEXT= `text`Link copied to clipboard

Explanation: The Control-O API is unable to execute the AutoEdit request. The API detected an error while trying to resolve or set an AutoEdit expression.

The Control-O API returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Ensure that the AutoEdit expression in the SETOLOC, SETOGLB or RESOLVE functions is correctly written.

The following table shows possible values for the error code (rc) and reason code (rsn), with the explanation of each:

Error Code (rc)	Reason Code (rsn)	Explanation
04		GETMAIN or FREEMAIN error
	1 through 6	GETMAIN failure
	7 through 10	FREEMAIN failure
08		Variable not found
	13	Variable not found and RESOLVE flag is on.
	36	%%$COMMSYS value length error.
	68	%%$TIMEINT first argument is not a valid date.
	69	%%$TIMEINT second argument is not a valid date.
	74	%%$X2C argument length is greater than 4.
	88	%%$DOLIMIT first argument is not numeric.
	89	%%$RULE functions argument is out of rule stack.
	90	%%%RULE functions argument is not numeric.
	98	Global variable pool not found.
	100	ISGENQ returned a non-zero return code.
	980	Internal error - global pool or database not found
	982	Internal error - global pool or database not found
12		Syntax error or general error
	11	Empty SET command.
	15	Empty IF command.
	21	%% not found in SET command.
	22	Separator not found after %%.
	23	‘=’ not found in SET command.
	24	%%$TIMEOUT value not numeric.
	25	%%$RESPMSG or %%$TIMEOUT - invalid parentheses.
	26	%%$RESPMSG or %%$TIMEOUT - too many values.
	27	%%$WAITKSL or %%$TSO or %%$CMD - invalid value (not YES/NO).
	28	%%$TIMEOUT - value too large.
	29	%%$STATID value length error.
	30	%%$AUTOLOG value length error.
	37	%%$AUTOSYS value length error.
	41	Function arguments not separated.
	42	Too few function arguments.
	45	CTMLINE# PARAMETER NOT NUMERIC when trying to set %%$CTMLINE# to a non-numeric value.
	46	CTMLINE# > CTMLINES when trying to set %%$CTMLINE# to a value greater than %%$CTMLINES.
	47	CTMLINE# < 0 when trying to set %%CTMLINE# to a value less than 0.
	52	%%$SUBSTR 2nd argument not numeric.
	53	%%$SUBSTR 3rd argument not numeric.
	54	%%$SUBSTR 2nd argument out of range.
	55	%%$SUBSTR 3rd argument out of range.
	56	%%$RESOLVE argument not recognized.
	57	%%$RANGE 1st argument not numeric.
	58	%%$RANGE 2nd argument not numeric.
	59	%%$RANGE 1st argument out of range.
	60	%%$RANGE 2nd argument out of range.
	61	%%$RANGE is too narrow.
	62	%%$CALCDATE 1st argument not in valid format.
	63	%%$CALCDATE 2nd argument not in valid format.
	64	%%$TIMEINT 1st argument is not 11 digits in length.
	65	%%$TIMEINT 1st argument is not numeric.
	66	%%$TIMEINT 2nd argument is not 11 digits.
	67	%%$TIMEINT 2nd argument is not numeric.
	71	More than one operator in one line.
	72	Less than two operands for an operator.
	73	More than two operands for an operator.
	75	%%$D2X argument length is greater than 10.
	76	%%$D2X argument is not numeric.
	77	%%$D2X argument number is greater than 2147483647 (2G).
	78	%%$X2D argument length is greater than 8.
	79	%%$X2D argument has an invalid character.
	81	First operand in arithmetic operation is not numeric.
	82	Second operand in arithmetic operation is not numeric.
	83	%%$DIV 2nd operand is 0.
	84	First operand is greater than 2G.
	85	Second operand is greater than 2G.
	86	Result of %%$PLUS case overflow.
	87	Result of %%$MINUS case overflow.
	91	Logical operand not numeric.
	92	Numeric logical operand out of range.
	93	Invalid logical operator.
	94	Logical atomic expression expected but not found.
	95	Unbalanced parentheses in logical expression.
	96	Too many nested parentheses in logical expression.
	97	Unbalanced quotes.
	99	%%$GLOBAL value length error.
16		Errors reading the global member
	08	Insufficient memory.
	12	Member not found.
	16	DSN is not a library.
	20	DSN is not fixed.
	24	Logical record length is not 80.
	28	Data set in use.
	36	Data set not in catalog.
	40	Dynamic allocation failed.
	52	Error when opening/processing a directory
	56	An abend was intercepted.
20		Errors writing the global member
	08	Insufficient memory.
	12	Member not found.
	16	DSN is not a library.
	20	DSN is not fixed.
	24	Logical record length is not 80.
	28	Data set in use.
	36	Data set not in catalog.
	40	Dynamic allocation failed.
	52	Error when opening/processing a directory
	56	An abend was intercepted.
24		Program buffers shortage
	12	Not enough space in RSL buffer.
	32	Not enough space in VCB for name and value. Variable name and data are too long.
	43	Arguments too long (ARG buffer overflow).
32		Program errors
	100	No last non-blank for non-blank value in SET command.
	101	No succeeding RSL for adjoining variables.
	102	Problems in PUTVAR while initiating.
	103	Too many arguments requested from PARSARGS.
	104	Problems calculating weekday.
	105	Invalid SET system variable.
	106	No local anchor was passed.
	107	No global anchor was passed.
	109	No MCT or SWT present in %%$IPLDATE for date formatting WO0816*.
36, 40, 44		Global variables errors
	04	Empty chain.
	08	End of chain.
	12	PNXH header error.
	16	PLBH header error.
	20	CTMMSK mash error, RC from IS is > 4.
	24	Pool is protected.
	32	Unable to get XAE information.
	33	Machine is not participating on XAE.
	34	Attempt made to set an XAE type 1 database variable in another system image.
	98	Pool not found.
	100	Timeout error. %%$DBROW = %%$DBSETVAR was used to set an IOAVAR variable, but the action could not be serialized for 2 minutes.
	107	No global anchor was passed. Program error.
	108	Field not defined in database.
	109	Requested row is out of range. To correct the problem, on the IOA Variables (IV) screen in ADMIN mode, use the U (Update) option to update the NUMBER OF ROWS attribute. Afterwards, issue the CMEM/Control-O LOADGLOBAL operator command to reload the modified database into memory. Control-M must be down when issuing this command to prevent possible loss of updates.
	110	Unable to lock the Global Variables pool.
48		Parse errors
	08	Invalid type.
	12	Place holder error.
	16	Position specification too long.
	20	Non numeric.
	24	Position null.
	28	Invalid variable. Specified variable is greater than 256, or the variable name is too long.
	32	String error.
	36	Invalid TPE type.
	40	Section vector overflow.
	44	Variable buffer overflow.
	107	No global anchor was passed.

API566E IOA SUBSYSTEM `subsys` NOT RESPONDING TO REQUESTSLink copied to clipboard

Explanation: The IOA subsystem subsys did not terminate rule execution within the expected time frame. The XAM requester, or the Control-O API, waits up to two minutes for the termination of the rule through a DORULE request.

The XAM interface, or the Control-O API, returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Review the rule execution results for errors and rectify as appropriate.

API567E IOA SUBSYSTEM `subsys` INACTIVELink copied to clipboard

Explanation: The requested service cannot be provided because the subsys IOA subsystem is not up.

The Control-O API, returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Start the Control-O or CMEM monitor.

API568E IOA SUBSYSTEM `subsys` DETECTED AN ERRORLink copied to clipboard

Explanation: An internal error was detected by the subsys IOA subsystem during the execution of a Control-O API request.

The Control-O API returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Do the following:

Check the Control-O or CMEM JOBLOG or SYSLOG for error messages.
Collect information about the functions requested by the Control-O API.
Determine whether or not the Control-O monitor is properly running for ongoing automation which is not related to the Control-O API.
Contact BMC Customer Support.

API569E IOA SUBSYSTEM `subsys` RETURNED AN INVALID RETURN CODELink copied to clipboard

Explanation: Due to an internal error, an invalid return code was returned by the subsys subsystem during the execution of a request issued through the Control-O API.

The Control-O API returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Do the following:

Collect information about the functions requested by the Control-O API.
Determine whether or not the Control-O or CMEM monitor is properly running for ongoing automation which is not related to the Control-O API.
Contact BMC Customer Support.

API56AE ERROR IN INAREA FIELDS ADDR= `add1, add2` LENGTH `len` DATA= `data_val`Link copied to clipboard

Explanation: This diagnostic error message appears when an error has occurred while calling an AutoEdit variable service.

The system action is aborted.

Corrective Action: Contact your INCONTROL administrator.

API56BE ERROR IN RESULT FIELDS ADDR= `add`, LENGTH `len` DATA= `data_val`Link copied to clipboard

Explanation: This diagnostic error message appears when an error has occurred while calling an AutoEdit variable service.

The system action is aborted.

Corrective Action: Contact your INCONTROL administrator.

API56CE INAREA LENGTH+RESULT= `xxxx`+ `xxxx`= `xxxx` > 255Link copied to clipboard

Explanation: This diagnostic error message appears when an error has occurred while calling an AutoEdit variable service.

The system action is aborted.

Corrective Action: Contact your INCONTROL administrator.

API56EE CHECKPOINT GLOBAL VARIABLE DATABASE `ioavar` TIMED OUT AFTER `num` SECONDSLink copied to clipboard

Explanation: CHECKPOINT was requested in order to save disk changes made in memory to the ioavar variable database. A timeout occurred while the request was being processed.

The CHECKPOINT request is terminated before completion. However, the changes made to the ioavar database are retained in memory, and a subsequent CHECKPOINT request will write them to disk.

Corrective Action: No user action is required.

API56FE CHECKPOINT GLOBAL VARIABLE DATABASE `ioavar` ENDED WITH ERROR. RC=16Link copied to clipboard

Explanation: CHECKPOINT was requested in order to save disk changes made in memory to the ioavar variable database. An error occurred while the request was being processed.

The CHECKPOINT request is terminated before completion. However, the changes made to the ioavar database are retained in memory, and a subsequent CHECKPOINT request will write them to disk.

Corrective Action: No user action is required.

API570I INITIALIZATION ENVIRONMENT COMPLETEDLink copied to clipboard

Explanation: This information message indicates that Control-O API initialization finished.

Corrective Action: No user action is required.

API573E IOA SUBSYSTEM `subsys` INACTIVE. INTERFACE CANNOT BE USEDLink copied to clipboard

Explanation: A request that requires the Control-O or CMEM monitor was issued through Control-O API, but the monitor is not active.

The action is aborted.

Corrective Action: Activate the Control-O or CMEM monitor, and reissue the request.

API575E SETOLOC/SETOGLB ERROR CODE = `rc` REASON = `rsn`, TEXT= `text`Link copied to clipboard

Explanation: A request to set a local or global variable failed.

The action is aborted.

Corrective Action: Check the return code (rc) and reason code (rsn) in the following tables to determine the reason for the failure. Correct the symbol in the rule definition, and reorder the table. If the return code or reason code is not listed, the error is an internal error, and you should notify BMC Customer Support.

Error Code (rc)	Reason Code (rsn)	Explanation
04		GETMAIN or FREEMAIN error.
	1 through 6	GETMAIN failure
	7 through 10	FREEMAIN failure
08		Variable not found.
	13	Variable not found and RESOLVE flag is on
	36	%%COMMSYS value length error
	68	%%TIMEINT first argument is not a valid date
	69	%%TIMEINT second argument is not a valid date
	74	%%X2C argument length is greater than 4
	88	%%DOLIMIT first argument is not numeric
	89	%%RULE functions argument is out of rule stack
	90	%%RULE functions argument is not numeric
	98	Global variable pool not found
	980	Internal error - global pool or database not found
	982	Internal error - global pool or database not found
12		Syntax error or General error.
	11	Empty SET command
	15	Empty IF command
	21	%% not found in SET command
	22	Separator not found after %%
	23	‘=’ not found in SET command
	24	%%$TIMEOUT value not numeric
	25	%%$RESPMSG/TIMEOUT - invalid parentheses
	26	%%$RESPMSG/%%TIMEOUT - too ?pmany values
	27	%%$WAITKSL/TSO/CMD - invalid value (not YES/NO)
	28	%%TIMEOUT - value too large
	29	%%STATID value length error
	30	%%AUTOLOG value length error
	37	%%AUTOSYS value length error
	41	Function arguments not separated
	42	Too few function arguments
	45	CTMLINE# PARAMETER NOT NUMERIC when trying to set %%CTMLINE# to a non-numeric value
	46	CTMLINE# > CTMLINES when trying to set %%CTMLINE# to a value greater than %%CTMLINES
	47	CTMLINE# < 0 when trying to set %%CTMLINE# to a value less than 0
	52	%%$SUBSTR 2nd argument not numeric
	53	%%$SUBSTR 3rd argument not numeric
	54	%%$SUBSTR 2nd argument out of range
	55	%%$SUBSTR 3rd argument out of range
	56	%%$RESOLVE argument not recognized
	57	%%$RANGE 1st argument not numeric
	58	%%$RANGE 2nd argument not numeric
	59	%%$RANGE 1st argument out of range
	60	%%$RANGE 2nd argument out of range
	61	%%$RANGE is too narrow
	62	%%$CALCDATE 1st argument not in valid format
	63	%%$CALCDATE 2nd argument not in valid format
	64	%%$TIMEINT 1st argument is not 11 digits in length
	65	%%$TIMEINT 1st argument is not numeric
	66	%%$TIMEINT 2nd argument is not 11 digits
	67	%%$TIMEINT 2nd argument is not numeric
	71	More than one operator in one line
	72	Less than two operands for an operator
	73	More than two operands for an operator
	75	%%$D2X argument length is greater than 10
	76	%%$D2X argument is not numeric
	77	%%$D2X argument number is greater than 2147483647 (2G)
	78	%%$X2D argument length is greater than 8
	79	%%$X2D argument has an invalid character
	81	First operand in arithmetic operation is not numeric
	82	Second operand in arithmetic operation is not numeric
	83	%%$DIV 2nd operand is 0
	84	First operand is greater than 2G
	85	Second operand is greater than 2G
	86	Result of %%$PLUS case overflow
	87	Result of %%$MINUS case overflow
	91	Logical operand not numeric
	92	Numeric logical operand out of range
	93	Invalid logical operator
	94	Logical atomic expression expected but not found
	95	Unbalanced parentheses in logical expression
	96	Too many nested parentheses in logical expression
	97	Unbalanced quotes
	99	%%$GLOBAL value length error
16		Errors reading the global member.
	08	Insufficient memory
	12	Member not found
	16	DSN is not a library
	20	DSN is not fixed
	24	LRECL is not 80
	28	Data set in use
	36	Data set not in catalog
	40	Dynamic allocation failed
	52	Error when opening/processing a directory
	56	An abend was intercepted
20		Errors writing the global member.
	08	Insufficient memory
	12	Member not found
	16	DSN is not a library
	20	DSN is not fixed
	24	LRECL is not 80
	28	Data set in use
	36	Data set not in catalog
	40	Dynamic allocation failed
	52	Error when opening/processing a directory
	56	An abend was intercepted
24		Program Buffers Shortage.
	12	Not enough space in RSL buffer
	32	Not enough space in VCB for name and value. Variable name and data are too long.
	43	Arguments too long (ARG buffer overflow)
32		Program Errors.
	100	No last non-blank for non-blank value in SET command
	101	No succeeding RSL for adjoining variables
	102	Problems in PUTVAR while initiating
	103	Too many arguments requested from PARSARGS
	104	Problems calculating weekday
	105	Invalid SET system variable
	106	No local anchor was passed
	107	No global anchor was passed
	109	No MCT or SWT present in %%$IPLDATE for date formatting WO0816*.
36, 40, 44		Global Variable Errors. Reason codes are:
	04	Empty chain
	08	End of chain
	12	PNXH header error
	16	PLBH header error.
	20	CTMMSK mash error, RC from IS is > 4
	24	Pool is protected
	32	Unable to get XAE information
	33	Machine is not participating on XAE
	98	Pool not found
	107	No global anchor was passed. Program error.
	108	Field not defined in database
	109	Requested row is out of range
48		Parse Errors.
	08	Invalid type
	12	Place holder error
	16	Position specification too long
	20	Non numeric
	24	Position null
	28	Invalid variable. Specified variable is greater than 256, or the variable name is too long
	32	String error
	36	Invalid TPE type
	40	Section vector overflow
	44	Variable buffer overflow
	107	No global anchor was passed

API576E IOA SUBSYSTEM `subsys` NOT RESPONDING TO REQUESTSLink copied to clipboard

Explanation: A request from the Control-O or CMEM monitor using the Control-O API failed due to timeout, but the subsystem is active.

The action is aborted.

Corrective Action: Check the status of the Control-O or CMEM monitor. If the timeout was the result of a termination process, the problem can be ignored. Otherwise, check for other error messages in the monitor JOBLOG, SYSPRINT or IOALOG, and respond accordingly.

API577E IOA SUBSYSTEM `subsys` INACTIVELink copied to clipboard

Explanation: A request from the Control-O or CMEM monitor failed, because the Control-O or CMEM monitor is not active.

The action is aborted.

Corrective Action: Start the Control-O or CMEM monitor and reissue the request.

API578E IOA SUBSYSTEM `subsys` DETECTED AN ERRORLink copied to clipboard

Explanation: A request from the Control-O or CMEM monitor failed, because the CTOWTO Control-O or CMEM executor module detected an error. The request was issued using the Control-O API.

The action is aborted.

Corrective Action: Check the Control-O or CMEM job log or syslog for error messages, and correct accordingly.

API579E IOA SUBSYSTEM `subsys` RETURNED AN INVALID RETURN CODELink copied to clipboard

Explanation: A request from the Control-O or CMEM monitor failed, because the CTOWTO Control-O or CMEM executor module returned an invalid return code. The request was issued by means of the Control-O API.

The action is aborted.

Corrective Action: Contact BMC Customer Support.

API57AE ERROR IN INAREA FIELDS ADDR= `add1, add2` LENGTH `len` DATA= `value`Link copied to clipboard

Explanation: An internal error occurred in the INAREA fields while calling an API service.

The action is aborted.

Corrective Action: Notify BMC Customer Support.

API57BE ERROR IN RESULT FIELDS ADDR= `add`, LENGTH `len` DATA= `value`Link copied to clipboard

Explanation: An internal error occurred in the RESULTS fields while calling an API service.

The action is aborted.

Corrective Action: Notify BMC Customer Support.

API57CE INAREA LENGTH `length3` + RESULT LENGTH `length2` > 255Link copied to clipboard

Explanation: Due to an internal error, the sum of the INAREA LENGTH and the RESULT LENGTH exceeded the maximum allowable data length of 255 characters when calling the API service.

The action is aborted.

Corrective Action: Notify BMC Customer Support.

API57EE CHECKPOINT GLOBAL VARIABLE DATABASE `dbName` ENDED DUE TO TIMEOUT AFTER `num` SECONDSLink copied to clipboard

Explanation: A timeout occurred during checkpoint processing of the Global Variables database. The checkpoint request terminated.

Corrective Action: Check the job log of the Control-O or CMEM monitor for additional messages that explain the cause of the problem. If the request ended OK after the timeout occurred, ignore the problem. Otherwise, respond accordingly.

ARC MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages ARCA00 through ARCAxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

ARCA01E CTDX004: ERROR IN CTMMEM RC=`rc` READING SKELETONLink copied to clipboard

Explanation: The restore skeleton that is used for restoring reports converted to Control-D from other products, such as: CA-View, CA Dispatch, and the like, cannot be read from the SKL library.

The restore request ends NOTOK.

Corrective Action: Proceed according to the CTMMEM return code displayed in the message. The CTMMEM return codes are described in the DOCIMEM member in the IOA DOC library. After correcting the action, request restore of the problematic report.

ARCA03E CTDX004: ERROR IN GETMAIN FOR SKELETONLink copied to clipboard

Explanation: There is insufficient memory to read the restore skeleton that is used for restoring reports converted to Control-D from other products, for example, CA-View, CA Dispatch.

The current restore request ends NOTOK.

Corrective Action: Increase the REGION size of the online environment.

ARCA04E CTDX004: UNABLE TO DYNAMICALLY ALLOCATE INTRDR `rc`Link copied to clipboard

Explanation: Dynamic allocation of the internal reader (INTRDR) by a Control-D command failed during an attempt to submit a restore job for reports converted to Control-D from other products such as CA-View, CA Dispatch.

In this message, rc is the return code of the failed dynamic allocation.

The restore job is not submitted. The current restore request ends NOT OK.

Corrective Action: Refer to the IBM manual that deals with information returned from an SVC 99. Take appropriate action based on the return code displayed in the message.

ARCA05E CTDX004: ERROR IN GETMAIN FOR SYSDATA RECORDLink copied to clipboard

Explanation: There is insufficient memory for the SYSDATA record that is needed to restore reports converted to Control-D from other products such as CA-View, CA Dispatch.

The current restore request ends NOTOK.

Corrective Action: Increase the REGION size of the Online environment.

BAO MessagesLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

Messages BAO500 through BAO5xxLink copied to clipboard

This group includes messages for the Control-M/Analyzer product.

BAO501I CTBBAO STARTEDLink copied to clipboard

Explanation: This information message signals the normal start of program CTBBAO. The Control-M/Analyzer Online Facility produces this message when it orders or forces a balancing mission to the Active Balancing file.

Corrective Action: No action is required.

BAO502S OPEN OF SCHEDULE DATA FAILED. DDNAME "DABAL"Link copied to clipboard

Explanation: Open of Control-M/Analyzer BALMIS library failed.

Possible causes are:

The DABAL DD statement is missing.
Either the data set referenced by the DAJOB DD statement cannot be opened for sequential read, or its record length is not 80.

The CTBBAO program ends with errors.

Corrective Action: Consult your INCONTROL administrator.

BAO505S PREVIOUS RUN OF CTBBAO DID NOT FINISH OKLink copied to clipboard

Explanation: A previous run of the CTBBAO program did not finish OK. This program is usually activated as part of the New Day procedure.

date_2 and date_3 (or date_4 and date_5) of the Date Control Record are not equal. Possible causes are:

The previous run of the CTBBAO program did not finish OK.
The contents of the User Date Control Record (the DACHK DD statement) have been manually modified.

The CTBBAO program ends with errors.

Corrective Action: Set date_3 (or date_5), positions 25 through 30 (or 50 through 55) in the Date Control Record (the DACHKK DD statement), to the values of date_2 (or date_4). To rerun the same New Day procedure, change all the dates to the value of the previous day.

When rerunning the New Day procedure, do not order the same mission twice on the same day. First delete previously ordered missions from the Active Balancing file, and then rerun the New Day procedure.

BAO510S SEVERE ERROR IN THE BALANCING DATA. PLEASE NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: A severe error was detected in the scheduling data. This message is issued by the New Day procedure. This message is produced when any scheduling mission (pointed to by the DABAL DD statement) contains erroneous data.

Possible causes are:

The contents of the mission were incorrectly modified, using an editor or program, and the format of the mission is invalid.
There was an internal error in Control-M/Analyzer.

The New Day procedure terminates with a condition of code 08.

Corrective Action: Do the following:

Try to restore the mission to its original state. If you cannot, have your IOA administrator call BMC Customer Support.
If the mission is a batch New Day procedure using a permanent Date Control Record, correct the contents of the Date Control record before running the New Day procedure again.
For more information, see the BAO505S message.

BAO511I ID= `orderId` TASK= `taskName` PLACED ON THE ACTIVE BALANCING FILE - `desc`Link copied to clipboard

Explanation: This information message indicates that a mission order was placed on the Active Balancing file. The task is now on the Active Balancing file in Wait Schedule state.

Corrective Action: No action is required.

BAO513I SCHEDULE FAILED FOR `num` CONTROL-M/ANALYZER CATEGORIESLink copied to clipboard

Explanation: This information message displays the number of Control-M/Analyzer balancing missions categories that were not found in the library allocated to the DABAL DD statement.

In this message, num is the number of balancing missions categories that were not found.

The Control-M/Analyzer New Day procedure continues processing.

Corrective Action: Examine the IOA Log file for the failed categories and associated reasons for failure.

BAO514S INSUFFICIENT STORAGE FOR THE BALANCING MISSIONLink copied to clipboard

Explanation: There is insufficient storage for processing the mission order.

The CTBBAO program of the New Day procedure terminates with a condition code of 08.

Corrective Action: Increase the REGION size of the New Day procedure.

BAO515S ERROR IN SCHEDULING DATA - TOO MANY STATEMENTS FOR ONE MISSIONLink copied to clipboard

Explanation: The scheduling mission contains too many statements. Scheduling data describing the mission order is too large to be processed by Control-M/Analyzer.

The mission order is not placed on the Active Balancing file. The New Day procedure terminates with a condition code of 08.

Corrective Action: Check the contents of the mission order using the Online Scheduling Facility and omit unnecessary scheduling data. Report this to your INCONTROL administrator.

BAO516S ERROR IN SCHEDULING DATA - FIRST STATEMENT SHOULD START WITH "B"Link copied to clipboard

Explanation: Invalid scheduling data was detected in the first data set pointed to by the DABAL DD statement. The first statement of a valid balancing mission should start with B.

The error could be due to one of the following:

The data set pointed to by the DABAL DD statement is not a Balancing Mission.
The Balancing Mission has been manually modified incorrectly.

The CTBBAO program ends with errors.

Corrective Action: Check that the DABAL DD statement refers to a valid Balancing Mission definition.

BAO524S CTBBAO ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTBBAO program ended with errors. It is activated as part of the New Day procedure.

The New Day procedure finishes executing with a condition code of 08. The IOA Log File contains one or more prior messages concerning the errors.

Corrective Action: Examine the IOA Log File for the errors. If necessary, correct the Date Control Record date-3 and date-5 manually for the next run of the New Day procedure.

BAO525I CTBBAO ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTBBAO terminating program, which is activated as part of the New Day procedure, has terminated.

Corrective Action: No action is required.

BAO528I MEMBER `memName` ID= `orderId` ODATE `odate` PLACED ON ACTIVE BALANCING FILE - `description`Link copied to clipboard

Explanation: This information message indicates that a mission order was placed on the Active Balancing file in WAIT SCHEDULE state.

Corrective Action: No action is required.

BAO532S OPEN OF CONTROL-M/ANALYZER ACTIVE BALANCING FILE FAILED. DDNAME “DAABF”Link copied to clipboard

Explanation: Open of Control-M/Analyzer Active Balancing file failed. This error message is issued by the CTBBAO program, which is usually activated as part of the New Day procedure.

Possible causes are:

The DAABF DD statement is missing.
The data set pointed to by the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.
The data set pointed to by the DAABF DD statement is a Control-M/Analyzer Active Balancing file from a different version of Control-M/Analyzer.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the mission or CLIST and rerun it.

BAO534S SEVERE ERROR ON CONTROL-M/ANALYZER ACTIVE BALANCING FILE. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Severe error on the Control-M/Analyzer Active Balancing file. This error message is issued by the CTBBAO program, which is usually activated as part of the New Day procedure.

Possible causes are:

An I/O error.
The file allocated to the DAABF DD statement is not the Control-M/Analyzer Active Balancing file.
The Active Balancing file has been corrupted.

The CTBBAO Control-M/Analyzer program ends with errors.

Corrective Action: Ask your IOA administrator to check whether the Active Balancing File has been updated from two computers without global ENQ control, or by an unauthorized program.

BAO535S CONTROL-M/ANALYZER ACTIVE BALANCING FILE IS BEING FORMATTED. TRY AGAIN LATERLink copied to clipboard

Explanation: The New Day procedure is currently formatting the Control-M/Analyzer Active Balancing file. This message is issued by the CTBBAO program which is usually activated as part of the New Day procedure.

Corrective Action: Try again later.

BAO536W THE CONTROL-M/ANALYZER ACTIVE BALANCING FILE IS NEARLY FULLLink copied to clipboard

Explanation: The Control-M/Analyzer Active Balancing file is over 90% full. It contains all the missions to be executed during the night. If it becomes full, it will be impossible to add new missions to Control-M/Analyzer for execution.

Corrective Action: Contact your INCONTROL administrator immediately. It may be necessary to compress the Active Balancing file, or to increase its size.

BAO537S INTERNAL ERROR IN ROUTINE CTBRSVLink copied to clipboard

Explanation: Internal error in the CTBRSV routine. The CTBBAO program ends with errors.

Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support.

BAO538S LOADING OF CONTROL-M/ANALYZER INSTALLATION PARAMETERS FAILEDLink copied to clipboard

Explanation: Loading of Control-M/Analyzer Installation Parameters, which are in the CTBPARM member in the IOA PARM library, failed.

Possible causes are:

There is insufficient memory to load the IOA Installation Parameters.
The CTBPARM member does not exist in the IOA PARM library.
The IOA PARM library was updated while you were working and the position of the CTBPARM member has changed.

The requested function is terminated.

Corrective Action: Look in the system log for additional related messages. Try one of the following:

If loading failed because of lack of memory: increase the REGION size for batch missions; for TSO, try to log on again using a larger SIZE parameter.
If you are using many IOA screens concurrently, try to exit a few using the END command. This releases memory used by the screens.
If the PARM library has been modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again.

BAO539S ERROR IN CONTROL-M/ANALYZER INSTALLATION PARAMETERS - INVALID DATETYPLink copied to clipboard

Explanation: Invalid DATETYP Control-M/Analyzer installation parameter. The DATETYP parameter specifies date format used at installation.

Valid values are:

A (mmddyy)
W (ddmmyy)
J (yymmdd)

For more information, see the operational parameters section in the IOA installation chapter in the INCONTROL for z/OS Installation Guide.

The requested function is terminated.

Corrective Action: Contact your INCONTROL administrator. Set the DATETYP parameter in the IOAPARM member to a valid value.

BAO540S CONTROL-M/ANALYZER ACTIVE BALANCING FILE IS FULL. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation:Highlighted, unrollable message.

The Control-M/Analyzer Active Balancing file is full. There is no more space in the Active Balancing file for new missions.

The mission order is not placed in the Active Balancing file.

Corrective Action: Contact your IOA administrator immediately. It may be necessary to increase its size. Compress the Active Balancing files.

BAT MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages BAT900 through BAT9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BAT9A3I BUILDING OF CONTROL-D ACTIVE TRANSFER FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDBAT program, which formats the Active Transfer file, started.

Corrective Action: No action is required.

BAT9A4I BUILDING OF CONTROL-D ACTIVE TRANSFER FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTDBAT program, which is used for formatting the Active Transfer file, has ended normally.

Corrective Action: No action is required.

BAT9A5S CONTROL-D ACTIVE TRANSFER FILE WAS NOT BUILLink copied to clipboard

Explanation: An error occurred during the formatting of the Active Transfer file (the CTDBAT program).

Formatting is terminated.

Corrective Action: Check the system log for a previous message regarding the error. Correct the problem, and reformat the file.

BAT9A6S OPEN OF CONTROL-D ACTIVE TRANSFER FILE FAILEDLink copied to clipboard

Explanation: The probable cause is a missing DAATF DD statement.

Formatting is terminated.

Corrective Action: Check and correct the DAATF DD statement.

BAT9A7S CONTROL-D ACTIVE TRANSFER FILE WRITE ERRORLink copied to clipboard

Explanation: The format routine received an I/O error when accessing the Active Transfer file. An I/O error was encountered by the CTDBAT program when accessing the Active Transfer file.

Possible causes are:

A hardware failure may have occurred.
The Active Transfer file specification contains invalid parameters.

Formatting is terminated.

Corrective Action: Do one of the following:

After the hardware problem has been resolved, reformat the file.
Check and correct the DCB parameters specified in the DAATF DD statement, then reformat the file.

BAT9A8S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: The IOA Log file is unavailable for processing.

Formatting is terminated.

Corrective Action: Check and correct the DALOG DD statement, then reformat the Active Transfer file.

BAT9A9S NUMBER OF RECORDS IN ACTIVE TRANSFER FILE IS LESS THAN 3Link copied to clipboard

Explanation: The CTDBAT program determines the number of records for the Active Transfer file from the ATFBLK installation parameter in the CTDPARM member. This value cannot be less than 3.

Formatting is terminated.

Corrective Action: Correct the CTDPARM member, then reformat the Active Transfer file.

BCL MessagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages BCL300 through BCL3xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

BCL306S ERROR WHILE READING PARAMETERS - CALENDAR NOT BUILTLink copied to clipboard

Explanation: There was an error in the parameters for the IOABLCAL utility, or no parameters were specified.

The IOABLCAL utility returns a condition code of 12. The calendar is not built.

Corrective Action: Correct the parameters and rerun the utility.

BCL307S INVALID SYNTAX IN THE PARAMETER CARD - CALENDAR NOT BUILTLink copied to clipboard

Explanation: There was an error in the parameters for the IOABLCAL utility, or no parameters were specified.

The IOABLCAL utility returns a condition code of 12. The calendar is not built.

Corrective Action: Correct the parameters and rerun the utility.

BCL308S INVALID/MISSING OPERATOR - CALENDAR NOT BUILTLink copied to clipboard

Explanation: An operator is missing between the calendars.

Valid operators for the IOABLCAL utility are:

+ (plus)
- (minus)
* (asterisk)

The IOABLCAL utility returns a condition code of 12. The calendar is not built.

Corrective Action: Correct the parameters and rerun the utility.

BCL309S CALENDAR `calName` DOES NOT CONTAIN THE YEAR `yr`Link copied to clipboard

Explanation: The yr year does not appear in the second calendar (calName), but it appears in the first calendar in the IOABLCAL utility. All years that are defined in one calendar must be defined in the other calendar as well.

The variables in this message are:

calName - the name of the second calendar that does not contain yr
yr - the year that does not appear in calName

The IOABLCAL utility returns a condition code of 12. The calendar is not built.

Corrective Action: Either add the year to the second calendar, or delete unnecessary years from the first calendar.

BCL311S MEMBER `memName` IS NOT A VALID CALENDARLink copied to clipboard

Explanation: The specified member (memName) is not a calendar in the IOABLCAL utility.

The IOABLCAL utility returns a condition code of 08. The calendar is not built.

Corrective Action: Specify a valid calendar name.

BCL312I CALENDAR `calName` HAS BEEN BUILT AND SAVEDLink copied to clipboard

Explanation: This information message indicates that the IOABLCAL utility has successfully built the calendar.

Corrective Action: No action is required.

BCL313S BUILDING A CALENDAR ENDED WITH ERRORSLink copied to clipboard

Explanation: An error occurred during the execution of the IOABLCAL utility.

Corrective Action: A previous message should describe the error.

BCL314E RELATIVE CALENDAR CAN APPEAR ONLY AS THE SECOND CALENDARLink copied to clipboard

Explanation: The calendar specified as the first in a calculation formula in the IOABLCAL utility is a relative calendar.

The IOABLCAL utility returns a condition code of 08. The calendar is not built.

Corrective Action: Correct the calendar calculation formula.

BCL315E CALENDAR2 MUST HAVE SAME NUMBER OF YEARS AS CALENDAR1Link copied to clipboard

Explanation: A shift operation was specified (, W, W,), but calendar_1 and calendar_2 both contain the same years in chronological order.

The calendar is not built. The IOABLCAL utility returns a condition code of 12.

Corrective Action: Adjust both calendars so that they contain the same years in chronological order.

BKC MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages BKC400 through BKC4xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BKC490I CHECKING OF RESULTS OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime`Link copied to clipboard

Explanation: This information message indicates that the backup (migration) mission began checking of the results of the backup (migration) utility run.

The variables in this message are:

misName - the name of the backup or migration mission
modate - the original scheduling date of the backup or migration mission
misTime - the time stamp of the backup or migration mission

Corrective Action: No action is required.

BKC491E INVALID PARAMETERS FOR BACKUP/MIGRATION ANALYZE PROGRAMLink copied to clipboard

Explanation: An invalid parameter is specified in the ANALYZE job step of the generated backup (migration) job.

This may occur because the backup (migration) job skeleton was incorrectly modified by a user.

The backup (migration) mission ends NOTOK.

Corrective Action: Call your INCONTROL Administrator.

BKC492W MISSING VOLUME SERIAL NUMBERS FOR DDNAME "TAPE"Link copied to clipboard

Explanation: The backup job could not find the volume serial numbers (volsers) of the backup tapes. The first step of the backup job backs up the compressed data sets on tapes specified by the DD name TAPE. The second step of the backup job executes the CTDBKC program, which analyzes the output of the backup process. The second step failed to retrieve volume serial numbers from the JFCB control block The volser is required for subsequent restores.

Possible causes are:

The user-tailored JCL of the backup job may contain errors.
An error occurred during processing of the first step.
The site backup and restore facility does not use standard label tapes. This is not an error situation.

For information about the correct JCL, refer to the section on backup mission management in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If there is an error in the JCL of the backup job, correct the JCL skeleton and rerun the backup job. If an error occurred during processing of the first step of the job, refer to earlier messages generated by the first step, correct the problem, and rerun the job.

BKC493E CDAM FILE WAS NOT BACKED UP: `dsname` BY MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime`Link copied to clipboard

Explanation: The backup utility is unable to backup the dsname data set.

The variables in this message are:

dsname - the data set name
misName - the name of the backup mission
modate - the original scheduling date of the backup mission
misTime - the time stamp of the backup mission

Possible causes are:

The data set may have been deleted or uncataloged.
An I/O error was encountered when backing up the data set.

The backup mission ends NOTOK.

Corrective Action: Check the output of the backup utility.

BKC494E OPEN OF BACKUP/MIGRATE UTILITY MESSAGES FILE FAILEDLink copied to clipboard

Explanation: The open of the SYSIN DD statement failed. This message is produced by the ANALYZE step of the backup or migration job.

Possible causes are:

The SYSIN DD statement has been deleted or its JCL has been modified incorrectly.
The data set referenced by the SYSIN DD statement cannot be opened for sequential read.

The requested backup or migration is not performed. The status of the Backup or Migration Mission is changed to ENDED NOTOK.

Corrective Action: Do the following:

Check the ANALYZE step of the backup or migration job in the library referenced by the DADSKL DD statement.
For the correct format for SYSIN JCL, see the BKPDFDSS sample skeleton job in the Control-D or Control-V SKL library.
Modify the JCL as required.
Rerun the Backup or Migration Mission.

BKC495E NO PENDING BACKUP/MIGRATION MISSION FOUND BY BKPRESET IN ACTIVE MISSION FILELink copied to clipboard

Explanation: This message indicates that BKPRESET utility did not find any pending backup or migration mission in the Active User file.

The utility resets status of all SYSDATA records pending in backup to WAITING FOR BACKUP.

Corrective Action: No action is required.

BKC496E OPEN OF ACTIVE MISSIONS FILE FAILED. DDNAME "DAAMF"Link copied to clipboard

Explanation: Open of the Active Missions file failed. This file is referenced by the DAAMF DD statement. This message is produced by the ANALYZE step of the backup or migration job. This step executes the CTDBKC program, which analyzes the output of the backup or migration process.

Possible causes are:

The DAAMF DD statement is missing.
The data set referenced by the DAAMF DD statement is not the Active Missions file.
The data set referenced by the DAAMF DD statement is the Active Missions file for another Control-D or Control-V monitor or a different version of Control-D or Control-V.

Backup or migration of the requested data sets is not performed. The status of the backup or migration mission remains BACKUP or MIGRATE IN PROCESS. This status will change to ENDED OK after the backup or migration job is corrected and rerun.

Corrective Action: Do the following:

Check the ANALYZE step of the backup or migration job in the library referenced by the DADJOB DD statement.
Modify or add the DAAMF DD statement.
Rerun the job.
To prevent a recurrence of this problem, make the same modification to the backup or migration skeleton JCL in the library referenced by the DADSKL DD statement.

BKC497E UNABLE TO UPDATE STATUS OF MISSION `misName` ODATE= `misoDate` TIMESTAMP= `misTime` (RC= `rc`)Link copied to clipboard

Explanation: where rc is the return code of the Active Mission file service.

Backup or migration job cannot update, in the Active Mission file, the status of the mission indicated in the message.

The mission remains in status IN PROCESS.

Corrective Action: Use the appropriate utility (BKPRESET or MIGRESET) to reset the mission status. If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.

BKC498I RESULT OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` IS OKLink copied to clipboard

Explanation: This information message indicates that the backup (migration) mission has finished successfully.

The variables in this message are:

misName - the name of the backup (migration) mission
modate - the original scheduling date of the backup (migration) mission
misTime - the time stamp of the backup (migration) mission

Corrective Action: No action is required.

BKC499E RESULT OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` IS NOT OKLink copied to clipboard

Explanation: This message indicates that an error was encountered in the backup (migration) mission execution. The detailed description of the error is given in the previous printed messages.

The variables in this message are:

misName - the name of the backup (migration) mission
modate - the original scheduling date of the backup (migration) mission
misTime - the time stamp of the backup (migration) mission

The backup (migration) mission ends NOTOK.

Corrective Action: Check the report of mission execution in the IOALOG and in the output of the backup (migration) job.

BKC49BE CDAM FILE WAS NOT MIGRATED : `dsname` BY MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime`Link copied to clipboard

Explanation: The migration utility was unable to migrate the dsname data set.

The variables in this message are:

dsname - the data set name
misName - the name of the migration mission
modate - the original scheduling date of the migration mission
misTime - the time stamp of the migration mission

Possible causes are:

The data set may have been deleted or uncataloged.
An I/O error was encountered when migrating the data set.

The migration mission ends NOTOK.

Corrective Action: Check the output of the migration utility.

BKC49CE INDEX FILE WAS NOT MIGRATED : `dsname` BY MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime`Link copied to clipboard

Explanation: The migration utility was unable to migrate the dsname data set.

The variables in this message are:

dsname - the data set name
misName - the name of the migration mission
modate - the original scheduling date of the migration mission
misTime - the time stamp of the migration mission

Possible causes are:

The data set may have been deleted or uncataloged.
An I/O error was encountered when migrating the data set.

The migration mission ends NOTOK.

Corrective Action: Check the output of the migration utility.

BKC49DS INVALID THIRD PARAMETER WAS SUPPLIED IN PARM FOR ANALYZE.PRIMARY OR SECONDARY MUST BE SPECIFIEDLink copied to clipboard

Explanation: During a generated migrating reports job, an invalid parameter was found in the PARM field of the ANALYZE job step.

The reports migration fails.

Corrective Action: Call your INCONTROL administrator.

BKC49ES ERROR WHEN ISSUING CTDBKC ENQ. RC : `rc`Link copied to clipboard

Explanation: While backing up reports or performing a reports migration mission, an internal error occurred.

In this message, rc is the internal return code of the error.

The backing up or reports migration mission fails.

Corrective Action: Call your INCONTROL administrator.

BKC49FS MIGRATION JOB RERUN IS NOT ALLOWEDLink copied to clipboard

Explanation: This message is issued when the user tries resubmit the primary or secondary migration job from the CTD.JOB library after this job has already been run.

The migration job fails with a return code of 20.

Corrective Action: Check if the previous run of this job ended successfully.

If the job ended successfully, do not rerun this job but run the secondary job if this is primary or the primary job if this is secondary.
If the job has not ended successfully before and it is necessary rerun it, perform following steps:
Run the MIGRESET utility several times until the BKC495E message is issued.
Rerun the migration mission from the Active Missions screen.

BKC49GS SECONDARY RUN IS REQUIRED AND SECPREF= IS NOT DEFINED IN IOASPRMLink copied to clipboard

Explanation: This message identifies an internal error that occurred during a reports migration mission.

The reports migration mission fails.

Corrective Action: Call your INCONTROL administrator.

BKC49HE `mig_stag`e WAS NOT SUBMITTED - ERRORLink copied to clipboard

Explanation: An error occurred during a reports migration mission, and the mission failed.

In this message, mig_stage identifies the migration stage at which the mission failed. Valid values are:

PRIMARY
SECONDARY

Corrective Action: Call your INCONTROL administrator.

BKC49JI `mig_stage` ENDED [NOT] OKLink copied to clipboard

Explanation: This information message indicates that a reports migration mission stage has ended.

In this message, mig_stage identifies the migration stage.

Valid values are:

PRIMARY
SECONDARY

Corrective Action: If the message indicates that the reports migration mission ended NOT OK, call your INCONTROL administrator.

BKC49KE INDEX FILE WAS NOT BACKED UP: `dsname` BY MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime`Link copied to clipboard

Explanation: The backup utility was unable to back up the dsname data set.

The variables in this message are:

dsname - the data set name
misName - the name of the backup mission
modate - the original scheduling date of the backup mission
misTime - the time stamp of the backup mission

Possible causes are:

The data set may have been deleted or uncataloged.
An I/O error was encountered when backing up the data set.

The backup mission ends NOTOK.

Corrective Action: Check the output of the backup utility.

BKC49ME NO PENDING MISSION WITH TIMESTAMP= `misTime` FOUND IN ACTIVE MISSION FILELink copied to clipboard

Explanation: This message indicates that the backup (migration) job did not find the related pending backup (migration) mission in the Active Mission file.

This may occur because the backup (migration) mission was removed from the Active Mission file or was reset by the BKPRESET utility before the job finished.

In this message, misTime is the time stamp of the backup (migration) mission.

The backup (migration) job only prints the LOG of the backup (migration) utility.

Corrective Action: Check the IOALOG.

BKC49NI {BACKUP | PRIMARY | SECONDARY} MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` IS RESETLink copied to clipboard

Explanation: This information message indicates that the BKPRESET utility successfully reset the backup (or primary migration or secondary migration) mission in the Active Mission file.

The variables in this message are:

misName - the name of the backup (migration) mission
modate - the original scheduling date of the backup (migration) mission
misTime - the time stamp of the backup (migration) mission

Corrective Action: No action is required.

BKC49PS DUE TO SEVERE ERROR POINTED ABOVE NEITHER SYSDATA NOR INDEX RECORD IS COPIED TO HISTORY/MIGRATION FILELink copied to clipboard

Explanation: Due to a severe error that occurred during the backup (migration) job execution, neither the SYSDATA nor INDEX record was copied to the History (Migration) User file.

This message is displayed with the previous messages in the backup (migration) job's output.

The backup (migration) job only prints the LOG of the backup (migration) utility.

Corrective Action: Check the output of the backup (migration) job.

BKC49QE UNABLE TO UPDATE STATUS OF MISSION `misName` ODATE= `misoDate` TIMESTAMP= `misTime` (UPDATE QUEUE OVERFLOW)Link copied to clipboard

Explanation: Backup or migration job cannot update, in the Active Mission file, the status of the mission indicated in the message because of overflow of the update queue in the Active Mission file service.

The mission remains in status IN PROCESS.

Corrective Action: Use the appropriate utility (BKPRESET or MIGRESET) to reset the mission status. If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.

BKP MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages BKP400 through BKP4xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BKP475I BACKUP/MIGRATE TASK STARTEDLink copied to clipboard

Explanation: This information message indicates that a backup or migration task is starting.

Corrective Action: No action is required.

BKP476I MISSION {STARTED | RESTARTED} WITH TIMESTAMP= `misTime`Link copied to clipboard

Explanation: This information message indicates which backup (migration) mission is starting or restarting, and its time stamp.

In this message, misTime is the identity of the backup (migration) mission that is starting or re-starting.

Corrective Action: No action is required.

BKP477E INSUFFICIENT STORAGE TO COMPLETE THIS `bkup/migrate` MISSIONLink copied to clipboard

Explanation: There is insufficient storage to complete the bkup/migrate backup or migration mission.

The status of this mission is set to ENDED NOTOK.

Corrective Action: Increase the REGION size for the Control-D or Control-V monitor and rerun the backup or migration mission. If the REGION size cannot be increased, make sure the backup or migration mission does not run concurrently with other missions. If the problem persists, contact your INCONTROL administrator.

BKP478I `bkup/migrate` MISSION ENDED OKLink copied to clipboard

Explanation: This information message indicates that a backup or migration mission finished executing with status ENDED OK.

In this message, bkup/migrate is the identity of the backup or migrate mission that has ended.

Corrective Action: No action is required.

BKP479E `bkup/migrate` MISSION ENDED NOT OKLink copied to clipboard

Explanation: This message indicates that a backup or migration mission finished executing with status ENDED NOTOK. The IOA Log file and the backup or migration job should contain one or more messages indicating the reason.

In this message, bkup/migrate is the identity of the backup or migrate mission that has ended.

Corrective Action: No action is required.

BKP47BI {BACKUP | PRIMARY | SECONDARY} `jobId` SUBMITTED WITH TIMESTAMP= `misTime`Link copied to clipboard

Explanation: This information message indicates that the backup (migration) job generated by the backup (migration) mission is submitted for execution.

The variables in this message are:

jobId - the system identifier of the submitted job.
misTime - the identity of the backup (migration) mission. It is copied to the generated job.

Corrective Action: No action is required.

BKP47CI {BACKUP | PRIMARY | SECONDARY} JOB PLACED IN CONTROL-D JOB LIBRARY WITH TIMESTAMP= `misTime`Link copied to clipboard

Explanation: This information message indicates that the backup (or the migration) job generated by the backup (or the migration) mission is placed to the Control-D JOB library.

In this message, misTime is the identity of the backup (migration) mission. It is copied to the generated job.

Corrective Action: No action is required.

BKP480E NO REPORTS TO BE BACKED UP/ MIGRATED BY THIS MISSIONLink copied to clipboard

Explanation: The Active User Report List file was searched for backup or migration requests. No backup or migration request with this mission name was waiting to be executed.

The status of this mission is set to ENDED NOTOK.

Corrective Action: No action is required.

BKP481E INVALID RETURN CODE `rc` FROM USER EXIT CTDX010 - `missionName` STOPPEDLink copied to clipboard

Explanation: The Control-D or Control-V exit CTDX010 ended with a return code of rc.

Possible values of rc are:

rc	Meaning
0	Submit the backup or migration job.
4	Do not submit the backup/migration job.

The status of this mission is set to ENDED NOTOK.

Corrective Action: Do the following:

Correct the problem in the CTDX010 exit.
Assemble and link-edit this exit.
Rerun the backup or migration mission. Control-V will call the new version of the exit automatically.

BKP482E INVALID RETURN CODE `rc` FROM CTMMEM - `missionName` STOPPEDLink copied to clipboard

Explanation: Control-D or Control-V received a return code of rc from the CTMMEM internal module, while trying to update the backup or migration job JCL library referenced by the DADJOB DD statement. The member name is the same as the name of the backup or migration mission.

The variables in this message are:

rc - the return code from the CTMMEM module
missionName - the identity of the problematic backup or migration mission

Possible return codes and their causes are:

Return Code	Meaning
12	DSN referenced by the DADJOB DD statement is not in the DADSKL member. This can occur when trying to read or write the data set.
16	DSN referenced by the DADJOB DD statement is not a partitioned data set.
20	DSN referenced by the DADJOB DD statement contains a record format which is not fixed.
24	DSN referenced by the DADJOB DD statement contains a record length which is not 80.
32	The DADJOB DD statement is missing.
36	DSN referenced by the DADJOB DD statement is not in the catalog.
56	Library referenced by the DADJOB DD statement is full or an abend occurred.

The status of this mission is set to ENDED NOTOK.

Corrective Action: Do the following:

Look for additional messages in the IOA Log file.
Correct the problem with the library.
Shut down Control-D or Control-V and reactivate it.
Rerun the backup or migration mission.

BKP483E INVALID RETURN CODE `rc` FROM CTDCND - `missionName` STOPPEDLink copied to clipboard

Explanation: Control-D or Control-V received the invalid return code rc from the CTDCND internal Control-D module while trying to add the %COND% prerequisite condition to the IOA Conditions file.

The variables in this message are:

rc - the return code from the CTDCND module
missionName - the identity of the problematic mission

The status of this mission is set to ENDED NOTOK.

Corrective Action: Note the return code (rc) and the mission name (missionName). Contact your INCONTROL administrator.

BKP484W ONLY `number` DATASETS WILL BE BACKED UP.Link copied to clipboard

Explanation: The number of data sets selected by the backup mission exceeded the maximum number of data sets that can be handled within one mission execution.

In this message, number is the specified number of data sets to be backed up.

Only number data sets will be backed up during the current mission execution.

Corrective Action: Order an additional appropriate backup mission (or order the same backup mission once again) to back up the remaining data sets.

BKP487S MIGRATION FILE WAS FORMATTED WITH INCORRECT COMPRESSION TABLELink copied to clipboard

Explanation: A migration file was opened for multistage migration, but the migration file was formatted with an old compression table.

A multistage migration mission stores log data about the last three migration stages in the SYSDATA record. If a migration file formatted with an old compression table is used, this data is lost.

The migration mission ends NOTOK.

Corrective Action: Do the following:

Use the CTDUFDUL job from the Control-D JCL library to unload the migration file.
Reformat the migration file.
Use the CTDUFRST job from the Control-D JCL library to reload the migration file.

BKP488W MIGRATION OF "`cdamName`" FROM OSS TO OSS REJECTEDLink copied to clipboard

Explanation: While building a migration mission, the Control-D monitor found a request to migrate a CDAM file from one OSS media to another OSS media, but this type of migration is not allowed.

In this message, cdamName is the identity of the CDAM file that was to be migrated.

The cdamName CDAM file is deleted from the list of CDAM files to be migrated.

Corrective Action: Change the migration path of the problematic migration mission.

BKP489I SHUT DOWN UPON REQUEST OF MAIN TASKLink copied to clipboard

Explanation: This information message indicates that the Control-D monitor is shutting down. The Control-D internal backup task is run upon request of the Control-D main task.

The Control-D monitor shuts down.

Corrective Action: No action is required.

BKP48AE `skelName` SKELETON MEMBER `missionName` NOT FOUND IN SKL LIBRARYLink copied to clipboard

Explanation: The specified backup or migration skeleton is not in the DADSKL member of the Control-D or Control-V monitor. For each backup and migration mission, a unique skeleton job (member) with the same name must exist in the DADSKL member.

The variables in this message are:

skelName - the identity of the problematic skeleton
missionName - the identity of the problematic mission

The problematic mission does not run.

Corrective Action: Rename the problematic mission, or create the required mission skeleton. Resubmit the mission.

BKP48BE CONTROL-D JOB LIBRARY FULL, COMPRESS THE JOB LIBRARY AND RERUN THE MISSIONLink copied to clipboard

Explanation: Control-D discovered that its JOB library was full when trying to backup, migrate or restore a file.

The file is not backed up, restored, or migrated.

Corrective Action: Compress the Control-D job library and rerun the backup, migrate, or restore mission.

BKP48CE BACKUP MISSION WAS CHANGED FROM GENERATION TO NUMBER OF DAYS TO KEEPLink copied to clipboard

Explanation: When running a backup job, the user changed the backup mission fields from NUMBER OF GENERATIONS TO KEEP to NUMBER OF DAYS TO KEEP. When at least one backup has been executed, the user cannot change the type of backup in this way.

The backup is not executed.

Corrective Action: Define a new backup mission specifying the NUMBER OF DAYS TO KEEP.

BKP48DE SECONDARY MIGRATION SKELETON `skel` WAS NOT SUBMITTED RC `rc` - MISSION CONTINUESLink copied to clipboard

Explanation: An error occurred during the generation of a secondary migration job.

More information about the error is provided in accompanying messages.

The variables in this message are:

skel - the name of the problematic migration job skeleton
rc - the return code of the error

The secondary migration job is not submitted.

Corrective Action: Call your INCONTROL administrator.

BKP48EE SECONDARY MIGRATION SKELETON `skel` DOES NOT CONTAIN %LEVEL% PARAMETERLink copied to clipboard

Explanation: The skeleton of a secondary migration mission job does not contain the mandatory %LEVEL% parameter.

In this message skel is the name of the problematic migration mission job skeleton.

The secondary migration mission job is not submitted.

Corrective Action: Call your INCONTROL administrator.

BKP48FE INVALID SKELETON MEMBER `skel`Link copied to clipboard

Explanation: A long line (more than 80 characters) is built by resolving variables in the skel skeleton member.

The problematic mission does not run.

Corrective Action: Fix the skeleton member and then resubmit the migration mission.

BKR MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages BKR300 through BKR3xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BKR340I BACKUP/MIGRATION RESET STARTEDLink copied to clipboard

Explanation: This information message indicates the start of the backup or migration reset process.

Corrective Action: No action is required.

BKR341E INVALID PARAMETERS FOR BACKUP/MIGRATION RESET PROGRAMLink copied to clipboard

Explanation: This message is issued by the backup/migration reset utility. An invalid parameter was specified for the utility.

A backup/migration reset is not performed.

Corrective Action: Correct the parameters in the backup/migration reset utility job, and rerun the job.

BKR342W BACKUP/MIGRATION JOB OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` IS RUNNING. THE MISSION WILL NOT BE RESET.Link copied to clipboard

Explanation: This message is issued by the backup/migration reset utility. The message warns that the indicated mission has reached the stage of checking the data sets’ backup/migration results, and the mission is therefore not affected by the utility.

The variables in this message are:

misName - the name of the backup/migration mission
modate - the original scheduling date of the backup/migration mission
misTime - the time stamp of the backup/migration mission

The backup/migration reset utility does not affect the indicated mission.

Corrective Action: Perform the appropriate action as described in the utility log.

BKR343E CDAM `dsname` OR A RELATED FILE HAS NOT BEEN BACKED UP BY MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime`Link copied to clipboard

Explanation: This message is issued by the backup/migration reset utility. The message indicates that the dsname CDAM file, or its related Control-V index file, has not been backed up by the indicated backup mission.

If the utility is running in RESET mode, it resets the backup status of the corresponding report to WAITING FOR BACKUP.

Corrective Action: Rerun the indicated mission.

BKR344I BACKUP/MIGRATION RESET ENDED WITH RC= `rc`Link copied to clipboard

Explanation: This information message indicates that the backup/migration reset utility has ended with a return code of rc. If the indicated return code is non-zero, the preceding messages explain the reason.

Corrective Action: Perform the appropriate action as noted in the preceding messages.

BKR345E NO PENDING MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` FOUND IN ACTIVE MISSION FILELink copied to clipboard

Explanation: This message is issued by the backup/migration reset utility when it is invoked with the MISNAME, MISTIME and MISODATE parameters, and the specified pending mission is not located in the Active Mission File.

A reset of the backup/migration is not performed.

Corrective Action: Correct the mission specification, and rerun the utility if needed.

BKR346E OPEN OF ACTIVE MISSIONS FILE FAILED. DDNAME=DAAMFLink copied to clipboard

Explanation: The backup/migration reset utility was unable to open the Active Mission File. The utility terminates execution.

Corrective Action: Check the messages in the utility log, and correct the situation accordingly.

BKR347E UNABLE TO UPDATE STATUS OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` (RC= `rc`)Link copied to clipboard

Explanation: This message is issued by the backup/migration reset utility. The message indicates that the utility was unable to reset the status of the indicated mission, due to an internal error.

Corrective Action: Processing of the indicated mission is skipped, and the utility continues processing the remaining missions. Contact your INCONTROL representative.

BKR348I RESULT OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` IS OKLink copied to clipboard

Explanation: This information message is issued by the backup/migration reset utility, and indicates that the utility found no report waiting for a completion of the indicated mission.

When running in RESET mode, the backup/migration utility sets the status of the indicated mission to ENDED OK.

Corrective Action: No action is required.

BKR349E RESULT OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` IS NOT OKLink copied to clipboard

Explanation: This message is issued by the backup/migration reset utility. The utility found a report waiting for completion of the indicated mission. The corresponding CDAM’s data set name is displayed in the preceding messages.

When running in RESET mode, the backup/migration reset utility sets the status of the indicated mission to ENDED NOTOK.

Corrective Action: Rerun the indicated mission.

BKR34AI MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` IS RESETLink copied to clipboard

Explanation: This information message is issued by the backup/migration reset utility while running in RESET mode. The message indicates that the status of the indicated mission is reset.

Corrective Action: Rerun the indicated mission if it ENDED NOTOK, or order another instance of the mission.

BKR34BE CDAM `dsname` OR A RELATED FILE HAS NOT BEEN PRIMARILY/ SECONDARILY MIGRATED BY MISSION `misName` TIMESTAMP= `misTime`Link copied to clipboard

Explanation: This message is issued by the backup/migration reset utility. The dsname CDAM file, or its related Control-V index file, has not been migrated by the indicated migration mission.

If the utility is running in RESET mode, it resets the status of the corresponding report to WAITING FOR MIGRATION.

Corrective Action: Rerun the indicated mission.

BKR34CE UNABLE TO UPDATE STATUS OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` (SECURITY VIOLATION)Link copied to clipboard

Explanation: This message is issued by the backup/migration reset utility. The utility was unable to update the status of the indicated mission in the Active Mission File due to security reasons.

The mission remains pending.

Corrective Action: Contact the security administrator to correct the problem, and then rerun the utility.

BKR34DI UNABLE TO UPDATE STATUS OF MISSION `misName` ODATE= `modate` TIMESTAMP= `misTime` (MISSION DELETED)Link copied to clipboard

Explanation: This information message is issued by the backup/migration reset utility. The utility was unable to update status of the indicated mission because the mission was deleted from the Active Mission File during the utility execution.

Corrective Action: Order another instance of the mission if its result is NOTOK.

BKR34EE ERROR IN PARAMETER MISNAMELink copied to clipboard

Explanation: This message is issued by the backup/migration reset utility when the MISNAME parameter is not specified or is specified incorrectly.

The backup/migration reset is not performed.

Corrective Action: Correct the MISNAME parameter’s specifications and rerun the utility.

BKR34FE ERROR IN PARAMETER MISTIMELink copied to clipboard

Explanation: This message is issued by the backup/migration reset utility when the MISTIME parameter is mandatory, but either it is not specified or it is specified incorrectly.

The backup/migration reset is not performed.

Corrective Action: Correct the MISTIME parameter’s specifications and rerun the utility.

BKR34GE ERROR IN PARAMETER MISODATELink copied to clipboard

Explanation: This message is issued by the backup/migration reset utility when the MISODATE parameter is mandatory, but either it is not specified or it is specified incorrectly.

The backup/migration reset is not performed.

Corrective Action: Correct the MISODATE parameter’s specifications and rerun the utility.

BKR34HI {BACKUP | MIGRATION} MISSION `misName` ODATE= `misoDate` TIMESTAMP= `misTime` IS ALLOWED FOR STARTLink copied to clipboard

Explanation: This information message is issued by the backup/migration reset utility. It means that the utility has detected the start of processing of the indicated mission, and will not affect it during the execution.

Corrective Action: No action is required.

BKR34SE UNABLE TO UPDATE STATUS OF MISSION `misName` ODATE= `misoDate` TIMESTAMP= `misTime` (UPDATE QUEUE OVERFLOW)Link copied to clipboard

Explanation: The BKPRESET or MIGRESET utility cannot reset the status of the mission indicated in the message because of overflow of the update queue in the Active Mission file service.

The mission remains in status IN PROCESS.

Corrective Action: Rerun the utility. If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.

BLD MessagesLink copied to clipboard

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.

Messages BLD900 through BLD9xxLink copied to clipboard

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.

BLD971S OPEN OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE FAILEDLink copied to clipboard

Explanation: Either the FORMCKP utility, which allocates and formats the Active Jobs file, or the FORMHST utility, which allocates and formats the Active History file, failed to open the file for formatting.

Possible causes are:

The DACKPT DD statement (for the Active Jobs file) is missing.
The DAHIST DD statement (for the History Jobs file) is missing.
There is insufficient memory for the job.

The utility ends with a condition code of 08.

Corrective Action: If a DD statement is missing, add the correct DD statement and rerun the job. If the problem is memory, specify a higher value for the REGION parameter.

BLD972I BUILDING OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of one of the following Control-M utilities:

the FORMCKP utility that allocates and formats the Active Jobs file
the FORMHST utility that allocates and formats the History Jobs file

Corrective Action: No action is required.

BLD973I BUILDING OF CONTROL-M {ACTIVE | HISTORY} JOBS FILE ENDEDLink copied to clipboard

Explanation: This information message indicates the normal termination of one of the following Control-M utilities:

the FORMCKP utility that allocates and formats the Active Jobs file
the FORMHST utility that allocates and formats the History Jobs file

Corrective Action: No action is required.

BLD974S CONTROL-M {ACTIVE | HISTORY} JOBS FILE WAS NOT BUILT.Link copied to clipboard

Explanation: Either the FORMCKP utility, which allocates and formats the Active Jobs file, or the FORMHST utility, which allocates and formats the Active History file, failed.

Corrective Action: Check the previous error messages which describe the type of error, and correct the problem accordingly.

BLD975S CONTROL-M {ACTIVE | HISTORY} JOBS FILE WRITE ERRORLink copied to clipboard

Explanation: An I/O error occurred while formatting the Control-M Active Jobs file or History Jobs file. This error may be caused by an incompatibility between the installation parameters, which are contained in CTMPARM, that define the Active Jobs file or the History Jobs file, and the JCL SPACE and DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters file.

BLD976S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: The FORMCKP utility, which is used to allocate and format the Active Jobs file, could not open the IOA Log.

Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is from a different version or a different IOA installation.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job. For more information about the FORMCKP utility, see the INCONTROL for z/OS Utilities Guide.

BLG MessagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages BLG900 through BLG9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

BLG961S IOA LOG FILE MUST CONTAIN MORE THAN 100 RECORDSLink copied to clipboard

Explanation: The value of the LOGSIZE IOA Installation Parameter is less than 100.

The utility stops executing with a condition code of 08.

Corrective Action: Do the following:

Enter the INCONTROL Installation and Customization Engine (ICE).
Redo the space calculation for the LOG file and save the parameters.
Rerun the utility.

BLG962S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: The Log file format program failed to open the file for formatting. A possible cause is that the DALOG DD statement is missing.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

BLG963S FORMATTING IOA LOG - WRITE I/O ERRORLink copied to clipboard

Explanation: An I/O error occurred while formatting the IOA Log file. This error may occur when there is incompatibility between the definition of the Log file in the Installation Parameters (IOAPARM) and the JCL SPACE and DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters.

BLG964I FORMATTING OF IOA LOG FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOA Log file format process has started.

Corrective Action: No action is required.

BLG965I FORMATTING OF IOA LOG FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOA Log file format process has terminated normally.

Corrective Action: No action is required.

BLG966S IOA LOG FILE WAS NOT BUILTLink copied to clipboard

Explanation: Formatting of the IOA Log file failed.

Corrective Action: Look in the job log or SYSPRINT for error messages that describe the type of error.

BLG967S IOA LOG FILE RECFM IS NOT F OR FBLink copied to clipboard

Explanation: The Record format parameter specified in the DALOG DD statement is not F (fixed) or FB (fixed blocked).

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

BLG968S IOA LOG FILE BLOCK SIZE MUST BE A MULTIPLE OF 200Link copied to clipboard

Explanation: The block size specified in the DALOG DD statement must be a multiple of 200, which is the Log file record length.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

BLG969S IOA LOG FILE ALLOCATION IS TOO SMALL. USE ICE TO CALCULATE THE IOA LOG FILE SIZELink copied to clipboard

Explanation: The space allocated for the IOA Log file cannot contain the number of records specified in the LOGSIZE IOA installation parameter.

The utility stops executing with a condition code of 08.

Corrective Action: Do the following:

Enter the INCONTROL Installation and Customization Engine (ICE).
Redo the space calculation for the LOG file and save the parameters.
Rerun the job with the new value calculated by ICE.

BLG96AW IOA LOG FILE IS TOO LARGE. ONLY `numBlocks` BLOCKS WILL BE FORMATTEDLink copied to clipboard

Explanation: The space allocated for the IOA Log file is greater than the space required to hold the number of records specified in the LOGSIZE IOA installation parameter.

In this message, numBlocks is the number of blocks that will be used.

The utility formats the file according to the LOGSIZE specification and ends with a condition code of 04. Some of the space in the file will not be used.

Corrective Action: To reformat the file with the correct space allocation, do the following:

Enter the INCONTROL Installation and Customization Engine (ICE).
Redo the space calculation for the LOG file and save the parameters.
Rerun the job with the new value calculated by ICE.

BLG96BS `serviceName` FAILED WITH RETURN CODE `rc` AND REASON CODE `rsn`Link copied to clipboard

Explanation: A service invoked by the Log format utility failed.

The variables in the message are:

serviceName - the name of the service.
rc - the return code returned by the service.
rsn - the reason code returned by the service.

The utility stops executing with a condition code of 08.

Corrective Action: Save the job’s SYSOUT and have your system programmer call your IOA representative for assistance.

BLG96CS IOA LOG FILE BLKSIZE MUST BE EQUAL TO LRECL WHEN RECFM=F IS USEDLink copied to clipboard

Explanation: The DCB attributes specified in the DALOG DD statement are incorrect.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job:

RECFM can be either F or FB
When RECFM=F, LRECL and BLKSIZE should be 200 or a multiple of 200.
When RECFM=FB, LRECL must be 200 and BLKSIZE must be a multiple of 200.

BLG96DS IOA LOG FILE LRECL MUST BE EQUAL TO 200 WHEN RECFM=FB IS USEDLink copied to clipboard

Explanation: The DCB attributes specified on the DALOG DD statement are incorrect.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job:

RECFM can be either F or FB
When RECFM=F, LRECL and BLKSIZE should be 200 or a multiple of 200.
When RECFM=FB, LRECL must be 200 and BLKSIZE must be a multiple of 200.

BLT MessagesLink copied to clipboard

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.

Messages BLT800 through BLT8xxLink copied to clipboard

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.

BLT893I CURRENT TABLE `tableName` LIBRARY `lib`Link copied to clipboard

Explanation: This information message is produced by the CTMBLT Control-M utility. It accompanies other messages that identify

the actual error condition
the data in the input stream that caused the error

The variables in this message are:

tableName - the name of the table in which the error occurred
lib - the name of the library in which the error occurred

Processing continues, and terminates with a nonzero return code.

Corrective Action: Correct the error and rerun the job.

BLT894I JOB =`jobName`Link copied to clipboard

Explanation: This information message is produced by the CTMBLT Control-M utility. It accompanies other messages that identify

the actual error condition
the data in the input stream that caused the error
In this message, jobName is the name of the job that was being processed when the error occurred. If no value is given for jobName, the problematic parameter may be job-independent, for example, a global or super-global parameter.

Processing continues, and terminates with a nonzero return code.

Corrective Action: Correct the error and rerun the job.

BLT895I JOB =`jobName`, KEYWORD=`keywd` (`reason`)Link copied to clipboard

Explanation: This information message is produced by the CTMBLT or CTMTLB Control-M utility. It usually accompanies other messages that identify

the actual error condition
the data in the input stream that caused the error

The variables in this message are:

jobName - the name of the job (MEMNAME) that was being processed when the error occurred
keywd - the problematic keyword parameter
reason - this can be one of the following values:
- For the CTMBLT utility, if GLOBAL appears in the message text, the keyword parameter is either a global or super-global parameter.
- For the CTMTLB utility, when NOSUPP appears in the message text, the field in the job scheduling definition designated by the keyword parameter is not supported when producing the XML file. The field may either be ignored by the utility or may require the user to modify the job scheduling definition. See the INCONTROL Utilities Guide and the User Response (below) for further information.

Processing continues, and terminates with a nonzero return code.

Corrective Action: Correct the error, if necessary, and rerun the job.

If the error is a result of executing one of the Control-M conversion tools, then the following scenario occurred: The conversion created a distributed job definition, but included in the definition a parameter which is not supported in the Control-M distributed platform.

For example, if the non-supported keyword is PREV_DAY, then the conversion determined that the job definition requires a SAC parameter (the equivalent of PREV_DAY on the mainframe platform) to properly schedule the job, because of a Control-M NEWDAY time that differs from midnight. However, the PREV_DAY parameter is not valid for distributed job definitions, so the user must either manually adjust the job's scheduling criteria or change the site's NEWDAY time and rerun the conversion.

BLT896I JOB=`jobName`, KEYWORD=`keywd` (GLOBAL), VALUE=`val`Link copied to clipboard

Explanation: This information message is produced by the CTMBLT Control-M utility. It accompanies other messages that identify

the actual error condition
the data in the input stream that caused the error

The variables in this message are:

jobName - the name of the job that was being processed when the error occurred
keywd - the problematic keyword parameter
val - the value that caused the error
GLOBAL - When GLOBAL appears in the text of the message, the keyword parameter is either a global or super-global parameter.

Processing continues, and terminates with a nonzero return code.

Corrective Action: Correct the error and rerun the job.

BLT897E MANDATORY PARAMETER `parm` IS MISSINGLink copied to clipboard

Explanation: A mandatory parameter statement (parm) is missing.

Processing continues, and terminates with a nonzero return code.

For ON-CAPTURE blocks, the message contains the following text:

PARAMETER INTO/SEARCH parm IS MISSING

Where parm is the value of the ON-CAPTURE parameter (block header ID or *END) that caused the previous block to be evaluated.

Note that "INTO/SEARCH" is an abbreviation for "CAPT-INTO or CAPT-SEARCH".

Corrective Action: Add the missing statement or statements, and rerun the job.

BLT898E KEYWORD= `keywd`, VALUE= `val` INVALIDLink copied to clipboard

Explanation: A CTMBLT utility keyword input statement is incorrect for one of the following reasons:

the keyword input statement does not specify a valid parameter
the value specified for val is too long
no value is specified for val
the value specified for val contains invalid characters

The values in this message are:

keywd - the problematic keyword input statement
val - the problematic value

The keywd keyword input statement is not processed. Processing continues and the utility ends with a return code of 08.

Corrective Action: Correct the keyword input statement and rerun the job.

BLT899E MISPLACED KEYWORD PARAMETER `keywd`Link copied to clipboard

Explanation: The keywd keyword parameter is incorrectly placed within the run stream of the CMTBLT Control-M utility control statement.

Many keyword parameters in CTMBLT control statements are location-sensitive, meaning that they must be placed in the correct position within the control statement.

This error is sometimes caused by a prior error.

Processing continues, and terminates with a nonzero return code.

Corrective Action: Correct the error and rerun the job.

BLT89AI TABLE `tableName action` IN LIBRARY lib BY `userId`Link copied to clipboard

Explanation: The CTMBLT or CTMTBUPD Control-M utility has added/replaced or updated the tableName table in the lib library. The action was performed by the userId user or job.

For the CTMBLT utility, ignore this message if it is displayed when both the following conditions exist:

a scheduling table is being ordered or forced
this scheduling table is not being saved into a scheduling library

This can occur, for example, if MEM-OVERWRITE is set to ORDER or FORCE.

For the CTMTBUPD utility, the table remains unchanged if the jobs selected in the table are not affected by the update criteria (for example, if the update criteria specifies IN or OUT but no IN or OUT condition in the job definitions match).

Corrective Action: No action is required.

BLT89BI TOTAL NUMBER OF TABLES PROCESSED= `num`Link copied to clipboard

Explanation: The CTMBLT or CTMTBUPD Control-M utility added or replaced num tables in the job scheduling library that was specified in the LIBRARY control statement (CTMBLT only) or the DASCHD DD statement.

For the CTMTBUPD utility, there are runs after which one or more of the replaced tables appear unchanged. For more information, see message BLT89AI.

Corrective Action: No action is required.

BLT89CW JOB SCHEDULING DEFINITION VERSION INCOMPATIBLE - MODEL VERSION USED.Link copied to clipboard

Explanation: In the CTMBLT utility, the MODEL parameter has specified a job scheduling definition which was created in a version earlier than the current version of Control-M. The utility creates the scheduling table using that earlier scheduling definition format of the job in the MODEL parameter. This might potentially cause corruption in the newly created scheduling table due to format differences.

The utility continues, but ends with a return code of 4.

Corrective Action: To prevent this error, ensure that all jobs specified in the MODEL parameter are in the current Control-M version format. To do so, run a combination of utility CTMTLB followed by CTMBLT on the the job scheduling table specified in the MODEL statement. See the INCONTROL for z/OS Utilities Guide, utility CTMTLB for details.

BLT89DI NO JOB DEFINITIONS SELECTED BY "SEL" CRITERIALink copied to clipboard

Explanation: In the CTMTBUPD utility, the SEL selection criteria did not cause any job definitions to be selected.

The job ends with a return code specified by the NOUPDRC control parameter (default 0).

Corrective Action: No action is necessary.

BLT89ES "EXCLUDE RBC" FEATURE NOT ENABLED - EXECUTION ABORTEDLink copied to clipboard

Explanation: During the execution of the CTMBLT utility, the creation of an ‘exclude RBC’ was attempted (RBC name beginning with the character ‘!’), but the parameter EXCLURBC in the CTMPARM member of the IOA PARM library was not set to Y.

CTMBLT terminates with a return code of 8.

Corrective Action: Update the EXCLRBC parameter and rerun the CTMBLT utility.

BLW MessagesLink copied to clipboard

This group includes messages for the Control-M for z/OS product.

Messages BLW000 through BLWxxxLink copied to clipboard

This group includes messages for the Control-M for z/OS product.

BLW000W WORKLOAD MEMBER: workload_member_name IS ENQED EXCLUSIVELY BY ANOTHER USERLink copied to clipboard

Explanation: The Workload Policies member is open or being used by another user. The CTMBLWK utility cannot read from it.

Corrective Action: Exit the member and exit the WL option in the Workload Management facility.

BLW001E THE UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: This general message notifies you that the CTMBLWK utility ended with errors.

Corrective Action: Review all messages that accompany this message for more information about the reasons that the utility ended with errors.

BLW002W WORKLOAD MEMBER: workload_member_name DOESN'T EXIST/IS EMPTYLink copied to clipboard

Explanation: The Workload Policies member does not exist in the specified location or does not contain any information.

Corrective Action: Find the correct location of the Workload Policies member and specify it correctly in the JCL that activates the utility. In addition, ensure that the member is not empty and contains valid values.

BLW003W PROBLEMS WHEN READING WORKLOAD MEMBER: workload_member_nameLink copied to clipboard

Explanation: Unexpected problems occurred when the CTMBLWK utility attempted to read from the Workload Policies member.

Corrective Action: Contact BMC Support.

BLW004W NOT ENOUGH MEMORY IN THE SYSTEMLink copied to clipboard

Explanation: A memory failure prevented the CTMBLWK utility from running.

Corrective Action: Free memory in the system and try running the utility again. If the problem persists, contact BMC Support.

BLW005W WORKLOAD MEMBER: workload_member_name IS CORRUPTEDLink copied to clipboard

Explanation: The Workload Policies member is corrupted.

Corrective Action: Restore the Workload Policies member to a valid version.

BLW006I WL POLICY: workload_member_name-WAS ADDED SUCCESSFULLYLink copied to clipboard

Explanation: This informative message notifies you that a Workload Policy was successfully added to the Workload Policies member.

Corrective Action: No action is required.

BLW007I WL POLICY: workload_member_name-WAS OVERRIDDEN SUCCESSFULLYLink copied to clipboard

Explanation: This informative message notifies you that a Workload Policy was successfully overridden in the Workload Policies member.

Corrective Action: No action is required.

BLW008I WL POLICY: workload_member_name-RULES WERE UPDATED SUCCESSFULLYLink copied to clipboard

Explanation: This informative message notifies you that Workload Policy rules were successfully overridden in the Workload Policies member.

Corrective Action: No action is required.

BLW009I TOTAL NUM. OF:UPDATED WL:number_updated,OVERRIDDEN WL: number_overridden,ADDED WL: number_addedLink copied to clipboard

Explanation: This informative message lists the total numbers of Workload Policies that were added, overridden, or had their rules updated by the CTMBLWK utility in the current run.

Corrective Action: No action is required.

BLW00AI THERE ARE SECURITY ISSUES - PLEASE MAKE SURE YOU ARE ALLOWED TO MODIFY THE WORKLOAD POLICIES MEMBERLink copied to clipboard

Explanation: Security issues were detected when the CTMBLWK utility attempted to modify the Workload Policies member.

Corrective Action: Ensure that you have the proper authorization to modify the Workload Policies member before you activate the CTMBLWK utility.

BLW00BE THE NEWLY RECEIVED ATTRIBUTES FOR WL POLICY: workload_member_name CAN'T BE APPLIED BECAUSE THE OVERRIDE PARAMETER SPECIFIES 'NO'Link copied to clipboard

Explanation: A logical problem was detected. You attempted to update an existing Workload Policy, but the OVERRIDE parameter is set to N (No). The CTMBLWK utility cannot proceed.

Corrective Action: If you want to update this Workload Policy, set the OVERRIDE input parameter to Y (full override) or U (update of policy rules). Alternatively, remove this Workload Policy from the input.

BLW011E WL POLICY workloadName FIELD fieldname INVALID LENGTH OF valueinp SHOULD BE valueexp CHARS LONG.Link copied to clipboard

Explanation: The CTMBLWK utility detected an invalid value length in one of the fields (parameters) in the Workload Policy that you are attempting to build.

Corrective Action: Correct the value of the specified field in the Workload Policy.

BLW012E WL POLICY workloadName FIELD fieldname INVALID SYNTAX/FORMAT FOR VALUE valueLink copied to clipboard

Explanation: The CTMBLWK utility detected invalid syntax in one of the fields (parameters) in the Workload Policy that you are attempting to build.

Corrective Action: Correct the value of the specified field in the Workload Policy.

BLW013E WL POLICY workloadName HAS A SEPARATE TYPE RULE THAT CONTAINS A NON-EXISTING REFERENCED WORKLOAD POLICY.Link copied to clipboard

Explanation: This error message indicates that there is a Workload Policy rule of type S (Separate Execution) that references a non-existent Workload Policy name within a SEPOST parameter. This message is issued by the CTMBLWK utility during the build of a new workload policy.

Corrective Action: Ensure that all SEPOST parameters within the specified Workload Policy reference existing Workload Policies.

BLW014E WL POLICY workloadName REFERENCES ITSELFLink copied to clipboard

Explanation: This error message indicates that there is a Workload Policy rule of type S (Separate Execution) that references itself within a SEPOST parameter. This message is issued by the CTMBLWK utility during the build of a new Workload Policy.

Corrective Action: Remove the SEPOST parameter that contains the incorrect reference to the specified Workload Policy.

BLW015E INTERNAL ERROR WITH REASON CODE XXXX.Link copied to clipboard

Explanation: The CTMBLWKD routine of the CTMBLWK utility encountered an internal error.

Corrective Action: Contact BMC Customer Support.

BLW020E PROGRAM START FAILURE - reasonLink copied to clipboard

Explanation: A basic component of the CTMBLWK utility could not load/initialize during an attempt to build a new Workload Policy.

Corrective Action: Try to activate the utility again. If the problem persists, contact BMC Support.

BLW021E MEMORY ALLOCATION FAILURELink copied to clipboard

Explanation: The CTMBLWK utility could not allocate sufficient memory during an attempt to build a new Workload Policy. The program terminated.

Corrective Action: Try to activate again. If the problem persists, contact BMC Support.

BLW022E INPUT FILE ERROR - reasonLink copied to clipboard

Explanation: The CTMBLWK utility could not open the input file during an attempt to build a new Workload Policy, or the input file was empty.

Corrective Action: Verify that the input file exists and contains valid data, and reactivate the utility.

BLW023E INVALID VALUE IN WORKLOAD POLICY: workloadName, IN KEY: keyName - reasonLink copied to clipboard

Explanation: This message is issued by the CTMBLWK utility during the build of a new Workload Policy. More information about the nature of the error appears in the reason of the message.

Corrective Action: Review the reason indicated in the message and correct the value of the keyword accordingly.

BLW024E INPUT ERROR IN WORKLOAD POLICY: workloadName - reasonLink copied to clipboard

Explanation: This message is issued by the CTMBLWK utility during the build of a new Workload Policy. More information about the nature of the error appears in the reason of the message.

Corrective Action: Correct the problem in the input parameters of the specified Workload Policy according to the reason provided in the message.

BLW025E SEPARATE LOGICAL ERROR IN WORKLOAD POLICY: workloadName - reasonLink copied to clipboard

Explanation: The CTMBLWK utility encountered a logical problem in a Separate Execution rule in the specified Workload Policy during the build of a new Workload Policy.

Corrective Action: Correct the problem in the rule, as indicated in the provided reason.

BLW026E INVALID VALUE LENGTH IN WORKLOAD POLICY: workloadName, IN KEY: keyName - VALUE LENGTH EXCEEDS MAXIMUM LENGTH OF: valueLengthLink copied to clipboard

Explanation: The CTMBLWK utility detected an invalid field length in one of the fields (parameters) in the Workload Policy that you are attempting to build.

Corrective Action: Correct the value of the specified field in the Workload Policy.

BLW027E DUPLICATE VALUE ERROR IN WORKLOAD POLICY: workloadName - reasonLink copied to clipboard

Explanation: The CTMBLWK utility detected one of the following errors during the build of a new workload Policy:

The Workload Policy has a non-unique name.
The same date was specified more than once by SDATES parameters.
A Separate Execution rule references the same Workload Policy more than once in SEPOST parameters.

Corrective Action: Remove the duplicate values, as indicated.

BLW028E SYNTAX ERROR IN WORKLOAD POLICY: workloadName | inputRecord - reasonLink copied to clipboard

Explanation: The CTMBLWK utility detected a syntax error in the Workload Policy that you are attempting to build.

Corrective Action: Correct the syntax error according to the information provided in the reason.

BLW029E INVALID KEY IN WORKLOAD POLICY: workloadName , KEY: keyName - reasonLink copied to clipboard

Explanation: The CTMBLWK utility detected one of the following errors in the specified key (parameter) during the build of a new workload Policy:

An invalid parameter was specified.
A parameter was defined in the wrong place in the input.
A mandatory parameter is missing.

Corrective Action: Correct the utility input, as indicated.

BLW02AI WORKLOAD POLICY workloadName WAS MODIFIED, A SEPARATE RULE WAS ADDED WITH R.SEPOST OF workloadName TO COMPLEMENT OTHER WORKLOAD POLICIESLink copied to clipboard

Explanation: This information message notifies you that the CTMBLWK utility added an inferred R.SEPOST parameter to a Separate Execution rule during the build of a new workload Policy.

Corrective Action: No action is required.

BMS MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages BMS900 through BMS9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BMS971S OPEN OF CONTROL-D ACTIVE MISSIONS FILE FAILEDLink copied to clipboard

Explanation: The CTDFRAMS Control-D utility, which is used to allocate and format the Active Missions file, failed to open the file for formatting.

Possible causes are:

The DAAMF DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

BMS972I BUILDING OF CONTROL-D ACTIVE MISSIONS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDFRAMS utility, which allocates and formats the Active Missions file, has started.

Corrective Action: No action is required.

BMS973I BUILDING OF CONTROL-D ACTIVE MISSIONS FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTDFRAMS utility, which allocates and formats the Active Missions file, has ended normally.

Corrective Action: No action is required.

BMS974S CONTROL-D ACTIVE MISSIONS FILE WAS NOT BUILTLink copied to clipboard

Explanation: The CTDFRAMS utility failed.

Corrective Action: Look for additional clarification messages on the IOA Log.

BMS975S CONTROL-D ACTIVE MISSIONS FILE WRITE ERRORLink copied to clipboard

Explanation: I/O error while formatting the Control-D Active Missions file.

This error may occur when there is incompatibility between the definition of the Active Missions file in one or more of the following:

the installation parameters (CTDPARM)
the JCL SPACE parameter
the DCB parameters

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the installation parameters.

BMS976S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: The CTDFRAMS utility, which is used to allocate and format the Active Missions file, could not open the IOA Log.

Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is from a different version or a different IOA installation.
The IOAFRLOG utility, which allocates and formats the IOA Log, has not yet been run, or did not finish executing normally.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

BNR MessagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages BNR900 through BNR9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

BNR941S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: The CTMFRNRS utility, which allocates and formats a new Conditions file, could not open the IOA Log.

Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA monitor.
The CTMFRLOG utility that allocates and formats the IOA Log was not yet run or did not finish executing normally.

The utility stops executing with a condition code of 08.

Corrective Action: Do one of the following:

Correct the JCL and rerun the job.
If the IOA Log is not yet formatted, run the CTMFRLOG utility, then rerun the job.

BNR943S OPEN OF IOA MANUAL CONDITIONS SYNCHRONIZATION FILE FAILEDLink copied to clipboard

Explanation: The IOAFRNRS utility, which is used to allocate and format the file, failed to open the file for formatting.

Possible causes are:

The DACKPT DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL, and rerun the job.

BNR944I BUILDING OF IOA MANUAL CONDITIONS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOAFRNRS utility started.

The IOAFRNRS utility allocates and formats the Manual Conditions file.

Corrective Action: No action is required.

BNR945I BUILDING OF IOA MANUAL CONDITIONS FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOAFRNRS utility, which allocates and formats the Manual Conditions file, ended normally.

Corrective Action: No action is required.

BNR946S IOA MANUAL CONDITIONS FILE WAS NOT BUILTLink copied to clipboard

Explanation: The IOAFRNRS utility failed.

Corrective Action: Look for previous error messages which will describe the type of the error.

BRS MessagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages BRS900 through BRS9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

BRS981S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: The IOAFRRES utility, which is used to allocate and format the Control-M Resources file, could not open the IOA Log.

Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA monitor.
The IOAFRLOG utility that allocates and formats the IOA Log was not yet run or did not finish executing normally.

The utility stops executing with a condition code of 08.

Corrective Action: Do one of the following:

Correct the JCL and rerun the job.
If the Log is not yet formatted, run the CTMFRLOG utility, then rerun the job.

BRS982S OPEN OF IOA CONDITIONS FILE FAILEDLink copied to clipboard

Explanation: The IOAFRRES IOA utility, which is used to allocate and format the IOA Conditions file, failed to open the IOA Conditions file for formatting.

Possible causes are:

The DARESC DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

BRS983S OPEN OF IOA SYNCHRONIZATION FILE FAILEDLink copied to clipboard

Explanation: The IOAFRRES IOA utility, which is used to allocate and format the Control-M Resources Synchronization file, failed to open the Resources Synchronization file for formatting.

Possible causes are:

The DASINC DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

BRS984I BUILDING OF IOA CONDITIONS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOAFRRES utility, which allocates and formats the IOA Conditions file, has started.

Corrective Action: No action is required.

BRS985I BUILDING OF IOA CONDITIONS FILE ENDED

Explanation: This information message indicates that the IOAFRRES utility, which allocates and formats the IOA Conditions file, has ended normally.

Corrective Action: No action is required.

BRS986S IOA CONDITIONS FILE WAS NOT BUILT

Explanation: The IOAFRRES utility failed.

Corrective Action: Look for previous error messages that describe the type of error.

BSD MessagesLink copied to clipboard

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.

Messages BSD300 through BSD3xxLink copied to clipboard

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.

BSD310I IOACPRM M2S=`ctm2sbs`Link copied to clipboard

Explanation: This information message provides you with the name of the CTM2SBS file.

Corrective Action: No action is required.

BSD311I SMFID=`smfid` SYSTEM=`system_name` S2M=`sbs2ctm`Link copied to clipboard

Explanation: This information message provides you with the SMFID, the system name, and the SBS2CTM file name.

Corrective Action: No action is required.

BSD314I ADDING SMFID `smfid` WAS SUCCESSFULLink copied to clipboard

Explanation: This information message indicates that a new SMFID (smfid) was added successfully to the CMEM monitor, to the M2S subsystem file, by the FORMSUB3 job.

Corrective Action: To make the definition active, stop and restart the Control-M monitor and the Control-O or CMEM monitor on the system with the SMFID.

BSD315I {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS STARTEDLink copied to clipboard

Explanation: This information message indicates that the FORMSUB1 and FORMSUB2 utilities, which allocate and format Console Subsystem communications files, have started.

Corrective Action: No action is required.

BSD316I {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS ENDEDLink copied to clipboard

Explanation: This information message indicates that the FORMSUB1 and FORMSUB2 utilities, which allocate and format Console Subsystem communications files, have ended normally.

Corrective Action: No action is required.

BSD317S {BUILDING | UPDATING} OF SUBSYSTEM COMMUNICATION DATASETS FAILEDLink copied to clipboard

Explanation: The FORMSUB1 or the FORMSUB2 utility failed.

Corrective Action: Look for a previous error message which describes the cause of the error.

BSD318S OPEN OF DDNAME `ddName` FAILEDLink copied to clipboard

Explanation: Open of the ddName DD statement failed.

Possible causes are:

The ddName DD statement is missing.
The ddName DD statement does not define a valid communication file.

Corrective Action: Correct the JCL of the formatting job.

BSD319S I/O ERROR OCCURRED WHILE BUILDING THE SUBSYSTEM COMMUNICATION DATASETSLink copied to clipboard

Explanation: An I/O error occurred while the FORMSUB1 or the FORMSUB2 utility was formatting a subsystem communication file.

Possible causes are:

The utility loaded old and incorrect IOACPRM installation parameters.
The JCL references an invalid data set.
The file size defined in the IOACPRM parameters member is different from the size that was defined in the JCL.

Corrective Action: Check the JCL of the formatting job, and the location and content of the IOACPRM member.

BSD325S SMFID `smfid` IS NOT DEFINED IN IOA INSTALLATION PARAMETERSLink copied to clipboard

Explanation: The FORMSUB1 or the FORMSUB2 utility is running under a CPU that was not defined in the IOACPRM parameters member.

Possible causes are:

The CPU in which the utility was run was not defined in IOACPRM.
The utility loaded an incorrect copy of the IOACPRM member.
The computer in which the utility was run is a multi-CPU computer, and the SID parameter in the SMFPRM xx member in SYS1.PARMLIB does not define all of the CPUs correctly.

Corrective Action: Do the following:

Check what CPUs were defined in IOACPRM.
Check where the IOACPRM member was placed.
If the IOACPRM definition seems to be correct, check the SMFID that was defined in SYS1.PARMLIB.
In a multi-CPU computer, issue the MVS command D M=CPU from the console to get a listing of all CPU serial numbers, and compare them with the PARMLIB definitions.

BSD326E MISSING/INVALID SUBSYSTEM PARAMETERS IN IOACPRMLink copied to clipboard

Explanation: The FORMSUB1 or the FORMSUB2 utility encountered one or more subsystem-related parameters in the IOACPRM member that were defined incorrectly or were not defined at all.

Corrective Action: Check the following parameter definitions in the IOACPRM member, and correct them if needed:

SUBSYS
CTM2SBS
CPUS.

BTR MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages BTR0 through BTR0xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BTR001S UNABLE TO OPEN BUNDLE TRACKING FILELink copied to clipboard

Explanation: The CTDTBTR (Bundle Tracking System screen) program failed to open the Bundle Tracking file.

The CTDTBTR program ends.

Corrective Action: Check the messages in the sysout of the program, and correct the problem accordingly. Return to the Bundle Tracking System screen (DT screen).

BTR002E SPECIFIED TIME IS INVALIDLink copied to clipboard

Explanation: An invalid TIME parameter was specified in the Bundle Tracking System screen (DT screen) SHOW option.

Corrective Action: Specify a valid time.

BTR003E "UNTIL TIME" IS EARLIER THAN "FROM TIME"Link copied to clipboard

Explanation: The UNTIL TIME specified in the SHOW window of the Bundle Tracking System screen (DT screen) is earlier than the FROM TIME.

Corrective Action: Change the value of either the UNTIL TIME or the FROM TIME appropriately.

BTR004E FIELD MUST BE NUMERICLink copied to clipboard

Explanation: A non-numeric symbol was entered into the JOBID field in the SHOW window of the Bundle Tracking System screen (DT screen).

Corrective Action: Replace the non-numeric symbol with a numeric one.

BTR005S INTERNAL ERROR 1. REQUESTED OPTION CANNOT BE PERFORMEDLink copied to clipboard

Explanation: Internal error occurred while processing an option in the BTR screen.

The requested option is not processed.

Corrective Action: Refer the problem to the INCONTROL administrator, who must check the system and IOA logs for further messages, and correct the problem accordingly.

BTR007E PROGRAM FAILED TO READ BUNDLE TRACKING FILELink copied to clipboard

Explanation: A record was deleted from the bundle tracking file.

Corrective Action: Reenter the BTR screen.

BTR008E ENTRY IS IN USE. TRY AGAIN LATERLink copied to clipboard

Explanation: The CTDTBTR program tried to read a record which was being used by another program.

Corrective Action: Try again later.

BTR009E THIS ENTRY WAS CHANGED BY ANOTHER USERLink copied to clipboard

Explanation: The entry was changed by another user just before the current user tried to update it.

Before the CTDTBTR program updates a record, it reads the record with exclusive ENQ to allow updating of the record by another user during its processing. This message is issued when the CTDTBTR program detects that the record was changed between the last READ function and READ with ENQ.

The update fails.

Corrective Action: Try again later.

BTR010S ERROR UPDATING BUNDLE TRACKING FILE. REASON `rsn`Link copied to clipboard

Explanation: An error occurred when updating the Bundle Tracking file.

In this message, rsn is the reason code issued by the File Access program.

The update of the current bundle fails.

Corrective Action: Refer the problem to your INCONTROL administrator who should check the system and IOA logs for further messages, and correct the problem accordingly.

BTR011E CANNOT PERFORM ZOOM DUE TO STORAGE ALLOCATION FAILURELink copied to clipboard

Explanation: There was not enough memory available to perform the zoom function.

Corrective Action: Increase the region size for this environment.

BTR012I BUNDLE `bundleName` SUCCESSFULLY UPDATEDLink copied to clipboard

Explanation: This information message indicates that the bundleName bundle was successfully updated.

Corrective Action: No action is required.

BTR013E INVALID VALUE. SPECIFY "B" OR "U"Link copied to clipboard

Explanation: An incorrect character was specified in the SORT OPTION field in the SHOW window of the Bundle Tracking System screen (DT screen). The only valid values are "B" or "U".

Corrective Action: Specify "B" or "U."

Messages BTR200 through BTR2xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BTR200I CTDCBTR STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDCBTR Control-D utility has started.

Corrective Action: No action is required.

BTR201I CTDCBTR ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDCBTR Control-D utility has ended normally.

Corrective Action: No action is required.

BTR202S CTDCBT ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDCBTR Control-D utility ended with errors.

The utility stops executing.

Corrective Action: Check the job sysout for any error messages, and correct the problem accordingly. Rerun the job.

BTR203S DELETE FAILED FROM BTR FILELink copied to clipboard

Explanation: The CTDCBTR utility failed to delete a record from the Bundle Tracking (BTR) file.

The CTDCBTR utility terminates.

Corrective Action: Check for other messages relating to this problem, and correct accordingly. Rerun the utility.

BTR204S PROBLEM DETECTED IN UTILITY CTDCBTR PARAMETERSLink copied to clipboard

Explanation: A problem was detected in the input parameters of the CTDCBTR utility. This message can be triggered by a number of causes, such as no parameters at all being specified, or the DABTRIN DD statement being absent.

The CTDCBTR utility ends.

Corrective Action: Do the following:

Check the parameters specified for the utility.
Check for a DABTRIN DD statement.
Correct the input as appropriate.
Rerun the job.

BTR205I NUMBER OF DELETED RECORDS: `num`Link copied to clipboard

Explanation: This information message indicates the number of records deleted by the CTDCBTR utility.

In this message, num is the number of deleted records.

Corrective Action: No action is required.

BTR206I INPUT CARDS: `input_cards`Link copied to clipboard

Explanation: This information message displays the input parameters that were specified in the JES log of the job for the CTDCBTR utility.

In this message, input_cards consists of the specified input parameters.

Corrective Action: No action is required.

BTR207E REDUNDANT PARAMETER: `input_card`Link copied to clipboard

Explanation: A superfluous parameter was specified for the CTDCBTR utility.

In this message, input_card is the superfluous parameter.

The CTDCBTR utility ends.

Corrective Action: Remove the superfluous input parameter and rerun the utility.

CAJ MessagesLink copied to clipboard

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.

Messages CAJA00 through CAJAxxLink copied to clipboard

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.

CAJA30I OLD JOBS FILE NEEDED `# recs` RECORDS FOR `# jobs` JOBSLink copied to clipboard

Explanation: The AJF conversion utility issues this information message to show the number of jobs on the old Active Jobs file, and the number of old Active Jobs file records that were needed to store these jobs.

The variables in this message are:

#recs - the number of old AJF records required to store #jobs
#jobs - the number of jobs on the old AJF

Corrective Action: No action is required.

CAJA31I NEW JOBS FILE NEEDS `#recs` RECORDS FOR `#jobs` JOBSLink copied to clipboard

Explanation: The AJF conversion utility issues this information message to show the number of jobs on the new Active Jobs file, and the number of new Active Jobs file records that are now needed to store these jobs.

The variables in this message are:

#recs - the number of new AJF records required to store #jobs
#jobs - the number of jobs on the new AJF

Corrective Action: No action is required.

CAJA32I PERCENTAGE OF RECORDS RELEASED IN NEW JOBS FILE: `nn%`Link copied to clipboard

Explanation: The AJF conversion utility issues this information message to show the percentage of unused records in the new Active Jobs file (AJF).

In this message, nn% is the percentage of unused records in the new AJF.

Corrective Action: No action is required.

CAJA33I AVERAGE NUMBER OF RECORDS PER JOB IN NEW JOBS FILE: `nn.nn`Link copied to clipboard

Explanation: The AJF conversion utility issues this information message to show the average number of records used to store one job on the new Active Jobs file.

In this message, nn.nn is the average number of records.

Corrective Action: No action is required.

CAJA34I AVERAGE NUMBER OF FREE BYTES PER JOB IN NEW JOBS FILE: `#bytes`Link copied to clipboard

Explanation: The AJF conversion utility issues this information message to show the average number of unused bytes (#bytes) in the records used to store one job on the new Active Jobs file.

In this message, #bytes is the average number of unused bytes.

Corrective Action: No action is required.

CAJA3AS OLD STEPLIB AND NEW STEPLIB ARE THE SAMELink copied to clipboard

Explanation: The CTMCAF utility cannot convert the file from one version to another because only one Load library was indicated. The STEPOLD DD statement should point to the Load library of the previous version, but it points to the Load library of the new version.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Correct the STEPOLD DD statement so that it points to the Load library of the previous version, and rerun the job.

CAJA3BS SIZE OF OLD JOBS FILE DIFFER FROM SIZE OF NEW ONELink copied to clipboard

Explanation: The CTMCAF utility cannot convert the file from one version to another because the CKP file sizes are not identical. The conversion requires the same size files for the new version and the old version. The file size should match the size specified in CTMPARM.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Correct the file sizes so they are identical for both versions, and rerun the job.

CAJA3CS LOAD MODULE CTMLOGR FAILEDLink copied to clipboard

Explanation: An internal error occurred during the load of the CTMLOGR module.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Have your INCONTROL administrator record the return code, prepare the Control-M monitor full output, and contact BMC Customer Support.

CAJA3DS DELETE MODULE CTMLOGR FAILEDLink copied to clipboard

Explanation: An internal error occurred during deletion of the CTMLOGR module.

The CTMCAF utility terminates with a return code of 08.

Corrective Action: Have your INCONTROL administrator contact your INCONTROL administrator.

CAJA40I JOBS FILE CONVERSION STARTEDLink copied to clipboard

Explanation: This information message indicates that the process of converting or copying an Active Jobs file has started.

Corrective Action: No action is required.

CAJA41S OPEN OF OLD JOBS FILE FAILED. DDNAME "DAOLDAJF"Link copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility failed to open the input Control-M AJF.

The conversion is terminated. No changes are made to the output file.

Corrective Action: Look at the JCL for the specific file and see if it contains a valid Control-M AJF. If it does not, correct and rerun the job.

CAJA42S OPEN OF NEW JOBS FILE FAILED. DDNAME "DANEWAJF"Link copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility failed to open the output Control-M AJF.

Corrective Action: Look at the JCL for the specific file and see if it contains a valid Control-M AJF. If it does not, correct and rerun the job.

The conversion is terminated. No changes are made to the output file.

CAJA43S FILE ALLOCATED TO DD STATEMENT "DAOLDAJF" IS NOT AN OLD FORMAT JOBS FILELink copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility opened the input Control-M AJF and found its format invalid.

The conversion is terminated. No changes are made to the output file.

Corrective Action: Check the JCL for the specific file and see if it contains a valid Control-M file from an earlier release. If it does not, correct and rerun the job.

CAJA44S NEW DAY PROCEDURE IS CURRENTLY WORKING ON THE OLD JOBS FILELink copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility opened the input Control-M AJF and found that it was being formatted by the Control-M New Day procedure, or that a previous run of the New Day procedure has failed.

The conversion is terminated. No changes are made to the output file.

Corrective Action: Check whether the New Day procedure is currently running. After it finishes executing, shut down the old Control-M and rerun the job.

CAJA45S FILE ALLOCATED TO DD STATEMENT "DANEWAJF" IS NOT A NEW FORMAT JOBS FILELink copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility opened the output Control-M AJF and found its format invalid.

The conversion is terminated. No changes are made to the output file.

Corrective Action: Look at the JCL for the specific file and see if it contains a valid Control-M AJF from a current or new release. If it does not, correct and rerun the job.

CAJA47S FILE ALLOCATED TO DD STATEMENT "DANEWAJF" IS NOT EMPTYLink copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility opened the output Control-M AJF and found it not to be empty.

The conversion is terminated. No changes are made to the output file.

Corrective Action: The file must be empty. Format the new file using the FORMCKP utility.

CAJA48E FILE ALLOCATED TO DD STATEMENT "DAOLDAJF" IS EMPTYLink copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility opened the input Control-M AJF and found it to be empty.

The conversion is terminated. No changes are made to the output file.

Corrective Action: Look at the JCL for the specific file and see if it contains the right AJF. If it does, no conversion is necessary.

CAJA49S OPEN OF OLD STEPLIB FAILEDLink copied to clipboard

Explanation: Open of the library allocated to the STEPOLD DD statement failed.

Possible causes are:

The STEPOLD DD statement is missing.
The file allocated to the STEPOLD DD statement is not a load module library.

The conversion program terminates with a condition code of 08.

Corrective Action: Check that the STEPOLD DD statement is allocated to a load module library.

CAJA50S INTERNAL ERROR WHILE CONVERTING RESOURCESLink copied to clipboard

Explanation: The Active Jobs file (AJF) conversion utility started executing but encountered an invalid format of job entries in the input file.

The conversion program has encountered a job which has invalid entries in the Control-M AJF.

The conversion is terminated at the job definitions which are invalid.

Corrective Action: Do the following:

Look in the new AJF for the last job converted. The next job in the old AJF is the problem job.
Supply your INCONTROL administrator with a dump of the old AJF, stating the job on which the error occurred.
Delete the job entry using the Control-M Online Facility.
Compress the old AJF.
Rerun the job.

CAJA51S QNAME PARAMETER DOES NOT FIT QNAME IN JOBS FILELink copied to clipboard

Explanation: The IOAPARM of the old or new version does not fit the Active Jobs file of that version. The probable cause is that STEPLIB (or STEPOLD) does not point to the library containing the appropriate CTMPARM, or that the file allocated to the DAOLDAJF or DANEWAJF DD name is not of the correct version.

The conversion program terminates with a condition code of 08.

Corrective Action: Check that the library allocated to the DAOLDAJF or DANEWAJF DD name contains the correct IOAPARM, and check that the file allocated to the DAOLDAJF or DANEWAJF DD name is the correct file.

CAJA52S INTERNAL ERROR OCCURRED DURING CONVERSION. RC=`rc`Link copied to clipboard

Explanation: An internal error has occurred during the execution of the conversion program.

The conversion program terminates with a condition code of 08.

Corrective Action: Notify your INCONTROL administrator.

CAJA53I CONVERSION OF JOBS FILE ENDED WELLLink copied to clipboard

Explanation: This information message indicates that the process of converting or copying the Active Jobs file ended OK.

Corrective Action: No action is required.

CAJA54S CONTROL-M/RESTART WAS INSTALLED IN PREVIOUS VERSION, AND IS NOT INSTALLED NOWLink copied to clipboard

Explanation: Control-M/Restart was installed in the old version, but not in the newly defined version.

The conversion program terminates with a condition code of 08.

Corrective Action: Check why Control-M/Restart is not installed in new version, and make sure that it is installed before rerunning the conversion program.

CAL MessagesLink copied to clipboard

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.

Messages CAL200 through CAL2xxLink copied to clipboard

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.

CAL295I BUILDING JOB CALENDARS STARTEDLink copied to clipboard

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.

CAL296I BUILDING JOB CALENDARS ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTMRCAL utility finished creating the calendars.

Corrective Action: No action is required.

CAL297E INVALID RETYPE PARAMETER VALUE - ‘S’ SUBPARAMETER REQUIREDLink copied to clipboard

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.

CAP MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages CAP900 through CAP9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CAP906I REFRESH OF PERMANENT USER FILE FROM THE ACTIVE USER FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTDCA2P utility is copying the list of reports from the Active User Report List file to the Permanent User Report List file. This is the normal start message of the CTDCA2P utility.

Corrective Action: No action is required.

CAP907I REFRESH OF PERMANENT USER FILE FROM THE ACTIVE USER FILE ENDED OKLink copied to clipboard

Explanation: This information message is the normal end message for the CTDCA2P utility. It indicates that the CTDCA2P utility successfully finished copying the list of reports from the Active User Report List file to the Permanent User Report List file.

Corrective Action: No action is required.

CAP909S REFRESH OF PERMANENT USER FILE FROM THE ACTIVE USER FILE ENDED WITH ERRORSLink copied to clipboard

Explanation: An error occurred during the execution of the CTDCA2P utility.

Corrective Action: An earlier message describes the error.

CAP90AI COPIED TO PERMANENT FILE `userName jobName cat fromUser reportName`Link copied to clipboard

Explanation: This information message indicates that a record from the Active Report List file was successfully copied to the Permanent Report List file. The CTDCA2P utility issues this message for each record successfully copied from the Active Report List file.

Corrective Action: No action is required.

CAP90BI TOTAL NUMBER OF RECORDS COPIED TO PERMANENT FILE IS: `num`Link copied to clipboard

Explanation: This information message displays the number of records copied from the Active Report List file to the Permanent Report List file. This message is issued by the CTDCA2P utility.

Corrective Action: No action is required.

CAP90CI ACTION USER JOB CATEGORY FROM USER REPORT NAMELink copied to clipboard

Explanation: This information message is issued by the CTDCA2P utility as a heading line for message CAP90AI.

Corrective Action: No action is required.

CAP90DI `userName jobName reportName cat`Link copied to clipboard

Explanation: This information message is issued by the CTDCA2P utility.

The variables in this message relate to the record copied from the Active User file to the Permanent user file, as follows:

userName - the identity of the user
jobName - the identity of the job
reportName - the identity of the report
cat - the category

Corrective Action: No action is required.

CCU MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages CCUF00 through CCUFxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CCUF00I `ctrl_stmt_text`Link copied to clipboard

Explanation: This information message is issued by the CTDCCU utility. It displays the input control statement of the CTDCCU utility.

Corrective Action: No action is required.

CCUF01I CDAM CLEAN-UP UTILITY STARTEDLink copied to clipboard

Explanation: This information message indicates the normal start of the CTDCCU Control-D utility. This utility identifies CDAM files that can be deleted from disk because they are no longer referenced by the Active User Report List file.

Corrective Action: No action is required.

CCUF02I CDAM CLEAN-UP UTILITY ENDED OKLink copied to clipboard

Explanation: This information message is the normal end message of the CTDCCU Control-D utility. This utility identifies CDAM files that can be deleted from disk because they are no longer referenced by the Active User Report List file.

Corrective Action: No action is required.

CCUF03S CDAM CLEAN-UP UTILITY ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTDCCU Control-D utility ended with errors. The job-name SYSOUT should contain other messages detailing the reasons.

The utility stops executing with a return code which depends on the severity of the error.

Corrective Action: Check the previous error message or messages, correct the problem and rerun the job.

CCUF04E OPEN OF HISTORY USER REPORT LIST FILE FAILED. DDNAME "DAVHST"Link copied to clipboard

Explanation: Open of the Control-D History User Report List file failed (the DAVHST DD statement). This error message is issued by the CTDCCU Control-D utility, which identifies CDAM files that are no longer referenced by the Active User Report List file.

Possible causes are:

The DAVHST DD statement is missing.
The data set pointed to by the DAVHST DD statement is not the Control-D History User Report List file.
The data set pointed to by the DAVHST DD statement, is the Control-D History User Report List file, but is of another Control-D monitor, or of a different version of Control-D.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CCUF05E OPEN OF INPUT FILE FAILED. DDNAME "DACCUIN"Link copied to clipboard

Explanation: Open of the file containing input parameters failed (the DACCUIN DD statement). This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

Possible causes are:

The DACCUIN DD statement is missing.
The DSNAME pointed to by the DACCUIN DD statement cannot be opened for sequential read.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CCUF06E INVALID PARAMETER:- `parm`Link copied to clipboard

Explanation: An invalid parameter was specified in the input for the CTDCCU Control-D utility.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file. For more information, see the CTDCCU utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the input and rerun the job.

CCUF07E ONLY ONE PARAMETER `parm` ALLOWEDLink copied to clipboard

Explanation: More than one DATE or SIMULATION parameter was specified in the input for the CTDCCU Control-D utility.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the input and rerun the job.

CCUF08E INVALID DATE VALUELink copied to clipboard

Explanation: An invalid date format was used in a DATE parameter for the CTDCCU Control-D utility.

Valid date formats are:

ddmmyy
mmddyy
yymmdd

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file. For more information, refer to the CTDCCU utility in the INCONTROL for z/OS Utilities Guide.

The CTDCCU Control-D utility stops executing with a condition code of 08.

Corrective Action: Correct the date format and rerun the job.

CCUF09E TODATE SHOULD NOT BE AFTER RUN DATE MINUS ONELink copied to clipboard

Explanation: An invalid value was set for TODATE in the input for the CTDCCU Control-D utility. The latest date which may be specified for TODATE is the day before the run date.

The utility stops executing with a condition code of 08.

Corrective Action: Set a valid value for TODATE and rerun the job.

CCUF0AE MISSING VALUE FOR PARAMETER `parm`Link copied to clipboard

Explanation: The parm parameter was specified with no value.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file. For more information, refer to the CTDCCU utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Enter the missing parameter value and rerun the job.

CCUF0BI WAITING FOR CTDDELRP OR RESTORE JOB TO TERMINATELink copied to clipboard

Explanation: This information message indicates that the CTDCCU utility is waiting for a CTDDELRP job or a restore job to terminate before the utility can resume executing.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

Note:

To ensure data integrity, do not run the CTDCCU utility concurrently with a CTDDELRP job or a restore job.

When the contending job terminates, the CTDCCU utility resumes processing.

Corrective Action: No action is required.

CCUF0CE SPECIFIED PREFIX IS LONGER THAN 23 CHARACTERSLink copied to clipboard

Explanation: An attempt has been made to invoke the CTDCCU Control-D utility, but the data set name prefix that was specified consisted of more than 23 characters. The length of a data set name prefix must not exceed 23 characters.

This error message is issued by the CTDCCU Control-D utility, which is used to identify

CDAM files that are no longer referenced by the Active User Report List file
Control-V index files that are not referenced by the Active User Report List file or the Migrate User Report List file

For more information, see the CTDCCU utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a return code of 08.

Corrective Action: Correct the value of PREFIX and rerun the job.

CCUF0EE MISSING DATE OR PREFIX PARAMETERLink copied to clipboard

Explanation: A DATE or PREFIX parameter for the CTDCCU Control-D utility is missing. At least one DATE and one PREFIX parameter must be specified, for the utility to execute. More than one PREFIX parameter may be specified.

The utility stops executing with a condition code of 08.

Corrective Action: Enter the missing parameter and rerun the job.

CCUF0FE INVALID VALUE FOR PARAMETER `parm`. VALUE SHOULD BE "YES" OR "NO"Link copied to clipboard

Explanation: An invalid value was specified for a VERIFY or SIMULATION parameter for the CTDCCU Control-D utility.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file. For more information, refer to the CTDCCU utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the input and rerun the job.

CCUF10E OPEN OF SORT FILE FAILED. DDNAME `ddName`Link copied to clipboard

Explanation: The site SORT utility, which was invoked by the CTDCCU Control-D utility, failed to open the data set pointed to by the ddName DD statement. This error message is issued by the CTDCCU Control-D utility, which identifies CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CCUF11E INVALID RETURN CODE FROM SORT. RC=`rc`Link copied to clipboard

Explanation: The site SORT utility, which was invoked by the CTDCCU Control-D utility, has ended with errors.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Refer to the SORT messages of the job and to the user guide for the SORT facility used at your site. If necessary, call your system programmer for assistance.

CCUF12E INVALID RETURN CODE FROM IDCAMSLink copied to clipboard

Explanation: The site IDCAMS program, which was invoked by the CTDCCU Control-D utility, has ended with errors. The usual cause is corrupted data in the system catalog.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Use the TSO command LISTC LVL (prefix) HISTORY to produce more detailed messages about the problem and correct accordingly.

CCUF13E OPEN OF WORK FILE FAILED. DDNAME "DAWORK"Link copied to clipboard

Explanation: The CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file, failed to open the Work List file (the DAWORK DD statement).

Possible causes are:

The DAWORK DD statement is missing.
The data set pointed to by the DAWORK DD statement cannot be opened for sequential write.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CCUF14E INVOCATION OF PROGRAM `pgm` FAILED. PROGRAM COULD NOT BE ACCESSEDLink copied to clipboard

Explanation: Invocation of the pgm program ended with errors. This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

The utility stops executing with a condition code of 08.

Corrective Action: Look for previous error messages which describe the type of error. If necessary, call your system programmer for assistance.

CCUF15I DATASET `dsn` WILL BE DELETEDLink copied to clipboard

Explanation: This information message indicates that the dsn CDAM data set was added to the Scratch List file (list of data sets to be scratched). If SIMULATION was set to NO, the data set is deleted in the next step of the job.

This message is issued by the CTDCCU utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file, and may therefore be deleted from the disk.

Corrective Action: No action is required.

CCUF16W JOB `jobName` JOBID `jobId` DATASET `dsn` NOT IN CATALOGLink copied to clipboard

Explanation: The Active User Report List file contains a reference to a CDAM file that is not in the VSAM catalog. The dsn data set, which was created by the jobName jobId job, is referenced by the Active User Report List file, but does not have an entry in the VSAM catalog.

This error message is issued by the CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file.

The utility continues executing, but will terminate with a condition code of 04.

Corrective Action: No action is required.

CCUF18W ONLY ONE VERIFY PARAMETER ALLOWED. RECORD IGNOREDLink copied to clipboard

Explanation: More than one VERIFY parameter was specified for the CTDCCU Control-D utility.

The utility continues executing, but terminates with a condition code of 04. Only the first VERIFY parameter in the input is processed, and all others are ignored.

Corrective Action: No action is required.

CCUF19W NO DATASET OR SYSDATA RECORD WAS FOUND MATCHING THE SELECTION CRITERIALink copied to clipboard

Explanation: The CTDCCU utility did not find any data set or SYSDATA record matching the specified selection criteria.

This warning message is issued by the CTDCCU utility, which is used to identify CDAM or Control-V index files that are no longer referenced by the Control-D/V database.

For more information, see the CTDCCU utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 04.

Corrective Action: If necessary, correct the selection criteria and rerun the job.

CCUF20E OPEN OF SCRATCH FILE FAILED. DDNAME "DASCRLST"Link copied to clipboard

Explanation: The CTDCCU Control-D utility, which is used to identify CDAM files that are no longer referenced by the Active User Report List file, was unable to open the Scratch List file (the DASCRLST DD statement).

Possible causes are:

The DASCRLST DD statement is missing.
The data set pointed to by the DASCRLST DD statement cannot be opened for sequential write.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CCUF21I DATA SET `dsn`NOT F0UND. SYSDATA {JOBNAME=`jobName`, COUNT='`key`'} WILL BE DELETEDLink copied to clipboard

Explanation: This message is issued by the CTDCCU utility when it is called with the DELSYSDATA parameter set to YES and when it detects an orphan SYSDATA record in the Active User Report file. The variables in the message identify the problematic record.

The variables in this message are

dsn - the name of the CDAM data set
jobName - the name of the job to which the problematic SYSDATA record relates
key - the unique key of the problematic SYSDATA record

If the CTDCCU utility is running in simulation mode, the problematic SYSDATA record remains in the Active User Report file. Otherwise, the record is deleted.

Corrective Action: No action is required.

CCUF22E INCORRECT DSNAME OF THE MIGRATED INDEX FILE ON $INDEX RECORD {JOBNAME=`jobName`, COUNT=`'key'`, ICNT='`seqNumber`'}Link copied to clipboard

Explanation: This message is issued by the CTDCCU utility when an error occurs during the evaluation of the data set name of a migrated index file.

The variables in this message are

jobName - the name of the job to which the data set name relates
key - the unique key of the relevant SYSDATA record
seqNumber - the sequence number of the problematic INDEX record

The problematic index file is ignored, but the utility is forced to run in Simulation mode.

Corrective Action: Contact your INCONTROL administrator.

CCUF23W SIMULATION=YES IS FORCEDLink copied to clipboard

Explanation: The CTDCCU utility issues this message when it is called with the SIMULATION parameter set to NO if during execution an error occurs of a type that may cause a risk of data loss.

Accompanying messages describe the error that occurred.

The utility continues execution in Simulation mode.

Corrective Action: Examine the accompanying messages, and take action accordingly.

CCUF25I TAPE DATA SET `dsn` HAS NO REFERRING $INDEX RECORDLink copied to clipboard

Explanation: This information message is issued by the CTDCCU utility and indicates that the dsn index data set migrated to a tape is no longer referred to by any $INDEX record, that is, it has been "orphaned" in terms of the utility.

Since the utility is only able to remove DASD data sets, this data set will not be deleted.

Corrective Action: Uncatalog and scratch this data set using standard system tools, if needed.

CDS MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages CDS0 through CDS0xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CDS012E LOGICAL DESTINATION `dest` IS NOT FOUND. CHOOSE A NEW ONELink copied to clipboard

Explanation: A user has specified a Delivery Server External Destination that does not exist.

Corrective Action: In this message, dest is the non-existent Destination.

The External Destination screen is opened. Either choose (from the External Destination list) an External Destination that is valid, or define a new External Destination.

CDS020I RECORD FOR DEST `dest` MODIFIEDLink copied to clipboard

Explanation: This information message indicates that the External Destination record relating to the Delivery Server External Destination dest was modified.

Corrective Action: No action is required.

CDS021I TYPE LOGICAL DESTINATION AND DESCRIPTION FOR THE FIRST CTDS RECORDLink copied to clipboard

Explanation: The Delivery Server External Destination list is empty.

Corrective Action: Add one or more External Destination records.

Messages CDSG00 through CDSGxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CDSG19E CANNOT COPY TO THE SAME DESTLink copied to clipboard

Explanation: In the COPY Option prompt window, the user has specified the External Destination to which the record belongs.

You can use the COPY Option to provide a copy of a record to another External Destination, but not to the External Destination to which the record already belongs.

Corrective Action: Either type another External Destination in the COPY Option prompt window, or cancel the COPY request by typing N (for NO) in the CONFIRM field in the COPY Option prompt window.

CDSG20I RECORD FOR DEST `dest` COPIED TO `dest`Link copied to clipboard

Explanation: This information message indicates that the dest record has been copied, using the COPY Option (option C) of the External Destination List screen.

Corrective Action: No action is required.

Messages CDSU00 through CDSUxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CDSU10E USER DATA BASE ERRORLink copied to clipboard

Explanation: At this site, the Delivery Server External Destinations are contained in the user’s own database, instead of the PERMANENT file. While processing a simulation request, the Control-D User Exit 26 found an error in the user’s database.

Processing of the request is terminated.

Corrective Action: Correct the error in the user’s Delivery Server External Destinations database.

CDT MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages CDTA00 through CDTAxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CDTA51W NO RESTORE RECORDS FOUND ON HISTORY FILE.Link copied to clipboard

Explanation: The ANALYZE step of the restore job found no restore control records in the History User Report List file to process.

The CTDRSC ANALYZE step program was invoked either by a restore job or the RSTRESET job but did not find any restore control records in the History User Report List file for the restore Mission specified in the PARM field.

The CTDRSC program terminates with a return code of 08.

Corrective Action: No action is required.

CHK MessagesLink copied to clipboard

This group includes messages for the Control-M for z/OS and Control-D products.

Messages CHK400 through CHK4xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, and Control-D products.

CHK422S OPEN OF USER DATE CONTROL-RECORD FAILED - DDNAME "DACHK"Link copied to clipboard

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). Issued by the CTMCHK, CTDCHK, or CTBCHK programs, which are usually activated by the New Day procedure.

Possible causes are:

The DACHK DD statement is missing.
The data set (member) described by the DACHK DD statement does not exist.

The CTMCHK, CTDCHK, or CTBCHK program ends with errors.

Corrective Action: Correct the JCL for the job or CLIST.

CHK423S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed (the DALOG DD statement). This error message is issued by the CTMCHK, CTDCHK, or CTBCHK programs, which are activated as part of the New Day procedure.

Possible causes are:

The DALOG DD statement is missing.
The data set or member described by the DALOG DD statement is not the IOA Log file.
The data set described by the DALOG DD statement is the IOA Log file, but of a different IOA Installation or of a different version.

The CTMCHK, CTDCHK, or CTBCHK program ends with errors.

Corrective Action: Correct the JCL for the job or CLIST.

CHK424S INVALID ORIGINAL SCHEDULING DATE IN USER DATES CONTROL-RECORD (POSITIONS 1-6)Link copied to clipboard

Explanation: Invalid original scheduling date in the User Date Control Record (positions 1 through 6). This date should be earlier than the current installation working date.

Valid formats are:

ddmmyy
mmddyy

Possible causes are:

The previous run of the CTDCHK or CTMCHK program did not finish OK.
Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more information, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure ends with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement).

CHK425S INVALID POST DATE IN USER DATES CONTROL RECORD (POSITIONS 67-72)Link copied to clipboard

Explanation: The contents of the Date Control Record for this Daily are invalid.

Valid formats are:

ddmmyy
mmddyy

This message usually indicates that the User Date Control Record was incorrectly modified. The date should be earlier than or equal to the original scheduling date defined in positions 1 through 6.

The New Day procedure ends with errors.

Corrective Action: Correct the Date Control Record (the DACHK DD statement).

CHK426W {GENERAL |`dailytype}` "DAILY" DID NOT RUN FOR `nnn` DAYSLink copied to clipboard

Explanation:Highlighted, unrollable message.

The difference between the current working date and the original scheduling date (positions 1 through 6 in the Date Control Record) is more than one day. The New Day procedure has not run for nnn days. A New Day procedure is expected to run once a day.

Probable causes are:

The computer has not been working for at least one day.
The Control-M or Control-D monitor has not been working for over 24 hours.
The contents of the Date Control Record were incorrectly modified for this Daily.
In the case of the New Day procedure, the computer may have been IPLed with the wrong date.
In the case of a User Daily, the User Daily has not run for a few days.

The value of dailytype can be GENERAL for the New Day procedure or the job name of a regular User Daily job.

For User Daily jobs, processing continues. Missions are selected according to the RETRO parameter.

For the New Day procedure, this message appears highlighted on the operator console, together with either the CTM427W or CTD427W and CTM428W or CTD428W message. If the operator answers YES, processing continues, taking the RETRO parameter of each job into consideration. If the operator answers NO, the New Day procedure stops executing with an error message.

If a long period of Control-D inactivity (more than 28 days) is detected, message CHK42AW is issued before message CHK427W, and you must manually update the date in the Date Control Record (DDATEREC member) before proceeding.

Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.

CHK427W IS IT TRUE? (ANSWER "YES" OR "NO")Link copied to clipboard

Explanation:Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK428W, CTM428W, or CTD428W messages. For more details, see the CHK426W message.Link copied to clipboard

The New Day procedure waits for the operator response.

CHK428W YOUR ANSWER IS:Link copied to clipboard

Explanation:Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK427W, CTM427W, or CTD427W messages. For details, see the CHK426W message.

The New Day procedure waits for the operator response.

CHK429S {CTMCHK | CTDCHK | CTBCHK} ENDED WITH ERRORSLink copied to clipboard

Explanation: The CTMCHK, CTDCHK, or CTBCHK program ended with errors. It is activated as part of the New Day procedure. The IOA Log should contain an earlier message about the error.

The New Day procedure finishes executing with a condition code of 08.

Corrective Action: Check the IOA Log for error messages. If necessary, manually correct the Date Control Record (date-3 and date-5) to allow the next run of the User Daily job. For more information, see the INCONTROL for z/OS Administrator Guide.

CHK42AW PLEASE UPDATE THE DDATEREC MEMBER BEFORE YOU ANSWERLink copied to clipboard

Explanation: A long period of Control-D inactivity was detected. The last run of the New Day procedure was more than 28 days ago. This message appears after the CHK426W message and before the CHK427W message.

Corrective Action: Before proceeding, manually update the dates that appear in the DDATEREC member in the CTD PARM library and are pointed to by ddname DACHK in the Newday procedure.

CHK430E POSSIBLE ABEND OF PREVIOUS DAILY RUN!Link copied to clipboard

Explanation: A previous run of the same New Day procedure probably abended.

The New Day procedure terminates with errors.

Corrective Action: Correct the Date Control Record and rerun the New Day procedure. As a result of the last abend, dates 2, 3 and dates 4, 5, in the Date Control Record are not identical - they should be. If you correct them to the values of date 3 or date 6, a rerun of the New Day procedure schedules all the jobs in the New Day procedure for the days after dates 2 through 5 until the date designated in date 1 (the current original scheduling date). Do not schedule the same job twice.

For more information, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

CHK431I {CTMCHK | CTDCHK | CTBCHK} STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, started executing.

Corrective Action: No action is required.

CHK432I {CTMCHK | CTDCHK | CTBCHK} ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, ended normally.

Corrective Action: No action is required.

CHK433S DIFFERENCE BETWEEN CURRENT AND LAST RUN OF THIS DAILY IS NEGATIVE BY `numDays`Link copied to clipboard

Explanation: The current working date in the computer is before the last original scheduling date of this New Day procedure.

This message is issued by the New Day procedure as a result of incorrect dates in the Date Control Record. For more information, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

The New Day procedure stops executing with an error message.

Corrective Action: Correct the contents of the Date Control Record, and rerun the Daily. If this problem occurs under the New Day procedure, call your system programmer. The problem should be resolved immediately as the Control-M or Control-D monitor will not be able to operate. Check whether the computer has been IPLed with the correct date.

CHK434W THIS DAILY HAS ALREADY BEEN RUN TODAYLink copied to clipboard

Explanation: The same New Day procedure has already been run today. The current working date in the computer is equal to the last original scheduling date - positions 1 through 6 in the Date Control Record (the DACHK DD statement).

For more information, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

Processing terminates with a return code of 8.

Corrective Action: Check the result of the run carefully for possible errors. If the Control-M or Control-D monitor is up and running, there is no need to run the New Day procedure. It was probably started by accident. In any case, have your INCONTROL administrator look at the problem. It is possible that the computer was IPLed with the wrong date.

CHK435S OPERATOR RESPONDED "NO"Link copied to clipboard

Explanation: The operator answered NO to the CHK428W, CTM428W, or CTD428W message.

The New Day procedure stops executing.

Corrective Action: Correct the problem, which is usually date-related, and rerun the New Day procedure.

CHK436S USER DATES CONTROL RECORD IS EMPTYLink copied to clipboard

Explanation: The data set described by the DACHK DD statement is empty (the New Day procedure).

The New Day procedure terminates with errors.

Corrective Action: Correct the JCL for the job and rerun it.

CHK437I date control record contentLink copied to clipboard

Explanation: This informational message is issued when Newday processing is initiated. In place of date control record content, it displays the contents of the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK in the Newday procedure. For explanations of the dates displayed, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”

Corrective Action: No action is required.

CHK438W REPLY 'U' TO UPDATE DATEREC TO CURRENT DAY EXECUTION OR 'E' TO ENDLink copied to clipboard

Explanation:Highlighted, unrollable message.

An error condition is detected while processing the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK in the Newday procedure. This message is usually preceded by another error message detailing the error encountered. Some reasons that this message might be issued are:

Invalid date date1 (see message CHK424S).
Invalid dates date2- date7 (see message CHK43BE).
The difference between the current working date and the date on which Newday was last run (date7) is negative (see message CHK433S).
The current working date is equal to date1 (Newday was already run--see message CHK434W).
The DATEREC member is empty (see message CHK436S).
An attempt was made to run the New Day procedure twice in the same day (see message FRM454E).
date7 is later than date1 (see message FRM455S).
date7 is more than 28 days in the past (see message FRS476S or JOB50S).
For an explanation of the dates in question, see INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”

The Newday procedure waits for operator response.

Corrective Action: Review the preceding error messages to determine the actions necessary to correct the problem. If the problem can be corrected by setting the dates in the DATEREC record to the current working date, enter U. After Control-M automatically updates the DATEREC record, Newday processing resumes.

Otherwise, enter E and then correct the problem manually. For example, if the computer was IPLed with the wrong date, enter E, correct the computer date, and then reactivate Newday manually.

CHK439W REPLY 'C' TO CONTINUE, 'U' TO UPDATE DATEREC TO CURRENT DAY EXECUTION, OR 'E' TO ENDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Following initiation of the Newday procedure, Control-M issued message CHK426W (warning that more than a day has passed since the previous run of Newday).

The Newday procedure waits for operator response.

Corrective Action: Review the explanation of message CHK426W to determine if this is an error situation. If this is not an error situation, enter C ; Newday proceeds using the existing dates in the DATEREC record. If this is an error situation and the problem can be corrected by setting the dates in the DATEREC record to the current working date, enter U. After Control-M automatically updates the DATEREC record, Newday processing resumes.

Otherwise, enter E and then correct the problem manually. For example, if the computer was IPLed with the wrong date, enter E, correct the computer date, and then reactivate Newday manually.

CHK43AI NEWDAY EXECUTION CONTINUING WITH ODATE `odate`Link copied to clipboard

Explanation: This informational message is issued when the response to message CHK438W or CHK439W was U. It informs the user that Newday processing continues, using odate as the current working date.

The Newday procedure resumes.

Corrective Action: No action is required.

CHK43BE DATE CONTROL RECORD CONTAINS AN INVALID DATE AT POSITION `col`Link copied to clipboard

Explanation: During Newday initiation, an invalid date was detected in the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK. The date in error is in column col of the record. (For explanations of the dates displayed, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”)

Message CHK438W is generated.

Corrective Action: Respond to message CHK438W as instructed.

CHK43CI CONTENTS OF DATE CONTROL RECORD:Link copied to clipboard

Explanation: This message serves as a header for message CHK437I, which follows.

Corrective Action: No action is required.

CHK43DW REQUESTED ODATE IS `odate`Link copied to clipboard

Explanation:Highlighted, unrollable message.

This message is issued in response to any of the following operator commands:

F CONTROLM,NEWDAY=hhmm [ ,date ]
F CONTROLM,NEWDAY=hhmm,ORDERONLY [ ,date]
F CTMTROLM,NEWDAY=hhmm,RERUN
S CTMTDAY,NEWDAY=date
S CTMTDAY,NEWDAY='ORDERONLY,date'

For more information, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Message CHK43GW is issued.

Corrective Action: Respond to message CHK43GW as instructed.

CHK43GW REPLY 'C' TO CONTINUE OR 'E' TO ENDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Upon entry of the F CONTROLM,NEWDAY=hhmm,date command, message CHK43DW displayed the ODATE entered. The current message asks the operator to either confirm that the Newday procedure continue with the specified ODATE or not continue.

The Newday procedure waits for operator response.

Corrective Action: One of the following responses:

C --confirm Newday execution using the ODATE displayed by message CHK43DW. (Dates in the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK are not modified.)
E --cause the NEWDAY command to be ignored.

CLH MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages CLH900 through CLH9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CLH943W TOO MANY DATASETS/TAPES HAVE TO BE SCRATCHED, THE CLEANING IS PARTIAL ONLY. RUN THE UTILITY ONCE MORE.Link copied to clipboard

Explanation: This message is issued by the CTDCLHST utility and indicates that the total number of expired CDAM and index files or the number of expired backup tapes exceeds the limit that the utility can process within one execution.

The utility does the following within its limit:

deletes the expired CDAM and index files
lists the expired backup tapes
removes the corresponding records from the History User Report List file.

The rest of the expired files and tapes will be processed in the next execution of the utility. When this message is issued, the CTDCLHST utility finishes with a return code of 08.

Corrective Action: Run the utility again.

CLH944I CLEANING OF HISTORY USER REPORTS LIST FILE STARTEDLink copied to clipboard

Explanation: This information message is the normal start message of the CTDCLHST utility, which clears entries from the History User Report List file.

Corrective Action: No action is required.

CLH945I CLEANING OF HISTORY USER REPORTS LIST FILE ENDED OKLink copied to clipboard

Explanation: This information message is the normal end message of the CTDCLHST utility, which clears entries from the History User Report List file.

Corrective Action: No action is required.

CLH946E CLEANING OF HISTORY USER REPORTS LIST FILE ENDED WITH ERRORS RC = `rc`Link copied to clipboard

Explanation: The CTDCLHST utility, which clears entries from the History User Report List file, ended with errors. Earlier messages describe the problem.

The utility ends with a return code of rc.

Corrective Action: Check the previous error messages, correct the problem, and rerun the job.

CLH947I TAPE `volser` - EXPIREDLink copied to clipboard

Explanation: This is information message is displayed by the CTDCLHST utility, and indicates that a backup tape has been found whose retention period has expired. The utility scans entries in the History User Report List file for reports whose retention period has expired, based on the # OF DAYS TO KEEP parameter or on the # OF GENERATIONS TO KEEP parameter specified in the Backup Mission Definition screen.

This tape may be added to the list of expired tapes.

Corrective Action: Return the expired tape to the Global Tape Pool.

CLH948E INSUFFICIENT MEMORY, THE CLEANING PROCESS STOPPED. INCREASE THE DATA VALUE IN WD2403.Link copied to clipboard

Explanation: There is insufficient memory for the CTDCLHST utility to complete cleaning of the History User Report List file. The situation is caused by a non-zero value that is too small, which has been specified in the DATA parameter in the definition of optional wish WD2403. It must not be smaller than the number of the SYSDATA records in the History User Report List file with the same job name.

The utility stops processing with no change being made to the History User Report List file, and finishes with a return code of 08.

Corrective Action: Increase the value of the DATA parameter appropriately in the definition of optional wish WD2403, or set it to zero. Increase the REGION size for the utility job, if needed, and rerun the utility.

CLH949I `number` USER RECORDS READ.Link copied to clipboard

Explanation: This information message indicates how many USER records have been read by the CTDCLHST utility from the History User Report List file.

Corrective Action: No action is required.

CLH94AI `number` SYSDATA RECORDS READ.Link copied to clipboard

Explanation: This information message indicates how many SYSDATA records have been read by the CTDCLHST utility from the History User Report List file.

Corrective Action: No action is required.

CLH94BI `number` NOTEPAD RECORDS READ.Link copied to clipboard

Explanation: This information message indicates how many NOTE records have been read by the CTDCLHST utility from the History User Report List file.

Corrective Action: No action is required.

CLH94CI `number` $INDEX RECORDS READ.Link copied to clipboard

Explanation: This information message indicates how many INDEX records have been read by the CTDCLHST utility from the History User Report List file.

Corrective Action: No action is required.

CLH94DI `number` RECORDS DELETED IN TOTALLink copied to clipboard

Explanation: This information message indicates how many records have been deleted by the CTDCLHST utility from the History User Report List file.

Corrective Action: No action is required.

Messages CLHD00 through CLHDxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CLHD73E INVALID RETURN CODE FROM SORT, RC=`rc`Link copied to clipboard

Explanation: A failure was detected in the SORT utility phase of the CTDCLHST utility. The main program (CTDCLH) of the CTDCLHST utility received a return code (rc) higher than 4 from the SORT utility phase.

The program terminates with a return code of 08.

Corrective Action: Additional information is in the Job log and the SORT messages. Correct all reported problems, and rerun the CTDCLHST utility.

CLHD75I WAITING FOR ANOTHER CTDCLHST JOB TO TERMINATELink copied to clipboard

Explanation: This information message indicates that the Control-D CTDCLHST utility is waiting for another CTDCLHST job to terminate. The Control-D utility clears unnecessary entries from the History User Report List file. To maintain data integrity, the CTDCLHST utility cannot run two or more jobs concurrently.

When the first job terminates, the CTDCLHST utility resumes processing.

Corrective Action: No action is required.

CLHD76E INVALID PARAMETER, VALID PARAMETER: MODE=TEST OR MODE=PRODLink copied to clipboard

Explanation: An invalid value for the MODE parameter was specified by the CTDCLHST utility call.

The CTDCLHST utility ends with a return code of 12.

Corrective Action: Correct the MODE parameter to either TEST or PROD, and rerun the utility.

CLHD77I * PARM=TEST SPECIFIED - SIMULATION MODE *Link copied to clipboard

Explanation: This information message indicates that the CTDCLHST utility ran in simulation mode. In this mode, messages are generated that indicate what actions would normally be performed. These actions are not performed, nor are any files changed.

Corrective Action: Check the SYSOUT of the CTDCLHST utility before running it in production mode.

CLHD78I NUMBER OF USER RECORDS TO BE DELETED =`number`Link copied to clipboard

Explanation: This information message indicates how many USER records will be deleted by the CTDCLHST utility.

Corrective Action: No action is required.

CLHD79I NUMBER OF SYSDATA RECORDS TO BE DELETED =`number`Link copied to clipboard

Explanation: This information message indicates how many SYSDATA records will be deleted by the CTDCLHST utility.

Corrective Action: No action is required.

CLHD7AI NUMBER OF NOTEPAD RECORDS TO BE DELETED =`number`Link copied to clipboard

Explanation: This information message indicates how many notepad records will be deleted by the CTDCLHST utility.

Corrective Action: No action is required.

CLHD7BI NUMBER OF $INDEX RECORDS TO BE DELETED =`number`Link copied to clipboard

Explanation: This information message indicates how many index records will be deleted by the CTDCLHST utility.

Corrective Action: No action is required.

CLHD7EW SYSDATA RECORD `jobName` ID `jobId` ODATE=`odate` HAS NO BACKUP DATE. THE DECOLLATION DATE IS ASSUMED.Link copied to clipboard

Explanation: The CTDCLHST utility discovered a SYSDATA record in the History User Report List file with a zero backup date.

The variables in this message are:

jobName - the name of the job to which the SYSDATA record belongs
jobId - the MVS identifier of the job to which the SYSDATA record belongs
odate - the originating date of the report to which the SYSDATA record belongs

The CTDCLHST utility assumes the record decollation date as its backup date, and processes the record accordingly.

Corrective Action: No action is required.

CLHD7FW SYSDATA RECORD {`jobName recordId`} HAS AN INVALID BACKUP DATE, RELATED REPORT WILL BE HELD.Link copied to clipboard

Explanation: The CTDCLHST utility discovered a SYSDATA record in the History User Report List file with an invalid backup date.

The variables in this message are:

jobName - the name of the job to which the SYSDATA record belongs
recordId - the unique key of the SYSDATA record

Neither the SYSDATA record nor the related report will be removed from the History User Report List file.

Corrective Action: Investigate the cause of this occurrence, and correct the problematic SYSDATA record.

CLHD7GI SELECTION PASS OVER THE HISTORY FILE.Link copied to clipboard

Explanation: This information message indicates that the CTDCLHST utility started the selection pass over the History User Report List file.

Corrective Action: No action is required.

CLHD7HI CHECK FOR ORPHANED SYSDATA RECORDS.

Explanation: This information message indicates that the CTDCLHST utility started the check for “orphaned” SYSDATA records.

Corrective Action: No action is required.

Messages CLHG00 through CLHGxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CLHG85E INVALID INPUT PARAMETER NOSYS=.Link copied to clipboard

Explanation: An invalid value was specified in the NOSYS parameter of the EXEC JCL statement activating the CTDCLHST utility, and was passed to the program. The only valid values are N, Y, or S.

The utility ends with a return code of 12.

Corrective Action: Correct the JCL, and rerun the job.

CLHG87I READING BACKUP CONTROL RECORDS.Link copied to clipboard

Explanation: This information message indicates that the CTDCLHST utility started reading backup control records.

Corrective Action: No action is required.

CLHG88I READING SYSDATA RECORDS.Link copied to clipboard

Explanation: This information message indicates that the CTDCLHST utility started reading SYSDATA records.

Corrective Action: No action is required.

CLHG89I `number` SYSDATA RECORDS READ.Link copied to clipboard

Explanation: This information message indicates the number of SYSDATA records read by the CTDCLHST utility from the History User Report List file.

Corrective Action: No action is required.

CLHG8BI DELETION OF THE SELECTED RECORDS.Link copied to clipboard

Explanation: This information message is issued by the CTDCLHST utility when it runs in PROD mode, and indicates that the utility started deleting selected records.

Corrective Action: No action is required.

CLHG8CI USER RECORD NOT FOUND FOR NOTEPAD RECORD `userId jobName` ODATE=`odate` RID=`recordId`Link copied to clipboard

Explanation: The CTDCLHST utility discovered a notepad record in the History User Reports List file without a matching USER record.

The variables in this message are:

userId
jobName
odate
recordId

The notepad record is deleted.

Corrective Action: Investigate the cause of this occurrence. It should not happen in a proper Control-D operation.

CLHG8DI SYSDATA RECORD NOT FOUND FOR USER RECORD `userId jobName` ODATE=`odate` RID=`recordId`Link copied to clipboard

Explanation: Unless NOSYS=N is requested in the CTDCLHST utility call, the utility scans all USER records in the History User Reports file and for each USER record, checks if there is a matching SYSDATA record. If a SYSDATA record is not found, this message is issued and the USER record is deleted.

The variables in this message are:

userId
jobName
odate
recordId

The USER record is deleted.

Corrective Action: Investigate the cause of this occurrence. It should not happen in a proper Control-D operation.

CLHG8EI SYSDATA RECORD NOT FOUND FOR INDEX RECORD `jobName` ODATE=`odate` RID=`recordId`Link copied to clipboard

Explanation: Running with parameter NOSYS=Y or NOSYS=S, the CTDCLHST utility scans all INDEX records in the History User Report List file and for each INDEX record, checks if there is a matching SYSDATA record in the file. This message indicates that the utility did find an INDEX record with no matching SYSDATA record. Such “orphan” INDEX records may appear in the History User Report List file as the result of situation described in message CLH943W.

The variables in this message are:

jobName
odate
recordId

The INDEX record and its related index file are deleted.

Corrective Action: Investigate the cause of this occurrence. It should not happen in a proper Control-D operation, except for the situation described in message CLH943W.

CLHG8FI USER RECORD NOT FOUND FOR SYSDATA RECORD `jobName` ID `jobId` ODATE=`odate` RID=`recordId`Link copied to clipboard

Explanation: Running with parameter NOSYS=S, the CTDCLHST utility found an “orphan” SYSDATA record in the History User Report List file. This means that a SYSDATA record is not referred to by any USER record in the file.

The variables in this message are:

jobName - the name of the job to which the orphaned SYSDATA record belongs
jobId - the MVS identifier of the job to which the orphaned SYSDATA record belongs
odate - originating date of the report to which the orphaned SYSDATA record belongs
recordId - the unique key of the orphaned SYSDATA record

The orphaned SYSDATA record will be removed from the History User Report List file in the next utility execution.

Corrective Action: No action is required.

CMEM MessagesLink copied to clipboard

This group includes messages for the Control-M Event Manager (CMEM) facility and the Control-O product.

Messages CMEMCxxLink copied to clipboard

This group includes messages for the Control-M Event Manager (CMEM) facility and the Control-O product.

CMEMCK5W THE IOAVAR DATABASE IS ALMOST FULL (percent FREE)Link copied to clipboard

Explanation: This message is issued to the CMEM or Control-O monitor when the IOAVAR database does not have enough memory space for additional IOA variables.

Corrective Action: Access the IV screen in MODE ADMIN and update the maximum number of rows for the IOAVAR database.

CMP MessagesLink copied to clipboard

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.

Messages CMP500 through CMP5xxLink copied to clipboard

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.

CMP541E DATASET `dsn` IS NOT CATALOGEDLink copied to clipboard

Explanation: The dsn data set specified in the PDS parameter in the scheduling table is not cataloged.

This message is issued by the New Day procedure.

The job or mission order is not issued. Processing continues to the next job or mission.

Corrective Action: Correct the parameters for this job or mission.

CMP542E DATASET `dsn` DOES NOT EXIST ON VOLUMELink copied to clipboard

Explanation: The dsn data set specified in the PDS parameter in the scheduling table appears in the catalog, but is not on the volume.

This message is issued by the New Day procedure.

The job or mission order is not issued. Processing continues to the next job or mission.

Corrective Action: Check the catalog, and recatalog the data set according to the current volume.

CMP543E DATASET `dsn` IS NOT A LIBRARY OR IS NOT MOVABLELink copied to clipboard

Explanation: The dsn data set specified in the PDS parameter in the scheduling table is not a movable partitioned data set.

This message is issued by the New Day procedure.

The job or mission order is not issued. Processing continues to the next job or mission.

Corrective Action: Correct the parameters of this job or mission.

CMP545E NEGATIVE FREE SPACE FOUND FOR DATASET `dsn`Link copied to clipboard

Explanation: An error has occurred in the calculation of free space in the library specified in the PDS parameter.

This message is issued by the New Day procedure.

Possible causes are:

VTOC error
Control-M or Control-D error

The job or mission order is not issued. Processing continues to the next job or mission.

Corrective Action: Use some other means to check the free space in the library. If necessary, have your system programmer call your INCONTROL administrator.

CMP547E ERROR IN SCHEDULE DATA - INVALID "MINIMUM"Link copied to clipboard

Explanation: The MINIMUM parameter contained nonnumeric characters. The production parameters have probably been incorrectly modified by an editor or by a program.

This message is issued by the New Day procedure.

The job or mission order is not issued. Processing continues with the next job or mission.

Corrective Action: Correct the parameters of the job or mission.

CND MessagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages CND600 through CND6xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

CND630S OPEN OF PARAMETER LIST FAILED. DDNAME "DACNDIN"Link copied to clipboard

Explanation: Open of control statements file failed (the DACNDIN DD statement in the IOACND utility or program).

Possible causes are:

The DACNDIN DD statement is missing.
The data set described by the DACNDIN DD statement does not exist, or cannot be opened for sequential read, or has a record length that is not 80.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job or the CLIST, and run it again.

CND631S INVALID FORMAT OF INPUT PARAMETERSLink copied to clipboard

Explanation: Severe syntax error in the parameters to the IOACND or CTMRELRS utilities.

The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.

Corrective Action: Correct the parameters and reactivate the utility.

CND632S INVALID DATE FORMATLink copied to clipboard

Explanation: There is an invalid date format in an ADD COND or DELETE COND statement, utility or the IOACND program. The date format should be mmdd or ddmm, depending on your site standard.

The utility stops executing with a condition code of 12. The condition is not added or deleted.

Corrective Action: Correct the parameters and reactivate utility.

CND633S INTERNAL ERROR IN IOACND. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: Internal error in the IOACND and CTMRELRS utilities.

The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.

Corrective Action: Call your IOA administrator for assistance.

CND634S OPEN OF PRINT FILE FAILED. DDNAME "DAPRINT"Link copied to clipboard

Explanation: Open of messages file failed (the IOACND and CTMRELRS utilities). Possible causes are:

The DAPRINT DD statement is missing.
The data set allocated to the DAPRINT DD statement cannot be opened for sequential write.

The utility stops executing with condition code of 12.

Corrective Action: Correct the JCL for the job or the CLIST and run it again.

CND635E INVALID FUNCTION. USE ADD/DELETE/CHECKLink copied to clipboard

Explanation: An invalid function was passed to the IOACND utility.

Valid functions are:

ADD
DELETE
CHECK

The utility stops executing with a condition code of 12. The condition is not added, deleted, or released.

Corrective Action: Correct the parameter syntax and reactivate.

CND636E INVALID FUNCTION OR FUNCTION NOT SUPPORTED YETLink copied to clipboard

Explanation: An attempt has been made to add or delete a Quantitative Resource or Control Resource using the IOACND utility. These are privileged operations for Control-M or Control-D support personnel.

The utility stops executing with a condition code of 12.

Corrective Action: Correct the parameter syntax and reactivate.

CND637E LOAD OF PROGRAM "CTMRS0" FAILEDLink copied to clipboard

Explanation: An attempt to load the CTMRS0 program failed.

Corrective Action: Check that the name of the load library is correct. If that does not solve the problem, contact your INCONTROL Administrator.

CND638E FUNCTION "RDIF" OF PROGRAM "CTMRS0" FAILEDLink copied to clipboard

Explanation: The IOACND utility failed in one of the initialization steps of the Control-M Resources file. Either the file accessed is not a valid Resources file, or the Resources file is being formatted.

The utility stops with a return code of 16.

Corrective Action: Ensure that the DARESF DD statement points to a valid resource file, and that the file is not corrupted.

CND639E ADD REQUESTED FOR AN EXISTING RESOURCE resourceLink copied to clipboard

Explanation: The IOACND utility was activated with a request to add a quantitative or control resource, but the resource already exists in the file.

The ADD request is not performed.

Corrective Action: Ensure that the utility is only activated with valid requests.

CND63BI WISH WI2232 IS ENABLED - UPPERCASING CONDITION NAMELink copied to clipboard

Explanation: This information message is generated by the IOACND utility when optional wish WI2232 is applied.

The IOACND utility translates a condition name from the PARM= parameter in the EXEC card of this utility to upper case.

Corrective Action: No action is required.

CNV MessagesLink copied to clipboard

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.

Messages CNVS00 through CNVSxxLink copied to clipboard

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.

CNVST1I CONTROL-M STATISTICS FILE CONVERSION STARTEDLink copied to clipboard

Explanation: This information message indicates that the conversion of the Control-M Statistics file for version 6.3 and later has begun.

Corrective Action: No action is required.

CNVST2I CONTROL-M STATISTICS FILE CONVERSION ENDEDLink copied to clipboard

Explanation: This information message indicates that the conversion of the Control-M Statistics file for version 6.3 and later has ended.

Corrective Action: No action is required.

CNVST3I STATISTICS FILE HAS BEEN SUCCESSFULLY CONVERTEDLink copied to clipboard

Explanation: This information message indicates that the Control-M Statistics file has been successfully converted from version 6. y.xx to version 6.3 format.

In this message, valid values for y are 0, 1, or 2.

Corrective Action: No action is required.

CNVST4E VSAM ERROR: DDNAME=`ddName` RC=`rc` REASON=`rsn` FUNCTION=`func`Link copied to clipboard

Explanation: A VSAM error occurred while attempting to convert the Control-M Statistics file to version 6.3 format. Consult the IBM manual Macro Instructions for Data Sets for an explanation of the return codes and reason codes.

Corrective Action: Correct the error and rerun the job.

CNVST5E STATISTICS FILE ALREADY CONVERTEDLink copied to clipboard

Explanation: The CTMCVSTT utility has been run against a Control-M Statistics file that is already in version 6.3 format.

Corrective Action: Do not run the CTMCVSTT utility.

COM MessagesLink copied to clipboard

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.

Messages COMF00 through COMFxxLink copied to clipboard

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.

COMF51I LOC SNDR `loc_sendr` INIT SESSION WITH RMT RCVR `rmt_recvr`Link copied to clipboard

Explanation: The loc_sendr local sender is trying to initiate a session with the rmt_rcvr remote receiver.

A session starts when the remote Gateway comes up.

Corrective Action: No action is required.

COMF52I LOC RCVR `loc_recvr` AWAITING SESSION WITH RMT SNDR `rmt_sendr`Link copied to clipboard

Explanation: The loc_recvr local receiver is waiting for a session to be initiated with the rmt_sendr remote sender.

A session starts when the remote Gateway comes up.

Corrective Action: No action is required.

COMF53I LOC SNDR `loc_sendr` NOW IN SESSION WITH RMT RCVR `rmt_recvr`Link copied to clipboard

Explanation: The loc_sendr local sender is now in a session with the rmt_recvr remote receiver.

Communication is established.

Corrective Action: No action is required.

COMF54I LOC RCVR `loc_recvr` INIT SESSION WITH RMT SNDR `rmt_sendr`Link copied to clipboard

Explanation: The loc_recvr local receiver is now in a session with the rmt_sendr remote sender.

Communication is established.

Corrective Action: No action is required.

COMF55E SERVER TYPE `x` FAILED IN `yyy`. RC = `rc`Link copied to clipboard

Explanation: An Application Server of type x has failed to perform service yyy.

The variables in this message are:

x - the type of Application Server
yyy - the problematical service Valid values are:

rc - the return code A value of 28 indicates communication recovery and is allowed.All other return codes are indicative of internal errors.

Corrective Action: If the value of rc is not 28, consult your INCONTROL administrator.

Messages COMG00 through COMGxxLink copied to clipboard

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.

COMG84I OPERATION WILL BE RE-ATTEMPTEDLink copied to clipboard

Explanation: The system will try again to perform an operation that failed.

This message follows other messages that provide details about an error that occurred.

Normal processing continues, and the system tries repeatedly to perform the operation until it succeeds, or until the retry limit is reached. When the retry limit is reached, the system tries to recycle the SNA channel only.

Corrective Action: No action is required.

COMG85I OPERATION WILL BE RE-ATTEMPTED AFTER ONE MINUTELink copied to clipboard

Explanation: A failed operation will be retried until the retry limit is reached. This message follows other messages that provide details about an error that occurred.

The failed operation is retried. When the retry limit is exceeded, an attempt is made to recycle communication.

Corrective Action: No action is required.

COMG89W APPCCMD `appccmd` FAILED. APPLID=`applId` R15=`r15` R0=`r0` RPL6RC=`rc` PARTNER LU=`partner_lu`Link copied to clipboard

Explanation: An APPC command has failed. The reason for the failure may be temporary, such as a shortage of storage.

This message is followed by the COMG84I message, indicating the action that will be taken by the Control-M NJE Gateway.

This message may be preceded by another message that provides more information about the error that occurred.

The following information in this message is for the VTAM system programmer:

appccmd - the command that failed
applId - the identity of the application that issued the command that failed
r15 - the value in Register 15 returned by VTAM
r0 - the value in Register 0 returned by VTAM
rc - the RPL6RC return code returned by VTAM

The following fields are documented in the VTAM Programming for LU 6.2 Manual:

APPCCMD - in the section on LU 6.2 macro instruction syntax and operands
RPL6RC - in the appendix on return codes
R0 and R15 - in the section on handling errors

Corrective Action: If a second message gives a probable cause for the error, proceed according to the User Response recommended in that message. Otherwise, contact your VTAM system programmer.

COMG90E APPCCMD `appccmd` FAILED. APPLID=`applId` R15=`r15` R0=`r0` RPL6RC=`rc` PARTNER LU=`partner_lu` Link copied to clipboard

Explanation: An APPC command failed.

This message is followed by a message indicating the action that will be taken by the Control-M NJE Gateway.

This message may be preceded by another message that provides more information about the error that occurred.

The following information in this message is for the VTAM system programmer:

appccmd - the command that failed
applId - the identity of the application that issued the command that failed
r15 - the value in Register 15 returned by VTAM
r0 - the value in Register 0 returned by VTAM
rc - the RPL6RC return code returned by VTAM

The following fields are documented in the VTAM Programming for LU 6.2 Manual:

APPCCMD - in the section on LU 6.2 macro instruction syntax and operands
RPL6RC - in the appendix on return codes
R0 and R15 - in the section on handling errors

Corrective Action: If a second message gives a probable cause for the error, proceed according to the User Response recommended in that message. Otherwise, contact your VTAM system programmer.

CON MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages CON200 through CON2xxLink copied to clipboard

This group includes messages for the Control-O product.

CON220I CONTROL-O ALLOCATED `num` SUBSYSTEM CONSOLESLink copied to clipboard

Explanation: During Control-O initialization, Control-O allocated num subsystem consoles for use by the DO COMMAND with WAITRESP Y. The number num must be equal to the value of the NUMCONS parameter in the CTOPARM member in the IOA PARM library.

Control-O acquires the allocated subsystem consoles and uses them for the DO COMMAND with RESPMODE set to Y.

Corrective Action: If the value of num is less than the value defined in CTOPARM by the NUMCONS=num statement, define more subsystem consoles in the system. For information on how to do this, see the description of the NUMCONS parameter in CTOPARM and subsystem consoles in the Control-O Installation chapter of the INCONTROL for z/OS Installation Guide.

CON221I CONTROL-O RELEASED THE SUBSYSTEM CONSOLESLink copied to clipboard

Explanation: This information message is the normal message issued during Control-O termination if subsystem consoles were allocated.

The subsystem consoles that were allocated to Control-O are freed during termination of the Control-O monitor.

Corrective Action: No action is required.

CON222W NO SUBSYSTEM CONSOLES ARE AVAILABLE FOR CONTROL-OLink copied to clipboard

Explanation: Control-O could not allocate subsystem consoles during initialization, as specified in the NUMCONS parameter in the CTOPARM member.

No subsystem consoles are allocated.

Corrective Action: Define a sufficient number of MVS consoles for Control-O use. If other products use a subsystem console, calculate the number of subsystem consoles required for all products. For more information, see the chapter on Control-O installation in the INCONTROL for z/OS Installation Guide, and the relevant MVS manuals.

CON223W INSUFFICIENT NUMBER OF CONSOLES ARE AVAILABLE FOR CONTROL-OLink copied to clipboard

Explanation: Control-O attempted to allocate subsystem consoles during initialization, but not enough consoles are available.

All the available subsystem consoles are allocated by Control-O. This message is followed by the CON220I message, which details how many consoles were allocated for Control-O use.

Corrective Action: Decrease the number of consoles required for Control-O (the NUMCONS parameter in CTOPARM), or define a sufficient number of consoles for Control-O use in MVS. If other products use a subsystem console, calculate the number of subsystem consoles required for all products. For more information, see the chapter on Control-O installation in the INCONTROL for z/OS Installation Guide, and the relevant MVS manuals.

CON224E ERROR IN SUBSYSTEM CONSOLE SERVICE ROUTINE. FUNCTION=`func` RC=`rc`. A SNAP IS PRODUCEDLink copied to clipboard

Explanation: Control-O attempted to perform an OBTAIN or RELEASE function on a subsystem console. The subsystem console service routine failed to perform the requested function.

The system action varies, depending on whether Control-O was initializing or terminating at the time of its issue, as follows:

If the message was issued during Control-O initialization, Control-O does not use subsystem consoles.
If the message was issued during Control-O termination, Control-O stops releasing the subsystem consoles. If not all the subsystem consoles were released, they remain allocated until a new Control-O monitor is started or until an IPL is performed.

In either event, snap dumps are produced with the relevant control blocks.

Corrective Action: Save the snap dumps and call your INCONTROL administrator for assistance.

CON225E INSUFFICIENT STORAGE FOR THE CONSOLE `func` FUNCTIONLink copied to clipboard

Explanation: There is insufficient storage in the Control-O address space to perform the OBTAIN or RELEASE subsystem console function.

The system action varies, depending on whether Control-O was initializing or terminating at the time of its issue, as follows:

If the message was issued during Control-O initialization, Control-O does not use subsystem consoles.
If the message was issued during Control-O termination, Control-O stops releasing the subsystem consoles. If not all the subsystem consoles were released, they remain allocated until a new Control-O monitor is started or until an IPL is performed.

Corrective Action: Increase the region size specified in the Control-O procedure.

CON226E INSUFFICIENT STORAGE IN (EXTENDED) CSA. CANNOT ALLOCATE SUBSYSTEM CONSOLESLink copied to clipboard

Explanation: This message is issued during Control-O initialization when there is insufficient space in CSA or ECSA for Control-O console-related control blocks.

Control-O initialization continues without using subsystem consoles.

Corrective Action: Check if the storage defined for CSA or ECSA is large enough. If not, increase the CSA or ECSA size.

CON227E ERROR IN SUBSYSTEM CONSOLE PROCESSING. REQUEST=`reqCode` FUNCTION=`func` ERRCODE={`abCode`|`rsn`}Link copied to clipboard

Explanation: The subsystem console service routine abended when attempting to perform the OBTAIN or RELEASE function for a subsystem console, and the function was not performed or was performed partially.

The system action varies, depending on whether Control-O was initializing or terminating at the time of its issue, as follows:

If the message was issued during Control-O initialization, Control-O will not use subsystem consoles.
If the message was issued during Control-O termination, Control-O stops releasing the subsystem consoles. If all the subsystem consoles were not released, they remain allocated until a new Control-O monitor is started or until an IPL is performed.

Abend and snap dumps are produced.

Corrective Action: Save the abend and snap dumps and call your INCONTROL administrator for assistance.

CON228I CONTROL-O ALLOCATED `num` EMCS CONSOLESLink copied to clipboard

Explanation: This information message indicates that Control-O allocated a total of num EMCS CONSOLES according to the definitions in the CTOPARM member.

Corrective Action: No action is required.

CON229I CONTROL-O ALLOCATED `num` EMCS CONSOLES WITH MIG IDSLink copied to clipboard

Explanation: This information message indicates that Control-O allocated a total of num EMCS CONSOLES with migration IDs according to the definitions in the CTOPARM member.

Corrective Action: No action is required.

CON22AE CONTROL-O ALLOCATED EMCS CONSOLE ERROR. IOAMCS RC=`rc` REASON=`rsn` CONSOLE=`consoleName`Link copied to clipboard

Explanation: Control-O failed to allocate an EMCS CONSOLE. The MCSOPER service ended with an error. When this happens, Control-O attempts to allocate an EMCS CONSOLE in order to issue a command or message. However, the attempt failed.

Control-O ignores the console.

Corrective Action: Do the following:

Record the return code (rc), reason number (rsn), and console name (consolname). For information about MCSOPER, see the manual for the IBM authorized macro services.
Correct the definitions of the EMCS CONSOLE in the CTOPARM EMCSCONS.
STOP the Control-O monitor and start a new monitor.

CON22BE CONTROL-O ALLOCATED EMCS CONSOLE ERROR. CONVCON RC=`rc` REASON=`rsn` CONSOLE=`consoleName`Link copied to clipboard

Explanation: Control-O failed to allocate an EMCS CONSOLE. The CONVCON service ended with an error. When this happens, Control-O tries to allocate an EMCS CONSOLE in order to issue a command or message. However, the attempt failed.

Control-O ignores the console.

Corrective Action: Do the following:

Record the return code (rc), reason number (rsn), and console name (consoleName). For information about CONVCON, see the manual for the IBM authorized macro services.
Correct the definitions of the EMCS CONSOLE in the EMCSCONS parameter in the CTOPARM member.
STOP the Control-O monitor and start a new monitor

COP MessagesLink copied to clipboard

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.

Messages COP0 through COP0xxLink copied to clipboard

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.

COP040S OPEN OF NEW ACTIVE JOBS FILE FAILEDLink copied to clipboard

Explanation: The CTMCAJF Control-M utility, which is used to copy the Active Jobs file to a new file, failed to open the file.

Possible causes are:

The DACKPTN DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

COP041I NEW ACTIVE JOBS FILE SUCCESSFULLY CREATEDLink copied to clipboard

Explanation: This information message indicates that the CTMCAJF utility has successfully copied the Active Jobs file.

Corrective Action: No action is required.

COP042S OPEN OF PARAMETERS FILE FAILED. DDNAME "DACOPPRM"Link copied to clipboard

Explanation: Open of the utility parameters file failed for the DACOPPRM DD statement, the CTMCAJF utility.

Possible causes are:

The DACOPPRM DD statement is missing.
The data set described by the DACOPPRM DD statement cannot be opened for sequential read.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

COP043S REQUIRED OPERATION CANNOT BE PERFORMED BECAUSE THE CONTROL-M MONITOR IS ACTIVELink copied to clipboard

Explanation: An attempt has been made to run the CTMCAJF utility or an AJF update function in utility IOAVERFY (DIAGNOSE CORRECT, ZAP, VERIFY ENQ) while the Control-M monitor is active. Maintenance of the Control-M Active Jobs file can be performed only when the Control-M monitor is not active.

A Control-M monitor is determined to be active by utilizing the enqueue management mechanism to enquire whether the QNAME of the monitor is in use. If the QNAME is not in use, the monitor is down.

Corrective Action: Shut down the Control-M monitor. Read the instructions for the utilities CTMCAJF and IOAVERFY (whichever applies) in the Control-M for z/OS User Guide.

COP044S YOU CANNOT COPY THE ACTIVE JOBS FILE TO ITSELFLink copied to clipboard

Explanation: The input and output DD statements point to the same Active Jobs file. The user attempted to copy the Active Jobs file to itself.

The CTMCAJF utility ends with an error.

Corrective Action: Correct the JCL and rerun utility.

COP049I NEW HISTORY JOBS FILE SUCCESSFULLY CREATEDLink copied to clipboard

Explanation: This information message indicates that the CTMHCOP utility successfully created a new History Jobs file from the old one.

Corrective Action: No action is required.

Messages COPB00 through COPBxxLink copied to clipboard

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.

COPB40S OPEN OF NEW ACTIVE MISSION FILE FAILEDLink copied to clipboard

Explanation: The CTDCAMF Control-D utility, which is used to copy the Active Missions file to a new file, failed to open the file.

Possible causes are:

The DAAMFN DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

COPB41I NEW ACTIVE MISSION FILE SUCCESSFULLY COPIEDLink copied to clipboard

Explanation: This information message indicates that the CTDCAMF utility has successfully copied the Active Missions file.

Corrective Action: No action is required.

COPB42S OPEN OF PARAMETERS FILE FAILED. DDNAME "DACOPPRM"Link copied to clipboard

Explanation: Open of the utility parameters file failed (the DACOPPRM DD statement). This message is issued by the CTDCAMF utility.

Possible causes are:

The DACOPPRM DD statement is missing.
The data set described by the DACOPPRM DD statement cannot be opened for sequential read.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

COPB43S REQUIRED OPERATION CANNOT BE PERFORMED BECAUSE THE CONTROL-D MONITOR IS ACTIVELink copied to clipboard

Explanation: An attempt was made to run the CTDCAMF utility while the Control-D monitor was active. Maintenance of the Control-D Active Missions file can be performed only when the Control-D monitor is not active.

The utility terminates with a condition code of 08.

Corrective Action: Shut down the Control-D monitor. If you are using the COPY function, refer to the description of the CTDCAMF utility in the Control-D and Control-V User Guide.

COPB44S YOU CANNOT COPY THE ACTIVE MISSION FILE TO ITSELFLink copied to clipboard

Explanation: The CTDCAMF utility is attempting to copy the Active Missions file to itself.

The utility terminates with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

COPB45I CONTROL-D ACTIVE MISSIONS FILE IS COPIED TO BACKUP FILELink copied to clipboard

Explanation: This information message is the normal start message of the CTDCAMF utility for the COPY option.

Corrective Action: No action is required.

COPB46I COMPRESSING OF CONTROL-D ACTIVE MISSIONS FILE STARTEDLink copied to clipboard

Explanation: This information message is the normal start message of the CTDCAMF utility for the COMPRESS option.

Corrective Action: No action is required.

COPB47I COMPRESSING OF CONTROL-D ACTIVE MISSIONS FILE ENDEDLink copied to clipboard

Explanation: This information message is the normal termination message of utility CTDCAMF for the COMPRESS option.

Corrective Action: No action is required.

COPB48S ERROR WHILE COMPRESSING ACTIVE MISSIONS FILE, FILE WAS NOT COMPRESSEDLink copied to clipboard

Explanation: The CTDCAMF Control-D utility failed.

Possible causes are:

The DAAMF DD statement is missing.
The data set described by the DD statement is not the Control-D Active Missions file.
The data set described by the DAAMF DD statement is the Control-D Active Missions file, but for another Control-D monitor or from a different Control-D version.
The DABKUP DD statement is missing.
The SYSPRINT DD statement is missing. See the CTM913S message.

Utility terminates with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

Messages COPC00 through COPCxxLink copied to clipboard

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.

COPC56S PREVIOUS FORMAT OF ACTIVE JOBS FILE ABENDEDLink copied to clipboard

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.

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

COPC57S TARGET ACTIVE JOBS FILE IS NOT A NEWLY FORMATTED FILELink copied to clipboard

Explanation: The target Active Jobs file should not be used before it is formatted by the FORMCKP procedure.

The copy program terminates with a condition code of 08.

Corrective Action: Format the Active Jobs file using the FORMCKP procedure.

COPC58S TARGET ACTIVE JOBS FILE IS NOT LARGE ENOUGHLink copied to clipboard

Explanation: The target Active Jobs file is not large enough to contain the source Active Jobs file.

The copy program terminates with a condition code of 08.

Corrective Action: Reallocate and reformat the new Active Jobs file.

COPC59I `num` JOBS WERE DELETED FROM THE ACTIVE JOBS FILELink copied to clipboard

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

COPC5AE UNABLE TO DELETE JOBS FROM THE ACTIVE JOBS FILELink copied to clipboard

Explanation: The CLEANUP function of the CTMCAJF utility was unable to delete the jobs from the Active Jobs file probably because the Control-M monitor was down. The CLEANUP function must run simultaneously with the Control-M monitor and the same Active Jobs file must be allocated to both the monitor and the batch utility job. Do not shut down the monitor when running the utility with this function.

Corrective Action: Ensure that the Control-M monitor is up and allocates the same Active Jobs file and then re-run the utility.

COPC67I `jobName` DELETED FROM THE ACTIVE JOBS FILELink copied to clipboard

Explanation: This information message identifies a job that was 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. Whenever a job is deleted, this message is issued.

The Control-M/Enterprise Manager (Control-M/EM) Mainframe Gateway shuts down.

Corrective Action: Correct the JCL for the Control-M/EM Gateway and restart it.

COPC69S EXECUTION STOPS DUE TO CONTROL-M MONITOR NOT RUNNINGLink copied to clipboard

Explanation: The CLEANUP function of the CTMCAJF utility stops because the Control-M monitor is not running. The CLEANUP function of the CTMCAJF utility can run only when the Control-M monitor is running.

The CTMCAJF utility terminates.

Corrective Action: BMC recommends the following:

If Control-M is down, run the CTMCAJF utility with the COMPRESS function.
If Control-M is up, run the CTMCAJF utility with the CLEANUP function.

COPC70S ACTIVE JOBS FILE (CKP) SIZE - PARM TABLE MISMATCHLink copied to clipboard

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

Corrective Action: Ask your INCONTROL administrator to determine the cause of the discrepancy in the CKPSIZE value, and correct the error.

COPC75S COMPRESS AND CLEANUP ARE NOT ALLOWED FOR HISTORY FILE PROCESSINGLink copied to clipboard

Explanation: The COMPRESS and CLEANUP parameters may not be specified when using the CTMHCOP procedure to copy or expand the History Jobs file. Only the COPY parameter can be used.

The CTMHCOP utility terminates with a return code of 8.

Corrective Action: Use the COPY parameter to copy or expand the History Jobs file.

COS MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages COS600 through COS6xxLink copied to clipboard

This group includes messages for the Control-O product.

COS620I CONTROL-O COSMOS INITALIZATION STARTED. CTOCOS `release` APAR `apar`Link copied to clipboard

Explanation: Control-O issues the message when starting the Control-O Status Monitoring System (COSMOS) and displays the version and the level of the COSMOS main module CTOCOS.

Corrective Action: No action is required.

COS621I CONTROL-O COSMOS STARTEDLink copied to clipboard

Explanation: This information message indicates that the Control-O Status Monitoring System (COSMOS) has been started in response to an operator command or as part of the Control-O startup process.

Corrective Action: No action is required.

COS622S CONTROL-O COSMOS TERMINATION ERRORLink copied to clipboard

Explanation: COSMOS terminated after an error was detected. This message is accompanied by other messages which explain the cause of the error.

COSMOS ends with errors.

Corrective Action: Examine the accompanying messages for the cause of the problem, and correct it as appropriate.

COS623I CONTROL-O COSMOS ENDEDLink copied to clipboard

Explanation: This information message indicates COSMOS terminated in response to an operator command or as part of the Control-O shutdown process.

Corrective Action: No action is required.

COS624S OPEN OF DDNAME `ddName` FAILEDLink copied to clipboard

Explanation: COSMOS was unable to open the file referenced by the ddName DD statement.

Possible causes are:

The ddName DD statement is misspelled.
The data set (member) described by the ddName DD statement does not exist.

COSMOS ends with errors.

Corrective Action: Check the Control-O starting procedure JCL to verify that the DD statement and the file referenced by it exist.

COS625S READ ERROR FOR `ddName`Link copied to clipboard

Explanation: COSMOS is unable to read the file referenced by the ddName DD statement.

Possible causes are:

The ddName DD statement is misspelled.
The data set (member) described by the ddName DD statement does not exist.

COSMOS ends with errors.

Corrective Action: Check that the appropriate file name is referenced correctly.

COS626S CONTROL-O COSMOS INITIALIZATION ERRORLink copied to clipboard

Explanation: An error was detected during COSMOS initialization. This message is accompanied by other messages that describe the error that occurred.

COSMOS shuts down.

Corrective Action: Examine the accompanying messages for more information about the initialization error.

COS627S CONTROL-O COSMOS MISSING OBJECT PLBLink copied to clipboard

Explanation: The pool of AutoEdit variables containing the Objects cannot be found. A search is made for this pool during COSMOS initialization.

COSMOS shuts down.

Corrective Action: Check if the object pool defined in the COSMOLST member was defined in DAGLBLST and exists in memory.

COS628S CONTROL-O COSMOS MISSING METHOD PLBLink copied to clipboard

Explanation: The pool of AutoEdit variables containing the Methods cannot be found. A search is made for this pool during COSMOS initialization.

COSMOS shuts down.

Corrective Action: Check if the method pool defined in the COSMOLST member was defined in DAGLBLST and exists in memory.

COS629S CONTROL-O COSMOS MISSING PREREQ PLBLink copied to clipboard

Explanation: The pool of AutoEdit variables containing the Prerequisites cannot be found. A search is made for this pool during COSMOS initialization.

COSMOS shuts down.

Corrective Action: Check if the prerequisites pool defined in the COSMOLST member was defined in DAGLBLST and exists in memory.

COS630S CONTROL-O COSMOS GETMAIN ERROR FOR CDTLink copied to clipboard

Explanation: COSMOS failed to acquire storage for the CDT control block. CDT is a required internal control block for COSMOS.

COSMOS shuts down.

Corrective Action: Check if the storage defined for the ECSA (Extended Common Service Area) is large enough. If not, increase the ECSA size.

COS631S CONTROL-O COSMOS GETMAIN ERROR FOR RESTEXTLink copied to clipboard

Explanation: COSMOS subtask failed to allocate a working area.

COSMOS terminated. Control-O continues to operate.

Corrective Action: Check MVS GETMAIN messages that appear in the SYSLOG and try to solve the problem.

COS632S CONTROL-O COSMOS POOL `poolname` WAS NOT LOADED GLOBAL VARIABLE DATABASE.Link copied to clipboard

Explanation: COSMOS subtask tries to initiate the COSMOS environment but the pool was not loaded.

COSMOS terminated. Control-O continues to operate.

Corrective Action: Do the following:

Check that the pool name is correct in COSMOLST and if not, correct it. If the pool name is missing, add it to the DAGLBLST, then load the pool name.
Check that pool name is in the DAGLBLST and its characteristics are correct.

If the pool name's characteristics are incorrect stop and start the Control-O monitor. After correcting the error you can restart COSMOS.

COS633S CONTROL-O COSMOS POOL `poolname` MAX ROW IS ZERO.Link copied to clipboard

Explanation: COSMOS subtask tries to initiate the COSMOS environment but the pool cannot be used by COSMOS because it cannot contain any data.

COSMOS terminated. Control-O continues to operate.

Corrective Action:Correct the pool definition in IOA Global Variable Database then load it again using LOADGLOBAL=poolname modify command.

COS634I CONTROL-O COSMOS HEADER MODE=`mode` PRE-REQUISITE=`poolname` OP-FLAGS=`flags` FSM-FLAGS=`flags`Link copied to clipboard

Explanation: COSMOS subtask displays record type "H" from COSMOLST.

MODE=mode - default status of COSMOS' objects

PRE-REQUISITE=poolname - name of prerequisite pool

OP-FLAGS=flags - COSMOS operation flags

FSM-FLAGS=flags - COSMOS control flags

For details on the flags, refer to the Control-O/COSMOS User Guide

Corrective Action:No action is required.

COS635I CONTROL-O COSMOS OBJECTS `source_pool-operating_pool` METHOD `method` MODE=`mode` UP=`up` DOWN=`down` UNKNOWN=`unknown`Link copied to clipboard

Explanation: COSMOS subtask displays record type "T" from COSMOLST.

OBJECTS source_pool-operating_pool - name of COSMOS source and its operating pool name

METHOD method - method's pool name for objects of this pair of pools

MODE=mode - default mode for objects of this pair of pools

UP=up - the code used in this pool pair to represent the UP state

DOWN=down - the code used in this pool pair to represent the DOWN state

UNKNOWN=unknown - the code used in this pool pair to represent the UNKNOWN state

Corrective Action:No action is required.

COS636I CONTROL-O COSMOS SYSTEMS a b c d e f gLink copied to clipboard

Explanation: COSMOS subtask displays record type "C" from COSMOLST.

a-g are the system names in the record

Corrective Action:No action is required.

COS637S CONTROL-O COSMOS SYSTEM `system` IS NOT IN COSMOS SYSTEMS LISTLink copied to clipboard

Explanation: COSMOS subtask displays the started system whose name is not included in record type "C" from COSMOLST.

COSMOS terminated. Control-O continues to operate.

Corrective Action:Add the started system to record type "C" in COSMOLST. Start COSMOS again.

Messages COSF00 through COSFxxLink copied to clipboard

This group includes messages for the Control-O product.

COSFSM `xx` CONTROL-O/COSMOS `Internal Message`Link copied to clipboard

Explanation: This is an internal message used by the Control-O/COSMOS rule with the same name as the message ID. For more information about the relevant rule, see the component details chapter of the Control-O/COSMOS User Guide.

Corrective Action: No action is required.

CPA MessagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages CPA800 through CPA8xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CPA881I COPYING PERMANENT USER FILE TO ACTIVE USER FILE STARTED WITH ODATE=`odate`Link copied to clipboard

Explanation: This information message indicates that the CTDCP2A utility is copying the list of reports from the Permanent User Report List file to the Active User Report List file.

Corrective Action: No action is required.

CPA882I COPYING PERMANENT USER FILE TO ACTIVE USER FILE ENDED OKLink copied to clipboard

Explanation: This information message indicates that the CTDCP2A utility has finished copying the list of reports from the Permanent User Report List file to the Active User Report List file. This is a normal end message for the CTDCP2A utility.

Corrective Action: No action is required.

CPA884S COPYING PERMANENT USER FILE TO ACTIVE USER FILE ENDED WITH ERRORSLink copied to clipboard

Explanation: An error occurred during the execution of the CTDCP2A utility.

Corrective Action: A previous message should describe the error.

CPA885E INVALID DATE SUPPLIED IN THE PARM FIELDLink copied to clipboard

Explanation: The content of the date parameter passed to the CTDCP2A utility is invalid. The valid format is ddmmyy or mmddyy.

Corrective Action: Correct the date, and rerun the CTDCP2A utility.

CPA886I COPIED TO ACTIVE USER FILE `userName jobName cat fromUser reportName`Link copied to clipboard

Explanation: This information message indicates that a record was successfully copied from the Permanent Report List file to the Active Report List file. The CTDCP2A utility issues this message for each record successfully copied from the Permanent Report List file.

Corrective Action: No action is required.

CPA887I TOTAL NUMBER OF RECORDS COPIED TO ACTIVE USER FILE IS: `num`Link copied to clipboard

Explanation: This information message displays the total number of records copied from the Permanent User Report List file to the Active User Report List file. The CTDCP2A utility issues this message after copying all records that satisfy the selection criteria.

Corrective Action: No action is required.

CPA888I ACTION USER JOB CATEGORY FROM USER REPORT NAMELink copied to clipboard

Explanation: This information message is issued by the CTDCA2P utility as a heading line for message CPA886I.

The CTDCA2P utility copies new user, job, report, and category entries from the Active User Report List file to the Permanent User Report List file.

Corrective Action: No action is required.

CPA889I `userName jobName reportName cat`Link copied to clipboard

Explanation: This information message is issued by the CTDCP2A utility.

The CTDCA2P utility copies new user, job, report, and category entries from the Active User Report List file to the Permanent User Report List file.

The variables in this message relate to the record copied to the Active User file, as follows:

userName - the identity of the user
jobName - the identity of the job
reportName - the identity of the report
cat - the category

Corrective Action: No action is required.

CPR MessagesLink copied to clipboard

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.

Messages CPR800 through CPR8xxLink copied to clipboard

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.

CPR846S INSUFFICIENT SPACE FOR `type cond odate`Link copied to clipboard

Explanation: The output IOA Conditions file has insufficient space for all the prerequisite conditions from the input file. The combination of the LRECL parameter with the CNDREC# parameter is smaller in the output file than in the input file, and some prerequisite conditions in the input file could not be copied to the output file.

The variables in this message are:

type - type of condition
cond - condition name
odate - original date

The conversion or copy of the file stops. The content of the output file is unpredictable.

Corrective Action: Create a larger output file and run the utility again.

CPS MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages CPS400 through CPS4xxLink copied to clipboard

This group includes messages for the Control-O product.

CPS421I CTOCPS STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTOCPS program, which compresses or verifies the Global AutoEdit library, started.

Corrective Action: No action is required.

CPS422S COMPRESS REQUIRED FOR GLOBAL AUTOEDIT VARIABLES LIBRARYLink copied to clipboard

Explanation: The Global AutoEdit library needs to be compressed but automatic compression was disabled. Control-O does not automatically compress the Global AutoEdit library because N is specified for the GLBCOMP parameter in the CTOPARM member.

The library is not compressed. The WRITEGLOBAL command fails.

Corrective Action: Do one of the following:

Use site compression procedures to compress the Global AutoEdit library.
Ensure that the Global AutoEdit library is large enough to prevent D37 abends between periodic compressions.

For information on how to set automatic compression, see the Control-O chapter in the INCONTROL for z/OS Installation Guide.

CPS423S DYNAMIC ALLOCATION ERROR DURING COMPRESS, ERROR=`rc/rsn/dsn`Link copied to clipboard

Explanation: Dynamic allocation (SVC 99) failed. The CTOCPS program uses SVC 99 to dynamically allocate and deallocate the Global AutoEdit library and its copy file.

The variables in this message are:

rc - the return code of the error
rsn - the reason for the failure
dsn - the name of the data set that cannot be allocated

The CTOCPS program ends with a return code of 08. The WRITEGLOBAL command fails.

Corrective Action: For an explanation of the return code (rc) and the reason code (rsn), see the IBM manual MVS Programming: Authorized Assembler Services Guide. Until this problem is resolved, use site compression procedures to compress the Global AutoEdit library.

CPS424I FIRST COMPRESSION PHASE STARTED - LIBRARY UNLOADLink copied to clipboard

Explanation: This information message indicates that the backup phase of the CTOCPS program has begun.

Corrective Action: No action is required.

CPS425I SECOND COMPRESSION PHASE STARTED - COMPRESS IN PLACELink copied to clipboard

Explanation: This information message indicates that the compress in place phase of the CTOCPS program has begun.

Corrective Action: No action is required.

CPS426I CTOCPS ENDEDLink copied to clipboard

Explanation: This information message indicates that the CTOCPS program has successfully completed compressing the Global AutoEdit library.

Corrective Action: No action is required.

CPS427S IEBCOPY RETURNED A NON-ZERO COMPLETION CODELink copied to clipboard

Explanation: IEBCOPY could not complete its task. IEBCOPY is invoked internally by the CTOCPS program to copy or compress a data set.

The CTOCPS program ends with a return code of 08. The WRITEGLOBAL command fails.

Corrective Action: If your system programmer can not resolve the problem, contact your INCONTROL administrator. Until this problem is resolved, use site compression procedures to compress the Global AutoEdit library.

CPS428S CTOCPS RECEIVED AN INVALID PARAMETER LISTLink copied to clipboard

Explanation: The CTOCPS program received a parameter list with an unexpected format. This message indicates an internal error.

The CTOCPS program ends with a return code of 08. The WRITEGLOBAL command fails.

Corrective Action: Contact BMC Customer Support. Until this problem is resolved, use site compression procedures to compress the Global AutoEdit library.

CPS429S PREVIOUS COMPRESS FAILED. GLOBAL LIBRARY CANNOT BE RESTORED FROM BACKUPLink copied to clipboard

Explanation: Compression cannot be performed because the Global AutoEdit library was corrupted during the last compression and no valid backup exists.

During CTOCPS processing, the $$COMPST control member is repeatedly updated to track completed operations. The contents of this control member indicate that the last time CTOCPS ran, Control-O did not successfully compress the Global AutoEdit library. As a result, there is no usable backup. Therefore, the Global AutoEdit library cannot be restored.

Control-O stops loading Global variables.

Corrective Action: If you are unable to restore the Global AutoEdit library, run the NEWGLOB job, which renames the corrupted Global AutoEdit library, and creates a new one with the old name using Global variable information from memory. If necessary, you can use the TAILOR JOB option available from ICE by selecting Maintain your Environment => ICE refresh=> OPTION 3.

For more information, see the section on automatic compression of the global AutoEdit library in the INCONTROL for z/OS Administrator Guide.

CPS430S ERROR READING AUTO-COMPRESS CONTROL-MEMBER $$COMPSTLink copied to clipboard

Explanation: The CTOCPS program was unable to read the $$COMPST control member. The $$COMPST control member is defined by the NEWGLOB job during installation of Control-O. The CTOCPS program checks the $$COMPST control member to determine if the last automatic compression was successfully completed.

The CTOCPS program ends with a return code of 08. The READGLOBAL and WRITEGLOBAL commands are ignored.

Corrective Action: Ensure that the $$COMPST control member exists in the Global AutoEdit library, and if the NEWGLOB job was not run during installation, submit this job. If the problem is not resolved, contact your INCONTROL administrator.

CPS431S ERROR WRITING AUTO-COMPRESS CONTROL-MEMBER $$COMPSTLink copied to clipboard

Explanation: The CTOCPS program was unable to write the $$COMPST control member. The $$COMPST member is defined by the NEWGLOB job during installation of Control-O.

The CTOCPS program ends with a return code of 08.

CPS432I RESTORE OF GLOBAL VARIABLES LIBRARY STARTEDLink copied to clipboard

Explanation: This information messages indicates that the CTOCPS program has begun restoring the Global AutoEdit library. The CTOCPS program was unable to read the Global AutoEdit library, but the backup file is intact.

CTOCPS restores the Global AutoEdit library from the backup file.

Corrective Action: No action is required.

CPS433S ABEND `abCode` INTERCEPTED DURING COMPRESSLink copied to clipboard

Explanation: The ESTAE recovery routine intercepted an abend during execution of a READGLOBAL or WRITEGLOBAL command.

The READGLOBAL or WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the names of the Global AutoEdit library and the backup copy. If these libraries are corrupt (for example, by a disk crash), restore them from a backup.

CPS434I COMPRESS OF GLOBAL VARIABLES LIBRARY STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTOCPS program has begun compressing the Global AutoEdit library.

Corrective Action: No action is required.

CRR MessagesLink copied to clipboard

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.

Messages CRR100 through CRR1xxLink copied to clipboard

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.

CRR101S LCT EXCEEDED MAXIMUM NUMBER OF ENTRIES (10000)Link copied to clipboard

Explanation: An attempt was made to add an entry to the Local Command Table (LCT), an internal program table, but it already contains the maximum number of allowable entries.

Control-M Extended MCS tracking is stopped.

Corrective Action: Examine the SPY289E message, which always accompanies this message, and proceed accordingly.

CRR102S JNF EXCEEDED MAXIMUM NUMBER OF ENTRIES (10000)Link copied to clipboard

Explanation: An attempt was made to add an entry to the Job Not Found Table (JNF), an internal program table, but it already contains the maximum number of allowable entries.

Control-M Extended MCS tracking is stopped.

Corrective Action: Examine the SPY289E message, which always accompanies this message, and proceed accordingly.

CRS MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages CRS900 through CRS9xxLink copied to clipboard

This group includes messages for the Control-O product.

CRS931I CLEAN FOR IOA CONDITIONS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOACLCND utility started.

Corrective Action: No action is required.

CRS932I CLEAN FOR IOA CONDITIONS FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the cleaning of the IOA Conditions file by the IOACLCND utility ended successfully.

Corrective Action: No action is required.

CRS933S FILE ALLOCATED TO DDNAME "DASINC" IS NOT IOA SYNCHRONIZATION FILELink copied to clipboard

Explanation: The data set described by the DASINC DD statement is not IOA Synchronization file. This message is produced by the IOACLCND IOA utility.

Possible causes are:

The file allocated to the DASINC DD statement is not the Synchronization file.
The file allocated to the DASINC DD statement is the Synchronization file, but it is of a different version or of a different IOA installation.

The utility stops executing.

Corrective Action: Correct the JCL for the job.

CRS934E INVALID PARAMETER: - `parm`Link copied to clipboard

Explanation: An invalid parameter was passed to the IOACLCND utility.

In this message, parm identifies the invalid parameter.

For a list of valid parameters, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CRS935E MISSING PARAMETER AFTER: - `parm`Link copied to clipboard

Explanation: A subparameter of a parameter to the IOACLCND utility is missing. A subparameter is expected after the parm parameter.

For valid syntax, see the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CRS936E REDUNDANT PARAMETER: - `parm`Link copied to clipboard

Explanation: There is a redundant parameter in a parameter line for the IOACLCND utility.

For details, refer to the IOACLCND utility in the INCONTROL for z/OS Utilities Guide.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameter line.

CRS937S IOA CONDITIONS FILE WAS NOT CLEANEDLink copied to clipboard

Explanation: This error is the result of a previous error in the IOACLRES utility. A previous message contains the reason for not cleaning the Conditions file.

The utility stops executing.

Corrective Action: Correct the problem and rerun the utility.

CRS938I CONDITION `cond` ODATE `odate` SCRATCHEDLink copied to clipboard

Explanation: This information message indicates that the specified condition was successfully deleted from the IOA Conditions file by the IOACLCND utility or by New Day processing.

Corrective Action: No action is required.

CRS939E DATE RANGE IS GREATER THAN ONE YEARLink copied to clipboard

Explanation: The date range specified in the FROM/TO parameter is greater than one year (the IOACLRES utility). The TO date is greater than the FROM date by more than a year. There is no way to IGNORE more than one year.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the parameters and rerun.

CSF MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages CSF300 through CSF3xxLink copied to clipboard

This group includes messages for the Control-O product.

CSF321S ERROR OPENING REPORT FILELink copied to clipboard

Explanation: The CTOCSF program was unable to open the file specified in the SYSPRINT DD statement. The SYSPRINT DD statement is either not specified in the JCL, or is specified incorrectly.

The CTOCSF program ends with a return code of 08.

Corrective Action: Check and correct the JCL job.

CSF322S ERROR OPENING STATISTICS INPUT FILELink copied to clipboard

Explanation: The source Statistics file cannot be opened. The CTOCSF program is unable to open the file referenced by the DASTF DD name.

Possible causes are:

The SMFID of the current CPU does not match the SMFID included as part of the name of the Statistics file.
The Statistics file may have been corrupted or moved from the expected location.

The CTOCSF program ends with a return code of 08.

Corrective Action: Do either or both of the following:

Examine and correct the JCL.
Examine any associated MVS messages for additional information, and correct any errors they may disclose.

CSF323S INSUFFICIENT SPACE IN TARGET FILELink copied to clipboard

Explanation: The new Statistics file is not large enough to contain all the records listed in the source Statistics file.

The CTOCSF program ends with a return code of 08.

Corrective Action: Create a larger Statistics file and resubmit the job.

CSF324W ERROR CLOSING STATISTICS INPUT FILELink copied to clipboard

Explanation: An internal error was encountered while closing the source Statistics file referenced by the DD name DASTF.

The CTOCSF program ends with a return code of 08.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact your INCONTROL administrator.

CSF325S ERROR OPENING STATISTICS OUTPUT FILELink copied to clipboard

Explanation: Control-O was unable to open the target Statistics file specified in the CTOPARM member.

The CTOCSF program ends with a return code of 08.

Corrective Action: Check the JCL and the CTOPARM member for errors and resubmit the job.

CSF326S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

Explanation: Dynamic allocation of the dsn Statistics file failed with a return code of rc and a reason code of rsn.

The CTORSTM Statistics Report utility terminates with a return code of 08.

Corrective Action: Examine the IBM manual MVS Programming: Authorized Assembler Services Guide to determine the cause of the error, and correct the error accordingly. If not successful, contact your INCONTROL administrator.

CSF327W ERROR CLOSING STATISTICS OUTPUT FILELink copied to clipboard

Explanation: An internal error was encountered while closing the target Statistics file. This message may be accompanied by an MVS message explaining the error. If such a message is issued, your system programmer may be able to fix the problem.

The CTOCSF program ends with a return code of 08.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact your INCONTROL administrator.

CSF328I COPY OF STATISTICS FILE ENDED OKLink copied to clipboard

Explanation: This information message indicates that the Statistics file was successfully copied by the CTOCSF utility.

Corrective Action: No action is required.

CSF329I COPY OF STATISTICS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that the CTOCSF utility has begun copying the Statistics file.

Corrective Action: No action is required.

CTA MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages CTA600 through CTA6xxLink copied to clipboard

This group includes messages for the Control-O product.

CTA660I ADDRESS SPACE `addrSpace` WILL BE PROCESSED NOWLink copied to clipboard

Explanation: This information message indicates that the CTOCTA utility has begun processing the addrSpace address space. The CTOCTA utility will display all programs running.

Corrective Action: No action is required.

CTA661I ADDRESS SPACE `addrSpace` IS SWAPPED OUT AND WILL BE SKIPPEDLink copied to clipboard

Explanation: This information message indicates that the CTOCTA utility attempted to get information from the addrSpace address space, but it failed because the address space is swapped out. An ALESERV function was invoked to analyze the address space, but failed.

The CTOCTA utility continues its analysis with the next address space.

Corrective Action: No action is required.

CTA662E ALESERV ADD FAILED WITH RETURN CODE `rc`Link copied to clipboard

Explanation: The CTOCTA utility was invoked to get information from the address space but failed with a return code of rc. An ALESERV function was invoked to analyze the address space, but failed.

The CTOCTA utility continues its analysis with the next address space.

Corrective Action: No action is required.

CTA663E ALESERV DELETE FAILED WITH RETURN CODE `rc`Link copied to clipboard

Explanation: The CTOCTA utility analyzed information from an address space but the attempt to disconnect from the address space failed. The DELETE ALESERV function was invoked to disconnect from the address space after analyzing it, but failed with a return code of rc.

The CTOCTA utility continues its analysis with the next address space.

Corrective Action: No action is required.

CTA664I ADDRESS SPACE `addrSpace status`Link copied to clipboard

Explanation: This information message indicates that the addrSpace address space is ACTIVE or INACTIVE. The CTOCTA utility displays the target address space and its status after completing its analysis of the system.

Corrective Action: No action is required.

CTA665E INPUT PARAMETER (ADDRESS SPACE NAME) ERROR DETECTEDLink copied to clipboard

Explanation: An input parameter is missing or is too large. Either the parameter is not present in the invocation JCL, or it is too large.

The CTOCTA utility terminates.

Corrective Action: Add or correct the input parameter and rerun the job.

CTA666I PROGRAM `pgm` FOUND IN THE RB CHAINLink copied to clipboard

Explanation: This information message indicates that the CTOCTA utility found at least one task in the address space running the pgm program.

Corrective Action: No action is required.

CTA667I SVC `svcno` (TYPE 2 NUCLEUS SVC) FOUND IN AN SVRBLink copied to clipboard

Explanation: This information message indicates that the CTOCTA utility found at least one task in the address space running the svcno SVC number.

Corrective Action: No action is required.

A–CTA

ACI MessagesLink copied to clipboard

Messages ACIF00 through ACIFxxLink copied to clipboard

ACIF40I ACIF PRINTING INTERFACE STARTEDLink copied to clipboard

ACIF41I ACIF PRINTING INTERFACE COMPLETED SUCCESSFULLYLink copied to clipboard

ACIF42E ACIF PRINTING INTERFACE ENDED IN ERRORLink copied to clipboard

ACIF43E CODE= err_cod, R15= reg_15, R0= reg_0, R1= reg_1Link copied to clipboard

ACIF44E descrLink copied to clipboard

ACIF45I MAXIMUM CONCURRENT ACIF/CCIF PRINTING MISSIONS ALREADY EXECUTINGLink copied to clipboard

ACIF46I WAITING FOR AN EXECUTING ACIF/CCIF PRINTING MISSION TO COMPLETELink copied to clipboard

ACIF47E MAXIMUM RETRIES LIMIT TO START AN ACIF/CCIF PRINTING MISSION REACHEDLink copied to clipboard

ACIF48W ACIFPARM MEMBER memName NOT FOUND - SEARCHING FOR MEMBER $$$$DFLTLink copied to clipboard

ACIF49W ACIF ISSUED WARNING MESSAGES - PROCESSING CONTINUESLink copied to clipboard

ACIF4BE CTVINDEX STATEMENT SYNTAX ERRORLink copied to clipboard

AES MessagesLink copied to clipboard

Messages AES100 through AES1xxLink copied to clipboard

AES171S BLDL/LOAD FAILED FOR MODULE "CTMLIB"Link copied to clipboard

AES172S OPEN OF INPUT CARDS FILE FAILED. DDNAME "DASIM"Link copied to clipboard

AES173S BLDL/ATTACH FOR MODULE "CTMSUB" FAILEDLink copied to clipboard

AES174S CTMSUB ABENDED CODE= abCode MEMBER memName LIBRARY libLink copied to clipboard

AES175I JOB SUBMISSION SIMULATION STARTEDLink copied to clipboard

AES176I JOB SUBMISSION SIMULATION ENDEDLink copied to clipboard

AES177I SUBMISSION SIMULATION OF MEMBER memName LIBRARY lib STARTEDLink copied to clipboard

AES178I SUBMISSION SIMULATION OF MEMBER memName LIBRARY lib ENDEDLink copied to clipboard

AES179E MISSING PARAMETER DURING MEMBER memNameLink copied to clipboard

AES180E INVALID COMMANDLink copied to clipboard

AES181I COMMANDS ARE: cmdsLink copied to clipboard

AES182E INVALID SUB-COMMAND VALUELink copied to clipboard

AES183I TEN (10) INTERVAL UNITS PASSEDLink copied to clipboard

AES184E REDUNDANT INFORMATION IN LINE linLink copied to clipboard

AES187E INTERNAL ERROR PROCESSING MASKS FOR MASK mask FOR MEMBER memNameLink copied to clipboard

AES188E MEMBER CONTROL CARD WAS NOT SPECIFIEDLink copied to clipboard

AES189E JOB jobName NOT FOUND IN SCHEDULING TABLE tableNameLink copied to clipboard

AES190I jobName RETRIEVED FROM TABLE tableName IN SCHEDULING LIBRARY libLink copied to clipboard

Messages AESL00 through AESLxxLink copied to clipboard

AESL45S DD STATEMENT "DASIM" IS EMPTY. UTILITY TERMINATED.Link copied to clipboard

AESL46S MANDATORY "SUBMIT" PARAMETER IS MISSING. UTILITY TERMINATED.Link copied to clipboard

AESL47I 'cmd' Control-STATEMENT FOUND - {JCL | SCHEDULING} LIBRARY MODE USEDLink copied to clipboard

AESL48E Control-STATEMENT INVALID FOR CURRENT MODE. STATEMENT IGNOREDLink copied to clipboard

AESL49E SCHEDLIB Control-STATEMENT NOT SPECIFIED OR INVALIDLink copied to clipboard

AESL50E TABLE Control-STATEMENT NOT SPECIFIED OR INVALIDLink copied to clipboard

AESL51E JOB Control-STATEMENT NOT SPECIFIED OR INVALIDLink copied to clipboard

AESL52I jobName NOT FOUND IN OVERLIB LIBRARY - MEMLIB LIBRARY WILL BE USEDLink copied to clipboard

AESL53I jobName RETRIEVED FROM MEMLIB/OVERLIB LIBRARY libLink copied to clipboard

AESL54I OWNER owner RETRIEVED FROM JOB SCHEDULING DEFINITION jobNameLink copied to clipboard

AESL55I APPLICATION applId RETRIEVED FROM SCHEDULE DEFINITION jobNameLink copied to clipboard

ALI MessagesLink copied to clipboard

Messages ALI300 through ALI3xxLink copied to clipboard

ALI360S AUTOMATION LOG DYNAMIC ALLOCATION ERROR rc/rsn/dsnLink copied to clipboard

ALI361S ERROR WHILE LOADING MODULE IDCAMSLink copied to clipboard

ALI362S INVALID PARAMETERS PASSED TO THE PROGRAMLink copied to clipboard

ALI363S NO PARAMETERS PASSED TO THE PROGRAMLink copied to clipboard

ALI364S ERRORS IN IDCAMS PROCESSINGLink copied to clipboard

ALI365S VOLUME PARAMETER MUST BE SPECIFIED FOR DIV DATASETSLink copied to clipboard

ALO MessagesLink copied to clipboard

Messages ALO200 through ALO2xxLink copied to clipboard

ALO290I {CONTROL-O | CTMCMEM} AUTOMATION LOG STARTEDLink copied to clipboard

ALO291E AUTOMATION LOG ERROR WHILE PROCESSING REQUESTSLink copied to clipboard

ALO292S {CONTROL-O | CTMCMEM} AUTOMATION LOG TERMINATION ERRORLink copied to clipboard

ALO293I CONTROL-O AUTOMATION LOG ENDEDLink copied to clipboard

ALO294E OPEN OF AUTOMATION LOG FAILED. LOG SWAPPEDLink copied to clipboard

ALO295S OPEN OF DAACTLOG FAILEDLink copied to clipboard

ALO296E ERROR DETECTED DURING ADDF. LOG SWAPPEDLink copied to clipboard

ALO297I AUTOMATION LOG STATUS CHANGE COMPLETEDLink copied to clipboard

ALO298E ERROR DETECTED DURING ENQ. LOG SWAPPEDLink copied to clipboard

ALO299E ERROR DETECTED DURING DEQ. LOG SWAPPEDLink copied to clipboard

Messages ALO300 through ALO3xxLink copied to clipboard

ALO303S {CONTROL-O | CTMCMEM} AUTOMATION LOG INITIALIZATION ERRORLink copied to clipboard

ALO304S CONTROL-O AUTOMATION LOG SWAPPING ERRORLink copied to clipboard

ALO305S {CONTROL-O | CTMCMEM} AUTOM. LOG SEVERE ERROR ID= errLink copied to clipboard

ALO306S ERROR DETECTED DURING LOGGINGLink copied to clipboard

ALO307E PROBLEMS WITH WRITEF. LOG SWAPPEDLink copied to clipboard

ALO308E AUTOMATION LOG I/O ERROR. RC = rcLink copied to clipboard

ALU MessagesLink copied to clipboard

Messages ALU300 through ALU3xxLink copied to clipboard

ALU370I COPY OF CONTROL-O AUTOMATION LOG STARTEDLink copied to clipboard

ALU371I COPY OF CONTROL-O AUTOMATION LOG ENDEDLink copied to clipboard

ALU372S COPY OF CONTROL-O LOG ENDED WITH ERRORSLink copied to clipboard

ALU373S ERROR OPENING SOURCE FILELink copied to clipboard

ALU374S ERROR OPENING TARGET FILELink copied to clipboard

ACIF43E CODE= `err_cod`, R15= `reg_15`, R0= `reg_0`, R1= `reg_1`Link copied to clipboard

ACIF48W ACIFPARM MEMBER `memName` NOT FOUND - SEARCHING FOR MEMBER $$$$DFLTLink copied to clipboard

AES174S CTMSUB ABENDED CODE= `abCode` MEMBER `memName` LIBRARY `lib`Link copied to clipboard

AES177I SUBMISSION SIMULATION OF MEMBER `memName` LIBRARY `lib` STARTEDLink copied to clipboard

AES178I SUBMISSION SIMULATION OF MEMBER `memName` LIBRARY `lib` ENDEDLink copied to clipboard

AES179E MISSING PARAMETER DURING MEMBER `memName`Link copied to clipboard

AES181I COMMANDS ARE: `cmds`Link copied to clipboard

AES184E REDUNDANT INFORMATION IN LINE `lin`Link copied to clipboard

AES187E INTERNAL ERROR PROCESSING MASKS FOR MASK `mask` FOR MEMBER `memName`Link copied to clipboard

AES189E JOB `jobName` NOT FOUND IN SCHEDULING TABLE `tableName`Link copied to clipboard

AES190I jobName RETRIEVED FROM TABLE `tableName` IN SCHEDULING LIBRARY `lib`Link copied to clipboard

AESL47I `'cmd'` Control-STATEMENT FOUND - {JCL | SCHEDULING} LIBRARY MODE USEDLink copied to clipboard

AESL53I jobName RETRIEVED FROM MEMLIB/OVERLIB LIBRARY `lib`Link copied to clipboard

AESL54I OWNER `owner` RETRIEVED FROM JOB SCHEDULING DEFINITION `jobName`Link copied to clipboard

AESL55I APPLICATION `applId` RETRIEVED FROM SCHEDULE DEFINITION `jobName`Link copied to clipboard

ALI360S AUTOMATION LOG DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

ALO305S {CONTROL-O | CTMCMEM} AUTOM. LOG SEVERE ERROR ID= `err`Link copied to clipboard

ALO308E AUTOMATION LOG I/O ERROR. RC = `rc`Link copied to clipboard

ALU375S NON-ZERO RETURN CODE RECEIVED: "`pgm`"Link copied to clipboard

ALU384S AUTOM. LOG SEQ. DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`Link copied to clipboard

APAF23I MEMBER `memName` IS TRANSFERRED TO VARIABLE BLOCKED LIBRARYLink copied to clipboard

API003I REQ= `requestText`Link copied to clipboard

API004I RC= `rc`Link copied to clipboard

API008E SERVICE_TYPE NOT RECOGNISED `serviceType`Link copied to clipboard

API563E IOA SUBSYSTEM `subsys` INACTIVE. INTERFACE CANNOT BE USEDLink copied to clipboard

API565E SETOLOC/SETOGLB ERROR CODE= `rc` REASON= `rsn`, TEXT= `text`Link copied to clipboard

API566E IOA SUBSYSTEM `subsys` NOT RESPONDING TO REQUESTSLink copied to clipboard

API567E IOA SUBSYSTEM `subsys` INACTIVELink copied to clipboard

API568E IOA SUBSYSTEM `subsys` DETECTED AN ERRORLink copied to clipboard

API569E IOA SUBSYSTEM `subsys` RETURNED AN INVALID RETURN CODELink copied to clipboard

API56AE ERROR IN INAREA FIELDS ADDR= `add1, add2` LENGTH `len` DATA= `data_val`Link copied to clipboard

API56BE ERROR IN RESULT FIELDS ADDR= `add`, LENGTH `len` DATA= `data_val`Link copied to clipboard

API56CE INAREA LENGTH+RESULT= `xxxx`+ `xxxx`= `xxxx` > 255Link copied to clipboard

API56EE CHECKPOINT GLOBAL VARIABLE DATABASE `ioavar` TIMED OUT AFTER `num` SECONDSLink copied to clipboard

API56FE CHECKPOINT GLOBAL VARIABLE DATABASE `ioavar` ENDED WITH ERROR. RC=16Link copied to clipboard

API573E IOA SUBSYSTEM `subsys` INACTIVE. INTERFACE CANNOT BE USEDLink copied to clipboard

API575E SETOLOC/SETOGLB ERROR CODE = `rc` REASON = `rsn`, TEXT= `text`Link copied to clipboard

API576E IOA SUBSYSTEM `subsys` NOT RESPONDING TO REQUESTSLink copied to clipboard

API577E IOA SUBSYSTEM `subsys` INACTIVELink copied to clipboard

API578E IOA SUBSYSTEM `subsys` DETECTED AN ERRORLink copied to clipboard

API579E IOA SUBSYSTEM `subsys` RETURNED AN INVALID RETURN CODELink copied to clipboard

API57AE ERROR IN INAREA FIELDS ADDR= `add1, add2` LENGTH `len` DATA= `value`Link copied to clipboard

API57BE ERROR IN RESULT FIELDS ADDR= `add`, LENGTH `len` DATA= `value`Link copied to clipboard

API57CE INAREA LENGTH `length3` + RESULT LENGTH `length2` > 255Link copied to clipboard

API57EE CHECKPOINT GLOBAL VARIABLE DATABASE `dbName` ENDED DUE TO TIMEOUT AFTER `num` SECONDSLink copied to clipboard