Messages CTO300 through CTO3xx

This group includes messages for the Control-O product.

CTO300S INTERNAL ERROR - REASON = rsn. NOTIFY THE IOA ADMINISTRATOR

Explanation: Control-O detected an internal Control-O error.

The Control-O monitor shuts down.

Corrective Action: Record the reason, and have your system programmer call BMC Customer Support.

CTO303S {CONTROL-O | CTMCMEM} AUTOMATION LOG INITIALIZATION ERROR

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.

CTO304S CONTROL-O AUTOMATION LOG SWAPPING ERROR

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 will be 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 gives up.

Corrective Action: Contact your INCONTROL administrator.

CTO305S {CONTROL-O | CTMCMEM} AUTOM. LOG SEVERE INTERNAL ERROR ID= err

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

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

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: Report the value of err to your INCONTROL administrator.

CTO306S ERROR DETECTED DURING LOGGING

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.

CTO307E PROBLEMS WITH WRITEF. LOG SWAPPED

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.

CTO308E AUTOMATION LOG I/O ERROR. RC = rc

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

CTO321S ERROR OPENING REPORT FILE

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.

CTO322S ERROR OPENING STATISTICS INPUT FILE

Explanation: The source Statistics file cannot be opened. The CTOCSF program is unable to open the file referenced by the DASTF DD name.

This problem may be due to one of the following:

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

CTO323S INSUFFICIENT SPACE IN TARGET FILE

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.

CTO324W ERROR CLOSING STATISTICS INPUT FILE

Explanation: An internal error was encountered while closing the source Statistics file referenced by 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.

CTO325S ERROR OPENING STATISTICS OUTPUT FILE

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. Resubmit the job.

CTO326S STATISTICS FILE DYNAMIC ALLOCATION ERROR rc/rsn/dsn

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: See 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.

CTO327W ERROR CLOSING STATISTICS OUTPUT FILE

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.

CTO328I COPY OF STATISTICS FILE ENDED OK

Explanation: This information message indicates that the Statistics file was successfully copied by the CTOCSF utility.

Corrective Action: No action is required.

CTO329I COPY OF STATISTICS FILE STARTED

Explanation: This information message indicates that the CTOCSF utility has begun copying the Statistics file.

Corrective Action: No action is required.

CTO333S ERROR FORMATTING AUTOMATION LOG FILE

Explanation: An I/O error was detected. The CTODVB program failed to execute an I/O operation with the Automation Log file.

Formatting of the Automation Log ends with a return code of 08.

Corrective Action: Check associated MVS messages detailing the cause of the error, for example, disk failure, incorrect data set, incorrect name or allocation parameters.

CTO334I FORMATTING OF AUTOMATION LOG FILE STARTED

Explanation: This information message indicates that formatting of the Automation Log file has begun.

Corrective Action: No action is required.

CTO335I FORMATTING OF AUTOMATION LOG FILE ENDED

Explanation: This information message indicates that formatting of the Automation Log file has ended successfully.

Corrective Action: No action is required.

CTO336S AUTOMATION LOG FILE WAS NOT BUILT

Explanation: Formatting of the Automation Log file failed. This message follows other messages detailing the problem.

The formatting of the Automation Log ends with a return code of 08.

Corrective Action: Consult previous messages detailing the reason for the error.

CTO337S AUTOMATION LOG DYNAMIC ALLOCATION ERROR rc/rsn/dsn

Explanation: A dynamic allocation problem occurred. The CTODVB program attempted to dynamically allocate the Automation Log file but failed.

Formatting of the Automation Log file ends with a return code of 08.

Corrective Action: Do the following:

1. For an explanation of return-code (rc) and the reason (rsn), see the IBM OS/390 Authorized Assembler Services Guide, and proceed accordingly.
2. Check the CTOPARM member.
3. Verify that an Automation Log file already exists for this CPU.

CTO338S INVALID PARAMETERS PASSED TO PROGRAM

Explanation: The CTODVB program detected an error in the parameters passed to it.

Formatting of the Automation Log file ends with a return code of 08.

Corrective Action: Check the parameters passed to the program and correct them.

