Messages CTO600 through CTO6xx

This group includes messages for the Control-O product.

CTO600E ERROR RUNNING CTOCMCK RC=rc

Explanation: The CTOGATE communication facility failed to initialize.

CTOMTO called the CTOCMCK module and then ended with an error. This message follows a CTOGATE error message generated by the CTOCMCK module.

CTOGATE aborts.

Corrective Action: Correct and re-initialize CTOGATE.

CTO601E STORAGE ALLOCATION FOR COMMUNICATION FAILED, MODULE modName RC=rc

Explanation: During communication initialization for the modName module, the storage allocation failed with a return code of rc. Storage allocation for the Control-O communication facility failed because the CTOGATE communication facility could not obtain enough working storage for processing.

Control-O ends.

Corrective Action: Increase the region size and restart Control-O. If increasing the region size does not resolve the problem, record the return code and contact BMC Customer Support.

CTO601S CTOTCOS INTERNAL ERROR - errorText

Explanation: An internal error was detected when a COSMOS Object Status screen option was activated.

The option is not performed.

Corrective Action: Contact BMC Customer Support.

CTO602E ACTION actionName IS NOT SUPPORTED

Explanation: An invalid command was specified in the COSMOS Object Status screen.

The command is ignored.

Corrective Action: See options of the Object Status Screen in the Control-O/COSMOS User Guide for a list of valid commands in COSMOS online screens.

CTO603E ERROR IN CTMMEM RC=rc ABEND=abCode

Explanation: Initialization of communication facility CTOGATE failed to load the parameter member. The error occurred when CTMMEM attempted to load the network map into memory. CTMMEM failed with a return code.

Valid values of rc are:

rc	Meaning
8	Not enough 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
32	Internal error
36	Data set not in catalog
40	Dynamic allocation failed
48	Number of lines exceeds the maximum
52	Error when opening processing directory
56	STAE has detected an abend
68	Inconsistent type

The CTOCMCK program ends. Control-O does not start.

Corrective Action: If possible, correct the problem and restart Control-O. If the error persists, contact BMC Customer Support.

CTO603I object action objectDb objectcpu

Explanation: This information message indicates that the user entered a valid line command in the COSMOS Object Status screen.

One of the COSMOS prepackaged rules is triggered to perform the task and this message is suppressed.

Corrective Action: No action is required.

CTO604E ERROR FREEING STORAGE, PROGRAM pgm, RC=rc

Explanation: An internal error was detected when a request was made to end Control-O. When Control-O ends, the Control-O communication module frees internal control blocks and work areas. The error occurred during this operation.

The CTOCMCK program ends with a return code. Control-O fails to end.

Corrective Action: Record the message and the return code. Contact BMC Customer Support.

CTO606E UNRESOLVED SYSTEM NAME IN RULE

Explanation: An invalid Communication ID was defined in the rule. The Communication module did not find the Communication ID name in the network map or as a SYSPLEX system partner. See the MVS SYSPLEX definitions.

The CTOCMCK program ends.

Corrective Action: Define your SYSTEM ID in the communication network map member or as a Sysplex system partner in the MVS PARMLIB. For more information, see the chapter on IOA installation in the INCONTROL for z/OS Installation Guide.

CTO607E COMMUNICATION CANNOT [BE] PERFORMED. IT WAS NOT INITIALIZED

Explanation: Control-O was not initialized with the Communication option. A system ID was specified in the rule, but the communication option was not active.

No communication rule is performed.

Corrective Action: To perform the rule, do one of the following:

Start Control-O with the CTOGATE communication parameter in the CTOPARM member set to YES.
If Control-O was started with CTOGATE set to YES, check if Control-O was stopped by the modify option, STOPCOMM. If Control-O was stopped by STOPCOMM, restart Control-O with STARTCOMM.

CTO609S BLDL/LOAD FAILED FOR THE MODULE modName

Explanation: Loading Control-O Application Server modName failed. The modName module did not exist in the library specified in DD statement STEPLIB or in the LINKLIST concatenation.

The Application Server (CTOGATE) ends.

Corrective Action: Verify that the correct library is specified in DD statement STEPLIB or in the LINKLIST concatenation.

CTO60AS MBX mbxopt TIME OUT ERROR

Explanation: Control-O Gateway used MBX option mbxopt and timed out. IOAGATE issues a message with a return code indicating when the time out was issued. Other messages in the IOAGATE message job log help explain the problem.

The Application Server subtask (CTOGATE) ends.