CTO339S NULL PARAMETERS PASSED TO PROGRAM

Explanation: The CTODVB program was called with no parameters.

Formatting of the Automation Log file ends with a return code of 08.

Corrective Action: Check and correct the JCL.

CTO341S AUTOMATION LOG FILE LEVEL INCONSISTENT WITH LEVEL OF CONTROL-O

Explanation: The Automation Log file is not compatible with this release of Control-O. While opening an Automation Log file, the CTODVL program checks the file validity and usability. A mismatch was found between the release number of the Automation Log file and the release number of the program accessing it.

Action fails. The Automation Log file is not accessed.

Corrective Action: Do any or both of the following:

• Check if the libraries specified in the STEPLIB and LINKLIST concatenation contain modules from different releases.
• Check the Automation Log file data set name. If you are using an older release of the program or an old file, correct the error.

CTO342S ERROR OPENING AUTOMATION LOG FILE

Explanation: This is one of two messages with the same ID, but different text.

The CTODVL program was unable to open the Automation Log file.

The action fails. The Automation Log file is not accessed.

Corrective Action: Do any or all of the following:

• Check the definitions in the CTOPARM member.
• Check the JCL for errors.
• Check the data set name for the Automation Log file.

CTO342S ERROR OPENING OPERLOG FILE

Explanation: This is one of two messages with the same ID, but different text.

The user tried to access the OPERLOG in a SYSPLEX environment. However, the OPERLOG could not be opened.

The system rejects the request and continues.

Corrective Action: Record the message and contact your system programmer.

CTO343S AUTOMATION LOG DYNAMIC ALLOCATION ERROR rc/rsn/dsn

Explanation: The CTODVL program was unable to dynamically allocate the Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: Do any or all of the following:

• See documentation on dynamic allocation in the IBM authorized guide to Assembler services for explanations of the return code (rc) and the reason code (rsn), and proceed accordingly.
• Check the CTOPARM member.
• Ensure that an Automation Log file exists for this CPU.

CTO344S AUTOMATION WRITE ERROR

Explanation: An I/O error occurred. The CTODVL program did not succeed in performing an I/O operation on the Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: If you cannot determine the reason for this I/O error (for example, a disk failure), contact BMC Customer Support.

CTO345S ERROR EXECUTING RDJFCB

Explanation: The CTODVL program received a non-zero return code from system service RDJFCB. The CTODVL program failed to read the JFCB of the dynamically allocated Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: Contact BMC Customer Support.

CTO346S ABEND abCode INTERCEPTED WHILE PROCESSING THE AUTOMATION LOG

Explanation: This is one of two messages with the same ID, but different text.

The CTODVL program intercepted an abend while processing the Automation Log.

The action fails. The Automation Log file is not accessed.

Corrective Action: Contact BMC Customer Support.

CTO346S ABEND abCode INTERCEPTED WHILE PROCESSING THE OPERLOG

Explanation: This is one of two messages with the same ID, but different text.

The user tried to access the OPERLOG in a SYSPLEX environment but an abend was generated.

For information about abCode, see the IBM Abend Codes manual.

The system terminates the requested action.

Corrective Action: Take appropriate corrective action.

CTO347S THE ALLOCATED AUTOMATION LOG FILE BELONGS TO ANOTHER CONTROL-O INSTALLATION

Explanation: This is one of two messages with the same ID, but different text.

The specified Automation Log file refers to another Control-O. While opening an Automation Log file, the CTODVL program checks the validity and usability of the file being opened. A mismatch was found between the current value specified for the CTOQNAME parameter in the CTOPARM member and the value of that parameter when the Automation Log file was formatted.

Action fails. The Automation Log file is not accessed.

Corrective Action: Do either or both of the following:

• Ensure that you are not using load libraries that belong to another installation of Control-O.
• Check if the CTOPARM member has changed.

CTO347S ERROR RETURN CODE FROM A SYSTEM LOGGER REQUEST rc

Explanation: This is one of two messages with the same ID, but different text.