Corrective Action: Check the messages in the IOAGATE message job log. Correct the error and restart CTOGATE.

CTO60BS MBX mbxopt TERMINATION ERROR

Explanation: Control-O detected an internal error when the user specified MBX option mbxopt. IOAGATE issued a return code indicating the internal error.

Application server subtask CTOGATE ends.

Corrective Action: Check the IOAGATE message job log for messages connected with this problem. Contact BMC Customer Support.

CTO60CS MBX mbxopt GTW SHUT DOWN ERROR

Explanation: IOAGATE issued a time out after the user specified MBX option MBXOPT. IOAGATE issues a return code indicating the reason for the shutdown.

The Application Server subtask CTOGATE ends.

Corrective Action: Restart IOAGATE and the Application Server CTOGATE.

CTO60DS MBX mbxopt INTERNAL ERROR OCCURRED

Explanation: The Application Server CTOGATE ended due to an unrecoverable error. Preceding messages contain information about the error.

The Application Server subtask CTOGATE ends.

Corrective Action: Check preceding messages, correct the problem, and restart the Application Server CTOGATE.

CTO60ES INTERNAL COMMUNICATION ERROR OCCURRED, RC=rc, DATA=data

Explanation: The Application Server CTOGATE ended due to an unrecoverable error. Preceding messages contain information about the error.

The Application Server subtask CTOGATE ends.

Corrective Action: Correct the problem and restart the Application Server CTOGATE. If the problem is not resolved, record the return code and contact BMC Customer Support.

CTO610W CONTROL-O IS NOT ACTIVE SUBSYSTEM subsys NOT ACTIVE

Explanation: CTOGATE attempted to access Control-O. However, Control-O was not active. CTOGATE checks whether or not Control-O functions of the IOA subsystem subsys are activated. The Application Server did not find the subsystem ready for use.

CTOGATE waits for Control-O to be started.

Corrective Action: Start the Control-O monitor.

CTO611S CTOTDBS INTERNAL ERROR - errorText

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

An internal error was detected when a COSMOS Database Status screen option was activated.

The option is not performed.

Corrective Action: Contact BMC Customer Support.

CTO611S GETRQC INTERNAL ERROR, RC=rc

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

An internal error caused the Application Server to fail to retrieve messages from the Control-O request chain.

The Application Server subtask CTOGATE issues a return code and ends.

Corrective Action: Restart the Application Server. If the problem persists, record all messages and return code and contact BMC Customer Support.

CTO612E ACTION actionName IS NOT SUPPORTED

Explanation: An invalid line command was specified in the COSMOS Database Status screen.

The line command is ignored.

Corrective Action: For a list of valid line commands in COSMOS online screens, see the description of the options of the Object Status Screen in the Control-O/COSMOS User Guide.

CTO613I object action objectDb objectcpu

Explanation: This information message indicates that the user entered a valid line command in the COSMOS Database Status screen.

One of the COSMOS prepackaged rules is triggered to perform the task, and this message is suppressed.

Corrective Action: No action is required.

CTO613S modName INTERNAL ERROR, R15=rsn, RC=rc

Explanation: An internal error was detected in the modName module.

The Application Server becomes unstable.

Corrective Action: Stop and restart IOAGATE and the Application Server CTOGATE. If the error persists, contact BMC Customer Support.

CTO614W CONTROL-O IS NOT ACTIVE

Explanation: CTOGATE attempted to access Control-O. However, Control-O was not active.

CTOGATE waits for Control-O to be started.

Corrective Action: Start the Control-O monitor.

CTO615I CONTROL-O control IS ACTIVE. APPLICATION SERVER IS READY.

Explanation: This information message indicates that CTOGATE detected that Control-O has started.

Control-O communication via CTOGATE starts.

Corrective Action: No action is required.

CTO616I COMMUNICATION WAS ALREADY STARTED.

Explanation: The user attempted to start communication. However, it was already operating.

Corrective Action: No action is required.

CTO617I COMMUNICATION WAS ALREADY STOPPED.

Explanation: The user attempted to stop communication. However, it had already been stopped.

Corrective Action: No action is required.

CTO619I COMMUNICATION CANNOT BE ACTIVATED.

Explanation: This information message indicates that the user was unable to activate Control-O communication.

STARTCOMM modify command cannot be performed. Control-O was started with the CTOGATE parameter set to NO.

Control-O communication is not activated.

Corrective Action: Start Control-O with the CTOGATE parameter in the CTOPARM member set to YES.

CTO61FI CONTROL-O COMMUNICATION IS ACTIVE. NETWORK NAME=sysname, NETWORK MAP=memName'