The user issued the OPER command in the OL screen to access the OPERLOG in a SYSPLEX environment. However, the request failed and the rc SYSTEM LOGGER return code was issued.

The system rejects the request.

Corrective Action: For information about the error, note the value of rc and see IBM LOGGER services (IXGxxx macros) in the Sysplex service manual.

CTO348S FILE NOT AN AUTOMATION LOG FILE

Explanation: This is one of two messages with the same ID, but different text.

The specified file is not a Control-O Automation Log file. While opening an Automation Log file, CTODVL checks the validity and usability the file. The specified file was not an Automation Log file.

Action fails. The Automation Log file is not accessed.

Corrective Action: Check if the formatting of the Automation Log file ended successfully. If it failed, redefine (reformat) the Automation Log.

CTO348S OPERLOG IS EMPTY

Explanation: This is one of two messages with the same ID, but different text.

The user issued the command OPER in the OL screen to access the OPERLOG in a SYSPLEX environment. In response, the system logger informed Control-O that the OPERLOG was empty.

The system rejects the request.

Corrective Action: For more information about the error, note the message and contact your system programmer.

CTO349S AUTOMATION LOG FILE IS BEING FORMATTED IT CANNOT BE ACCESSED

Explanation: This is one of two messages with the same ID, but different text.

The specified Automation Log file is currently being formatted. While opening the Automation Log file, the CTODVL program checks the validity and usability of the file. The specified file has a status incompatible with the requirements of the program.

Action fails. The Automation Log is not accessed.

Corrective Action: Check if the formatting of the Automation Log file ended successfully. If it failed, redefine (reformat) the Automation Log.

CTO349S OPERLOG END OF FILE IS REACHED

Explanation: This is one of two messages with the same ID, but different text.

The user attempted to access the OPERLOG in a SYSPLEX environment and reached the end of the OPERLOG. However, no more data was available in the OPERLOG.

The system rejects the request.

Corrective Action: Reattempt access to the OPERLOG.

CTO350E ERROR FREEING STORAGE. ADDR= addr LEN= length SP= subpool RELATED = rel

Explanation: An internal error was detected.

During termination, Control-O or CMEM frees internal control blocks and work areas. An error occurred while this was being done.

Control-O or CMEM continues termination.

Corrective Action: Contact BMC Customer Support.

CTO352W SERVER serverId DID NOT RESPOND TO STOP REQUESTS. SERVER STATUS OVERRIDDEN

Explanation: Server serverId did not respond to a STOP request.

When Control-O executes a server STOP request, it waits for acknowledgment from the server. If the server does not respond within thirty seconds, this message is displayed.

The specified server is given the status ENDED WITH AN ERROR.

Corrective Action: Check output and messages issued by the problem server. If necessary, bring down the server and start a new one.

CTO353I module RELOADED. OLD: datetime1 NEW: datetime2

Explanation: This information message indicates that the RELOAD command completed execution successfully.

This message provides the installation date and time of the old and newly-replaced modules in mm/dd/yy hh.mm format.

• module - the name of the module that was successfully reloaded
• datetime1 - the assembly date of the old module
• datetime2 - the assembly date of the newly installed module

Corrective Action: No action is required.

CTO354I SERVER STCID TYP QLN STIME STATUS

Explanation: This information message is the normal response of the Control-O monitor to the F CONTROLO,SERVER= serverId,DISPLAY operator command.

This message is the header for information in messages CTO355I and MTO355I.

Corrective Action: No action is required.

CTO355I serverId jobId type queueLength statusTime status

Explanation: The Control-O monitor sends this information message to the console in response to the command:

F CONTROLO,SERVER=serverId,DISPLAY

Each occurrence of this message describes a server defined to Control-O. These messages are preceded by message CTO354I or MTO354I that provides the header. The information in this message is in the same format as the Option SERVERS screen of the Automation Options facility.

For more information, see the Control-O User Guide.

Corrective Action: No action is required.

CTO356I modifyCmdText

Explanation: This information message displays the text of the submitted modify command.

Corrective Action: No action is required.

CTO357I COMMAND ENDED SUCCESSFULLY

Explanation: This information message indicates that the last modify command ended successfully.

Corrective Action: No action is required.

CTO358W LIMIT OF LINES REACHED. FURTHER LINES NOT DISPLAYED

Explanation: More than 1,000 lines were issued in response to a MODIFY command specified with the DISPLAY parameter.

When more than 1,000 lines are issued to the operator’s console, Control-O terminates the command which is creating the lines, to avoid a shortage of space in the console’s buffer.

Only the first 1,000 lines are displayed.

Corrective Action: No action is required.

CTO359W CONTROL-O COSMOS IS NOT ACTIVE

Explanation: The user attempted to stop COSMOS while it was not active.

The COSMOSSTOP command is ignored.

Corrective Action: No action is required.

CTO35AW CONTROL-O COSMOS IS ALREADY ACTIVE

Explanation: The user attempted to start COSMOS while it was active.

The COSMOSSTART command is ignored.

Corrective Action: No action is required.

CTO35BI OBJECTDB METHODDB MODE

Explanation: This information message is the header for data provided in message CTO35CI.

This message is the normal response of Control-O to the F CONTROLO,COSMOS=cosmosdb,DISPLAY operator command.

This command displays general information about COSMOS Object databases.

Corrective Action: No action is required.

CTO35CI objectDb methodDb mode

Explanation: This information message is the normal response of Control-O to the F CONTROLO,COSMOS= cosmosdb,DISPLAY operator command.

Each occurrence of this message describes an Object database under COSMOS control. Message CTO35BI generates the message header.

The variables in this message are:

• objectDb - the working COSMOS object database
• methodDb - the COSMOS Method database
• mode - the current COSMOS database mode

Corrective Action: See COSMOS commands in the Control-O User Guide.

CTO35DW INVALID COSMOS MODIFY COMMAND - errorText

Explanation: The user issued a COSMOS command with invalid parameters.

In this message, errorText describes the error.

The command is ignored. Processing continues.

Corrective Action: Specify the COSMOS command with valid parameters. For more information, see “Control-O/COSMOS Commands” in the Control-O/COSMOS User Guide.

CTO35EW action COSMOS id FAILED - text

Explanation: The specified action (action) on the id COSMOS ID failed.

An invalid syntax, action or ID was specified.

The system ignores the command.

Corrective Action: Correct the syntax, action, or ID and reissue the command.

CTO35FW MODIFY COMMAND REJECTED

Explanation: The user attempted to issue an invalid modify command to the Control-O monitor.

The system rejects the command.

Corrective Action: Correct the command syntax and reenter the command

CTO360E ERROR IN RELOAD INITIALIZATION

Explanation: The RELOAD modify command encountered a problem with the Control-O SSVT or one of its function routines.

The internal control block structure has been corrupted.

The RELOAD modify command is terminated.

Corrective Action: Bring down and restart Control-O. RELOAD is not necessary.

CTO360S AUTOMATION LOG DYNAMIC ALLOCATION ERROR rc/rsn/dsn

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 programs ends with a return code of 08.

Corrective Action: No action is required.

CTO361E ERROR IN RELOAD PRELIMINARY PHASE

Explanation: The RELOAD modify command encountered a problem with an MVS macro instruction.

The user tried to reload the CTOWTO Control-O module in storage but this module was not found in the Control-O STEPLIB libraries.

The RELOAD modify command is terminated.

Corrective Action: No action is required.

CTO361S ERROR WHILE LOADING MODULE IDCAMS

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.

CTO362E ERROR IN RELOAD PROCESSING

Explanation: The RELOAD modify command encountered a problem with an MVS macro instruction.

There may not be enough CSA (Common Service Area) storage available to load the new CTOWTO module.

The RELOAD modify command is terminated.

Corrective Action: Bring down and restart Control-O. RELOAD is not necessary.

CTO362S INVALID PARAMETERS PASSED TO THE PROGRAM

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.

CTO363E ERROR IN RELOAD BACK-END PROCESSING

Explanation: In response to the RELOAD modify command, Control-O encountered a problem when attempting to deallocate a routine.

The internal control block structure has been corrupted.