Explanation: This information message indicates that Control-O communication initialization is complete.

Communication is operating using system name sysname and communication network map memName.

Corrective Action: No action is required.

CTO620I CONTROL-O COSMOS INITALIZATION STARTED. CTOCOS release APAR apar

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.

CTO621I CONTROL-O COSMOS STARTED

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.

CTO622S CONTROL-O COSMOS TERMINATION ERROR

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: See the accompanying messages for the cause of the problem and correct it accordingly.

CTO623I CONTROL-O COSMOS ENDED

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.

CTO624S OPEN OF DDNAME ddName FAILED

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.

CTO625S READ ERROR FOR ddName

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.

CTO626S CONTROL-O COSMOS INITIALIZATION ERROR

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: See the accompanying messages for more information about the initialization error.

CTO627S CONTROL-O COSMOS MISSING OBJECT PLB

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.

CTO628S CONTROL-O COSMOS MISSING METHOD PLB

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.

CTO629S CONTROL-O COSMOS MISSING PREREQ PLB

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.

CTO630S CONTROL-O COSMOS GETMAIN ERROR FOR CDT

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 ECSA (Extended Common Service Area) is large enough. If not, increase the ECSA size.

CTO631S CONTROL-O COSMOS GETMAIN ERROR FOR RESTEXT

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.

CTO632S CONTROL-O COSMOS POOL poolname WAS NOT LOADED GLOBAL VARIABLE DATABASE.

Explanation: COSMOS subtask tries to initiate the COSMOS environment but the pool was not loaded.

COSMOS terminated. Control-O continues to operate.

Corrective Action:

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.

CTO633S CONTROL-O COSMOS POOL poolname MAX ROW IS ZERO.

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.

CTO634I CONTROL-O COSMOS HEADER MODE=mode PRE-REQUISITE=poolname OP-FLAGS=flags FSM-FLAGS=flags

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.

CTO635I CONTROL-O COSMOS OBJECTS source_pool-operating_pool METHOD method MODE=mode UP=up DOWN=down UNKNOWN=unknown

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.

CTO636I CONTROL-O COSMOS SYSTEMS a b c d e f g

Explanation: COSMOS subtask displays record type "C" from COSMOLST.

a-g are the system names in the record

Corrective Action: No action is required.

CTO637S CONTROL-O COSMOS SYSTEM system IS NOT IN COSMOS SYSTEMS LIST

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.

CTO650E STORAGE OBTAIN FAILED WITH RETURN CODE rc

Explanation: An attempt to acquire storage for an internal table failed with a return code of rc. The CTOCTI utility requested working storage for an internal table.

The CTOCTI utility terminates.

Corrective Action: Increase the region size specified in the JOB or EXEC JCL statement and rerun the job.

CTO651E OPEN FAILED FOR DDNAME OBJFILE

Explanation: The CTOCTI utility attempted to open the data set referenced by the OBJFILE DD statement but failed.

Possible causes are:

The OBJFILE DD statement is misspelled.
The data set (member) referenced by the OBJFILE DD statement does not exist.

The CTOCTI utility terminates.

Corrective Action: Verify that the data set exists and is spelled correctly. Rerun the job.

CTO652S INTERNAL OBJECT TABLE MUST BE ENLARGED

Explanation: The amount of storage allocated for an internal table is insufficient. The system has more started tasks than the CTOCTI utility anticipated. The storage allocated for one of the internal tables is insufficient.

The CTOCTI utility terminates.

Corrective Action: Contact your INCONTROL administrator.

CTO653E ALESERV ADD FAILED FOR addrSpace WITH RETURN CODE rc

Explanation: Function ALESERV was invoked to analyze address space addrSpace, but failed with return code rc.

Control-O continues its analysis with the next address space.

Corrective Action: No action is required.

CTO654I ADDRESS SPACE addrSpace IS SWAPPED OUT AND WILL BE SKIPPED

Explanation: This information message indicates that Control-O failed to get information from address space addrSpace. Function ALESERV was invoked to analyze the address space but failed because the specified address space is swapped out.

Control-O continues its analysis with the next address space.

Corrective Action: No action is required.

CTO655E ALESERV DELETE FAILED FOR addrSpace WITH RETURN CODE rc

Explanation: Control-O acquired information from address space addrSpace but the attempt to disconnect from the address space failed.

After analyzing the address space, ALESERV function DELETE tried to disconnect from the address space but failed with return code rc.

Control-O continues its analysis with the next address space.