The RELOAD modify command is completed, but cleanup processing is aborted.

Corrective Action: No action is required.

CTO363S NO PARAMETERS PASSED TO THE PROGRAM

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

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.

CTO364E ALTERNATE SUBSYSTEM SSCT ENTRY NOT FOUND

Explanation: The alternate subsystem SSCT entry specified in the ALTSSN CTOPARM parameter is not in the system.

Control-O monitor failed to find the SSCT prior to activating the alternate subsystem.

Control-O monitor routine continues without activating the alternate subsystem.

Corrective Action: Add the alternate subsystem name to the IEFSSNxx member in the SYS1.PARMLIB library and then IPL the system. The alternate subsystem cannot be activated until after the IPL.

CTO364S ERRORS IN IDCAMS PROCESSING

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.

CTO365S VOLUME PARAMETER MUST BE SPECIFIED FOR DIV DATASETS

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.

CTO366E CONTROL-O COSMOS IS NOT INSTALLED

Explanation: The user attempted to enter a COSMOS command. However, Control-O COSMOS was not installed

Control-O ignores the command and processing continues.

Corrective Action: Install Control-O COSMOS.

CTO367E SMODE VALID VALUES ARE F, Y, AND N

Explanation: An invalid value was specified for the SMODE parameter in an operator command.

Valid values for SMODE (stand alone mode) are:

• F (Forced) - Each Control-O copy is responsible for updating the IOA Log file. Default. BMC recommends that you do not change this default.
• Y (Yes) - Each Control-O copy passes requests to write to the IOA Log file to Control-M by means of the communications file, except for requests initiated by the New Day procedure (which are treated as if SMODE is set to F). Setting SMODE to Y causes less ENQ contention for the IOA Log file but increases pressure on the Control-M monitor.
• N (No) - Control-O always passes requests to write to the IOA Log file to Control-M by means of the communications file.

The operator command is ignored.

Corrective Action: Specify a valid value for the SMODE parameter and reissue the command. For more information, see SMODE in the relevant appendix of the INCONTROL for z/OS Administrator Guide.

CTO36GW CTOWTO CANNOT BE RELOADED BECAUSE XES SYSTEM-MANAGED REBUILD IS IN PROGRESS. TRY TO RELOAD LATER.

Explanation: CTOWTO cannot be reloaded until the system-managed process ends.

The RELOAD command is rejected.

Corrective Action: Wait for the system-managed process to end and reissue the RELOAD command.

CTO36HE INVALID MODULE NAME SPECIFIED IN RELOAD COMMAND.

Explanation: A REALOD modify command has been issued for an invalid module name. The module name is either not a module or not a reloadable module. The invalid module name appears in the previous CTO356I message, which echoed the modify command.

The command is ignored.

Corrective Action: Issue the command again with the correct reloadable module name.

CTO370I COPY OF CONTROL-O AUTOMATION LOG STARTED

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

Corrective Action: No action is required.

CTO371I COPY OF CONTROL-O AUTOMATION LOG ENDED

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

Corrective Action: No action is required.

CTO372S COPY OF CONTROL-O LOG ENDED WITH ERRORS

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: See the previous message for the cause of the error, correct the problem, and resubmit the job.

CTO384S AUTOM. LOG SEQ. DYNAMIC ALLOCATION ERROR rc/rsn/dsn

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

The CTOALOCP utility ends with a return code of 08.

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

CTO390S OPEN OF DDNAME ddName FAILED.

Explanation: Open of the ddName DD name failed. Possible causes are:

• The ddName DD statement is missing.
• The data set described by the ddName DD statement does not exist.

Execution stops.

Corrective Action: Correct the JCL of the job and rerun.

CTO392S OPEN OF DDNAME ddName FAILED

Explanation: The opening of the data set referenced by the DD name ddName failed.

Possible causes are:

• the DD statement referring to the data set referenced by the DD name ddName is missing.
• The data set referenced by the DD statement ddName does not exist.

System action depends on the calling program. Execution may continue, or it may stop with a condition code of 08, 12, or 16.

Corrective Action: Correct the JCL and rerun.