Corrective Action: No action is required.

CTO656I STARTED TASK taskName WILL BE ADDED TO THE DATABASE

Explanation: This information message indicates that started task taskName was not specified in the Object file but was active in the system.

The started task is added to the COSMOS database.

Corrective Action: No action is required.

CTO657I OBJECT_NAME/DESC CLASS_NAME / DESCR ADDRSPAC STATUS

Explanation: This information message is the header for data displayed by message CTO659I. It is generated when invoking the CTOCTI utility.

The J field at the end of this message is usually blank. When J is displayed, it means JOINed, and indicates that the address space is part of a composite address space. For example, CICS monitors use three address spaces: AOR, TOR and FOR.

Corrective Action: No action is required.

CTO658I text.

Explanation: This information message is an internal message issued by the CTOCTI utility. When running the CTOCTI utility to define started tasks for the Control-O/COSMOS database, a Control-O rule traps these internal messages and creates the required definitions for Control-O/COSMOS.

Corrective Action: No action is required.

CTO659I objName classname addrSpace status

Explanation: This information message displays the object name (16 characters), class name (16 characters), address space name (8 characters), status (ACTIVE, INACTIVE, EXCLUDED) and J (1 character)

The J field at the end of this message is usually blank. When J is displayed, it means JOINed and indicates that the address space is part of a composite address space. For example, CICS monitors are use three address spaces: AOR, TOR and FOR.

Corrective Action: No action is required.

CTO660I ADDRESS SPACE addrSpace WILL BE PROCESSED NOW

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.

CTO661I ADDRESS SPACE addrSpace IS SWAPPED OUT AND WILL BE SKIPPED

Explanation: This information message indicates that the CTOCTA utility attempted to get information from the addrSpace address space, but 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.

CTO662E ALESERV ADD FAILED WITH RETURN CODE rc

Explanation: The CTOCTA utility was invoked to get information from the address space but failed with return code 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.

CTO663E ALESERV DELETE FAILED WITH RETURN CODE rc

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.

CTO664I ADDRESS SPACE addrSpace status

Explanation: This information message indicates that address space addrSpace 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.

CTO665E INPUT PARAMETER (ADDRESS SPACE NAME) ERROR DETECTED

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.

CTO666I PROGRAM pgm FOUND IN THE RB CHAIN

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.

CTO667I SVC svcno (TYPE 2 NUCLEUS SVC) FOUND IN AN SVRB

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.

CTO670E ACB CONTROL BLOCK IS NOT VALID

Explanation: The alternate subsystem encountered an ACB control block that does not have a valid identifier.

The Control-O subsystem terminates the connection between the alternate subsystem and the Control-O subsystem.

Corrective Action: Contact BMC Customer Support.

CTO671E SSI ROUTINE SUBSYSTEM IS INACTIVE

Explanation: The CTODMI alternate subsystem module failed to invoke the Control-O subsystem. Because the Control-O subsystem is not active, there is no connection between the alternate subsystem and the Control-O subsystem.

Communication between the alternate subsystem and the Control-O subsystem fails.

Corrective Action: Reactivate Control-O in order to reestablish communication.

CTO672E SSI ROUTINE DETECTED AN ERROR

Explanation: Control-O encountered an internal error (a return code of 16) while attempting to process the SSI request to transmit information from the alternate subsystem to the Control-O subsystem.

The information is not transmitted.

Corrective Action: Contact BMC Customer Support.

CTO673E SSI ROUTINE RETURNED AN UNDEFINED RETURN CODE

Explanation: Control-O encountered an internal error (a return code of 20) while processing an SSI request. The alternate subsystem was trying to transmit data to the Control-O subsystem.

The data is not transmitted.

Corrective Action: Contact BMC Customer Support.

CTO674E CTO SSCT POINTER NOT SET - SSI ROUTINE INVOCATION BYPASSED

Explanation: The pointer to the Control-O subsystem SSCT was not set. The initialization process normally sets the pointer to the Control-O subsystem SSCT.

Communication between the Control-O subsystem and the alternate subsystem terminates.

Corrective Action: Contact BMC Customer Support.

CTO681E DSN dsn - NOT A LIBRARY

Explanation: The requested DSN is not a partitioned data set. Possible causes are:

New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.
Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.

The system action depends on the cause, as follows:

New Day procedure - ends with errors.
AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.

Corrective Action: The appropriate response depends on the cause, as follows:

New Day procedure - Correct the name of the data set described by the DACAL DD statement to the name of your calendar library.
AutoEdit facility - Correct the JCL for the job and rerun it.
Online facility - Correct the library name and retry.

CTO683E DSN dsn - LRECL NOT 80

Explanation: Record length of the requested DSN is not 80. Possible causes are:

New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.
Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
Control-M Online facility - schedule definition or calendar definition.

The system action depends on the cause, as follows:

New Day procedure ends with errors.
AutoEdit facility - job submission stops.
Online facility - reading or updating of the table calendar is not performed.

Corrective Action: The appropriate response depends on the cause, as follows:

New Day procedure - Correct the name of the data set described by the DACAL DD statement to the name of your calendar library.
AutoEdit facility - Correct the JCL for the job and rerun it.
Online facility - Correct the library name and retry.

CTO684E DSN dsn IN USE (DISP=OLD)

Explanation: The DSN is held exclusively by another user.

Possible causes are:

Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.
Control-O initialization.
CMEM initialization.

The system action depends on the cause, as follows:

AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.
Control-O is not started.
CMEM is not started.

Corrective Action: Try again.

CTO686E DSN dsn NOT IN CATALOG

Explanation: The requested DSN dsn is not in the catalog. Possible causes are:

Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.
New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.

The system action depends on the cause, as follows:

AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.
New Day procedure ends with errors.

Corrective Action: The appropriate response depends on the cause, as follows:

AutoEdit facility - correct the JCL for the job and rerun it.
Online facility - correct the library name and retry.
New Day procedure - correct the New Day procedure and retry.

CTO687E DSN dsn - DYNAMIC ALLOCATION FAILED

Explanation: Dynamic allocation for the requested DSN dsn failed. Possible causes are:

Control-M AutoEdit facility - failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - schedule, calendar or rule definition.

This can also happen when the Control-M Online facility is activated under the Control-M Online facility (nesting) and you are trying to access the same library in two screens.

The system action depends on the cause, as follows:

AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.

Corrective Action: Exit the Online facility and retry. If this happens under batch environment or in Control-M AutoEdit facility, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTO688E INTERNAL ERROR - INVALID REQUEST TO CTMMEM. INFORM IOA ADMINISTRATOR

Explanation: Internal IOA error while trying to read a member from a library. Possible causes are:

New Day procedure - failure to read a calendar from the data set described by the DACAL DD statement.
IOA AutoEdit facility - failure to allocate or read a symbols member (a %%GLOBAL statement, or a %%LIBSYM %%MEMSYM statement, or a %%INCLIB %%INCMEM statement). When using the %%INCMEM DDNAME= ddn format, ensure that ddn is allocated by the required procedure (Control-M monitor, IOA Logon procedure, and so on).
IOA Online facility - schedule, calendar or rule definition.

The system action depends on the cause, as follows:

New Day procedure ends with errors.
AutoEdit facility - job submission stops.
IOA Online facility - reading or updating of the table, calendar or rule is not performed.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTO690E INVALID RETURN CODE FORM CTMMEM - INFORM IOA ADMINISTRATOR

Explanation: Internal IOA error while trying to read a member from a library. Possible causes are:

New Day procedure - Failure to read a calendar from the data set described by the DACAL DD statement.
IOA AutoEdit facility - Failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement).
IOA Online facility - Schedule definition or calendar definition.

The system action depends on the cause, as follows:

New Day procedure ends with errors.
AutoEdit facility - Job submission stops.
Online facility - Reading or updating of the table or calendar is not performed.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

CTO691E ERROR WHILE PROCESSING DIRECTORY OF LIBRARY

Explanation: Internal Control-M error while trying to read a directory of a library during schedule definition, calendar definition, batch utility, etc.

Online facility - Tables or calendars list is not shown.

Corrective Action: For batch utility, correct the error and rerun the job.

CTO692E LIBRARY OPERATION FAILED. REASON rsn

Explanation: Internal Control-M error while trying to process a member from a library. Possible causes are shown in the following table:

Circumstances	System Action	Possible Cause
New Day procedure	New Day procedure terminates with errors	Failure to read a calendar from the data set described by the DACAL DD statement
Control-M AutoEdit facility	Job submission is stopped	Failure to read a symbols member (%%GLOBAL statement, or %%LIBSYM %%MEMSYM statement)
Control-M Online facility	Processing of schedule, mission, rule or calendar definition is not performed	Internal failure to process the schedule, mission, rule or calendar definition

Corrective Action: Examine any prior system message. If there is no such message, prepare the Control-M monitor full output and contact BMC Customer Support for assistance.

Parent Topic

CTO messages