CTO–CTT

This group includes messages for the Control-O Control-M for z/OS , Control-M/Assist, Control-M/Links for z/OS , Control-M/Restart and Control-M/Tape products.

CTO Messages

This group includes messages for the Control-O product.

Messages CTO0 through CTO0xx

This group includes messages for the Control-O product.

CTO001I {CONTROL-O | CTMCMEM} `monitor` TIMER SUBTASK STARTED. LEVEL `sting`

Explanation: This information message indicates the start of the Control-O TIMER task, which controls the product timer and cleanup processing.

Corrective Action: No action is required.

CTO002I {CONTROL-O | CTMCMEM} TIMER SUBTASK ENDED.

Explanation: This information message indicates the normal termination of the Control-O TIMER task which controls the product timer and cleanup processing.

Corrective Action: No action is required.

CTO004I SVCDUMP WAS CAPTURED SUCCESSFULLY.

Explanation: The Control-O or CMEM monitor successfully captured an SVC dump as a result of an internal process request.

The monitor continues to operate normally.

Corrective Action: Verify that the dump has been successfully written to the system dump files.

CTO005E SVCDUMP WAS FAILED. A PARTIAL DUMP WAS TAKEN BECAUSE THE DUMP DATA SET DID NOT HAVE SUFFICIENT SPACE.

Explanation: The Control-O or CMEM monitor tried to dump the monitor and ECSA. The dump request failed because the dump dataset is too small to contain all the areas that are dumped.

The monitor continues to operate normally.

Corrective Action: Increase the dump files, since they are too small for Control-O or CMEM requirements. Take into account that the ECSA is also dumped by the request.

CTO006E SVCDUMP CAPTURED FAILED RC 8 REASON= `reason` (HEX).

Explanation: The Control-O or CMEM monitor tried to dump the monitor and ECSA storage areas. The dump request failed. The SDUMPX system service returns a return code of 8.

The monitor continues to operate normally.

Corrective Action: Refer to SDUMPX Reason Codes for Return Code 08 in IBM’s MVS Programming Authorized Assembler Services Reference.

CTO007W RELEASING ORPHAN WSC AT `address` JOBNAME= `jobName` ASID= `asid`

Explanation: The Control-O or CMEM monitor found that the WSC block is marked as in use, but it is not in use.

The monitor continues to operate normally. It may issue an SVCDUMP request.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

The SVCDUMP file
The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

CTO008W RELEASING TIMED-OUT WSC AT `address` JOBNAME= `jobName` ASID= `asid`

Explanation: The Control-O or CMEM monitor found that the WSC block has been marked as being in use for a very long time. Normally, the Control-O or CMEM process should hold the WSC block only for a very short time.

The monitor continues to operate normally. It may issue an SVCDUMP request.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

The SVCDUMP file
The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

CTO009I TIMEOUT WSC AT `address` JOBNAME= `jobName` ASID= `number`

The monitor continues to operate normally. The monitor will check the WSC again in subsequent cycles and then decide what action to take.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

The SVCDUMP file
The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

CTO00AE CTOTMO RESUMED AFTER ABENDING WHILE TRYING TO RELEASE A WSC

Explanation: Control-O subtask CTOTMO has resumed normal execution after abending while trying to release a WSC that was locked for a long time.

A SYSABEND is generated for the first occurrence of this abend.

Corrective Action: Send the dump to BMC Customer Support for investigation.

CTO046S BLDL/LOAD FAILED FOR THE MODULE " `modName` "

Explanation: Loading of the modName module failed.

Possible causes are:

The IOA Load library is not in the load modules search list (STEPLIB + Linklist).
There is insufficient memory.
There is some other system-oriented reason, which may be found in the syslog.

Execution might stop.

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

Messages CTO100 through CTO1xx

This group includes messages for the Control-O product.

CTO100I {CONTROL-O | CTMCMEM} RELEASE `x.x.xx`- MONITOR STARTED

Explanation:This information message is a normal message issued when the Control-O or CMEM monitor is started. The version of the monitor that is starting (x.x.xx) is indicated in the message text.

Corrective Action:No action is required.

CTO101S MONITOR STARTED WITH INCORRECT STORAGE KEY. CHECK PPT DEFINITION

Explanation:During initialization self-checks, the Control-O or CMEM monitor discovered that a storage key was specified that was not in the range from 1 through 7. The Control-O or CMEM monitor only works using storage keys 1 through 7.

The monitor terminates.

Corrective Action:Perform the following steps:

Define the CTOMTO7 in SYS1.PARMLIB(SCHED xx) with a key in the range from 1 through 7.
Refresh the SCHED xxusing the MVS SET command.
Stop the Control-D subsystem by means of the command S IOASTERM,TYPE=D
Disconnect the IOA subsystem by means of the command S IOASDISC,SSNAME= ioa_subsystem
Start the Control-O or CMEM monitor.
Start the Control-D monitor and subsystem.

CTO102I CONTROL-D FUNCTIONS ENABLED

Explanation:This information message indicates that during Control-O monitor startup, an installed Control-D was detected. Therefore, Control-D functionality using DO CTD REQ was enabled.

Corrective Action:No action is required.

CTO102S {CONTROL-O | CTMCMEM} MONITOR IS NOT APF-AUTHORIZED

Explanation:The Control-O or CMEM monitor has lost APF-authorization. Possible causes are:

The IOA Load library is not authorized.
An internal error.

The Control-O or CMEM monitor shuts down.

Corrective Action:Make sure that the IOA Load library is authorized, and restart Control-O or CMEM.

CTO103E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

Explanation:An invalid parameter was passed to the Control-O or CMEM monitor by an operator modify (F) command. This is a header message for message CTO125I. A list of valid modify parameters is displayed on the operator console in message CTO125I.

The modify command is rejected.

Corrective Action:Enter a valid modify parameter.

CTO103W CONTROL-D FUNCTIONS DISABLED. "DO CTD REQ." WILL BE REJECTED

Explanation:During Control-O monitor startup, no installed Control-D was detected. Therefore, Control-D functionality using DO CTD REQ was disabled.

Monitor startup continues.

Corrective Action:Notify your INCONTROL administrator.

CTO104S BLDL/ATTACH FAILED FOR TASK `taskName`

Explanation:Initialization of one of the Control-O or CMEM monitor internal tasks failed.

Possible causes are:

The task is not found in the IOA Load library.
There is insufficient storage for the Control-O or CMEM monitor.

The Control-O or CMEM monitor shuts down.

Corrective Action:Call your systems programmer for assistance. If necessary, increase the Control-O or CMEM REGION size.

CTO105S UNRECOVERABLE ERROR ENCOUNTERED

Explanation:An unrecoverable error occurred in the operation of the Control-O or CMEM monitor.

The IOA Log usually contains a previous message concerning the error.

The Control-O or CMEM monitor shuts down with user abend 0006.

Corrective Action:Call your systems programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.

CTO106S SUBTASK `taskName` ABENDED `abCode`

Explanation:The Control-O or CMEM monitor internal taskNamehas abended.

The Control-O or CMEM monitor shuts down.

Corrective Action:Call your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support for assistance.

CTO107I SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation:This information message indicates that the Control-O or CMEM monitor is shutting down upon operator request.

The Control-O or CMEM monitor is shut down.

Corrective Action:No action is required.

CTO108S UNABLE TO ESTABLISH THE CROSS MEMORY ENVIRONMENT. STEP `stepName`

Explanation:Control-O or CMEM monitor could not establish the cross memory environment required for its operation.

Corrective Action:Call your systems programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance and provide the step name indicated in the message.

CTO109I CONTROL-O MONITOR IS SHUTTING DOWN. A NEW MONITOR WAS STARTED

Explanation:This information message indicates that a new Control-O or CMEM monitor has been started. This message is issued by the previous Control-O or CMEM monitor to indicate that it is shutting down.

The Control-O or CMEM monitor that was operating previously shuts down.

Corrective Action:No action is required.

CTO10AI CONTROL-M FUNCTIONS ENABLED

Explanation:This information message indicates that during Control-O or CMEM monitor startup, Control-M was detected, and therefore, Control-M functions DO FORCEJOB and DO RESOURCE were enabled.

Corrective Action:No action is required.

CTO10BW CONTROL-M FUNCTIONS DISABLED. "DO FORCEJOB / RESOURCE" WILL BE REJECTED

Explanation:During Control-O or CMEM monitor startup, Control-M functions DO FORCEJOB and DO RESOURCE were disabled because no installed Control-M was detected.

Monitor startup continues.

Corrective Action:Notify the INCONTROL administrator.

CTO10DW CTOPARM PARAMETER DAYTIMEO ( `cto_time`) SHOULD BE EQUAL TO DAYTIMEM ( `ctm_time`) OF CTMPARM.

Explanation:During the startup of the Control-O monitor, it was found that the value of the DAYTIMEO Control-O parameter was not identical with the value of the DAYTIMEM Control-M parameter.

The DAYTIMEO Control-O parameter sets the start of the work day for Control-O. The DAYTIMEM Control-M parameter sets the start of the work day for Control-M. Any discrepancy between these two parameters may result in the same time being interpreted differently by Control-O and Control-M.

The variables in this message are:

cto_time- the value of the DAYTIMEO Control-O parameter
ctm_time- the value of the DAYTIMEM Control-M parameter

Monitor startup continues.

Corrective Action:Contact your INCONTROL administrator.

CTO111E INVALID DATE IN ORDER/FORCE MODIFY COMMAND

Explanation:An invalid date was specified in the ORDER or FORCE modify command. If a date (D) is specified in the ORDER or FORCE modify (F) operator command, it must have a valid site-dependent format.

Valid formats are:

mmddyy
ddmmyy

The command is not executed.

Corrective Action:Issue the command with the correct date.

CTO112E SMFID `smfid` IS NOT DEFINED IN IOACPRM INSTALLATION PARAMETERS

Explanation:The Control-O or CMEM subsystem initialization routine is running under a CPU that was not defined in the IOACPRM member.

Possible causes are:

The CPU in which Control-O or CMEM runs is not defined in the IOACPRM member.
The computer in which Control-O or CMEM runs is a multi-CPU computer, and the SID parameter in the SMFPRMxx member in SYS1.PARMLIB does not define all the CPUs correctly.

The Control-O or CMEM monitor shuts down.

Corrective Action:Do the following:

Check that the SMFID of the computer in which Control-O or CMEM is being initialized is defined in the list of SMFIDs in the IOACPRM member.
If the IOACPRM definition appears correct, check the SMFID defined in SYS1.PARMLIB.
In a multi-CPU computer, issue from the console the MVS command D M=CPU to receive a listing of all CPU serial numbers, and compare them with the PARMLIB definition.

CTO115W FORMSUB3 DOES NOT NEED TO BE RUN WHEN SYSTLOGR=Y, NO ACTION TAKEN

Explanation:This message is received when you attempt to run FORMSUB3 (typically, when adding a new system), and the SYSTEM LOGGER is active (that is, the System Logger manages the communication between Control-M CMEM or Control-O and the subsystems). In such a scenario, there is no need to update the Monitor-to-Subsystem file.

Corrective Action:No action is required.

CTO120I CONTROL-O MONITOR SHUTTING DOWN

Explanation:This information message is produced by Control-O or CMEM when shutting down the Control-O or CMEM monitor by a P command, or on certain internal Control-O or CMEM events.

The IOA Log usually contains additional messages concerning the reason for the Control-O or CMEM shutdown.

Control-O or CMEM monitor shuts down.

Corrective Action:No action is required.

CTO121S CONTROL-O MONITOR ENDED WITH ERROR

Explanation:Highlighted, unrollable message.

A severe error has occurred. Control-O or CMEM monitor is shutting down.

The IOA and systems logs usually contain additional messages concerning the reason for the Control-O or CMEM shutdown.

Control-O or CMEM monitor shuts down. Before shutting down, the Control-O or CMEM monitor attempts to start a new CONTROLO or CMEM monitor to replace itself. If it cannot start after a few attempts, Control-O or CMEM gives up.

Corrective Action:Check the IOA and systems logs for additional messages, and take appropriate corrective action.

CTO122S NOT ENOUGH STORAGE IN EXTENDED CSA FOR `blockname`. RETURN CODE= `rc`

Explanation:Control-O or CMEM was unable to acquire enough storage in ECSA for the specified control block ( blockname).

Control-O acquires storage in ECSA for its working areas (WSC), and for wait elements (PND). The number of wait elements is specified by the WAITPR# parameter in the CTOPARM member.

CMEM acquires storage in ECSA for its working areas (WSC).

In this message, rcis the return code issued by the failed GETMAIN call.

Control-O or CMEM terminates.

Corrective Action:Check ECSA utilization of the system. For Control-O, if necessary, reduce the number of wait elements specified by the WAITPR# parameter in the CTOPARM member.

CTO123I CONTROL-O INTERVAL IS SET TO `nn` SECONDS

Explanation:This information message is a result of setting a Control-O or CMEM sleeping interval by an operator command.

For more information, see the section on modifying the Control-O or CMEM sleeping interval in the INCONTROL for z/OS Administrator Guide.

Control-O or the CMEM monitor will “wake up” every nnseconds and check on time-related events.

Corrective Action:No action is required.

CTO124E INTERVAL MUST BE A TWO DIGIT NUMBER BETWEEN 01-99 SECONDS

Explanation:An invalid Control-O or CMEM sleeping interval was specified in an operator modify (F) command. The Control-O or CMEM sleeping interval must be a 2-digit number of seconds, from 01 through 99 seconds. For more information, see the section on modifying the Control-O or CMEM sleeping interval in the INCONTROL for z/OS Administrator Guide.

Corrective Action:No action is required.

CTO124W CONTROL-O PARAMETER `parmName`= `parmValue`{ > | < } `parmDefault`- USING DEFAULT VALUE

Explanation:When the Control-O monitor starts, it checks to ensure that the values of the parameters in CTOPARM are within the valid range. One of the parameters ( parmName) is set to a value ( parmValue) that is either too high (>) or too low (<).

Control-O resets the value of parmNameto the default value for that parameter, and the monitor continues its startup.

Corrective Action:Correct the value of parmNamein CTOPARM. If required, stop and restart the Control-O monitor.

CTO125I `parmList`

Explanation:This information message provides a list of valid modify parameters that can be passed to the Control-O or CMEM monitor by an operator modify (F) command. This message appears after header message CTO125I.

Corrective Action:No action is required.

CTO126W LOAD OF IOADEST TABLE FAILED: DO SHOUT WILL NOT BE SUPPORTED

Explanation: During the startup of the Control-O monitor or the execution of a NEWDEST command, the Dynamic Destination table was not successfully loaded or renewed.

Monitor startup or operation continues. The Dynamic Destination table is not loaded or renewed. DO SHOUT requests will not be performed.

Corrective Action: Contact your INCONTROL administrator.

CTO127I NEWDEST COMMAND ACCEPTED

Explanation:This information message is a result of the acceptance of an operator NEWDEST command passed to the Control-O or CMEM monitor.

A new dynamic destination table is loaded. The next time that the Control-O or CMEM monitor sends a message using the SHOUT facility, it will use the new destination table.

Corrective Action:No action is required.

CTO128I RULE TYPE TABLE STATUS LIBRARY PRIORITY

Explanation:Normal response of the Control-O or CMEM monitor after the DISPLAY command is issued. This information message is the header of the list of rules being shown in response to the DISPLAY command.

Corrective Action:No action is required.

CTO129I `ruleName type tableName status lib priority`

Explanation:Messages sent by the Control-O or CMEM monitor to the console in response to the DISPLAY command. Each message describes a rule. These information messages are preceded by the MTO128I or CTO128I message, which supplies the header for each field.

Corrective Action:No action is required.

CTO12BI WISH WO0949 IS {ENABLED | DISABLED} - CICS LONG MESSAGES SUPPORT

Explanation:This information message is issued by the Control-O monitor when it enables or disables optional wish WO0949.

Corrective Action:No action is required.

CTO12CI WISH WO0975 IS ENABLED - MONITOR WILL WAIT UNTIL MIGRATED LIBRARIES WILL BE RESTORED

Explanation:This information message is issued by the Control-O monitor when it enables optional wish WO0975.

Corrective Action:No action is required.

CTO12DI WISH WO0975 IS DISABLED - MONITOR WILL IGNORE MIGRATED LIBRARIES

Explanation:This information message is issued by the Control-O monitor when it disables optional wish WO0975.

Corrective Action:No action is required.

CTO12EI WISH WO0976 IS ENABLED - MESSAGES HANDLED AS IS

Explanation:This information message is issued by the Control-O monitor when it enables optional wish WO0976.

Corrective Action:No action is required.

CTO12FI WISH WO0976 IS DISABLED - MESSAGES HANDLED IN UPPER CASE

Explanation:This information message is issued by the Control-O monitor when it disables optional wish WO0976.

Corrective Action:No action is required.

CTO12SI RULE LIST DISPLAY FOR LPAR `lpar_name`:

Explanation: This message is a header for a detailed list of rules generated by the Control-O monitor or CMEM monitor in response to the following commands:

F CONTROLO,DISPLAY=DETAIL
F CTMCMEM,DISPLAY=DETAIL

For more information about the generated list of rules, see Displaying Active Rules (for Control-O) or Displaying Active Rules (for CMEM).

Corrective Action: No action is required.

CTO130I IN `condName date`

Explanation:Messages sent by the Control-O monitor to the console in response to the DISPLAY command. The message describes the prerequisite conditions necessary for the rule to become eligible.

Corrective Action:No action is required.

CTO131I TIME FROM `hhmm` UNTIL `hhmm` INTERVAL `interval`

Explanation:Messages sent by the Control-O monitor to the console in response to the DISPLAY command. This information message describes the time dependencies required by the specific rule in order to become eligible.

Corrective Action:No action is required.

CTO132I REQUEST TO STOP THE CONTROL-M API ACCEPTED

Explanation:The Control-O monitor accepted an F CONTROLO,CTMAPISTOP command.

The monitor confirms it received the command for execution.

Corrective Action:No action is required.

CTO133I CONTROL-M API STOPPED

Explanation:The Control-O monitor successfully processed an F CONTROLO,CTMAPISTOP command.

The monitor confirms it executed the command.

Corrective Action:No action is required.

CTO134I {CONTROL-O | CTMCMEM} WORKING DATE HAS CHANGED FROM `old_dateTO new_date`

Explanation:This information message is displayed when Control-O or CMEM changes the working date.

In Control-O, the time is set according to the DAYTIMEO parameter in the CTOPARM member. In CMEM, the time is set according to the DAYTIMEO parameter in the CMMPARM member, which must be the same as the DAYTIMEM parameter in the CTMPARM member.

Control-O or CMEM monitor displays the new date.

Corrective Action:No action is required.

CTO135I {CONTROL-O | CTMCMEM} DEBUG LEVEL IS SET TO lvl

Explanation:This information message indicates that the Control-O or CMEM debug level was set by an operator modify (F) command.

The DEBUG level is set to a new level. Each debug level activates the trace option on different components of Control-O or CMEM.

Corrective Action:No action is required.

CTO136E DEBUG LEVEL MUST BE A NUMBER BETWEEN 0-255

Explanation:An invalid DEBUG level has been entered in the modify (F) operator command to activate Control-O or CMEM debugging facilities. Valid DEBUG levels are from 0 through 255. 0 specifies no debugging.

Issue the command with the correct debugging level. The required debugging level should be supplied by BMC Customer Support.

Corrective Action:No action is required.

CTO136I THE CONTROL-M API WILL BE RESTARTED WITH THE FIRST API REQUEST

Explanation:The Control-O monitor successfully processed anF CONTROLO,CTMAPISTART command.

Corrective Action:The monitor confirms that it executed the command, and that the next API request will reallocate the API resources (such the Control-M Active Job File or Control-M Resources file).

CTO137S INVALID PARAMETERS ( `parmList`) PASSED TO THE {CONTROL-O | CTMCMEM} MONITOR

Explanation:One or more parameters passed to the Control-O or CMEM monitor in a start command are invalid.

The Control-O or CMEM monitor shuts down.

Corrective Action:For additional information regarding starting a Control-O or CMEM monitor, see the INCONTROL for z/OS Administrator Guide. Check and correct the parameters, and start the Control-O or CMEM monitor again.

CTO138I CONTROL-O OPERATING MODE IS `opermode`

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

This information message indicates that the command MODE=RESUME,CANCEL, the command MODE=RESUME,CONTINUE, or a query about Control-O current status was issued.

Control-O resumes automatic processes.

Corrective Action:No action is required.

CTO138I CANNOT START THE CONTROL-M API - FIRST REQUEST ALREADY PROCESSED

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

The Control-O monitor successfully processed an F CONTROLO,CTMAPISTART command, but failed. Either the monitor has already processed this command and also processed its first API request, or the monitor processed a CTMAPISTOP command since it was started, and it already has processed API requests.

Corrective Action:No action is required.

CTO139I {CONTROL-O | CTMCMEM} SUBSYSTEM `subsys` IS ALREADY ACTIVE

Explanation:This information message indicates that the subsystem cannot be activated or initialized because it has already been activated. This is a normal message during subsystem initialization, when Control-O or CMEM determines that a subsystem was already activated by a previous monitor.

A new subsystem is not activated.

Corrective Action:No action is required.

CTO13AI WISH WO0986 IS NO LONGER SUPPORTED. USE MESSAGE REROUTING FEATURE TO GET THE SAME SERVICE.

Explanation:Wish WO0986 was used in earlier Control-O releases to suppress message LDT507I from being written to the IOALOG. As of Control-O 6.2.01, the same functionality is obtained using the standard IOA Messages routing function.

The wish is ignored and Control-O or CMEM monitor starts. If you do not perform the following steps, message LDT507I will be written to the IOALOG.

Corrective Action:Perform one of the following options:

In order to prevent the message from being written to the IOALOG, add the following card to the MSGROUT member in IOA.V620.PARM: MSGCODE=LDT507I,ROUT=(OUT)
The constraint created by message LDT507I in previous releases can be prevented by increasing the value of RQC# in CTOPARM. Generally, increase the RQC# by 10%.

CTO13BI CURRENT DATE IS `new_date`

Explanation:This information message is displayed at midnight when the date is changed.

Corrective Action:No action is required.

CTO13JI WISH O10261 IS ENABLED - REGULAR WTO MESSAGES WILL TERMINATE COMMAND-RESPONSE MODE; %%$WAITRC CORRECTIONS

Explanation: This information message is issued by the Control-O monitor when it enables optional wish O10261.

Corrective Action:No action is required.

CTO140I CONTROL-O OPERATING MODE IS `opermode`

Explanation:Highlighted, unrollable message

This information message indicates that Control-O issued a MODE=FREEZE, MODE=LOGONLY or MODE=TRIGGERONLY command. The Control-O internal log indicates any rules that failed to run.

Control-O automatic processes act as follows:

FREEZE - Control-O stops operating
LOGONLY - Control-O continues logging but stops triggering new rules
TRIGGERONLY - Control-O continues but only simulates the triggering of new rules.

Corrective Action:Possible responses are:

Stop Control-O and start a new Control-O monitor (recommended).
Issue command RESUME,CONTINUE. Control-O ignores rules in wait mode and continues.
Issue command RESUME,CANCEL. Control-O cancels rules in wait mode and continues.

CTO141W {CONTROL-O | CTMCMEM} MONITOR WAS CANCELLED BY OPERATOR

Explanation:Highlighted, unrollable message.

This message is issued when the Control-O or CMEM monitor is cancelled by an operator MVS cancel command.

The Control-O or CMEM monitor is shut down.

Corrective Action:No action is required.

CTO142S CONTROL-O MONITOR DETECTED AN INTERNAL `abCode` ABEND

Explanation:This message is issued when Control-O or CMEM has detected certain internal system abend codes during operation.

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 cannot start after a few attempts, Control-O or CMEM ceases trying.

Corrective Action:Call you systems programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.

CTO143I A NEW {CONTROL-O | CTMCMEM} MONITOR IS INITIATED

Explanation:This information message occurs after Control-O or CMEM detected an internal problem and started a new monitor as a recovery measure.

A new Control-O or CMEM monitor is started, and takes control over the current one.

Corrective Action:Check for additional messages in the IOA and system logs detailing the cause of the abend.

CTO144E INVALID ORDER/FORCE PARAMETERS

Explanation:An invalid syntax of ORDER or FORCE commands was passed to the Control-O or CMEM monitor by an operator modify (F) command. See the INCONTROL for z/OS Administrator Guide for additional information regarding the parameters of the ORDER or FORCE command.

The command is not executed.

Corrective Action:Correct the syntax of the ORDER or FORCE command.

CTO145S AUTOEDIT FAILED, RC= `rc`, REASON= `rsn`

Explanation:The Control-O or CMEM monitor failed to perform an AutoEdit function.

The problem was probably caused by a failure to read or write the global AutoEdit member, or invalid data in the global AutoEdit member.

The AutoEdit function is not performed.

Corrective Action:Consult the table of return codes and reason codes in the following table to determine the cause of the error, and correct accordingly. If the return code or reason code is not in the table, the cause of failure is an internal error. In this case, contact BMC Customer Support.

Return 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 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, and 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.
	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.

CTO146W MISSING GLOBAL AUTOEDIT LIBRARY/MEMBER

Explanation:During Control-O initialization, a Global AutoEdit member or its library was not found.

When Control-O is started, it reads the $GLOBAL member. A different Global library (in which a $GLOBAL AutoEdit member resides) is used for each computer (SMFID) on which Control-O operates. Each unique library name is composed of the prefix defined in the GLBPREF parameter of the Control-O installation parameters, and as the last data set name qualifier, the letters CPU followed by the SMFID of the specified computer.

Although Control-O will process Global variables, it will not read or write to this particular Global member/library.

Corrective Action:Check the designation of the GLBPREF parameter in the Control-O installation parameters. You must allocate a Global AutoEdit library for every computer in which Control-O runs. See “Control-O Operational Parameters” in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTO147I CONTROL-O INITIALIZATION COMPLETE. TYPE= `type` SUB= `subsys` RUN#= `nnnn`

Explanation:This information message indicates that Control-O or CMEM initialization has completed successfully and Control-O or CMEM facilities are active.

The variables in this message are:

type- the type of the startup which was passed to Control-O or CMEM as a parameter in the START commandIf no TYPE value was passed to Control-O or CMEM, the default is TYPE=REGULAR.
subsys- the name of the subsystem that started Control-O or CMEM (JES2, JES3, MSTR, and so on)
nnnn- the number of times Control-O was replaced by a new Control-O or CMEM

Control-O or CMEM facilities are now active.

Corrective Action:No action is required.

CTO148W CONTROL-O STATISTICS ALREADY ACTIVE

Explanation:Control-O received the F CONTROLO,STARTSTAT command to start the Message Statistics facility, but the facility was already active.

The STARTSTAT command is ignored.

Corrective Action:No action is required.

CTO149W CONTROL-O STATISTICS NOT ACTIVE

Explanation:Control-O received the F CONTROLO,STOPSTAT command to stop the Message Statistics Facility, but the facility was not active.

The STOPSTAT command is ignored.

Corrective Action:No action is required.

CTO14AE INVALID `modifyCommand` COMMAND KEYWORD = `keyword`

Explanation:Control-O or the CMEM monitor received the modifyCommand command with an invalid keyword.

The modifyCommand command is rejected.

Corrective Action:Correct the invalid command and reissue it.

CTO14BI SVC DUMP `keyword` NOW ENABLED

Explanation:This information message is in response to the modify SVCDUMP command, and indicates that a valid keyword has been enabled.

Corrective Action:No action is required.

CTO14CI SVC DUMP `keyword` NOW DISABLED

Explanation:This information message is in response to the modify SVCDUMP command, and indicates that a valid keyword has been disabled.

Corrective Action:No action is required.

CTO14DE CTOXOH RESUMED AFTER ABENDING WHILE PROCESSING PENDING REQUESTS

Explanation:The Control-O XES subtask CTOXOH has resumed normal execution after abending while trying to purge an XES request that was pending for excessively long time.

An SVCDUMP is generated for the first occurrence of this abend.

Corrective Action:Send the dump to BMC Customer Support for investigation.

CTO14DW SHUTDOWN IS DELAYED DUE TO XES SYSTEM-MANAGED REBUILD PROCESS. TO CANCEL THE DELAY REPLY "FORCE"

Explanation:Control-O or CMEM cannot shut down when an XAE structure is unavailable due to system-managed rebuild. Control-O will resume its termination process when the system-managed process finishes and the structure becomes available again.

When FORCE is replied, Control-O or CMEM will continue termination without waiting for the system-managed process to finish and the XAE structures to become available. Beware that after forcing immediate termination, the following may occur:

Abends in processes accessing the IOA Global variables (subsystem environment, online, and so on.).
Further delays in Control-O termination due to requests issued to the XAE structures when writing the IOA Global pools to the databases as part of the termination process may be deferred by the system-managed process in progress.

Corrective Action:None, unless immediate termination is required. If immediate termination is required, reply FORCE.

See System actionfor considerations before replying FORCE.

CTO14EW `monitor` INITALIZATION IS CANCELLED. START `monitor` WHEN XAE STRUCTURES ARE AVAILABLE

Explanation:The operator replied CANCEL to message IOAFBCW to cancel Control-O or CMEM initialization, after connection to an XAE structure was prevented.

Control-O or CMEM terminates.

Corrective Action:Start Control-O or CMEM after making sure that:

The coupling facility required for XAE structures is available.
XAE structures, if already allocated, are available.

CTO14FS XAE `function` FUNCTION FAILED. RC=`rc` RSN=`rsn`

Explanation:A request to the XES AutoEdit facility (XAE) to either put or get a variable from an S1 or S2 database (typically IOAVAR) has failed. The failure might have been caused by either a Coupling Facility-related error or by a Control-O/CMEM internal error.

An SVCDUMP is generated for the first occurrence of this failure.

Corrective Action:Review the SYSLOG, which may contain Coupling Facility-related error messages. If the problem persists, consider starting a new Control-O/CMEM monitor over the old one. Send the dump to BMC Customer Support for investigation.

CTO150I SNAP COMMAND WAS PERFORMED. SNAP ID= `id`

Explanation:This information message indicates that Control-O or CMEM successfully executed the F CONTROLO,SNAP or F CMEM,SNAP command.

In this message, id is the snap ID as shown in the snap title.

A set of diagnostic snapshots is printed.

Corrective Action:No action is required.

CTO151W IOA LOG UPDATE FAILED. SOME MESSAGES MAY BE LOST

Explanation:Control-O or CMEM was unable to write messages to the IOA Log file. This message follows other messages indicating the cause of the error.

Processing continues. Some messages to the IOA Log file may be lost.

Corrective Action:Check the preceding messages and act accordingly.

CTO152I STANDALONE FACILITY ENABLED, `rsn`

Explanation:This information message indicates that Control-O is now entering standalone mode and will now update the IOA Log file.

When Control-M is active, update of the IOA Log file is performed by Control-M. When Control-M is not installed or inactive, update of the IOA Log file is performed by Control-O.

Control-O enters standalone mode and updates the IOA Log file.

Corrective Action:No action is required.

CTO153I STANDALONE FACILITY DISABLED, `rsn`

Explanation:This information message indicates that Control-O is exiting standalone mode.

When Control-O is in standalone mode, it updates the IOA Log file. When Control-M becomes active, Control-M takes over the updating of the IOA Log file.

Control-O exits standalone mode and Control-M takes over the updating of the IOA Log file.

Corrective Action:No action is required.

CTO154E CONTROL-O CANNOT START. CONTROL-M IS NOT INSTALLED

Explanation:Control-O was set to run with SMODE set to N, but Control-M, which must execute some activities on behalf of Control-O, is not installed. If the SMODE (Stand Alone mode) installation parameter is set to N, Control-M must be installed. If Control-M is not installed, SMODE must be set to Y.

Control-O terminates.

Corrective Action:Either install Control-M, or set the SMODE installation parameter to Y.

CTO155W SWAP OF `addr` CHAIN ERROR, TYPE= `type` RC= `rc`

Explanation:Control-O is unable to pass internal request blocks to the new Control-O monitor.

This message indicates an internal error.

The old Control-O monitor terminates with an error. The new monitor, however, will continue processing. Some requests may be lost.

Corrective Action:Contact BMC Customer Support.

CTO156W AUTOMATION LOG STATUS UNCHANGED

Explanation:This warning message is issued in response to an invalid AUTOLOG MODIFY command. Either the specified parameter is invalid, or the user specified a MODIFY command (F CONTROLO,AUTOLOG=YES/NO) designed to set the Automation Log status to a status that it already had.

The status of writing to the Automation Log is unchanged.

Corrective Action:Verify the command and retry if necessary.

CTO157I `action` SERVER `serverId` REQUESTED

Explanation:This information message indicates that Control-O has begun performing the action requested in a SERVER MODIFY command.

Corrective Action:No action is required.

CTO158W `action` SERVER `serverId` FAILED - `rsn`

Explanation:Control-O was unable to execute the requested SERVER MODIFY command (action).

Processing continues. The status of the server remains unchanged.

Corrective Action:Check the reason specified in the message and proceed accordingly.

CTO159E INVALID SERVER MODIFY COMMAND - `cmd`

Explanation:This message is issued in response to a SERVER MODIFY command with invalid parameters.

Processing continues. The command is ignored.

Corrective Action:Specify the MODIFY command with valid parameters.

CTO15AE INVALID SNAP KEYWORD = `keyName`

Explanation:The operator specified an invalid SNAP keyword in an F CONTROLO,SNAP/F CTMCMEM,SNAP command.

The CTOMTO program ignores this keyword. If there was only one keyword, no SNAP request is performed.

Corrective Action:Specify an F CONTROLO,SNAP/F CTMCMEM,SNAP command with valid keywords. For more information, see the SNAP command in the INCONTROL for z/OS Administrator Guide.

CTO15AI INTERNAL CONTROL-O DUMMY MESSAGE

Explanation:This information message is an internal message generated by Control-O.

An internal Control-O process is triggered.

Corrective Action:No action is required.

CTO15BE INVALID LOG KEYWORD = `keyName`

Explanation:The CTOMTO program detected an invalid keyword for the LOG request. Valid keywords are:

ALL
DEFAULT
TRIGGER

The CTOMTO program ignores this LOG command request.

Corrective Action:Resubmit the F CONTROLO,LOG/F CTMCMEM,LOG command with a valid keyword.

CTO15CI RULE LOGGING MODE WAS SET TO `modeType`

Explanation:This information message indicates that Control-O or CMEM have successfully executed the F CONTROLO,LOG command.

Rules will be traced according to the new log mode.

Corrective Action:No action is required.

CTO15DI WATERMARK INFORMATION: FREE= `freeNum`PND= `waitNum` EVC= `execNum` WSC= `wscNum`

Explanation:This Control-O or CMEM message displays statistics in response to a WATERMARKS command.

The variables in this message are:

freeNum- the lowest number of RQC blocks that have been free simultaneously since the monitor was startedRQC blocks are used when information is being transferred from various address spaces to the address space of the monitor. A total of 20,000 RQC blocks are available.
waitNum- the highest number of PND blocks that have been in use simultaneously since the monitor was startedPND blocks store information about rules that are in Wait mode, meaning rules that are in execution and waiting to be redispatched. The allocation of PND blocks is controlled by the WAITPR# parameter.
execNum- the number of events (meaning messages, commands, and so on) that have been handled by the monitor since it was startedThis number is reset to zero each time it reaches 1,000,000.
wscNum- the number of WSC blocks that are allocated for use by the monitor WSC blocks store temporary information while handling events. The allocation of WSC blocks is controlled by the WSC# parameter.

The WATERMARKS command is currently supported for compatibility reasons only. More detailed statistical information about the usage of internal resources is available by means of the USAGESTATS command. For more information, see the INCONTROL for z/OS Administrator Guide.

Corrective Action:No action is required.

CTO15DW LOAD OF EXIT `exitName` FAILED, USER CHECKING IS NOT PERFORMED

Explanation:Loading of the exitNameControl-O user exit by Control-O failed. Possible causes are:

The installation is not using the exitNameuser exit, and erased the default exit supplied with Control-O.
IOA Load library is not in the load modules search list of the job (STEPLIB and Linklist).
There is insufficient storage to load the exit.
Another system oriented reason which can be found in the MVS system log.

As a result, no user checking is performed for the rule order.

Corrective Action:Contact your INCONTROL administrator. This is a potential security risk. Someone may be attempting to violate security.

CTO15EI `typeUSAGE`: CURRENTLY `currp%,` HIGHEST `highp%`( `curr` AND `high` OUT OF `total`)

Explanation:This message displays usage statistics relating to internal Control-O or CMEM resources in response to a USAGESTATS command.

The variables in this message are:

type- the type of resource to which the displayed usage statistics relateValid values are:
- PND - PND blocks, also known as "wait elements" PND blocks hold information about rules that are in Wait mode, meaning rules that are in execution and waiting to be redispatched. The allocation of PND blocks is controlled by the WAITPR# parameter.
- RQC - RQC blocks, also known as "request elements"RQC blocks transfer information from various address spaces to the address space of the monitor. A total of 20,000 RQC blocks are available.
- WSC - WSC blocks, also known as "work buffers" WSC blocks hold temporary information while handling events. The allocation of WSC blocks is controlled by the WSC# parameter.
currp- the percentage of the allocated type resources that are currently in use
highp- the highest percentage of type resources that have been in use simultaneously since the monitor was started
curr- the amount of type resources currently in use
high- the highest amount of type resources that have been in use simultaneously since the monitor was started
total- the total amount of type resources currently allocated

Corrective Action:In normal circumstances, highp should remain below 50%. If you notice higher usage percentages, contact your INCONTROL administrator. Possible causes are:

There are rules in the system that consume excessive amounts of internal resources.
Some parameters require adjustment to accommodate the workload of the system.

CTO15FE INVALID USAGESTATS KEYWORD =`arg`

Explanation:A USAGESTATS command was issued, to display usage statistics relating to internal Control-O or CMEM resources. However, the command contained an invalid argument.

In this message, arg is the invalid argument of the USAGESTATS command.

Valid arguments of the USAGESTATS command are:
- PND - requests statistics relating to PND blocks, also known as "wait elements" PND blocks hold information about rules that are in Wait mode, meaning rules that are in execution and waiting to be redispatched. The allocation of PND blocks is controlled by the WAITPR# parameter.
- RQC - requests statistics relating to RQC blocks, also known as "request elements"RQC blocks transfer information from various address spaces to the address space of the monitor. A total of 20,000 RQC blocks are available.
- WSC - requests statistics relating to WSC blocks, also known as "work buffers" WSC blocks hold temporary information while handling events. The allocation of WSC blocks is controlled by the WSC# parameter.
- ALL - requests statistics relating to all resource types supported by the USAGESTAT commandThe response to the command when this option is used is a series of CTO15EI messages.
Alternatively, the USAGESTATS command can be issued with no argument, which is equivalent to issuing the command with the argument ALL.

For more information on the USAGESTATS command, see the INCONTROL for z/OS Administrator Guide.

Corrective Action:Reissue the command in a valid format.

CTO15LE SERVER `server` IS NOT DEFINED

Explanation:A modify command F CONTROLO,SERVER= server,command has been issued for a server which has not been defined.

The command is ignored.

Corrective Action:Specify the correct server name.

CTO160I {CONTROL-O | CTMCMEM} SELECTOR STARTED

Explanation:This information message indicates the start of the Control-O Selector task, which controls the runtime selection criteria for rules.

Corrective Action:No action is required.

CTO161I {CONTROL-O | CTMCMEM} SELECTOR ENDED

Explanation:This information message indicates normal termination of the Control-O Selector task that controls the runtime selection criteria for rules.

Corrective Action:No action is required.

CTO162I INTERNAL CONTROL-O EVENT TRIGGERED

Explanation:This internal message triggers an ON EVENT rule after the criteria for triggering the rule have been satisfied. The text may include unprintable characters.

Corrective Action:No action is required.

CTO163I `cmdName` COMMAND COMPLETED

Explanation:This information message indicates the successful completion of a Control-O ORDER, FORCE, DELETE, READGLOBAL, or WRITEGLOBAL command.

Corrective Action:No action is required.

CTO163S OPEN FAILED FOR DDNAME "DARESF" OR "DASINC"

Explanation:Open of IOA Conditions or Resources file failed (the DARESF or DASINC DD statement).

Possible causes are:

The DARESF DD statement is missing.
The DASINC DD statement is missing.
The data set described by the DARESF DD statement is not the IOA Conditions or Resources file.
The data set described by the DASINC DD statement is not the Control-O Conditions or Resources Synchronization file.
The data set described by the DARESF DD statement is the Control-O Conditions or Resources file, but it is of a different version or of a different Control-O monitor.
The volume of this data set cannot be accessed by the Control-O monitor.
The data set is not on the volume specified in the Control-O procedure.

Control-O monitor shuts down with error message.

Corrective Action:Correct the JCL for the Control-O procedure, and restart the monitor.

CTO164S INTERNAL ERROR PROCESSING RESOURCE FILE FOR CONDITION `cond`

Explanation:An internal error occurred while the cond condition was being processed.

The Control-O monitor is terminated.

Corrective Action:Contact BMC Customer Support.

CTO166W COND `name date`NOT UPDATED BY CONTROL-O - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

There is no more space for adding output conditions to the IOA Conditions file.

The record for the specified day of the month is full. For example, if a condition with date reference of January 3rd cannot be added, an entry in the conditions file which contains conditions for January 3rd, February 3rd, March 3rd, and so on, is full.

The format for the date specified in this message is mmdd.

The condition is not added. A highlighted message is displayed on the operator console. Control-O or CMEM continues to function, but the rules that depend on the condition may not be triggered.

Corrective Action:Perform the following immediate actions and then perform the long term actions described below.

Immediate actions:

Enter the IOA Conditions list (Screen 4).
Look for conditions with the same day (but with a different month) as the condition that could not be added. Delete them manually if they are not needed.
Add the failing condition manually in order to maintain production flow.
Report the event to your System Programmer.

Long term actions:

Run the IOACLCND utility more often.

Increase the record length of the IOA Conditions file. For more information on how to do this, see the description of expanding IOA files in the INCONTROL for z/OS Administrator Guide.

CTO168I COND `name date`ALREADY `action`

Explanation:This information message indicates that the user requested an action that has already been performed.

The user either tried to add a condition that already exists or tried to delete a condition that had already been deleted.

Corrective Action:No action is required.

NOT ADDED BY CONTROL-O - GLOBAL DATE ADDITION IS NOT SUPPORTED

Explanation:A DO COND statement in a rule requested the addition of the specified condition with date **** or $$$$. This date specification is valid only when conditions are being deleted.

The DO COND request is not performed.

Corrective Action:Correct the DO COND statement.

CTO171S STATISTICS FILE OVERFLOW

Explanation:All Statistics file index entries are in use. No new statistics can be accumulated.

The Statistics Facility could not accumulate statistics because the number of message ID’s exceeds the maximum number of allowable entries in the Statistics file.

Statistics accumulation stops.

Corrective Action:Please review the following recommendations; then format the Statistics file and restart the Statistics Facility:

Enlarge the Statistics file by using the following procedure:
1. Increase the value of the STREC# parameter in CTOPARM.
2. Delete or rename the old Statistics file to allow a new Statistics file allocation.
3. Allocate and format a new Statistics file.
Use AutoEdit option %%STATID to customize message ID determination. This option can be used to decrease the number of message IDs that are generated. See the INCONTROL for z/OS Administrator Guide for more information.

CTO172S STATISTICS FILE IS NOT FREE

Explanation:The Statistics file is locked.

Either the Statistics file is in use by another Control-O monitor or utility, or Control-O abended previously while updating the Statistics file.

Statistics accumulation is not performed.

Corrective Action:Check if another Control-O monitor or utility uses this Statistics file. If this is not the case, then reformat the Statistics file and restart the Statistics Facility.

CTO173S OPEN OF STATISTICS FILE FAILED

Explanation:The Control-O Statistics facility attempted to open the Statistics file but did not succeed.

Failure to open the Statistics file may be due to the following:

The data set allocated to DD statement DASTF was not formatted as a Control-O Statistics file.
The data set allocated to DD statement DASTF was formatted as a Control-O Statistics file by a different version of Control-O.
The data set allocated to DD statement DASTF belongs to a different installation of Control-O.

Statistics accumulation is not performed.

Corrective Action:Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.

CTO174S FILE ALLOCATED TO DDNAME "DASTF" IS NOT A CONTROL-O STATISTICS FILE

Explanation:The Control-O Statistics Facility attempted to read the file allocated to DD name DASTF, but it is not a formatted Statistics file.

Statistics accumulation is not performed.

Corrective Action:Format the Statistics file and restart the Statistics Facility.

CTO175E RELEASE OF THE STATISTICS FILE IS NOT SUPPORTED BY THIS RELEASE

Explanation:The format of the Statistics file is not supported by the current release of Control-O. The Statistics file could not be read by the Control-O Statistics Facility.

The Statistics file was formatted by an earlier release of Control-O.

Statistics accumulation is not performed.

Corrective Action:Format the Statistics file in the currently supported format, and restart the Statistics Facility.

CTO176E THE STATISTICS FILE BELONGS TO A DIFFERENT CONTROL-O MONITOR

Explanation:The assigned ID of the Statistics file does not match the ID of the Control-O monitor.

When a Statistics file is formatted, it is associated with a particular Control-O monitor. The CTOMFST Statistics Formatting utility takes the ID of the Control-O monitor from the QNAME parameter of CTOPARM, and assigns it to the Statistics file.

The ID of the active Control-O monitor does not match the assigned ID of the Statistics file. The likely cause of the error is that the value of QNAME was changed without reformatting the Statistics file.

Statistics accumulation is not performed.

Corrective Action:Format the Statistics file with the correct Control-O ID and restart the Statistics Facility.

CTO177S CONTROL-O STATISTICS SEVERE INTERNAL ERROR, ID= `code`

Explanation:The Control-O Statistics Facility encountered an internal error.

In this message, code is the internal error code.

Statistics accumulation stops.

Corrective Action:Look for previous messages to identify the cause of the problem and contact BMC Customer Support.

CTO178S STORAGE ALLOCATION FOR STATISTICS FAILED

Explanation:Storage allocation for the Control-O Statistics Facility failed because the Statistics Facility could not obtain enough working storage for processing.

Statistics accumulation is not performed.

Corrective Action:Increase the Control-O region size and restart a new Control-O monitor.

CTO179S I/O ERROR ACCESSING THE STATISTICS FILE

Explanation:A READ/WRITE error occurred when accessing the Statistics file.

Statistics accumulation stops.

Corrective Action:Look for previous MVS error messages regarding Statistics file I/O errors, and correct accordingly. If MVS messages do not clarify the error, please contact BMC Customer Support.

CTO180S CONTROL-O STATISTICS FILE INTERNAL ERROR. RECORD TYPE MISMATCH

Explanation:The Statistics Facility has encountered a corruption in the Statistics file. The Statistics file cannot be processed.

Statistics accumulation stops.

Corrective Action:Contact BMC Customer Support.

CTO181S CONTROL-O STATISTICS INTERNAL ERROR. WRITE FAILED FOR SECTION `section`

Explanation:Due to an internal error, update of the Statistics file failed while writing a section of the Statistics file.

Statistics accumulation stops.

Corrective Action:Contact BMC Customer Support.

CTO182S CLOSE OF CONTROL-O STATISTICS FILE FAILED

Explanation:During termination, the Control-O Statistics Facility failed to close the Statistics file.

The Statistics Facility continues terminating without closing the Statistics file.

Corrective Action:Check the system log for previous error messages. If none are found, please contact BMC Customer Support.

CTO184I CONTROL-O STATISTICS ACCUMULATION STARTED

Explanation:This informative message indicates that the Control-O Statistics Facility initialization completed successfully and that Control-O statistics are being accumulated.

Corrective Action:No action is required.

CTO185S CONTROL-O STATISTICS INITIALIZATION ERROR

Explanation:Control-O Statistics Facility did not initialize successfully.

Statistics accumulation is not performed.

Corrective Action:Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

CTO186E STATISTICS ACCUMULATION ERROR WHILE PROCESSING SUBSYSTEM REQUESTS

Explanation:The Statistics Facility detected an error while processing requests from the Control-O subsystem.

Statistics accumulation stops.

Corrective Action:Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

CTO187E STATISTICS ACCUMULATION ERROR DURING FILE UPDATE

Explanation:The Statistics Facility detected an error while updating the Statistics file.

Statistics accumulation stops.

Corrective Action:Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

CTO189I CONTROL-O STATISTICS ACCUMULATION ENDED

Explanation:This informative messages is issued after normal termination of the Statistics Facility. Statistics accumulation is discontinued.

Corrective Action:No action is required.

CTO190S CONTROL-O STATISTICS TERMINATION ERROR

Explanation:Control-O Statistics Facility did not terminate successfully.

The Statistics Facility continues the termination process.

Corrective Action:Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

CTO191S STATISTICS ACCUMULATION ERROR WHILE PROCESSING USER REQUESTS

Explanation:The Statistics Facility detected an error while processing a SHOW, EXCLUDE or RESET online user request.

Statistics accumulation stops.

Corrective Action:Look for previous error messages in the IOA Log to determine the cause of the error, and correct accordingly.

CTO192E STATISTICS REQUEST FOR MESSAGE ID `msgId`FAILED - MESSAGE ID NOT FOUND

Explanation:A SHOW, EXCLUDE or RESET request for message ID msgId failed.

An online user requested a SHOW/EXCLUDE/RESET for message ID msgId. This message ID was not found in the Statistics file.

The online request is not performed. The Statistics Facility continues processing.

Corrective Action:Notify BMC Customer Support of the problem.

CTO193E STATISTICS REQUEST FOR MESSAGE ID `msgId` FAILED - INVALID REQUEST

Explanation:Due to an internal error, the user’s online request regarding message ID msgId was not recognized.

The request is not performed. The Statistics Facility continues processing.

Corrective Action:Notify BMC Customer Support.

CTO194W WAITING FOR THE STATISTICS FILE. FILE IN USE

Explanation:Control-O is attempting to access the Statistics file, but it is in use by another Control-O monitor or Control-O utility.

Control-O waits and attempts to access the Statistics file again.

Corrective Action:This message is not necessarily the result of an error. It may be issued while generating a statistics report or when the Online Facility attempts to access the Statistics file. If the Statistics file is not freed in a reasonable period of time, check what job is using it and free it.

CTO195E RESET OF STATISTICS FOR MESSAGE ID `msgId` FAILED

Explanation:An online user requested a RESET of the statistics for message ID msgId, but due to internal error, the request could not be performed by Control-O.

The RESET request is not performed. The Statistics Facility continues processing.

Corrective Action:Notify BMC Customer Support.

CTO196S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`

Explanation:Dynamic allocation of Statistics file dsn failed with return code rc and reason code rsn.

Statistics accumulation is not performed.

Corrective Action:See the IBM manual MVS Programming: Authorized Assembler Services Guide to determine this cause of the error, and correct the error accordingly. If not successful, contact BMC Customer Support.

CTO197I CONTROL-O STATISTICS GLOBAL RESET COMPLETE

Explanation:This information message indicates that the global statistics reset command F CONTROLO, RESETSTAT was issued and performed successfully.

Corrective Action:No action is required.

CTO198E RESET OF DATE FOR MESSAGE ID `msgId` FAILED

Explanation:Statistics for message ID msgId were reset as requested, but due to an internal error, update of the last reset date was not successful.

Statistics are reset. The Statistics Facility continues processing, but the indicated last reset date is incorrect.

Corrective Action:Notify BMC Customer Support.

CTO1A0E INVALID PARAMETERS, OR NULL COMMAND

Explanation:No command or mask was specified as selection criteria for display in the Option COMMAND window.

The selection window remains displayed.

Corrective Action:Specify a mask or operator command to be displayed.

CTO1A1E INTERNAL ERROR: ONLY ACTIONS "GETLINES" OR "END" ARE SUPPORTED

Explanation:The CTOTMCS Automation Options program was invoked with an invalid action. This message indicates an internal error.

The option is not performed.

Corrective Action:Contact BMC Customer Support.

CTO1A3E INVALID TIME INTERVAL PARAMETER

Explanation:The PARM menu definition statement for this option specifies an invalid time interval. The PARM statement for a menu option can specify the time interval between the issuing of the command and the collection of response messages.

The option is not performed.

Corrective Action:Correct the menu definition, and choose the menu option again.

CTO1A6E CONSOLE ERROR. R15 = `rc`, REASON- CODE = `rsn`

Explanation:The MVS Extended MCS Console facilities used by Option COMMAND detected an error. The return code rc and reason code rsn are returned by the MCSOPER MVS macro.

The option is not performed.

Corrective Action:For an explanation of rc and rsn, see the appropriate IBM manuals.

CTO1A8E CONSOLE `name` IN USE. TRY AGAIN LATER

Explanation:The MVS Extended MCS Console specified in the message is being used by another user. The console name is the same as the user name used by the IOA Online Facility. Either the same user name is being used by different users, or a previous console session was not closed correctly.

The option is not performed.

Corrective Action:Use operator command DISPLAY CONSOLES to determine who is using the console. If under TSO, log off from TSO and log on again to free any previous session.

CTO1ABE COMMAND INVOCATION DENIED BY SECURITY EXIT

Explanation:The user requested an operator command that cannot be issued by the Control-O Automation Options Facility because security exit IOASE07 detected a security violation.

The command is not issued.

Corrective Action:Contact your security administrator.

CTO1ACE VM COMMAND NOT ISSUED; MVS NOT RUNNING UNDER VM

Explanation:A VM command was requested by means of the Automation Options facility. Such a command can be issued only when MVS runs under VM.

The command is not issued.

Corrective Action:No action is required.

CTO1ADW VM COMMAND OUTPUT TRUNCATED

Explanation:The response of the IOA VM command interface exceeded the 4096 bytes that the buffer can hold. The remainder of the response is truncated.

Corrective Action:Change the command so it can be held in the available buffer of 4096 bytes.

CTO1B2E INTERNAL ERROR: ONLY ACTIONS "GETLINES" OR "END" ARE SUPPORTED

Explanation:Option CONSOLE was invoked with an invalid action. This message indicates an internal error.

The option is not performed.

Corrective Action:Contact BMC Customer Support.

CTO1B3E MCS CONSOLE IS INACTIVE OR NOT FOUND

Explanation:The console name or console ID specified for option CONSOLE could not be found.

The option is not performed.

Corrective Action:Do the following:

Verify the console name and ID. You can use the MVS operator command DISPLAY CONSOLES to do this.
Specify the option with a valid console name or ID.

Messages CTO200 through CTO2xx

This group includes messages for the Control-O product.

CTO200I {CONTROL-O | CTMCMEM} EXECUTOR STARTED

Explanation: This information message is the normal start message of the Control-O or CMEM Executor task that handles tasks that cannot be executed by the Control-O or CMEM subsystem. Certain of these actions require communication with other IOA products.

Corrective Action: No action is required.

CTO201I {CONTROL-O | CTMCMEM} EXECUTOR ENDED

Explanation: This information message is the normal termination message of the CONTROLO or CMEM Executor task that handles tasks that cannot be executed by the CONTROLO or CMEM subsystem. Certain of these actions require communication with other IOA products.

Corrective Action: No action is required.

CTO202S ERROR ALLOCATING THE SUBSYSTEM-TO-MONITOR COMMUNICATION DATASET

Explanation: The CONTROLO or CMEM monitor failed to allocate the subsystem-to-monitor communication file. The communication file links the CONTROLO or CMEM and Control-M monitors.

Possible causes are:

The communication file is not cataloged on the correct disk.
The communication file is cataloged in a catalog that cannot be accessed from the local CPU.
The MVS allocation exit failed the allocation request.
A security product failed the allocation request.
The data set was not specified correctly in the Control-M CPU installation parameter in the IOACPRM member.
The data set was never allocated. That is, the Control-M Console Subsystem was not installed in the current computer.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the potential reasons for the error listed above. Correct as necessary, and restart the Control-O or CMEM monitor.

CTO203S THE SUBSYSTEM-TO-MONITOR COMMUNICATION DATASET COULD NOT BE OPENED

Explanation: The Control-O monitor failed to open a subsystem-to-monitor communication file. The communication file links the Control-O or CMEM and Control-M monitors. Possible causes are:

A communication file was incorrectly defined.
The MVS DADSM exit failed the open request.
A security product failed the open request.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the communication files that are in use, and make sure that they were properly defined, formatted, and cataloged. In addition, make sure that no restrictions are imposed, for example by MVS or a security package, and the like.

CTO204S I/O ERROR WHILE READING THE MONITOR-TO-SUBSYSTEM COMMUNICATION DATASET

Explanation: The Control-O monitor could not read a monitor-to-subsystem communication file due to an I/O error. The communication file links the Control-O or CMEM and Control-M monitors. The Control-O monitor-to-subsystem communication file may not have been formatted correctly during Control-M Installation Procedure, or may have been incorrectly modified.

The Control-O or CMEM monitor shuts down.

Corrective Action: For formatting information, see the section that describes how to install the Control-M Event Manager Subsystem (CMEM) in the Control-M chapter of the INCONTROL for z/OS Installation Guide. Reformat or restore as necessary, and restart the Control-O or CMEM monitor.

CTO205S ERROR ALLOCATING THE MONITOR-TO-SUBSYSTEM COMMUNICATION DATASE

Explanation: The Control-O monitor failed to allocate the monitor-to-system communication file. The communication file links the Control-O or CMEM and Control-M monitors.

Possible causes are:

The communication file is not cataloged on the correct disk.
The communication file is cataloged in a catalog that cannot be accessed from the local CPU.
The MVS allocation exit failed the allocation request.
A security product failed the allocation request.
The data set was not specified correctly in the Control-M CTM2SBS installation parameter in IOACPRM.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the potential reasons for the error listed above. Correct as necessary, and restart the Control-O or CMEM monitor.

CTO206S THE MONITOR-TO-SUBSYSTEM COMMUNICATION DATASET COULD NOT BE OPENED

Explanation: The Control-O or CMEM monitor failed to open a monitor-to-subsystem communication file. The communication file links the Control-O or CMEM and Control-M monitors. Possible causes are:

A communication file was incorrectly defined.
The MVS DADSM exit failed the open request.
A security product failed the open request.

The Control-O or CMEM monitor shuts down.

Corrective Action: Check the communication files that are in use, and make sure that they were properly defined, formatted and cataloged. In addition, make sure that no restrictions are imposed by MVS, a security package, and so on.

CTO207S I/O ERROR WHILE READING THE SUBSYSTEM-TO-MONITOR COMMUNICATION DATASET

Explanation: The Control-O or CMEM monitor could not read a subsystem-to-monitor communication file due to an I/O error. The communication file links the Control-O or CMEM and Control-M monitors. The Control-O or CMEM subsystem-to-monitor communication file may not been formatted correctly during Control-M Installation procedure, or may have been incorrectly modified.

The Control-O or CMEM monitor shuts down.

CTO208S INVALID FORMAT OF THE SUBSYSTEM-TO-MONITOR COMMUNICATION DATASET

Explanation: The Control-O or CMEM subsystem-to-monitor communication file has not been formatted correctly during the Control-M Installation Procedure or may have been incorrectly modified.

The Control-O or CMEM monitor shuts down.

CTO209S OPEN OF THE CONTROL-O TRACE FILE FAILED. DDNAME DAACTLOG

Explanation: The Control-O monitor failed to open the trace file used when Control-O is operating in LOG and TEST modes.

The Control-O monitor shuts down.

Corrective Action: Make sure that DD name DAACTLOG is allocated to the Control-O monitor, or if no trace is required, to DUMMY.

CTO20BE SYSTEM LOGGER REQUEST `req` FAILED: R15= `r15` RETURN= `rc` REASON= `rsn`

Explanation: One of the following System Logger requests failed:

DEFCFS, IXGINVNT - Define coupling facility structure.
DEFLGS, IXGINVNT - Define log stream.
CONLGS, IXGCONN - Connect to log stream.
WRITEL, IXGWRITE - Write a log stream log block.
BRWSEL, IXGBRWSE - Browse a log stream log block.
DELETL, IXGDELET - Delete a log stream log block.
DISLGS, IXGCONN - Disconnect from log stream.
DELLGS, IXGINVNT - Delete log stream.
DELCFS, IXGINVNT - Delete coupling facility structure.

CMEM issues r15. Possible values of r15 are:

08 - Minor System Logger request error.
12 - Intermediate System Logger request error.
16 - Major System Logger request error.
20 - Permanent System Logger request error.
24 - Internal CMEM error
28 - Operating system does not support System Logger interface.
32 - Internal CMEM error.

To determine the system action, check the descriptions of return and reason codes in the IBM manual MVS Programming: Assembler Services Reference, where they are described for each System Logger request separately.

Corrective Action: If you cannot correct the problem, call BMC Customer Support.

CTO20CW IOACPRM NOT DEFINED. CMEM FUNCTION IS NOT SUPPORTED

Explanation: During Control-O or CMEM start up, the IOACPRM member was not found in the IOA PARM library, and therefore could not be loaded.

Initiation of CMEM fails CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: Have the INCONTROL administrator check if the situation is valid. If not, create the IOACPRM member in the IOA PARM library and restart the Control-O or CMEM monitor.

CTO20DW NO CPU ENTRY FOR THIS SYSTEM WAS DEFINED. CMEM FUNCTION IS NOT SUPPORTED

Explanation: During Control-O or CMEM start up, the IOACPRM member in the IOA PARM library does not contain the definition for the system where the Control-O or CMEM monitor is active.

Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: Have the INCONTROL administrator check if the situation is valid. If not, add the definitions for the current system to IOACPRM, and restart the Control-O or CMEM monitor.

CTO20EW S2M FILE WAS NOT DEFINED IN CPU ENTRY. CMEM FUNCTION NOT SUPPORTED

Explanation: During Control-O or CMEM start up, Control-O or CMEM could not allocate the Subsystem-to-Monitor file S2M, because the name of the file is missing from the definition of the current system in the IOACPRM.

Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: Call the INCONTROL administrator to check if the situation is valid. If not, add the name of the Subsystem-to-Monitor file S2M and the definitions for the current system to the IOACPRM in the IOA PARM library, and restart the Control-O or CMEM monitor.

CTO20FE NO CMMPLEX MEMBER. CMEM FUNCTION NOT SUPPORTED

Explanation: During Control-O or CMEM start up, the CMEM Logger facility was required, but the CMMPLEX member that should contain the definition of the logger was not found.

Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.

Corrective Action: No action is required.

CTO210E INVALID DATE `date` IN A DO COND STATEMENT

Explanation: An invalid date reference format was used in a DO COND statement.

Valid date reference formats are:

ODAT - Control-O or CMEM working date (default)
DATE - Current Gregorian computer date
PREV - Previously scheduled activation date for rule
NEXT - Next scheduled activation date for rule
mmdd - Month and day of the scheduling date
ddmm - Day and month of the scheduling date
%% xx - An AutoEdit symbol.

Corrective Action: Correct the date format, and reorder the rule table.

CTO211I INTERNAL TIMEOUT DETECTED BY CONTROL-O

Explanation: This information message indicates that a rule remained in Command-Response mode or Wait mode for longer than specified in the TIMEOUT subparameter.

The rule continues executing.

Corrective Action: No action is required.

CTO212W CONTROL-O WAITING FOR SUBSYSTEM CONSOLE

Explanation: A Command-Response rule could not obtain a subsystem console because all valid subsystem consoles were in use by other Command-Response rules.

Command execution is delayed until the next Control-O interval, when a new attempt to obtain a subsystem console will be made.

Corrective Action: Check the Status screen for Command-Response rules which are executing. Verify that the number of Command-Response rules with a status of EXECUTING matches the number of subsystem consoles.

If this message is issued frequently, there may be an insufficient number of subsystem consoles to handle the Command-Response rules. In this case, increase the number of subsystem consoles in CTOPARM, and define new subsystem consoles to MVS accordingly. For details about subsystem console definition, see the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTO213E NO VALID SUBSYSTEM CONSOLE EXISTS

Explanation: A Command-Response rule could not obtain a subsystem console because no valid subsystem consoles were allocated by Control-O. The cause of the problem is probably in the subsystem console definition.

The command is not executed.

Corrective Action: Make sure that the NUMCONS parameter in CTOPARM is greater than zero, and that the correct number of subsystem consoles is defined in MVS. For details about subsystem console definition, see the Control-O chapter of the INCONTROL for z/OS Installation Guide.

If the console subsystem definition does not seem to be the cause of the problem, check for previous console allocation error messages, and contact BMC Customer Support.

CTO214E MAXIMUM NUMBER OF DO TSO/KSL/SHELL REQUESTS WAS EXCEEDED. TSO/KSL/SHELL PROCESSING IS ABORTED

Explanation: In the process of executing DO TSO, DO KSL, or DO SHELL requests, all of the TSP (TSO PARM) blocks in CSA or ECSA were used. Possible causes are:

A JCL error in the TSO or KSL procedure.
Started tasks in the system are not being processed due to system corrective measures, such as auxiliary storage shortage.

Further TSO, KSL, or SHELL requests are temporarily suspended until at least one TSP is available.

Corrective Action: If started tasks are not processed due to system corrective measures, wait until they run and their corresponding TSP blocks are freed.

If a started task failed due to a JCL error, perform the following recovery action:

Correct the JCL error.
Manually reissue the START command that Control-O previously issued, that is, S O2TTSOCM,PARM= parm, where parm is in the console log or the Control-O JES log.

This action frees one TSP, and message CTO215I is issued when the next TSO or KSL request is processed. TSPs also become available when Control-O is brought down after a standard shutdown or an IPL.

CTO215I TSO/KSL/SHELL PROCESSING IS RESUMED

Explanation: This information message indicates that normal TSO, KSL, or SHELL processing resumed. TSO, KSL, or SHELL processing was suspended as a result of a shortage of TSP blocks. For more details see message CTO214E.

Corrective Action: No action is required.

CTO216W REQUEST PROCESSING BYPASSED DUE TO CONTROL-O STANDALONE MODE

Explanation: A DO RESOURCE or DO FORCEJOB request was made when Control-M was not installed. These statements are not supported if Control-M is not installed.

The rule is not ordered.

Corrective Action: Correct the rule or install Control-M.

CTO217E COND `name date` NOT `action` BY {CONTROL-O | CTMCMEM} - SECURITY VIOLATION

Explanation: Control-O issued a DO COND request, but the prerequisite condition was not added or deleted. There is no authorization by the security exit to add or delete this condition in the IOA Conditions file.

The DO COND request is ignored and the rule continues execution.

Corrective Action: Contact your INCONTROL administrator.

CTO218E COMMAND `cmdName` NOT ISSUED BY {CONTROL-O | CTMCMEM} - SECURITY VIOLATION

Explanation: There is no authorization for the requested DO COMMAND statement. Security exit IOASE012 detected a violation. This exit is invoked for each command issued by a rule in which value OWNER or TRIGGER was specified for the RUNTSEC parameter.

The DO COMMAND statement is ignored and the rule continues execution.

Corrective Action: Contact your INCONTROL administrator.

CTO219E RUNTIME SECURITY CACHE INITIALIZATION ERROR - `rsn`

Explanation: This message indicates an internal error.

Control-O or CMEM continues to perform security checks without a security cache.

Corrective Action: Contact BMC Customer Support.

CTO21AE M2S FILE IS OF ANOTHER INSTALLATION QNAME `qname1`. IOA QNAME `qName2` DSN `dsn`

Explanation: The Control-O or the CMEM monitor could not allocate the monitor to the Monitor-to-Subsystem (M2S) file of another IOA environment. During initialization the Control-O or the CMEM monitor compares the QNAME in the IOA environment with the QNAME in the M2S file. They should match.

CMEM stops. Control-O issues the CTO21FS and CTO21SE messages.

Corrective Action: Respond to the CTO21SE message. Then check the CTMPARM member and do one of the following:

If it points to the wrong file, correct the name and start a new monitor.
If there is no problem in the CTMPARM member, the M2S file was created in a different IOA environment. Delete the file and create a new M2S file using the correct IOA environment (IOAPARM).

CTO21BE S2M FILE IS FOR SMFID `smfid` QNAME `qName1`. IT DOES NOT MATCH IOA QNAME `qName2` DSN `dsn`

Explanation: The Control-O or the CMEM monitor could not allocate the subsystem to the Subsystem-to-Monitor (S2M) file of another IOA environment. During initialization the Control-O or the CMEM monitor compares the qName1 in the IOA environment with the qName2 in the S2M file. They should match.

CMEM stops. Control-O issues the CTO21FS and CTO21SE messages.

Corrective Action: Respond to the CTO21SE message. Then check the IOACPRM member and do one of the following:

If it points to the wrong file, correct the name, compile the member and start a new monitor.
If there is no problem in the IOACPRM member, the S2M file was created in a different IOA environment. Delete the file and create a new S2M file using the correct IOA environment.

CTO21CI M2S FILE FOR IOA QNAME `qName`. DSN= `dsn`

Explanation: This information message identifies the Monitor-to-Subsystem (M2S) file that the Control-O or the CMEM monitor allocated for communication with the Control-M monitor.

qName is defined in the M2S file with the DSN dsn.

Corrective Action: No action is required.

CTO21DI S2M FILE FOR SMFID `smfid` QNAME `qName` DSN= `dsn`

Explanation: This information message identifies the Subsystem-to-Monitor (S2M) file that the Control-O or the CMEM monitor allocated for communication with the Control-M monitor. QNAME is defined in the S2M file with the DSN dsn.

Corrective Action: No action is required.

CTO21EE REPLY ABORT, CONTINUE OR TERMINATE

Explanation: The error described in message CTO21ES prevents communication between the Control-O monitor and Control-M. The response to this message determines the next action.

The subtask is suspended until a response to this message is received.

Corrective Action: Select one the following responses:

ABORT - Abend the Control-O monitor.
CONTINUE - Disable communication with Control-M.
TERMINATE - End Control-O monitoring with a return code of 8.

CTO21EI THE REPLY TO MESSAGE EX021EE WAS: `reply`

Explanation: The information message echoes the response to message CTO21EE.

Corrective Action: No action is required.

CTO21ES SUBSYSTEM TO CONTROL-M MONITOR FUNCTION DISABLED

Explanation: An error occurred during initialization of Subsystem-to-Monitor (S2M) communication for the Control-O monitor. Initialization checks failed for the function that communicates with the Control-M monitor. For details, see previously issued error messages in the JOBLOG or IOA Log file.

Control-O issues the CTO21EE message.

Corrective Action: Respond to the CTO21EE message.

CTO21FE SUPPORT FOR 'DO FORCEJOB' AND 'DO RESOURCE' IS DISABLED

Explanation: Either Control-O disabled communication with Control-M because of a CONTINUE response to message CTO21EE, or a DO FORCEJOB or DO RESOURCE statement was encountered during execution of a Control-O rule with communication disabled.

DO FORCEJOB, DO RESOURCE and NEWCONLIST requests from Control-M are ignored.

Corrective Action: No action is required.

CTO21IE S2M FILE IS 80% FULL. WHEN FULL, REQUESTS TO CONTROL-M WILL BE LOST

Explanation: When Control-M processes events (received through the Subsystem-to-Monitor communication dataset) slower than CMEM or Control-O adds them, file space shortage may occur, and this could eventually lead to lost events.

The message is issued when the Subsystem-to-Monitor (S2M) communication dataset reaches 80% utilization.

Corrective Action: Perform the following actions:

Eliminate the cause of the delay in event processing by Control-M.
Consider increasing the size of the Subsystem-to-Monitor communication dataset, as described in Reformatting communication files for only one SMFID in the INCONTROL for z/OS Installation Guide.

CTO21JI S2M FILE RECORDS SHORTAGE HAS BEEN RELIEVED

Explanation: The Subsystem-to-Monitor (S2M) communication dataset space shortage that was reported by message CTO21IE has been relieved.

Dataset utilization returned to a level below 60%.

Corrective Action: No action is required.

CTO220I CONTROL-O ALLOCATED `num` SUBSYSTEM CONSOLES

Explanation: This information message indicates that during Control-O startup, 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 number 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.

CTO221I CONTROL-O RELEASED THE SUBSYSTEM CONSOLES

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.

CTO222W NO CONSOLES ARE AVAILABLE FOR CONTROL-O

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 details, see the Control-O installation chapter in the INCONTROL for z/OS Installation Guide, and to the relevant MVS manuals.

CTO223W INSUFFICIENT NUMBER OF CONSOLES ARE AVAILABLE FOR CONTROL-O

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 message CON220I 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 details, see the Control-O installation chapter in the INCONTROL for z/OS Installation Guide, and the relevant MVS manuals.

CTO224E ERROR IN SUBSYSTEM CONSOLE SERVICE ROUTINE. FUNCTION= `func` RC= `rc`. A SNAP IS PRODUCED

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.

Snap dumps are produced with the relevant control blocks.

Corrective Action: Save the snap dumps and call your INCONTROL administrator for assistance.

CTO225E INSUFFICIENT STORAGE FOR THE CONSOLE `func` FUNCTION

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.

CTO226E INSUFFICIENT STORAGE IN (EXTENDED) CSA. CANNOT ALLOCATE SUBSYSTEM CONSOLES

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.

CTO227E ERROR IN SUBSYSTEM CONSOLE PROCESSING. REQUEST= `reqCode` FUNCTION= `func` ERRCODE={ `abCode|rsn` }

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.

CTO228I CONTROL-O ALLOCATED `num` EMCS CONSOLES

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.

CTO229I CONTROL-O ALLOCATED `num` EMCS CONSOLES WITH MIG IDS

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.

CTO22AE CONTROL-O ALLOCATED EMCS CONSOLE ERROR. IOAMCS RC= `rc` REASON= `rsn` CONSOLE= `consoleName`

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 (consoleName). 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.

CTO22BE CONTROL-O ALLOCATED EMCS CONSOLE ERROR. CONVCON RC= `rc` REASON= `rnum` CONSOLE= `consoleName`

Explanation: Control-O failed to allocate an EMCS CONSOLE. 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

CTO230E SUBSYSTEM `subsys` INITIALIZATION FAILED - JES COMMAND SUPPRESSION NOT ACTIVATED

Explanation: During Control-O initialization, Control-O failed to activate the Control-O subsystem that suppresses JES2 commands. To suppress JES2 commands, Control-O uses the subsystem whose name is specified in the statement JCMDSSN= subsys in the CTOPARM member in the IOA PARM library.

Control-O initialization continues, but the JES2 command suppression function is disabled.

Corrective Action: Notify the INCONTROL administrator.

CTO231E SUBSYSTEM `subsys` WAS NOT PRE-DEFINED - JES COMMAND SUPPRESSION NOT ACTIVATED

Explanation: During Control-O initialization, Control-O failed to activate the Control-O subsystem that suppresses JES2 commands, because the subsystem was not properly predefined. To suppress JES2 commands, Control-O uses the subsystem whose name is specified in the statement JCMDSSN= subsys in the CTOPARM member in the IOA PARM library. This subsystem should be, but was not, defined in SYS1.PARMLIB(IEFSSN xx), and activated in the last IPL before Control-O is started.

Control-O initialization continues, but the JES2 command suppression function is disabled.

Corrective Action: Notify the INCONTROL administrator.

CTO234W SUBSYSTEM `subsys` ALREADY INACTIVE

Explanation: During Control-O termination, Control-O tried to deactivate the IOA subsystem and the Control-O subsystem currently in use, but the subsystem identified in the message was already inactive.

Control-O termination continues.

Corrective Action: Notify the INCONTROL administrator.

CTO235W `subsys` ALREADY ACTIVE

Explanation: During Control-O initialization, Control-O tried to activate the IOA subsystem and the Control-O subsystem, but the subsystem identified in the message was already active.

Control-O initialization continues.

Corrective Action: Notify the INCONTROL administrator.

CTO236E SUBSYSTEM NAME IS NOT SPECIFIED IN IOAPARM

Explanation: The subsystem initialization routine found a blank subsystem name definition in the IOAPARM member.

Corrective Action: Correct the SSNAME parameter in the IOAPARM member to specify a valid subsystem name, and check that the other subsystem-related parameters were defined correctly.

If Control-D subsystem functions are requested, check the AMNAME parameter in CTDPARM and correct if necessary.

CTO237E ERROR WHILE ATTEMPTING TO LOCATE (BLDL) ONE OF THE SUBSYSTEM FUNCTION ROUTINES

Explanation: Control-O could not find at least one of the alternate subsystem function routines.

While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries and reactivate Control-O.

CTO238E ERROR WHILE ATTEMPTING TO LOAD ONE OF THE SUBSYSTEM FUNCTION ROUTINES

Explanation: Control-O could not load at least one of the alternate subsystem function routines.

While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries and reactivate Control-O.

CTO239E ERROR WHILE ATTEMPTING TO ACQUIRE STORAGE FOR SUBSYSTEM FUNCTION ROUTINES OR THE SSVT

Explanation: Control-O could not acquire enough CSA (Common Service Area) storage to load alternate subsystem function routines or to build the SSVT for the alternate subsystem.

Control-O continues without activating the alternate subsystem.

Corrective Action: If storage defined for CSA is not large enough, increase the CSA size and perform an IPL.

CTO23AI ALTERNATE SUBSYSTEM `subsys` SUCCESSFULLY INITIALIZED

Explanation: This information message indicates that the CTOSSO module successfully activated the alternate subsystem.

Corrective Action: No action is required.

CTO240I NEWCONLIST COMMAND RECEIVED. THE CMEM TABLE WAS RELOADED SUCCESSFULLY

Explanation: This information message indicates that the Control-M or Control-O subsystem functions received the NEWCONLIST request from the Control-M monitor, and accordingly reloaded (refreshed) the CMEM table.

The Control-M or Control-O subsystem functions reloaded the CMEM table.

Corrective Action: No action is required.

CTO240W STATISTICS FILE NEARLY FULL - `percentage` USED

Explanation:Highlighted, unrollable message.

The Statistics file is approaching its maximum capacity.

The Statistics file continues accumulating statistics until it becomes full.

Corrective Action: The user can do one of the following:

Reformat the Statistics file using the DEFSTAT installation job. This deletes all saved statistics and restarts the tracking process.
Enlarge the Statistics file using the CTOCSF utility. This retains the existing statistics and increases the space available for the tracking of new message IDs.
Do nothing. If the Statistics file becomes full, statistics of message IDs which exist in the file will continue to be tracked, but new message IDs will not be added to the file.

CTO241E STATISTICS FILE IS FULL. NEW MESSAGE IDS WILL BE LOST

Explanation:Highlighted, unrollable message.

The Statistics file is full.

All statistics records according to the number (STREC#) set in the CTOPARM parameter file have been utilized.

Control-O continues to collect statistics for existing messages, but the statistics for new message IDs are not saved.

Corrective Action: The user can do one of the following:

Reformat the Statistics file using the DEFSTAT installation job. This deletes all saved statistics and restarts the tracking process.
Enlarge the Statistics file using the CTOCSF utility. This retains the existing statistics and enables new message IDs to be tracked.
Do nothing. Statistics of message IDs which exist in the file will continue to be tracked. Statistics of new message IDs will not be tracked.

CTO250E RUNTIME SECURITY CLEANUP FAILED, RC= `rc`

Explanation: An error occurred during interface with the locally used security product.

Control-O or CMEM continues working.

Corrective Action: Contact BMC Customer Support.

CTO251I RUNTIME SECURITY REFRESH ENDED OK

Explanation: This information message indicates a normal response to operator command F CONTROLO,NEWSECDEF or F CTMCMEM,NEWSECDEF. The runtime security cache containing previously handled security definitions was successfully refreshed.

If security definitions were changed, the new definitions are used.

Corrective Action: No action is required.

CTO252I SNMP REQUEST HOST=`hostname` PORT=`portNumber` SEVERITY=`s` TEXT=`msgText`

Explanation: This information message is an audit message that logs a DO SNMP request executed by Control-O.

Corrective Action: No action is required.

CTO253E SNMP REQUEST ERROR, RETURN CODE=`rc`, REASON CODE=`rsn`

Explanation: Control-O tried to send an SNMP request using a DO SNMP statement, but the request contained an error.

Possible return and associated reason codes are described in the following table:

Return Code ( rc )	Reason Code ( rsn )	Explanation
04
	00	Successful completion, minor errors discovered.
	04	SHL value exceeds 70, truncated.
08
	04	Failed to get local IP address.
	08	Failure to get storage for an SNMP trap.
	12	Allocation storage has failed.
	16	Hostname could not be resolved.
	20	SNMP trap sending failed.
	24	Socket call failed.
	28	Internal error; buildTrapMessage() failed.
	32	See message SNMT10S for details.
	36	See message SNMT11S for details.
	40	See message SNMT12S for details.
	44	See message SNMT13S for details.
	48	See message SNMT14S for details.
	52	See message SNMT15S for details.
	56	See message SNMT16S for details.
	60	See message SNMT17S for details.
	64	See message SNMT18S for details.
	68	See message SNMT19S for details.
	72	See message SNMT20S for details.
	76	See message SNMT21S for details.
	80	See message SNMT22S for details.
	84	See message SNMT23S for details.
	96	ISTACK parameter is specified in the IOAPARM member and the system has TCP/IP dual stack mode, but the specified stack is not running.
	100	Invalid IPv6 destination. The destination contains the colon (:) character, but the address is not a syntactically valid IPv6 address.
	104	SNMP destination contains the colon (:) character, but IPv6 is not enabled in the z/OS system.
12
	04	Missing SNMP message address.
	08	Invalid or missing SNMP message length.
	12	Neither Destination Table nor HOST and PORT provided.
	20	Bad or missing HOST parameter when no Destination Table.
	24	Bad or missing PORT parameter when no Destination Table.
	28	Invalid Destination Table.
	32	Specified Destination Table unavailable.
	36	Specified Translation Table unavailable.
	40	An invalid IP address was provided in HOST.
20		Internal error.
24
	04	Invalid or missing MCT address.
	08	Invalid or missing SNMV vector.
	12	Failure to load IOAMEM.
	24	Insufficient storage to read Destination Table.
	28	Destination Table is empty.
	32	Destination Table unavailable.
	36	Insufficient storage to build Destination Table.
	40	IOASNMC failed SNMV not initialized.
	44	Call can be issued after MODE=INIT only.
	48	Failure to refresh Destination Table.

The DO SNMP request is not sent, and fails.

Corrective Action: Notify the INCONTROL administrator.

CTO254E {CONTROL-O | CTMCMEM} SECURITY ENVIRONMENT CLEANUP FAILED BY USER EXIT RC= `rc` REASON= `rsn`

Explanation: The IOASECUR security module was unable to delete the security environment. This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO255W CONTROL-O SERVER ERROR. SERVER `id reason`

Explanation: A server action cannot be performed because the server is not in the expected status. An action was attempted on a server that is either stuck or has disappeared.

Server status is set to IN ERROR.

Corrective Action: Do the following:

Check the sysout of the server in error for the cause of the error.
Correct the detected errors, for example, errors in the JCL.
Restart the server.

CTO25FW MONITOR USE SYSPRINT SYSOUT INSTEAD OF ACTLOG SYSOUT

Explanation: Control-O monitor or CMEM monitor tries to write a message to ACTLOG sysout. The DD card ACTLOG is missing from the Control-O or CMEM procedure.

The monitor writes the message to the SYSPRINT sysout. In the monitor address space this may cause ABEND S02A with a return code of 0C in some cases. Since the Monitor can recover itself from the abend, the monitor is not immediately terminated.

Corrective Action: Add the following DD statement to the Control-O procedure (CTOTROLO) and the CMEM procedure (CTMCMEM):

//ACTLOG DD &OUTLIST,SYSOUT=&OUT

CTO25HE REQUEST TO OBTAIN LOAD-INDEX LIST FAILED. RC=`rc` REASON=`rsn`

Explanation: Control-O or CMEM issued a CTMAPI request for a list of MVA-type Load-Indexes, but the request failed. The message provides the return code and reason code from CTMAPI. The message is always followed by message CTO25JS.

As a result of the failed request, setting of levels for MVA-type Load-Indexes was disabled.

Corrective Action: Check the reasons for the error. Correct as necessary, and restart the Control-O or CMEM monitor.

CTO25IE FAILED TO BUILD LOAD-INDEX LIST DUE TO MEMORY SHORTAGE

Explanation: Control-O or CMEM faced a private memory shortage when attempting to obtain buffers for a CTMAPI request for a list of MVA-type Load-Indexes. The message is always followed by message CTO25JS.

As a result of this issue, setting of levels for MVA-type Load-Indexes was disabled.

Corrective Action: Contact BMC Customer Support.

CTO25JS UPDATING LOAD-INDEXES BASED ON MAINVIEW ALARMS STOPPED

Explanation: Control-O or CMEM failed to build a list of MVA-type Load-Indexes, due to the reason described in message CTO25HE or message CTO25IE. This message always follows one of those messages.

Corrective Action: See message CTO25HE or message CTO25IE.

CTO25KI UPDATING OF LOAD-INDEXES BASED ON MAINVIEW ALARMS STARTED

Explanation: Control-O or CMEM successfully built a list of MVA-type Load-Indexes, and is ready to set Load-Index levels based on MainView Alarms.

Corrective Action: No action is required.

CTO25LI UPDATING OF LOAD-INDEXES BASED ON MAINVIEW ALRAMS {STOPPED | NOT STARTED}, NO LOAD-INDEXES FOUND

Explanation: Control-O or CMEM issued a CTMAPI request for a list of MVA-type Load-Indexes, but no defined MVA-type Load-Indexes were found.

As a result of this issue, setting of levels for MVA-type Load-Indexes was disabled.

Corrective Action: If no MVA-type Load-Indexes exist, consider setting OPTMVLID=N in CTMPARM, to disable setting levels for MVA-type Load-Indexes based on MainView Alarms.

CTO260E EXECUTION OF VM/CP COMMAND ABORTED. RC= `rc`

Explanation: A DO COMMAND statement specifying a VM CP command failed. The return code indicates the cause of the error, as follows:

Return Code	Explanation
4	MVS not running under VM.
8	Insufficient space (GETMAIN failed).
12	IOAVMC not APF authorized.
16	FREEMAIN error.

The specified command is ignored.

Corrective Action: The recommended action depends on the return code, as follows:

4 - Correct the rule containing this DO COMMAND statement.
8 - Increase the region size of the Control-O monitor.
12 or 16 - Contact BMC Customer Support for assistance.

CTO261I ATTEMPTING TO RECONNECT TO MVS SYSTEM LOGGER DUE TO ERROR `rsn`

Explanation: Control-O or CMEM has detected an MVS System Logger error, and is attempting to reconnect to the MVS System Logger.

In this message, rsn is a reason code that is documented in the IBM manual MVS Programming: Assembler Services Reference. Check that publication for the system action relevant to the reason code in the message. Each System Logger request is in a separate section of the guide. The reason codes are described in the topic “Return and Reason Codes” for the IXGWRITE System Logger request.

Control-O or CMEM tries several times to reconnect to the MVS System Logger.

Corrective Action: No action is required.

CTO262E ATTEMPT TO RECONNECT TO MVS SYSTEM LOGGER FAILED

Explanation: Control-O or CMEM detected an MVS System Logger error, and attempted several times to reconnect to the MVS System Logger, without success.

Corrective Action: No action is required.

CTO263E MVS SYSTEM LOGGER ERROR - CMEM FEATURE DISABLED

Explanation: Control-O or CMEM detected an MVS System Logger error. Either this error was so severe as not to be recoverable, or Control-O or CMEM attempted several times to reconnect to the MVS System Logger, without success.

Control-O or CMEM has stopped attempting to reconnect to the MVS System Logger. The CMEM facility is deactivated.

Corrective Action: If and when the MVS System Logger becomes operational, stop and restart the Control-O or CMEM monitor.

CTO26AI `text`

Explanation: Ignore this message. It is an internal message used by Control-O to pass information to Control-M/Links for Distributed Systems executing in a WINDOWS NT machine using MVS console emulation, when Control-O processes a DO CTOPCMSG statement. The message text contains the event that should trigger the rule on Control-M/Links for Distributed Systems.

Corrective Action: No action is required.

CTO26BI `text`

Explanation: Ignore this message. It is an internal message used by Control-M/Links for Distributed Systems in a WINDOWS NT machine to satisfy the ON CTOPCMSG event that triggers the rule. Control-M/Links for Distributed Systems passes the information in this message to Control-O using its MVS console emulation.

Corrective Action: No action is required.

CTO271I `text`

Explanation: Ignore this message. It is an internal message used by the CTOJFRQ Control-O IEFJFRQ exit module to trigger a SYSOUT event. The text may include unprintable characters.

Corrective Action: No action is required.

CTO272I CTOJFRQ EXIT POINT SUCCESSFULLY REMOVED

Explanation: This information message indicates that as part of its termination process, the Control-O monitor successfully disabled and removed dynamic exit IEFJFRQ, which uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.

Corrective Action: No action is required.

CTO273W CTOJFRQ EXIT POINT NOT REMOVED RC = `rc` REASON CODE = `rsn`

Explanation: Upon termination, the Control-O monitor failed to disable and remove dynamic the exit IEFJFRQ that uses the CTOJFRQ module. This exit should have been disabled and removed upon monitor termination. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.

Control-O terminates without removing the dynamic exit IEFJFRQ that uses the CTOJFRQ module. This may cause an S0C4 code in various jobs under the subsystem interface. In this case, MVS automatically disables the dynamic exit IEFJFRQ that uses the CTOJFRQ module.

Corrective Action: Inform the system programmer, and check the return code and reason code of macro CSVDYNEX in the IBM manual MVS Programming: Authorized Assembler Services Reference.

CTO274E ERROR WHILE LOADING CTOJFRQ EXIT POINT

Explanation: When Control-O monitor started, it failed to load and enable the IEFJFRQ dynamic exit, which uses the CTOJFRQ module. This exit should have been loaded at monitor startup. Control-O uses the CTOJFRQ module for ON SYSOUT and JES2 command suppression function.

Control-O starts without enabling the IEFJFRQ dynamic exit that uses the CTOJFRQ module. As a result, ON SYSOUT and JES2 command suppression functions will not be active.

Corrective Action: Inform your system programmer.

CTO275E CTOJFRQ EXIT POINT NOT INSTALLED RC = `rc` REASON CODE= `rsn`

Explanation: When the Control-O monitor started, it failed to load and activate the dynamic exit IEFJFRQ that uses the CTOJFRQ module. This exit should have been loaded and activated at monitor startup. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.

Control-O starts without enabling the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Therefore, ON SYSOUT and/or JES2 command suppression functions will not be active.

Corrective Action: Inform your system programmer and check the RC and REASON CODE of the CSVDYNEX macro in the IBM OS/390 Authorized Macros and Services Guide.

CTO276I CTOJFRQ EXIT POINT SUCCESSFULLY INSTALLED

Explanation: This information message indicates that when the Control-O monitor started, it successfully enabled the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.

Corrective Action: No action is required.

CTO281I `usr msg`

Explanation: This information message displays the message issued from a Control-O rule.

(Note: CTO281I cannot be trapped with an ON MESSAGE rule and therefore it cannot trigger any rule.)

Corrective Action: No action is required.

CTO282I `text` (`userId`)

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT facility.

In this message, userId is the user ID of the job order requesting the SHOUT.

Corrective Action: No action is required.

CTO284I `text`

Explanation: Ignore this message. It is an internal message used by the CMEM executor module to trigger a CMEM event using ON DSNEVENT and ON STEP. The text may include unprintable characters.

Corrective Action: No action is required.

CTO285E OID= `orderId` JOB TERMINATED BY CONTROL-O DUE TO ‘STOPJOB’ REQUEST

Explanation: Control-O stopped job execution due to a DO STOPJOB statement. This message is issued for all DO STOPJOB statements for events, except data set events for an NCT2 disposition.

The steps following the current step are not executed.

Corrective Action: No action is required.

CTO285W RULE `ruleName` SUSPENDED AT THRESHOLD `num`. TABLE `table` LIB `library`

Explanation: The rule identified in the message was suspended because it reached the rule threshold limit, which determines the maximum number of times a rule may be triggered. The rule threshold limit is defined in the THRSHOLD parameter in the CONTROL section of the CTOPARM member in the IOA PARM library.

The rule is suspended.

Corrective Action: Check why the rule reached the limit, and if there is a problem correct it. Adjust the threshold value, if needed, or use the Rule Status screen to release the rule from its SUSPEND state.

CTO286E ALL REQUEST ELEMENTS IN USE. REQUEST ABORTED

Explanation: Control-O could not obtain a free element. Control-O has an internal queuing request mechanism that obtains a request from a free chain, and puts it on one of various work chains. Once processing is complete, the request is returned to the free chain. This message is issued when trying to obtain a free request element, and there are none available.

The request is aborted.

Corrective Action: Inform BMC Customer Support.

CTO287W RULE `ruleName` SUSPENDED AT THRESHOLD `num`. TABLE `table` LIB `library`

Control-O scans suspended rules every few minutes, according to the message interval set by the RLSPMSGI parameter in the CTOPARM member in the IOA.PARM library. This message is issued every time Control-O determines that the rule is still suspended. This message can be trapped by a Control-O rule.

CTO288E MAXIMUM NUMBER OF ‘DO’ STATEMENTS EXCEEDED.

Explanation: A rule executed more than 10,000 DO statements. This message is followed by another message containing the name of the problematic rule.

In order to avoid an infinite loop, only a limited number of DO statements can be executed. The default setting is 10,000. You can override this default by setting %%DOLIMIT to a higher value.

The rule is aborted.

Corrective Action: Either correct the rule to perform less than 10,000 DO statements, or set %%DOLIMIT to a higher value.

CTO289E GLOBAL DATE IS NOT SUPPORTED FOR ADD CONDITION REQUESTS

Explanation: The dateref field in the DO COND statement contains wildcard symbols ($$$$ or ****).

The rule is aborted or ignored.

Corrective Action: Specify a distinct date in the dateref field.

CTO28AE MAXIMUM NUMBER OF NESTED RULES EXCEEDED

Explanation: The maximum number of nested rules executed in response to a DO RULE statement has been exceeded. Rules can be nested up to 20 deep.

The rule at the twenty first level is aborted or ignored

Corrective Action: Correct the logic so that there are no more than 20 nesting levels for rules.

CTO28BE INVOKED RULE NOT FOUND

Explanation: The rule invoked by means of a DO RULE statement was not found in the specified, or default, table.

The rule is aborted or ignored

Corrective Action: Correct the DO RULE statement to contain a rule defined in the specified or default table, or define the rule in the specified table.

CTO28CW RULE IS IN "WAIT ACTIVATION" STATUS. "DO RULE" IS IGNORED

Explanation: A rule invoked another rule by using the DO RULE statement did not satisfy the Runtime Scheduling criteria.

Processing continues. The invoked rule is ignored.

Corrective Action: If this is not intentional, correct the invoked rule definition so that it satisfies the Runtime Scheduling criteria.

CTO28DE RULE= `ruleName` ABORTED. TABLE= `tableName` LIBRARY= `dsn`

Explanation: A rule aborted because of an error. This message is preceded by another message that describes the cause of the error.

The rule is aborted at the point of error.

Corrective Action: Correct the error according to the preceding message.

CTO28EW RULE= `ruleName` IGNORED. TABLE= `tableName` LIBRARY= `dsn`

Explanation: This warning message indicates that a problem occurred when processing a rule. This message is preceded by another message that describes the problem.

The rule is ignored. Processing continues.

Corrective Action: Correct the problem according to the preceding message.

CTO290I {CONTROL-O | CTMCMEM} AUTOMATION LOG STARTED

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

Corrective Action: No action is required.

CTO291E AUTOMATION LOG ERROR WHILE PROCESSING REQUESTS

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.

CTO292S {CONTROL-O | CTMCMEM} AUTOMATION LOG TERMINATION ERROR

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

Corrective Action: Contact your INCONTROL administrator.

CTO293I CONTROL-O AUTOMATION LOG ENDED

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.

CTO294E OPEN OF AUTOMATION LOG FAILED. LOG SWAPPED

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 IOA PARM library.
Check to see if the Automation Log file exists for this CPU.

CTO295S OPEN OF DAACTLOG FAILED

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 DAACTLOG DD statement exists. If the problem is not resolved, contact your INCONTROL administrator.

CTO296E ERROR DETECTED DURING ADDF. LOG SWAPPED

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.

CTO297I AUTOMATION LOG STATUS CHANGE COMPLETED

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.

CTO298E ERROR DETECTED DURING ENQ. LOG SWAPPED

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.

CTO299E ERROR DETECTED DURING DEQ. LOG SWAPPED

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 will be written to the DAACTLOG sysout of the Control-O monitor.

Corrective Action: Contact your INCONTROL administrator.

CTO2A6S SEVERE WSC SHORTAGE DETECTED FOR MONITOR `mon` (`subsys`) - WSC USAGE: CURRENTLY 100%

Explanation:Highlighted, unrollable message.

The Control-O or CMEM monitor detected a severe shortage of WSC blocks. All WSC blocks were in use simultaneously. This is a severe condition, and must be avoided, because the operation of Control-O may be affected in unexpected ways.

Possible causes are:

There are rules in the system that consume excessive quantities of WSC blocks.
The WSC# parameter requires adjustment to accommodate the workload of the system.
This can be done dynamically by using the MODIFY SETPARM command.

The availability of WSC blocks is essential for the monitor to be able to process system events.

This message is issued only the first time there is no free WSC. After the CTO2A7I message indicates that the shortage has been relieved, the CTO2A6S message is deleted and can be issued again.

This message is highlighted, and will be deleted when message CTO2A7I is issued.

The variables in this message are:

mon - the name of the Control-O or CMEM monitor
subsys - the IOA subsystem associated with mon

For more information, see the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.

As long as all WSC blocks remain in use, the Control-O or CMEM monitor cannot react to events. However, the Control-O or CMEM monitor continues to function and is not terminated.

Corrective Action: Contact your INCONTROL administrator.

CTO2A7I WSC SHORTAGE RELIEVED FOR MONITOR `mon` (`subsys`)

Explanation:Highlighted, unrollable message.

A severe shortage of WSC blocks was previously detected by the Control-O or CMEM monitor, and the CTO2A6S message was displayed. As of the last check, at least 25% of the WSC blocks are free. The check is performed every minute, or longer if the Control-O/CMEM INTERVAL parameter is greater than 1 minute.

This message is highlighted, but if another WSC shortage occurs and is then relieved, the message relating to the preceding shortage is deleted.

The variables in this message are:

mon - the name of the Control-O or CMEM monitor
subsys - the IOA subsystem associated with mon

For more information, see the description of the preceding CTO2A6S message and the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.

Control-O or CMEM resumes normal operation. However, it is possible that information was lost during the period of the shortage, and the shortage may have unexpected effects.

Corrective Action: Contact your INCONTROL administrator.

CTO2A9W `nnnnnnnn` EVENT(S) LOST FOR MONITOR `mon` (`subsys`) DUE TO 100% WSC USAGE

Explanation:One or more system events occurred of a type which is usually tracked by the Control-O or CMEM monitor. However, because a severe shortage of WSC blocks existed at the time of the events (as indicated by the display of the CTOA6S message), the events are ignored by the Control-O or CMEM monitor.

The variables in this message are:

nnnnnnnn - the number of events lost during the last minute interval, or longer if the Control-O/CMEM INTERVAL parameter is greater than 1 minute.
mon - the name of the Control-O or CMEM monitor
subsys - the IOA subsystem associated with mon

For more information, see the description of the preceding CTO2A6S and CTO2A7I messages and the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.

The events are ignored, and future events might also be ignored until the shortage of WSC blocks is relieved.

Corrective Action: Contact your INCONTROL administrator.

CTO2AAW 85% `xxx` UTILIZATION DETECTED FOR MONITOR `mon` (`subsys`)

Explanation:Highlighted, unrollable message.

WSC, RQC, or PND might be soon exhausted, causing serious Control-O/CMEM functional impairment, as follows:

WSC - See message CTO2A6S for more details.
RQC - If exhausted, unexpected results might occur.
PND - Rules that use wait mode will not be triggered if there are no free PNDs available.

The variables in this message are:

xxx - WSC/RQC/PND
mon - the name of the Control-O or CMEM monitor
subsys - the IOA subsystem associated with mon

Corrective Action: Contact your INCONTROL administrator.

A Control-O rule may be written so that WSC allocation is increased automatically using the MODIFY SETPARM,WSC#= command. See the INCONTROL for z/OS Administrator Guide.

Also, the WSC#,RQC# and WAITPR# parameters can be increased in CTOPARM, and Control-O/CMEM recycled. See the INCONTROL for z/OS Installation Guide: Installing.

This message is not re-issued until a corresponding relief message (CTO2ABI) for the resource type (WSC/RQC/PND) is issued.

CTO2ABI `xxx` SHORTAGE RELIEVED FOR MONITOR `mon` (`subsys`)

Explanation:85% utilization of WSC/RQC/PND blocks was previously detected by the Control-O or CMEM monitor, and the CTO2AAW message was displayed. As of the last check, at least 25% of the WSC/RQC/PND blocks are free. The check is performed every minute, or longer if the Control-O/CMEM INTERVAL parameter is greater than 1 minute.

This message is highlighted, but if another WSC/RQC/PND 85% utilization condition occurs and is then relieved, the message relating to the preceding shortage is deleted.

The variables in this message are:

xxx - WSC/RQC/PND
mon - the name of the Control-O or CMEM monitor
subsys - the IOA subsystem associated with mon

For more information, see the description of the preceding CTO2AAW message and the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.

Corrective Action: Contact your INCONTROL administrator.

CTO2B5E XCF GETMAIN ERROR RC= `rc`

Explanation: Control-O failed to activate XCF support. Control-O detected this error while allocating internal storage by means of a STORAGE OBTAIN operation.

In this message, rc is the contents of register R15 from macro STORAGE OBTAIN.

The CTOXCF Control-O program ends with an error.

Corrective Action: Based on the return code, determine the cause of the error, and fix the problem. Restart Control-O to activate XCF support.

CTO2B6E XCF FREEMAIN ERROR RC= `rc`

Explanation: Control-O detected an error during a STORAGE RELEASE operation. STORAGE RELEASE operations are used to free internal storage.

In this message, rc is the contents of register R15 from the STORAGE RELEASE macro.

The CTOXCF program ends with an error. Control-O fails to start or terminate XCF support.

Corrective Action: Based on the return code, determine the cause of the error, and fix the problem. Restart Control-O.

CTO2B7E CONTROL-O HAS NOT INITIALIZED XCF SESSION

Explanation: Control-O attempted to initialize an XCF session. The attempt failed. When Control-O begins initializing an XCF session, it observes the session start. If the session starts with status XCF-LOCAL, this message is issued and Control-O does not connect to XCF.

Corrective Action: None, if Sysplex configuration is not needed. However, if Sysplex configuration is needed, configure the session as MONOPLEX or SYSPLEX. For more information, see MVS documentation on initialization and tuning.

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.

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:

For an explanation of return-code (rc) and the reason (rsn), see the IBM OS/390 Authorized Assembler Services Guide, and proceed accordingly.
Check the CTOPARM member.
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.

Messages CTO400 through CTO4xx

This group includes messages for the Control-O product.

CTO403I `text`

Explanation: This information message is an internal message used by the Control-O or CMEM USS (UNIX Services for OS/390) interface module to trigger a CMEM event using ON DSNEVENT and ON STEP in the USS address space. The message indicates that a forked process started. The text may include unprintable characters.

Corrective Action: No action is required.

CTO410I ALLOCATION OF GLOBAL AUTOEDIT LIBRARY STARTED

Explanation: This information message indicates the normal start of the CTODFG program that allocates the Global library.

Corrective Action: No action is required.

CTO411E INVALID PARAMETERS: `parms`

Explanation: The CTODFG program detected invalid parameters.

The program terminates with a return code of 08.

Corrective Action: Verify the parameters, correct them, and resubmit the utility.

CTO412E THIS CPU HAS SMFID `cpuSmfId` AND NOT `parmSmfId`

Explanation: The SMFID of the CPU on which the CTODFG program is running does not match the SMFID passed as a parameter to the program.

The variables in this message are:

cpuSmfId - the SMFID of the CPU on which the CTODFG program is running
parmSmfId - the SMFID passed as a parameter to the program

The program terminates with a condition code of 08.

Corrective Action: Verify the SMFID of the CPU on which Control-O is running, and resubmit the utility with the correct parameter.

CTO416E DYNAMIC ALLOCATION ERROR RC=`rc`,ERROR=`rsn`, DSN=`dsn`

Explanation: The CTODFG program failed while attempting to dynamically allocate the Global library.

The CTODFG program terminates with a condition code of 08.

Corrective Action: For an explanation of the return and reason codes, see the IBM OS/390 Authorized Assembler Services Guide.

CTO417E CTMMEM ERROR, RC= `rc`

Explanation: The CTODFG program received return code rc from the CTMMEM module while attempting to update the Global library. The error occurred when the CTODFG program attempted to create the $$GLOBAL member in the Global library.

Possible causes indicated by values of rc:

08 - The region size is too small.
28 - The data set is in use.
32 - Internal error.
56 - The library is full or an abend occurred.
64 - The member already exists.

The CTODFG program terminates with a condition code of 08.

Corrective Action: If possible, correct the problem with the library, and resubmit the utility. If the error persists, contact BMC Customer Support.

CTO418E ALLOCATION OF GLOBAL AUTOEDIT LIBRARY FAILED

Explanation: Allocation of the Global library failed. This error message, which is issued by the CTODFG program, is preceded by another message detailing the reason for the failure.

The CTODFG program terminates with a condition code of 08.

Corrective Action: See the preceding message.

CTO419I ALLOCATION OF GLOBAL AUTOEDIT ENDED

Explanation: This information message indicates that the CTODFG program successfully allocated the Global library.

Corrective Action: No action is required.

CTO421I CTOCPS STARTED

Explanation: This information message indicates that the CTOCPS program, which compresses or verifies the Global AutoEdit library, started.

Corrective Action: No action is required.

CTO422S COMPRESS REQUIRED FOR GLOBAL AUTOEDIT VARIABLES LIBRARY

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. Command WRITEGLOBAL 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 installation chapter in the INCONTROL for z/OS Installation Guide.

CTO423S DYNAMIC ALLOCATION ERROR DURING COMPRESS, ERROR= `rc/rsn/dsn`

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.

CTO424I FIRST COMPRESSION PHASE STARTED - LIBRARY UNLOAD

Explanation: This information message indicates that the backup phase of the CTOCPS program has begun.

Corrective Action: No action is required.

CTO425I SECOND COMPRESSION PHASE STARTED - COMPRESS IN PLACE

Explanation: This information message indicates that the compress in place phase of the CTOCPS program has begun.

Corrective Action: No action is required.

CTO426I CTOCPS ENDED

Explanation: This information message indicates that the CTOCPS program has successfully completed compressing the Global AutoEdit library.

Corrective Action: No action is required.

CTO427S IEBCOPY RETURNED A NON-ZERO COMPLETION CODE

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 resolved the problem, contact your INCONTROL administrator. Until this problem is resolved, use site compression procedures to compress the Global AutoEdit library.

CTO428S CTOCPS RECEIVED AN INVALID PARAMETER LIST

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.

CTO429S PREVIOUS COMPRESS FAILED. GLOBAL LIBRARY CANNOT BE RESTORED FROM BACKUP

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. The NEWGLOB Job is in the INSTWORK library.

For more information, see the section on automatic compression of the global AutoEdit library in the INCONTROL for z/OS Administrator Guide.

CTO430S ERROR READING AUTO-COMPRESS CONTROL-MEMBER $$COMPST

Explanation: The CTOCPS program was unable to read the $$COMPST control member. The $$COMPST 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. Commands READGLOBAL and WRITEGLOBAL 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.

CTO431S ERROR WRITING AUTO-COMPRESS CONTROL-MEMBER $$COMPST

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.

CTO432I RESTORE OF GLOBAL VARIABLES LIBRARY STARTED

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.

CTO433S ABEND `abCode` INTERCEPTED DURING COMPRESS

Explanation: Recovery routine ESTAE 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.

CTO434I COMPRESS OF GLOBAL VARIABLES LIBRARY STARTED

Explanation: This information message indicates that the CTOCPS program has begun compressing the Global AutoEdit library.

Corrective Action: No action is required.

CTO440I READ/WRITE GLOBAL VARIABLES STARTED

Explanation: This information message indicates that the CTOVPL program, which is responsible for loading and writing global variables, has begun read/write to the Control-O global pools.

Corrective Action: No action is required.

CTO441S INVALID PARAMETERS

Explanation: The CTOVPL program received an incorrect parameter list while executing a LOADGLOBAL or WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO442S ERROR OPENING DAGLBLST

Explanation: The CTOVPL program was unable to open the Global Pool List during execution of a LOADGLOBAL or WRITEGLOBAL command.

The Global Pool List is defined by the DAGLBLST DD name in the procedure of the Control-O monitor.

The LOADGLOBAL/WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the DD name and related data set specifications in the Control-O monitor procedure.

CTO443S POOL `poolid` - GETMAIN ERROR

Explanation: The user issued a LOADGLOBAL command with the specified Variable Global pool. However, the variables in this pool could not be loaded.

There is insufficient storage in ECSA for loading Global variables from the specified Global variable pool.

Command LOADGLOBAL is ignored.

Corrective Action: Increase the size of ECSA storage.

CTO444S POOL `poolid` - ERROR LOADING GLOBAL VARIABLES

Explanation: Control-O could not load variables from the specified Global variable pool.

This message is preceded by messages describing the cause of the error.

Command LOADGLOBAL is ignored.

Corrective Action: See the accompanying messages for details about the cause of the error and possible solutions.

CTO445S POOL `poolid` - ERROR WRITING GLOBAL VARIABLES

Explanation: Control-O could not write variables to the specified Global pool.

This message is preceded by messages describing the cause of the error.

Command WRITEGLOBAL is ignored.

Corrective Action: See the accompanying messages for details about the cause of the error and possible solutions.

CTO446S POOL `poolid` - NOT FOUND IN MEMORY

Explanation: The user specified a LOADGLOBAL/WRITEGLOBAL command, but Control-O could not locate the specified pool.

Control-O could not locate the specified pool while executing a LOADGLOBAL/WRITEGLOBAL command and could not locate the control block for the specified pool name. This usually happens when either the specified pool name is not defined in the Global Pool List member (DAGLBLST) or the specified member was never loaded.

The LOADGLOBAL/ WRITEGLOBAL command is ignored.

Corrective Action:

Define the pool in the DAGLBLST member.
Use the LOADGLOBAL command to load the pool.

CTO447S FREEMAIN INTERNAL ERROR

Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL or WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO448S ERROR FREEING AUTO-EDIT INTERNAL BLOCKS

Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL or WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO449S ERROR FREEING GLOBAL MEMBER INTERNAL BLOCKS

Explanation: Control-O could not free internal control blocks of a Global variable pool.

Control-O could not free internal control blocks while executing a LOADGLOBAL/WRITEGLOBAL command. This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO44AS ERROR RELEASING COUPLING FACILITY RESOURCES

Explanation: Old data was not successfully deleted from the Coupling facility.

When newly loaded variables became effective after a LOAGLOBAL operation for an XAE (SYSPLEX-wide AutoEdit) database, Control-O or CMEM failed to delete the old copy of the AutoEdit databases from the Coupling facility.

Old data from the Coupling facility structure is not deleted.

As a result, unnecessary data may accumulate in the space allocated for the Coupling facility structure until the space is exhausted.

Corrective Action: Shut down all Control-O or CMEM monitors as soon as possible and restart them, one at a time.

In addition, send the sysout files for your monitor to BMC Customer Support for analysis.

CTO44BE ERROR SWITCHING COUPLING FACILITY INFORMATION

Explanation: During an attempt to switch to the new version of XAE database variables that were being loaded, an error occurred.

XAE variables are loaded in three steps. They are loaded to ECSA, copied to the Coupling facility and then marked effective in the Coupling facility. This message indicates a failure during the third step.

During the implicit LOADGLOBAL operation at startup, Control-O initialization fails. During ongoing operations, only the LOADGLOBAL operation fails.

Corrective Action: Send all the Control-O sysout files and the contents of the DAGLBLST library member to BMC Customer Support for analysis.

CTO44CE `request` (X’ `code`’) FOR STRUCTURE `structureName` FAILED. REASON: `rsn`

Explanation: A request to the XAE structure failed. The message details the request name and code, and the reason for the failure.

Additional information is written to DATRACE.

Corrective Action: Check that all XAE structures are allocated and that Control-O or CMEM did not lose a connection to them. If a connection was lost, restart Control-O or CMEM. Otherwise, contact BMC Customer Support for assistance.

CTO450S POOL `poolid` IS NOT SPECIFIED IN DAGLBLST

Explanation: Control-O could not locate the poolid pool in the DAGLBLST Global Variable Pool List member.

This message is normally issued in response to a failure of a LOADGLOBAL/ WRITEGLOBAL command in the DAGLBLST Global Pool List member.

The LOADGLOBAL/WRITEGLOBAL command is ignored.

Corrective Action: Do the following:

Define the pool in the DAGLBLST Global Pool List member.
Use the LOADGLOBAL command to load the pool.

CTO451S INVALID CARD IN DAGLBLST

Explanation: The CTOVPL program detected an invalid statement in the Global Pool List.

The Global Pool List is defined in the DAGLBLST DD statement in the Control-O monitor procedure.

The LOADGLOBAL/ WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the Global Pool List member.

CTO452S POOL `poolid` IS PROTECTED. IT CANNOT BE UPDATED

Explanation: Control-O cannot execute a WRITEGLOBAL command for the poolid Global Variable pool.

The poolid pool name is defined in the DAGLBLST Global Variable Pool List member as protected or temporary.

The WRITEGLOBAL command is ignored.

Corrective Action: Check the definition of the pool in the DAGLBLST member and correct the definition if necessary.

CTO453S pooling ERROR HANDLING PNX BLOCKS

Explanation: This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

CTO454S POOL `poolid` - AUTOEDIT ERROR, RC= `rc`, REASON= `rsn`

Explanation: Control-O detected an invalid AutoEdit expression in the poolid Global Variable pool at startup or while executing the LOADGLOBAL command.

The poolid Global variable specified in the AutoEdit expression was not loaded. The error was caused for one of the following reasons:

A mistake was made when the POOL member was manually edited.
There was an internal error.

Depending on poolid type, the pool is stored in one of two locations: the Global Variables Library or a Control-O AutoEdit Variable database.

The AutoEdit statement is ignored. The LOADGLOBAL command continues with the next line in the DAGLBLST member.

Corrective Action:

For an explanation of the return code and reason code included in this message, see the following table.
Check the source of the AutoEdit expression.
Correct the error and reissue command LOADGLOBAL.
If the problem is due to an internal error, contact BMC Customer Support.

Return 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 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, and 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.
	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.

CTO455I POOL `poolid` HAS BEEN LOADED TYPE= `pool_type` ROWS= `loaded_variables` / `max_variables_allowed`

Explanation: This information message indicates that the Global Variable pool poolid was successfully loaded. If pool_type starts with DB, S1 or S2 the numbers in ROWS= are the loaded value and the maximum variables allowed. In other cases the values will be 0.

Corrective Action: No action is required.

CTO457W DATABASE `database` NOT FOUND IN DATABASES FILE

Explanation: During Control-O or CMEM initialization, Control-O or CMEM failed to load the Global AutoEdit Variable database because the database does not exist in the Global AutoEdit Variable Database file. The member pointed to by the DAGLBLST DD statement contains a list that specifies the Control-O Load Global AutoEdit Variable databases and the IOA Load Global AutoEdit Variable database. The required database that appears in the list does not exist in the Global AutoEdit Variable Database file.

Control-O or CMEM initialization continues.

Corrective Action: Notify the INCONTROL administrator

CTO458S POOL `poolid` - ERRORS WHILE READING POOL

Explanation: Control-O could not read the poolid Global variable pool during execution of command LOADGLOBAL.

The poolid pool is not loaded.

Corrective Action: Verify that the Global pool is in the Global AutoEdit library and that the library is not corrupted.

CTO459I READ/WRITE GLOBAL VARIABLES ENDED

Explanation: This information message indicates that the CTOVPL program successfully completed execution of command LOADGLOBAL/WRITEGLOBAL.

Corrective Action: No action is required.

CTO45AW WARNING! `poolName` CONVERTED FROM `Stype` TO `DBtype`

Explanation: There is a conflict between inconsistent IOAPLEX and DAGLBLST settings, as follows:

In IOAPLEX, the ENABXES parameter or ENABXAE parameter is set to N.
In DAGLBLST, the XAE database is specified as S1 type and S2 type, where type is the one of the following database types:
- TEMP
- PROT
- INPUT
- INOUT

Control-O loads the database as a standard, or non-XAE, database. Database loading continues.

Corrective Action: Check whether, and how, the reduced capability affects any applications that use the downgraded XAE pool.

CTO45BE -- MEMBER TYPE ERROR ---

Explanation: Control-O or CMEM monitor encounter an invalid POOL TYPE in control record in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45CE --- KEYWORD NOT RECOGNIZED ---

Explanation: Control-O or CMEM monitor encounter an invalid keyword in a record in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45DE --- ALL BLANKS - ERROR ---

Explanation: Control-O or CMEM monitor the control record in the DAGLOBAL list file is all blank.

Corrective Action: No action is required.

CTO45EE --- NO BLANKS - ERROR ---

Explanation: Control-O or CMEM monitor encounter an empty control record format in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45FE --- LESS THAN ZERO ---

Explanation: Control-O or CMEM monitor encounter an invalid control record value in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45GE --- INVALID CARD FORMAT ---

Explanation: Control-O or CMEM monitor encounter an invalid control record format in the DAGLOBAL list file.

Corrective Action: No action is required.

CTO45HE RECORD= `record`

Explanation: Control-O or CMEM monitor encounter an error in the DAGLOBAL list file the previous error messages.

The record has been rejected.

Corrective Action: Correct the record and LOADGLOBAL or WRITEGLOBAL as necessary.

CTO45IE MAXIMUM NUMBER OF ROWS `max-num-rows` EXCEEDED WHILE LOADING POOL `pool-name`. LOAD STOPPED.

Explanation: During LOADGLOBAL of AutoEdit POOL pool-name, excessive rows were encountered beyond the maximum number of defined rows max-num-rows in screen IV.

The loading stops.

Corrective Action: If the unloaded AutoEdit variable is required, increase the maximum number of rows for the pool using the screen IV and re-issue the LOADGLOBAL command.

CTO45JI XAE TYPE 2 POOL `pool-name` HAS NOT BEEN LOADED BECAUSE ANOTHER LPAR HAS ALREADY LOADED IT.

Explanation: During initial loading of AutoEdit POOLs, loading of the POOL pool-name, has been skipped because the POOL has already been loaded by Control-O/CMEM on another LPAR.

Corrective Action: No action is required.

CTO45KE DATABASE IOAVAR IS ALREADY LOADED AS DBINOUT ON ANOTHER LPAR

Explanation: IOAVAR is the database that Control-M uses to store pool AutoEdit variables (%%\M\..). It can be defined (in IOAGLBVL) as either DBINOUT or S2INOUT. DBINOUT should be used only when IOAVAR is loaded by CMEM or Control-O in a single LPAR. Defining the same IOAVAR as DBINOUT in multiple LPARs creates a serious integrity exposure.

This message indicates that IOAVAR has already been loaded on another LPAR as DBINOUT and loading it again in this LPAR is unsafe. It may result in each LPAR having a different image of the database (different variable names, different variable values) and in one LPAR overwriting the other LPAR’s database when issuing WRITEGLOBAL (automatically or manually).

Corrective Action: If IOAVAR (AutoEdit variables) is not in use, this message can be ignored and no action is necessary.

If IOAVAR is in use, enable IOAPLEX and define IOAVAR as XES AutoEdit facility (XAE) Type 2 (S2INOUT). Defining IOAVAR as S2INOUT uses the XES AutoEdit facility (XAE), which allows for resolution of variables on a Sysplex-wide level by utilizing Coupling Facility structures. For more information, see "Step 7.6 – IOAPLEX considerations (optional)" in the INCONTROL for z/OS Installation Guide: Installing, and "IOAVAR Database" and "using XAE Type Databases Instead of Standard Type Databases" in the INCONTROL for z/OS Administrator Guide.

Messages CTO500 through CTO5xx

This group includes messages for the Control-O product.

CTO500I INPUT LEN= `inplen` REC= `inputRecordMsg`

Explanation: This information message is generated when the CTOTEST Control-O utility is invoked.

Corrective Action: This message is sent to CTOTEST. It echoes the input record.

CTO501I `func` OF RULE TABLE(S) STARTED

Explanation: This information message indicates that the function func started on the rule tables.

Corrective Action: No action is required.

CTO501S OPEN FAILED FOR DDNAME CMDMSGFL

Explanation: The attempt to open input file CMDMSGFL failed.

Possible causes are:

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

CTOTEST execution terminates.

Corrective Action: Check if the CMDMSGFL DD statement is present in the JCL.

CTO502S INPUT PARAMETER ERROR

Explanation: The subsystem name input parameter is invalid or missing.

CTOTEST execution terminates.

Corrective Action: Check if PARM= subsystemName is present in the parameter string.

CTO503I RC `rc` LEN= `len` REC= `msgText`

Explanation: This information message is generated when the CTOTEST Control-O utility is invoked.

The variables in this message are:

rc - the return code
len - the new message length
msgText - the new message text

Corrective Action: No action is required.

CTO503S RULE ORDER LIST IS EMPTY. DDNAME="DARULLST"

Explanation: Open of rule list data set failed (the DARULLST/DACTMLST DD statement).

The message may be due to one of the following reasons:

The DARULLST/DACTMLST missing.
Data set described by the DARULLST/DACTMLST DD statement cannot be opened for sequential read or record length is not 80.

The Control-O/CMEM monitor shuts down or continues processing according to the status of the monitor.

Corrective Action: Correct the JCL and restart the Control-O/CMEM monitor.

CTO504S INVALID DATA IN RULE ORDER LIST CARDS

Explanation: Invalid data has been found in the rule order list. See INCONTROL for z/OS Administrator Guide for valid format information.

Corrective Action: Check the format of the rule list in the PARM library; correct and restart the Control-O/CMEM monitor.

CTO505S MEMBER `memName` NOT FOUND IN LIBRARY `lib`

Explanation: The memName member in the rule order was not found in library lib.

The member (rule table) may be specified incorrectly or may be missing from the library.

The rule table is not ordered.

Corrective Action: Check and correct the member specification; reorder the rule table.

CTO506S ORDER OF TABLE `tableName` RULE `ruleName` FAILED

Explanation: The order of rule ruleName from table tableName failed. Prior messages usually explain why the rule table could not be ordered.

The rule is not be ordered.

Corrective Action: Check earlier messages for reasons the rule order failed. Correct as necessary, and reorder the rule table.

CTO507I LOAD ENDED FOR TABLE `table` LIBRARY `lib`

Explanation: This information message indicates that after ordering or forcing a Control-O rule table, loading of rules from the table ended.

Corrective Action: No action is required.

CTO508I {ORDER | FORCE} OF RULE TABLE(S) ENDED

Explanation: This information message indicates that Order or Force of the Control-O rule table ended.

Corrective Action: No action is required.

CTO509I NUMBER OF TABLES `numtbl` PROCESSED. `numrul1` RULES LOADED AND `numrul2` RULES REJECTED

Explanation: This information message indicates the number of tables processed, and the number of rules that were loaded or deleted (not loaded) as a result of an ORDER or FORCE request. This information can be used for manual verification purposes.

Corrective Action: Check the results to ensure that the rule loading was performed correctly.

CTO50BE HOLD BY `jobId` ASID `asid` ON SYSTEM `systemId`

Explanation: An ORDER or FORCE command to the Control-O or CMEM monitor to load a table or tables of rules failed, because the library is held by the job jobId with the ASID asid on system systemId.

The command fails.

Corrective Action: Try to determine why the library is held. If possible, release it, and try again to ORDER or FORCE the table or tables.

CTO50CE LIBRARY WAS MIGRATED BY HSM DSNAME=

Explanation: An ORDER or FORCE command to the Control-O or CMEM monitor to load a table or tables of rules failed, because the library had been migrated by HSM.

The command fails.

Corrective Action: If possible, restore or recall the library, then try again to ORDER or FORCE the table or tables.

CTO50FI `text`

Explanation: This information message displays the control record from the DARULLST or DACTMLST DD statement.

Corrective Action: No action is required.

CTO516S ERROR IN RULE DATA - MANDATORY `stmt_type` CARD IS EITHER MISSING OR IN AN INCORRECT ORDER

Explanation: A stmt_type statement is either missing or in the wrong order in a rule definition member.

Someone may have tampered with the rule definition data; the data do not conform to a valid Control-O or CMEM format.

The rule is not ordered.

Corrective Action: Restore the table to its original state from a backup copy, and reorder the rule table.

CTO517S RULE DATA NOT AVAILABLE: MEMBER `memName` IS EMPTY

Explanation: A member designated in the rule list is empty. This error message is issued by the CTOLDT program, which loads tables when a new Control-O or CMEM monitor is activated.

The table is not ordered.

Corrective Action: Check that the specification of the member in the rule list is correct. If so, check why the member is empty. Correct, and reorder the rule table.

CTO518S INVALID SCHEDULING DATE - `date`

Explanation: An invalid scheduling date format was used in the rule list or in a order/force request.

Valid date formats are:

ddmmyy - Day, month, and year
mmddyy - Month, day, and year
* (Asterisk) - Current Control-O or CMEM working date.

The requested table order fails.

Corrective Action: Correct the date. Reorder the rule table.

CTO523S ERROR IN RULE DATA: INVALID IF-THEN-ELSE NESTING

Explanation: This message is issued during the ordering of the rule. The rule definition contains an invalid IF-ELSE-ENDIF nesting.

The rule is not ordered.

Corrective Action: Correct the rule definition and order it again.

CTO524S RULE TABLE(S) ENDED WITH ERROR

Explanation: The indicated function of the CTOLDT program ended with errors. This program loads rule tables when a new Control-O/CMEM monitor is activated, and performs order/force of rule tables.

The IOA Log should contain prior messages concerning the errors.

Depending on when it fails, either the Control-O/CMEM monitor shuts down, or the table is not ordered.

Corrective Action: No action is required.

CTO525I RULE TABLE(S) ENDED

Explanation: This information message is a normal message issued when the indicated function of the CTOLDT program has terminated successfully. This program loads rule tables when a new Control-O or CMEM monitor is activated, or performs an ORDER or FORCE of rule tables.

Corrective Action: No action is required.

CTO526S ** ERROR IN RULE CARDS. CHECK THE FOLLOWING CARDS *

Explanation: The rule definition has been corrupted and the data do not conform to a valid Control-O/CMEM format.

This message is followed by one or more LDT527S messages describing all statements belonging to the damaged rule order. An asterisk (*) appears in the line under the erroneous data.

The rule is not ordered.

Corrective Action: Using the Online Viewing Facility, or by editing the member, restore the table to its original state, and reorder the rule table.

CTO527S CARD = `card`

Explanation: The rule definition has been corrupted.

This message follows message LDT526, and displays each statement in the damaged rule in the scheduling table. An asterisk * appears in the line under a damaged statement.

Corrective Action: Restore the table to its original state.

CTO528I RULE `ruleName rule_type` TABLE `tableName` LIBRARY `lib` ODATE `odate` LOADED

Explanation: This information message is a normal message when a rule order is successfully loaded by the Control-O/CMEM monitor.

The rule is now in Control-O/CMEM memory.

Corrective Action: No action is required.

CTO529I TABLE `tableName` LIBRARY `lib` DELETED

Explanation: This information message indicates that rule table tableName has been deleted from the Control-O/CMEM monitor as a result of an F CONTROLO,D=... operator command.

Corrective Action: No action is required.

CTO530E TABLE `tableName` LIBRARY `lib` REQUESTED DELETED NOT FOUND

Explanation: A request to delete a rule table from the Control-O/CMEM monitor has failed. Table tableName has not been found under Control-O/CMEM.

The table may be specified incorrectly or it may never have been ordered.

The table is not deleted.

Corrective Action: If the table specification incorrect, check and correct the table specification and issue the delete request again. If the table was never ordered, there is no reason to attempt to delete it.

CTO531I NO RULE WAS LOADED - TABLE `tableName` LIBRARY `lib`

Explanation: This information message indicates that the Control-O monitor did not load new rules from the tableName table in the lib library.

While ordering or forcing a rule library, Control-O found no rules that matched the Basic Scheduling parameters.

No rule is loaded.

Corrective Action: No action is required.

CTO532E MASK `mask` DOES NOT MATCH IN DSN=`dsn`

Explanation: The specified mask does not match any members in the rule library.

During rule ordering, the Control-O monitor found no members matching the specified mask.

No rule is loaded.

Corrective Action: Check and correct the parameters specified in the ORDER/FORCE command or in the rule list.

CTO536S SEVERE ERROR IN RULE DATA CARDS

Explanation: Severe error was found in the rule definition data statements. It is followed with additional messages regarding the error.

The rule table is not ordered.

Corrective Action: Check for additional messages concerning the errors in the systems and IOA Log and Control-O or CTMCMEM sysprint; correct the error and reorder the table.

CTO537S INSUFFICIENT STORAGE IN (EXTENDED) CSA. CANNOT LOAD TABLE

Explanation: Insufficient storage in the Extended Common Service Area (CSA) to load the rule table.

If any rules have been previously loaded, the Control-O/CMEM monitor proceeds without loading the table. If no rules were previously loaded, the Control-O/CMEM monitor shuts down.

Corrective Action: Check why there is insufficient CSA. You may need to contact your systems programmer. After correcting the problem, reload the table, or restart Control-O/CMEM, as necessary.

CTO539W ORDER CANCELLED BY USER EXIT: RULE `ruleName` TABLE `tableName` LIBRARY `lib`

Explanation: The specified rule order failed as a result of a user exit check.

The IOA Log should contain prior messages concerning the reason for failure.

The rule order is not ordered/loaded by the Control-O/CMEM monitor.

Corrective Action: Check the IOA Log for further information.

CTO545E DO-MISSION NOT SUPPORTED WITHOUT CONTROL-D INSTALLED

Explanation: An attempt was made to order a rule specifying DO MISSION, but Control-D is not installed. DO MISSION is supported only if Control-D is installed.

The rule is not ordered.

Corrective Action: Either remove this statement from the rule or install Control-D.

CTO548E SEVERE ERROR IN CALENDAR `calName` OR YEAR NOT FOUND IN CALENDAR

Explanation: Severe error in the IOA calendar calName, or the year not found in the calendar.

Either the year is not defined in the calendar or the calendar has been incorrectly modified.

The rule is not ordered.

Corrective Action: Check the contents of the rule order and the calendar. Correct and reorder the rule.

CTO54DE RULE TYPE IS INCORRECT. TABLE `tableName` LIBRARY `dsn`

Explanation: The user attempted to order or force a CMEM rule table from Control-O screen OR, or a Control-O rule table from CMEM screen C.

Control-O rules can only be ordered or forced from Control-O screen OR. CMEM rules can only be ordered or forced from CMEM screen C.

The table specified in the message is not loaded.

Corrective Action: If you issued the command from screen OR, issue it from screen C, or vice versa.

CTO54FW RULE WAS NOT LOADED: {SYSTEM | SMF ID} {`rul_sysname`|`rul_smfid`} DOES NOT MATCH {`cur_sysname`|`cur_smfid`}

Explanation: Control-O did not load a rule because the environment specified for that rule does not match the current environment.

When Control-O loads a table of rules during startup or as a result of an order, it does not load rules whose specified environment does not match the current one.

The Control-O monitor sends this message to SYSPRINT and to the IOALOG, and does not load the rule.

Corrective Action: To load a rule, make the environment specified for it match the current one and reload the table containing the rule.

CTO555S INSUFFICIENT STORAGE. INCREASE THE REGION SIZE

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

CTO560I ENVIRONMENT INITIALIZATION COMPLETE.

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 action is required.

CTO561E REQUESTED FUNCTION NOT SUPPORTED

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

The XAM interface or 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.

CTO562E INTERNAL RESOURCES EXHAUSTED

Explanation: The space in an internal table is exhausted. The XAM interface keeps an internal table of all XAM activities in the address space. The table can contain a maximum 256 concurrent TCBs requesting XAM services. There is no address space for a new XAM user.

Some TSO, REXX, or CLISTs running in the address space probably did not execute the TERM(inate) function, which releases the acquired XAM resources.

The XAM interface returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Determine why there is insufficient space, and correct the problem accordingly.

CTO563E IOA SUBSYSTEM `subsys` INACTIVE. INTERFACE CANNOT BE USED

Explanation: A request has been received through the XAM interface, or 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.

CTO565E SETOLOC/SETOGLB ERROR CODE=`rc` REASON=`rsn`, TEXT=`text`

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

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: 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.
	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, and 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.
	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.

CTO566E IOA SUBSYSTEM `subsys` NOT RESPONDING TO REQUESTS

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 a DORULE request to terminate the rule. If no such request is received within two minutes, this message is displayed.

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.

CTO567E IOA SUBSYSTEM `subsys` INACTIVE

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

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: Start the Control-O monitor.

CTO568E IOA SUBSYSTEM `subsys` DETECTED AN ERROR

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

The XAM interface, or 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 XAM interface or the Control-O API.
Determine whether or not the Control-O monitor is properly running for ongoing automation which is not related to XAM or the Control-O API.
Contact BMC Customer Support.

CTO569E IOA SUBSYSTEM `subsys` RETURNED AN INVALID RETURN CODE

Explanation: Due to an internal error, an invalid return code was returned by the subsystem subsys during the execution of a XAM DORULE request or a Control-O or CMEM 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: Do the following:

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

CTO56AE ERROR IN INAREA FIELDS ADDR=`add1 , add2` LENGTH `len` DATA=`data_val`

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.

CTO56AW SOME LOCAL VARIABLES NOT COPIED FROM XAM TO RULE, REASON=`rsn`

Explanation: A request was made to execute a Control-O rule by means of the DORULE function of the XAM interface. However, by the time the request was made, the XAM program that was executing had created an excessive number of local AutoEdit variables. The XAM service cannot share all these local AutoEdit variables with the Control-O rule, so some are discarded before the rule is given control.

In this message, rsn is an internal reason code used by BMC Customer Support.

The DORULE function continues, and control is given to the rule, but some local AutoEdit variables that cannot be copied to the rule environment are discarded. These discarded local AutoEdit variables are not available to the executed rule, nor are they available to the original XAM program once execution of the rule is complete.

Corrective Action: Use less local AutoEdit variables in the XAM program. You may be able to achieve this by using global, rather than local, AutoEdit variables. If the problem persists, contact BMC Customer Support.

CTO56BE ERROR IN RESULT FIELDS ADDR=`add`, LENGTH `len` DATA=`data_val.`

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

The system action is aborted.

Contact your INCONTROL administrator.

Corrective Action: No action is required.

CTO56BW SOME LOCAL VARIABLES NOT COPIED BACK FROM RULE TO XAM, REASON=`rsn`

Explanation: A request was made to execute a Control-O rule by means of the DORULE function of the XAM interface. However, by the time the rule finished executing, an excessive number of local AutoEdit variables had been created. The XAM service cannot share all these local AutoEdit variables with the original environment (the calling XAM program), so some are discarded before returning from the rule.

In this message, rsn is an internal reason code used by BMC Customer Support.

Execution of the DORULE request is completed, and control returns to the calling XAM program. However, some of the local AutoEdit variables that cannot be copied to the environment of the calling program are discarded. These discarded local AutoEdit variables are then no longer available to the original XAM program.

Corrective Action: Use less local AutoEdit variables in the XAM program and in the Control-O rule that you were executing. You may be able to achieve this by using global, rather than local, AutoEdit variables.

If the problem persists, contact BMC Customer Support.

CTO56CE INAREA LENGTH+RESULT=`xxxx` +`xxxx` =`xxxx` > 255.

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.

CTO56EE CHECKPOINT GLOBAL VARIABLE DATABASE `ioavar` TIMED OUT AFTER `num` SECONDS.

Explanation: CHECKPOINT was requested in order to save disk changes made in memory to the ioavar variable database. A time-out 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 action is required.

CTO56FE CHECKPOINT GLOBAL VARIABLE DATABASE `ioavar` ENDED WITH ERROR. RC=16

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 action is required.

CTO570I INITIALIZATION ENVIRONMENT COMPLETED.

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

Corrective Action: No action is required.

CTO573E IOA SUBSYSTEM `subsys` INACTIVE. INTERFACE CANNOT BE USED

Explanation: A request that requires the Control-O or CMEM monitor was issued by means of 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.

CTO575E SETOLOC/SETOGLB ERROR CODE = `rc` REASON = `rsn`, TEXT=`text`

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

Code	Description
Return Code 04	GETMAIN or FREEMAIN error. Reason codes are:
1 through 6	GETMAIN failure
7 through 10	FREEMAIN failure
Return Code 08	Variable not found. Reason codes are:
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
Return Code 12	Syntax error or General error. Reason codes are:
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 ?πmany 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
980	Internal error - global pool or database not found
982	Internal error - global pool or database not found
Return Code 16	Errors reading the global member. Reason codes are
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
Return Code 20	Errors writing the global member. Reason codes are:
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
Return Code 24	Program Buffers Shortage. Reason codes are:
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)
Return Code 32	Program Errors. Reason codes are:
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*.
Return Codes 36, 40, 44	>Global Variables 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
Return Code 48	Parse Errors. Reason codes are:
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

CTO576E IOA SUBSYSTEM `subsys` NOT RESPONDING TO REQUESTS

Explanation: A request from the Control-O or CMEM monitor by means of the Control-O API failed due to time-out, 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.

CTO577E IOA SUBSYSTEM `subsys` INACTIVE

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.

CTO578E IOA SUBSYSTEM `subsys` DETECTED AN ERROR

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.

CTO579E IOA SUBSYSTEM `subsys` RETURNED AN INVALID RETURN CODE

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: Notify BMC Customer Support.

CTO57AE ERROR IN INAREA FIELDS ADDR= `add1, add2` LENGTH `len` DATA= `value`

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

The action is aborted.

Corrective Action: Notify BMC Customer Support.

CTO57BE ERROR IN RESULT FIELDS ADDR= `add`, LENGTH `len` DATA= `value`

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

The action is aborted.

Corrective Action: Notify BMC Customer Support.

CTO57CE INAREA LENGTH `length1` + RESULT LENGTH `length4` > 255.

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.

CTO57EE CHECKPOINT GLOBAL VARIABLE DATABASE `dbName` ENDED DUE TO TIMEOUT AFTER `num` SECONDS

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

The checkpoint request terminated.

Corrective Action: Check the Control-O or CMEM monitor job log 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.

CTO5A0E SERVER `serverId`, SECURITY ENVIRONMENT CREATION FAILED RC=`rc` REASON=`rsn`

Explanation: The IOASECUR security handling module failed to establish the security environment.

In rules in which value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

This message is often accompanied by the SRV5A1I or CTO281I message, which contains the error message returned by the locally active security product.

The KSL/TSO/SHELL request is not performed.

Corrective Action: See the DOCSECUR member in the IOA DOC library for a description of rc and reason.

Correct the security definitions, and/or verify changes made to the IOASECUR security module. Additional information is provided in the CTO5A1I or CTO281I message (if issued).

CTO5A1I ERROR MESSAGE = `text`

Explanation: This information message indicates that the IOASECUR security module failed to establish the security environment.

In rules in which the value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

In this message, text is the error message returned by the security product active at the site.

The KSL/TSO/SHELL request is not performed.

Corrective Action: Depending on the message text, correct the security definitions and verify changes made to the IOASECUR security module.

CTO5A2W SERVER `serverId`, SECURITY ENVIRONMENT CLEANUP FAILED RC=`rc` REASON=`rsn`

Explanation: The IOASECUR security handling module failed to reset the security environment.

In rules in which value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

This message is often accompanied by message SRV5A1I which contains the error message text returned by the locally active security product.

Depending on the rc and reason, the DO KSL/TSO/SHELL request may or may not be performed.

Corrective Action: See the DOCSECUR member in the IOA DOC library for a description of rc and rsn.

Correct the security definitions, and/or verify changes made to the IOASECUR security module. More information is provided in the CTO5A1I or CTO281I message (if issued).

CTO5A3I CONTROL-O SERVER `serverId` STARTED

Explanation: This information message indicates that the specified Control-O server has been successfully started.

Corrective Action: No action is required.

CTO5A4I CONTROL-O SERVER `serverId` ENDED

Explanation: This information message indicates that the specified Control-O server has been successfully terminated.

Corrective Action: No action is required.

CTO5A5E SERVER `serverId` SEVERE ERROR - `details`

Explanation: The specified server detected an internal error.

The server is terminated.

Corrective Action: Contact BMC Customer Support.

CTO5A9S CONTROL-O SERVER `serverId` HAS ABENDED. ABEND CODE = `abCode`

Explanation: The server detected an internal abend.

This message indicates an internal error.

Server serverId is terminated.

Corrective Action: Contact BMC Customer Support for assistance.

CTO5AFE SERVER `serverName`, TIMEOUT OCCURRED. REQUEST WILL BE CANCELED

Explanation: The server is executing a DO KSL, DO TSO, or DO SHELL with TIMEOUT and STOP=Y defined. This DO KSL or DO TSO command, z/OS SHELL script, REXX, or CLIST has reached its timeout limit and the sub-task running it will be canceled.

After this message is issued, the server will usually terminate. In the case of a General or Dedicated server with SRVTERM set to N, the server will continue to accept other requests.

Corrective Action: Either enlarge the TIMEOUT amount defined for the execution or correct the TSO Command, z/OS SHELL script, REXX, or CLIST whose time limit was reached.

CTO5AGE DYNAMIC ALLOCATION OF SYSTSIN FAILED. R15=`rc` REASON=`rsn`

Explanation: Control-O was unable to dynamically allocate SYSTSIN DD.

Control-O uses the SYSTSIN DD used to pass the TSO command to the Control-O server address space.

Corrective Action: Refer to the IBM MVS Programming: Authorized Assembler Services Guide for the Dynamic Allocation return code and reason code explanation.

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.

Messages CTO700 through CTO7xx

This group includes messages for the Control-O product.

CTO720I FORMATTING OF STATISTICS FILE STARTED

Explanation: This informative message is issued when the CTOFST Statistics Formatting utility starts formatting the Statistics file.

Corrective Action: No action is required.

CTO721S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`

Explanation: Dynamic allocation of the Statistics file dsn failed with the return code rc and the reason code rsn.

The CTOFST Statistics Formatting utility terminates with a return code of 08.

CTO722S STATISTICS FILE ALLOCATION ERROR - ACTIVE SMF ID DOES NOT MATCH PARAMETER SMF ID

Explanation: The SMF ID specified for the CTOFST Statistics Formatting utility does not match the active MVS SMF ID. The SMF ID for the CTOFST utility is specified in the input PARM string. The current MVS SMF ID is specified in IEASMFxx of SYS1.PARMLIB. These SMF IDs should match.

The CTOFST utility terminates with return code of 08.

Corrective Action: Correct the PARM string to reflect the active SMF ID, and rerun the job.

CTO723S STATISTICS FILE IN USE. FORMATTING CANNOT BE PERFORMED

Explanation: The CTOFST Statistics Formatting utility failed to format the Statistics file because the file is allocated to another user. The CTOFST Statistics Formatting utility attempts to allocate the Statistics file with DISP set to OLD.

The utility terminates with a return code of 08.

Corrective Action: Make sure that no user is allocated to the Statistics file, and rerun the job.

CTO724E OPEN OF STATISTICS FILE FAILED

Explanation: The CTOFST Statistics Formatting utility could not successfully open the Statistics file.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.

CTO725E OPEN OF MESSAGES FILE FAILED

Explanation: The CTOFST Statistics Formatting utility unsuccessfully attempted to open the Messages file specified in the SYSPRING DD statement. An OPEN request was issued to the Messages file but was unsuccessful. A possible cause is that the SYSPRINT DD statement may not have been specified in the job stream.

The utility terminates with a return code of 08.

Corrective Action: Look for earlier MVS error messages regarding the opening of the Messages file. Correct the error, and rerun the job.

CTO726S FORMATTING OF STATISTICS FILE ENDED WITH ERROR

Explanation: The formatting of the Statistics file was unsuccessful.

The CTOFST Statistics Formatting utility terminates with a return code of 08.

Corrective Action: Look for earlier error messages to determine the cause of the error. Correct the error and rerun the job.

CTO729S WRITE OPERATION TO THE STATISTICS FILE FAILED

Explanation: A WRITE request failed during the formatting of the Statistics file.

The CTOFST Statistics Formatting utility terminates with a return code of 08.

Corrective Action: Delete the Statistics file. Then rerun the job, specifying smfid volser and unit. Earlier MVS error messages regarding the Statistics file may indicate the cause of the error.

CTO730I FORMATTING OF STATISTICS FILE ENDED SUCCESSFULLY

Explanation: This information message is issued when the CTOFST Statistics Formatting utility completes with no errors.

Corrective Action: No action is required.

CTO731E INVALID PARAMETERS

Explanation: The DEFSTAT utility was called with incorrect parameters.

The utility terminates with a return code of 08.

Corrective Action: Correct the parameters and rerun the utility.

CTO742S ERROR IN OPEN OF INPUT FILE

Explanation: The CTORSTM Statistics report utility could not open the input file specified in the DAREPIN DD statement.

An OPEN request was issued to the input file, but was unsuccessful. A possible cause of the problem is that the DAREPIN DD statement may not have been specified in the job stream.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the input file. Correct the error and rerun the job.

CTO743S INTERNAL ERROR - `errorText`

Explanation: The CTORSTM Statistics report utility encountered internal error errorText.

The utility terminates with a return code of 08.

Corrective Action: Contact BMC Customer Support.

CTO744S ERROR IN OPEN OF REPORT FILE

Explanation: The CTORSTM Statistics report utility could not open the report file specified in the SYSPRINT DD statement.

An OPEN request was issued to the REPORT file, but was unsuccessful. A possible cause of the problem is that the SYSPRINT DD statement may not have been specified in the job stream.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the report file. Correct the error and rerun the job.

CTO745S ERROR IN OPEN OF STATISTICS FILE

Explanation: The CTORSTM Statistics report utility could not open the Statistics file.

Failure to open the Statistics file may have been caused by one of the following:

The data set allocated to the DASTF DD statement was not formatted as a Control-O Statistics file.
The data set allocated to the DASTF DD statement was formatted as a Control-O Statistics file by a different version of Control-O.
The data set allocated to the DASTF DD statement belongs to a different installation of Control-O.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.

CTO746S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`

Explanation: Dynamic allocation of Statistics file dsn failed with return code rc and reason code 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 BMC Customer Support.

CTO747W ERROR IN CLOSE OF STATISTICS FILE

Explanation: The CTORSTM Statistics file utility could not successfully close the Statistics file.

The utility terminates with a return code of 08.

Corrective Action: If no MVS error messages clarifying the error were issued, this is probably an internal error. In this case, please report it to BMC Customer Support.

CTO750E NO ROOM AVAILABLE TO INSERT LINE HERE

Explanation: There was an attempt to insert a row in a Variable database, but no row number is available at the point of insertion. Variable database rows are originally numbered by thousands. Rows added later are assigned numbers in the gaps. This message is generated if a suitable row number is not available at the location where a new row is to be inserted. See the description of the IOA Variable Database facility in the Control-O User Guide for an explanation of how database row numbers are assigned.

The row is not added to the Variable database.

Corrective Action: Renumber the existing rows in the database, as follows:

Unload the Variable Database Variables file by means of the CTOVARUL job in the Control-O JCL library. This job invokes the IOADUL utility.
Reload this file by means of the CTOVARLD job in the Control-O JCL library. This job invokes the IOADLD utility. Be sure the RENUM parameter is included.

For more information about the IOADUL and IOADLD utilities, see the INCONTROL for z/OS Utilities Guide.

CTO754E NO AUTHORIZATION FOR PERFORMING THIS OPERATION

Explanation: The user is unauthorized to perform the requested insert or update on the variable.

The variable is not created or updated.

Corrective Action: To be authorized to perform the attempted operation, contact your INCONTROL administrator.

CTO756E INSUFFICIENT SPACE IN THE VARIABLES FILE

Explanation: An attempt was made to create a new variable, but there is insufficient space in the Variables file. New variables cannot be defined until sufficient space is provided.

The new variable is not created.

Corrective Action: Provide more free space in the Variables file. For information about increasing the size of IOA Access Method files and about compressing the data in such files, see the INCONTROL for z/OS Administrator Guide.

CTO757E INSUFFICIENT SPACE IN THE MODELS FILE

Explanation: An attempt was made to create a new column, but there is insufficient space in the Columns file. New columns cannot be defined until sufficient space is provided.

Corrective Action: Provide more free space in the Columns file. For information about increasing the size of IOA Access Method files and about compressing the data in such files, see the INCONTROL for z/OS Administrator Guide.

CTO758E INSUFFICIENT SPACE IN THE INDEX FILE

Explanation: An attempt was made to create a new variable, but there is insufficient space in the Variables database index file. New variables cannot be defined until sufficient space is provided.

The new variable is not created.

Corrective Action: Provide more free space in the Variables database index file. For information about increasing the size of IOA Access Method files and about compressing the data in such files, see the INCONTROL for z/OS Administrator Guide.

CTO759E COLUMN ALREADY EXISTS. IT CANNOT BE CREATED

Explanation: An attempt was made to create a column, but a column with that name already exists in the database. The column cannot be created, because it already exists. It cannot be saved, because it was specified by means of command Insert.

The Exit Option Window is closed. The database Column Definition screen remains displayed.

Corrective Action: Either specify a database column name that does not currently exist in the database, or use the CANCEL command to exit without saving the database column definition.

CTO75AE UPDATE OF COLUMN DEFINITION FAILED

Explanation: An error occurred while attempting to update a column in the variable database Column Definition screen.

The variable database column definition is not updated.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTO75CE OPERATION FAILED. ERROR DURING FILE ACCESS RC=`rc`, FUNCTION=`func`

Explanation: An internal error occurred while trying to update the columns definition of the Global Variable database.

The update is not performed.

Corrective Action: Call your INCONTROL administrator.

CTO780I INITIALIZATION OF OPENEDITION ENVIRONMENT STARTED

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor detected an environment which supports the MVS OpenEdition interface with Control-O and began initializing the OpenEdition environment.

Corrective Action: No action is required.

CTO781I OPENEDITION INTERFACE MODULE SUCCESSFULLY LOADED

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor loaded the OpenEdition interface module into storage. This message is issued only for the first Control-O or CMEM monitor in the system.

Corrective Action: No action is required.

CTO782I SUBSYSTEM REGISTERED WITH OPENEDITION INTERFACE

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

The current Control-O or CMEM subsystem has registered itself (meaning, recorded its name) with the OpenEdition interface in order to receive OpenEdition events from the interface.

Corrective Action: No action is required.

CTO783I INITIALIZATION OF OPENEDITION ENVIRONMENT ENDED SUCCESSFULLY

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

OpenEdition support for the current Control-O or CMEM monitor is successfully installed. Control-O or CMEM will trigger rules based on OpenEdition events.

Corrective Action: No action is required.

CTO784W OS/390 VERSION IS 2.4 OR HIGHER BUT PTF LEVEL IS TOO LOW

Explanation: Control-O or CMEM tried to install OpenEdition support but found an incompatible PTF level.

Control-O or CMEM support for OpenEdition events is required for OS/390 version 2.4 and later. The PTF level in MVS is too low to install the OpenEdition interface.

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action: Install IBM PTF for APAR OW36163, which enables Control-O or CMEM support for OpenEdition.

CTO785W UNABLE TO REGISTER WITH OPENEDITION INTERFACE: LOCK CANNOT BE OBTAINED

Explanation: The Control-O or CMEM subsystem could not register with the OpenEdition interface during initialization because Control-O or the CMEM monitor cannot acquire the OpenEdition interface lock, which is required for registration.

Initialization of the OpenEdition interface fails. Initialization of Control-O or the CMEM monitor continues. Control-O or the CMEM monitor will not be able to handle OpenEdition events, such as data set triggering based on FTP transmissions.

Corrective Action: Restart the current monitor. If the problem persists, call your INCONTROL administrator.

CTO786W LOAD OF OPENEDITION INTERFACE MODULE FAILED: LOAD TO PRIVATE FAILED

Explanation: During initialization of the OpenEdition interface, Control-O or CMEM could not load the OpenEdition support module because Control-O or CMEM monitor could not load the OpenEdition support module in its own private region.

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action: Determine the cause of the failure using previous messages. Possible causes are:

The Control-O or CMEM region is too small.
The CTOAODT module is not in the Control-O CMEM STEPLIB.

CTO787E INITIALIZATION OF OPENEDITION ENVIRONMENT FAILED

Explanation: Control-O or CMEM tried to install the OpenEdition interface but an error occurred during initialization of the interface.

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action: Look for previous messages which explain the cause of the failure. Call your INCONTROL administrator.

CTO788I SUBSYSTEM ALREADY REGISTERED WITH OPENEDITION INTERFACE

Explanation: This information message indicates that Control-O or the CMEM monitor tried to register with the OpenEdition interface but found the subsystem was already registered.

A possible cause is a previous uncompleted termination of CMEM or Control-O.

Initialization of the OpenEdition interface continues.

Corrective Action: No action is required.

CTO789W OPENEDITION ADDRESS SPACE HAS NOT COMPLETED INITIALIZATION

Explanation: During Control-O startup, Control-O tried to activate OPENEDITION (UNIX for MVS) support. The attempt failed for one of the following reasons:

The system is earlier than OS/390 version 2.4.
IBM APAR OW36163 is missing.

The preconditions for using Control-O/ OPENEDITION (UNIX for MVS) are:

The system must be at OS/390 version 2.4 or later.
IBM APAR OW36163 must be applied.

The Control-O startup process completes but does not support OPENEDITION.

Corrective Action: If the system is earlier than OS/390 version 2.4, ignore this message. Otherwise, apply IBM APAR OW36163.

CTO78BW UNABLE TO REGISTER WITH OPENEDITION INTERFACE: NO PROPER ENTRY IN SSTABLE

Explanation:The Control-O or CMEM subsystem could not register with the OpenEdition interface during initialization because Control-O or the CMEM monitor cannot locate its entry in the INCONTROL internal subsystems table.

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action:Restart the current monitor. If the problem persists, call your INCONTROL administrator.

CTO78CW LOAD OF OPENEDITION INTERFACE MODULE FAILED: CSA GETMAIN FAILED

Explanation: During initialization of the OpenEdition interface, Control-O or CMEM could not load the OpenEdition support module because Control-O or CMEM monitor could not acquire storage in the Common Service Area (CSA) for the OpenEdition support module.

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action:Make sure that the CSA has at least 8K of free storage, then restart the Control-O or CMEM monitor.

CTO78DW LOAD OF OPENEDITION INTERFACE MODULE FAILED: LOAD TO CSA FAILED

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action:Use the contents of previous messages to determine the cause of the failure.

CTO790I DEACTIVATION OF OPENED4ITION ENVIRONMENT STARTED

Explanation: This information message is the normal message issued during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor detected an active OpenEdition interface environment and started its termination procedure.

Corrective Action: No action is required.

CTO791I SUBSYSTEM REMOVED FROM OPENEDITION INTERFACE

Explanation: This information message is the normal message generated during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

The current Control-O or CMEM subsystem removed itself from the OpenEdition interface in order to stop receiving OpenEdition events.

Corrective Action: No action is required.

CTO792I OPENEDITION INTERFACE MODULE REMOVED

Explanation: This information message is the normal message issued during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor removed the OpenEdition support module from storage. This message is displayed only during termination of the last Control-O or the CMEM monitor in the system.

Corrective Action: No action is required.

CTO793I DEACTIVATION OF OPENEDITION ENVIRONMENT ENDED SUCCESSFULLY

Explanation: This information message is the normal message issued during termination of the CMEM monitor or Control-O when using OS/390 version 2.4 or later.

The OpenEdition interface for the current Control-O or CMEM monitor has been successfully removed.

Corrective Action: No action is required.

CTO794W DEACTIVATION OF OPENEDITION ENVIRONMENT FAILED

Explanation: Control-O or CMEM tried to remove OpenEdition support but encountered an error.

An error occurred during termination of the OpenEdition interface.

Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.

Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.

CTO795W OPENEDITION INTERFACE MODULE NOT INSTALLED

Explanation: Control-O or the CMEM monitor could not find the OpenEdition interface module during termination.

During termination Control-O or CMEM detected an environment which supports the OpenEdition interface but could not find the OpenEdition support module which should have been installed during initialization.

Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.

Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.

CTO796W SUBSYSTEM NOT REMOVED FROM OPENEDITION INTERFACE: `rsn`

Explanation: Control-O or CMEM could not remove its subsystem name from the OpenEdition interface during termination.

If reason is SUBSYSTEM NOT FOUND, Control-O or CMEM could not find its subsystem name registered with the OpenEdition interface.

If reason is LOCK CANNOT BE OBTAINED, Control-O or the CMEM monitor could not get the OpenEdition interface lock it needs to remove its name.

Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.

Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.

CTO797E EINVALID REFRESH SUBPARAMETERS. VALID PARAMETER is: XCF

Explanation: The user issued the command F Control-O, REFRESH= parm to refresh the Control-O communication definitions, but the value of parm was invalid.

The valid value of the subparameter is XCF.

Refresh of the Control-O communication definition fails.

Corrective Action: Correct and reenter the command.

CTO798E ERROR IN MODIFY-REFRESH PROCESSING

Explanation: An error was detected while attempting to refresh the XCF configuration map of Control-O, which defines the MVS image names with which Control-O can work.

Refresh of the Control-O communication definition by the REFRESH command fails.

Corrective Action: Examine the earlier accompanying messages in the Control-O JOBLOG or SYSLOG.

CTO7B0E SMSCLASS and SMSMSG are valid in 'ON SMS' only

Explanation: An attempt was made to add a DO SMSCLASS or DO SMSMSG in an SMS rule that was not ON. DO SMSCLASS or DO SMSMSG can only be used in ON SMS rules.

The statement is not accepted.

Corrective Action: Delete the DO SMSCLASS or DO SMSMSG statement from the rule.

CTO7B1E SMSCLASS and SMSMSG are invalid after ASKOPER, DO COMMAND+WAIT or WAIT

Explanation: An attempt was made to add a DO SMSCLASS or DO SMSMSG statement in an invalid location in the Control-O rule. DO SMSCLASS or DO SMSMSG can be used only in an ON SMS rule, and only before any WAIT.

The statement is not accepted.

Corrective Action: Delete the DO SMSCLASS or DO SMSMSG from the rule, or move it to a correct location.

CTO7B2E SHARELOC or TIMEOUT are valid if SYSTEM is not set

Explanation: The Control-O communication function does not support the sharing of AutoEdit variables or TIMEOUT. Therefore, neither SHARELOC nor TIMEOUT can be used in rule definition when the system field is not null.

The action is rejected.

Corrective Action: Correct the DO KSL, DO TSO, or DO SHELL command.

CTO7B3E SMSCLASS id is between 1 and 15 only

Explanation: An attempt was made to add a DO SMSCLASS with an ID value of 0 or greater than 15. To be valid, an ID value must be from 1 through 15.

The value in the ID field is not accepted.

Corrective Action: Insert a valid ID value in the DO SMSCLASS, from 1 through 15.

CTO7B4E SIGN OF QUANTITY MUST BE EITHER "+","-", "?" OR BLANK

Explanation: In a DO RESOURCE statement, an invalid sign was entered in the quantity change field.

Valid values for the quantity change subparameter are:

- (Minus) - Decreases the associated quantity by the amount specified.
+ (Plus) - Increases the associated quantity by the amount specified.
? (Question mark) - Check the status of the resource.
' ' (Blank) - Sets a new associated quantity for the resource.

Corrective Action: Correct the value of the quantity change subparameter by entering a valid sign.

CTO7B5E INVALID CONDITION OPTION. USE "+" (ADD), "-" (DELETE) OR "?" (QUERY)

Explanation: In a DO COND statement, an invalid sign was entered in the condition option field.

Valid values for the condition option subparameter are:

- (Minus) - Delete the prerequisite condition.
+ (Plus) - Add the prerequisite condition.
? (Question mark) - Check the status of the condition.

Corrective Action: Correct the value of the CONDOPT subparameter by entering a valid sign.

CTO7B6E Valid Priority MNEMONICs: CL, CR, IN, MA, MI, WA or 1 to 6

Explanation: In an ON MVALARM statement, an invalid value was entered in the PRIORITY field.

Valid values for the PRIORITY subparameter are (in increasing order of severity):

CLEAR (or the numeral 6)
INFORMATIONAL (or the numeral 5)
WARNING (or the numeral 4)
MINOR (or the numeral 3)
MAJOR (or the numeral 2)
CRITICAL (or the numeral 1)

Corrective Action: Correct the value of the PRIORITY subparameter by entering a valid value.

CTO7B7E INVALID ALARM type. Valid value: Start or End

Explanation: In an ON MVALARM statement, an invalid value was entered in the TYPE field.

Valid values for the TYPE subparameter are:

S - A new MAINVIEW alarm.
E - The end of the MAINVIEW alarm.

Corrective Action: Correct the value of the TYPE subparameter by entering a valid value.

CTO7B8E INVALID RUNTSEC. ON RULE supports "T"-TRIGGER or BLANK

Explanation: In an ON RULE statement, an invalid value was entered in the RUNTSEC field.

Valid values for the RUNTSEC subparameter are:

T (Trigger) - Runtime security checks are carried out using the user ID associated with the started task, TSO use or batch job that issued the message or command that invoked the rule.
' ' (Blank) - Runtime security checks are or are not performed, depending on the value set for the RUNTDFT global parameter in the CTOPARM member during the installation of Control-O. Default.

For more information, see the description of the RUNTSEC subparameter in the Control-O User Guide.

Corrective Action: Correct the value of the RUNTSEC subparameter by entering a valid value.

CTO7C1E AT LEAST ONE "DO" STATEMENT MUST BE FILLED IN

Explanation: A DO statement (action) is not complete. At least one DO statement is required in the Rule Definition. The DO statement specifies actions to be performed after Message or Event Selection criteria are fulfilled.

For DO statement requirements, see the parameter descriptions in the Control-O User Guide or the Control-M for z/OS User Guide.

Corrective Action: Complete at least one DO statement.

CTO7C3E PLEASE FILL IN THE FIELD (BLANKS ARE INVALID)

Explanation: The field was left blank, but some data are required. The field is obligatory, and it does not have a default value. An entry must be made.

Corrective Action: Enter a value in the field.

CTO7C4E VALID DESCRIPTOR CODE CAN BE FROM 00 TO 16

Explanation: An invalid descriptor code was entered in the DESC field of the Rule Definition.

DESC is an optional parameter which specifies the message descriptor code. The DESC parameter value (if specified) must be a valid 1- 2 digit descriptor code (00 - 16).

Corrective Action: Enter a valid descriptor code in the DESC field or leave it blank.

CTO7C5E VALID ROUTE CODE CAN BE FROM 000 TO 255

Explanation: The ROUTE field of the Rule Definition has an invalid routing code. ROUTE is an optional parameter. The ROUTE parameter value, if specified, must be a valid 1- to 3-digit route code (000-255).

Corrective Action: Enter a valid routing code in the ROUTE field or leave it blank.

CTO7CAE VALID COLUMN RANGE IS 001-128

Explanation: An invalid range was specified in the COLS subparameter in the ON statement. When specifying a string using the S option in the ON statement, the search for this string may be limited to a specific column range by entering the range in the COLS subparameter.

The format is: COLS fromcol tocol, where fromcol or tocol may be any number from 1- 128, and the fromcol value may not be greater than the tocol value.

Corrective Action: Enter a valid range, or do not enter a search range.

CTO7CBE FROM COL GREATER THAN UNTIL COL

Explanation: The specified fromcol range is greater than the specified tocol range in the COLS subparameter of the ON statement. When specifying a string using the S option in the ON statement, the search for this string may be limited to a specific column range by entering the range in the COLS sub-parameter.

The format is: COLS fromcol tocol, where fromcol or tocol may be any number from 1- 128, and the fromcol value may not be greater than the tocol value.

Corrective Action: Enter a valid search range or do not enter a search range.

CTO7CCE BOTH "APPEARED" AND "TIMES IN" MUST BE FILLED IN OR BLANK

Explanation: Only one value was provided for the APPEARED n TIMES IN m MINUTES parameter. While entries in the APPEARED n TIMES IN m MINUTES parameter are optional, values must be specified for both n and m, if this parameter is used.

Valid values are:

n - Appeared n times. Must be a numeric value from 2 through 999.
m - In m minutes. Must be a numeric value from 1 through 9999.

Corrective Action: Specify values for both n and m, or do not specify values for either.

CTO7CDE INVALID "ON". USE M, STR, CO, CT, E, JA, JE, D, STE, OM

Explanation: An invalid ON statement is specified in a Control-O rule. ON statements specify Message or Event criteria that must be met before Control-O triggers a rule.

For more information about ON statements, see the parameter descriptions in the Control-O User Guide.

The statement is ignored.

Corrective Action: Specify a valid ON statement.

CTO7CEE INVALID DATE (USE "DATE", "ODAT", SPECIFIC DATE OR AUTOEDIT VAR)

Explanation: An invalid scheduling date was entered in the DATE subparameter of the FORCEJOB parameter. The DATE subparameter specifies the scheduling date for the job or jobs.

Valid date formats are:

DATE - Resolves to the current Gregorian computer date.
ODAT - Resolves to the Control-M original scheduling date of the job.
%%xx - An AutoEdit symbol may be assigned by a DO SET command in the rule, or it can be a Global variable.
ddmm - Day and month of scheduling date.
mmdd - Month and day of scheduling date (USA format).

Corrective Action: Enter a valid date.

CTO7CFE PLEASE FILL IN A VALID AUTOEDIT STATEMENT

Explanation: There is an invalid AutoEdit statement or expression in the DO SET statement. The DO SET statement is used to specify AutoEdit variables that are resolved at runtime.

See the Control-O User Guide for an explanation of the AutoEdit Facility.

Corrective Action: Enter a valid AutoEdit statement.

CTO7D7E INVALID CAPS ON / OFF COMMAND. COMMAND IGNORED

Explanation: An attempt was made to use the CAPS primary command in BROWSE mode. The CAPS primary command is not valid in BROWSE mode.

The command is not performed.

Corrective Action: No action is required.

CTO7D8I CAPS IS ON / OFF

Explanation: This information indicates a change in status of CAPS mode (ON or OFF) after entry of the CAPS primary command. The CAPS mode determines whether characters can be entered only in upper case, or also in lower case.

Corrective Action: No action is required.

CTO7DFE INVALID `‘type` ’ EXPRESSION. RC=`rc`, REASON CODE=`rsn`

Explanation: The rule definition contains an invalid evaluation expression of type, where type is IF or WHILE. Probable causes are:

invalid nesting of parentheses
invalid AutoEdit expressions
invalid logical operands

The rule definition is not saved.

Corrective Action: Correct the invalid expression. If necessary, check the return code and reason code in the table in message WTO283E, to determine the reason for the failure.

CTO7DGW MODE CAPS OFF IGNORED. RUNNING IN DBCS MODE

Explanation:User entered CAPS OFF command, but the user is working at a DBCS terminal.

The command is ignored because DBCS terminals do not support lower case.

Corrective Action: No action is required.

CTO7DHI FOUND LOWER CASES. FORCING CAPS OFF

Explanation:User entered a Control-O or CMEM rule and the control program found lower case characters.

CAPS OFF is forced to prevent upper casing by mistake. The user's online profile is not changed when saving and exiting the rule screen.

Corrective Action: No action is required.

CTO7F1E `field1` AND `field2` ARE MUTUALLY EXCLUSIVE

Explanation: The ON or DO statement combinations are not valid. When defining or updating a Control-O rule, some statement combinations cannot be used together. In this case, the setting of one statement precludes the desired setting of the other statement. Possibly, the logical check picked up statement combinations that were defined, but not rejected in a previous release.

The rule is not saved.

Corrective Action: Correct the rule so that the statement combinations are valid.

CTO7F3E Invalid AND/NOT relations between 'ON' statements

Explanation: The AND/OR/NOT field in the ON statement is invalid. Inappropriate definition of AND, OR, or NOT fields connecting ON statements can create logic problems, such as a rule that is never triggered. Control-O checks each rule to ensure that the combination of ON statements and AND/OR/NOT connectors is logical.

For example,

The statement ON MESSAGE X AND ON MESSAGE Y is not logical because the message cannot be both X and Y
The statement ON JOBARRIV A AND ON JOBEND B is not logical, because the ON statements in a single rule cannot refer to two different EVENTs; these must be in separate rules

It is possible that the logic problem was detected in a rule that was defined in a previous Control-O release.

The rule is not saved.

Corrective Action: Correct the ON statement and then save the rule.

CTO7F4E Invalid AND/NOT relations between 'ON' `field1 field2` fields

Explanation: Values have been entered into two fields that are mutually exclusive, in that only one of the fields can have a value.

In this message, field1 and field2 are the identities of the two fields that are mutually exclusive.

Corrective Action: Enter a value for the field you require, and delete the value in the other field.

CTO7F5E DDNAME or JOBNAME must be specified

Explanation: A value must be set for the DDNAME and JOBNAME fields in ON SYSOUT. These fields may not be left blank or contain only the value * (Asterisk).

The rule is not saved.

Corrective Action: Correct the ON SYSOUT statement, and save the rule.

CTO7F6E JOBNAME=`jobName` not allowed in ON SYSOUT

Explanation: The JOBNAME fields in ON SYSOUT may not be any of the following:

' ' (Blank)
* (Asterisk)
JES2
JES3
*MASTER*
CATALOG
SMS

The rule is not saved.

Corrective Action: Correct the JOBNAME field in the ON SYSOUT statement, and then save the rule.

CTO7F7E DDNAME=`ddName` not allowed when JOBNAME is not specified

Explanation: An invalid value was found in the DDNAME parameter in the ON SYSOUT statement. The value in the DDNAME parameter in the ON SYSOUT may not be any of the following:

' ' (Blank)
* (Asterisk)
SYSUT*
SYSUDUMP
SYSMDUMP
SYSABEND
SYSTERM
INTRDR

The rule is not saved.

Corrective Action: Correct the value of the DDNAME parameter in the ON SYSOUT statement, and then save the rule.

CTO7F8E DO KSL/TSO/SHELL/WAIT with WAIT=YES not allowed in ENDMSG block

Explanation: The expression WAIT=YES was defined in a DO KSL, DO TSO, DO SHELL, or DO WAIT statement for a multi-line block that ends with an ENDMSG statement. WAIT mode actions are not allowed in multiline block processing that ended by ENDMSG.

The rule is not saved.

Corrective Action: Delete the expression WAIT=YES, then save the rule.

CTO7F9E DO EXIT valid only with MSG/MESSAGE or WHILE

Explanation: Use of DO EXIT in this situation is not valid. DO EXIT can only be used in one of the following cases:

with MSG or MESSAGE to exit multi-line block processing that ended with ENDMSG
with WHILE to exit WHILE block processing that ended with ENDWHILE

Rule definition cannot continue until the mistake is corrected.

Corrective Action: Correct the mistake, and continue defining the rule.

CTO7FAE DO EXIT invalid - missing 'ENDMSG'

Explanation: Exit from the Control-O rule definition failed because a DO EXIT MESSAGE statement is not followed by an ENDMSG statement to indicate the end of the multi-line message processing block. A DO EXIT MESSAGE statement is valid only in a multi-line message processing block, which must be closed by an ENDMSG statement.

The rule cannot be saved.

Corrective Action: Do one of the following:

Delete the DO EXIT MESSAGE command.
Add ENDMSG at the end of the block.

CTO7FBE DO EXIT invalid - no DO WHILE block is open

Explanation: An attempt was made to add a DO EXIT W (while) statement outside of a DO WHILE block. An EXIT W (while) statement is valid only in a DO WHILE block.

The EXIT W statement is rejected.

Corrective Action: Delete the EXIT W statement.

CTO7FCE ACS CALL values are: Management, Data, Storage, All, '*'

Explanation: The ACS CALL field in an ON SMS statement has an invalid value.

Valid values for the ACS CALL field are:

MANAGMNT - Management class selection routine
DATA - Data class selection routine
STORAGE - Storage class selection routine
ALL - All of the above
* (Asterisk) - All of the above (the same as ALL)

The value in the ACS CALL field is rejected.

Corrective Action: Correct the ACS CALL field in the ON SMS statement.

CTO7FDE DSORG values are: PS, SEQ, PO, PDS, VS, or DA

Explanation: The DSORG field in an ON SMS statement has an invalid value. Valid values are:

PS or SEQ - Sequential file
PO or PDS - Partitioned data set
VS - VSAM file
DA - Direct file

The value in the DSORG field is rejected.

Corrective Action: Correct the DSORG field in the ON SMS statement.

CTO7FEE DS-type values are: GDg or GDs, PErm or Temp

Explanation: The DS-TYPE field in an ON SMS statement has an invalid value. Valid values are:

GDG or GDS - Generation data set
PERM - Permanent data set
TEMP - Temporary data set

The value in the DSORG field is not accepted.

Corrective Action: Correct the DS-TYPE field in the ON SMS statement.

CTO7FFE SMSMSG ID valid number is 1 to 6. BLANK is NOT allowed.

Explanation: The ID field in a DO SMSMSG statement contains an invalid value. The value in such a field must be from 1 through 6.

The value is not accepted.

Corrective Action: Specify a valid value (from 1 through 6) in the ID field of the DO SMSMSG statement.

CTO7FGI Use CAPS OFF to turn off uppercasing of this field

Explanation: The Shell script name contains UPPERCASE symbols.

Corrective Action: To prevent uppercasing by mistake, type CAPS OFF.

Messages CTO800 through CTO8xx

This group includes messages for the Control-O product.

CTO820I INITIALIZATION OF SMS SUPPORT STARTED

Explanation: This information message indicates that Control-O started initializing SMS support.

Corrective Action: No action is required.

CTO821I SMS INTERFACE MODULE SUCCESSFULLY LOADED

Explanation: This information message indicates that a Control-O subsystem loaded the SMS interface module into storage.

The first Control-O subsystem to initialize itself loads the SMS interface.

Corrective Action: No action is required.

CTO822I SUBSYSTEM REGISTERED WITH SMS INTERFACE

Explanation: This information message indicates that the current Control-O subsystem registered itself with the SMS interface.

Control-O subsystems must be registered with the SMS interface to receive SMS events from it.

Corrective Action: No action is required.

CTO823I INITIALIZATION OF SMS SUPPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that SMS support for the current Control-O subsystem was installed successfully.

Control-O requires SMS ACS exit routines to trigger rules based on SMS events.

Corrective Action: No action is required.

CTO824W LOAD OF CAB ALLOCATOR MODULE FAILED

Explanation: Control-O could not load IOACAB.

Control-O needs the IOACAB program to install the SMS interface module.

The following system actions result:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Check the IOA load library.

CTO825W UNABLE TO REGISTER WITH SMS INTERFACE `rsn`

Explanation: Control-O could not register with the SMS interface during initialization.

The value of rsn may be one of the following:

TOO MANY SUBSYSTEMS - The SMS interface had already registered the maximum number of subsystems.
LOCK CANNOT BE OBTAINED - Control-O could not get the SMS interface lock that it needs for registration.

All of the following result:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Do one of the following:

If the value of rsn is TOO MANY SUBSYSTEMS, shut down a different Control-O monitor and restart the current one.
If the value of rsn is LOCK CANNOT BE OBTAINED, restart the current Control-O monitor.

If the problem persists, call your INCONTROL administrator.

CTO826W LOAD OF SMS INTERFACE FAILED: `rsn`

Explanation: Control-O could not load the SMS interface module.

In this message, rsn may be one of the following:

LOAD TO PRIVATE REGION FAILED - Control-O could not load the SMS interface module into its own private region.
CSA GETMAIN FAILED - Control-O could not get the storage in the Common Service Area (CSA) that it needs for the SMS interface module.
LOAD TO CSA FAILED - Control-O could not load the SMS interface module into the CSA.

The following system actions result:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Do one of the following:

If the value of rsn is LOAD TO PRIVATE REGION FAILED, check earlier messages to determine the cause of failure. The following are possible causes:
The region allocated for Control-O is too small.
The CTOACS module is not in the Control-O STEPLLIB library.
If the value of rsn is CSA GETMAIN FAILED, make sure that at least 8KB are allocated for the CSA and restart Control-O.
If the value of rsn is LOAD TO CSA FAILED, check earlier messages to determine the cause of failure.

CTO827E INITIALIZATION OF SMS SUPPORT FAILED

Explanation: An initialization error occurred when Control-O tried to install the SMS interface.

The following system actions result:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

CTO828I SUBSYSTEM ALREADY REGISTERED WITH SMS INTERFACE

Explanation: This information message indicates that the current Control-O subsystem did not register with the SMS interface because it was already registered.

This may be because a previous Control-O subsystem did not end correctly.

SMS interface initialization continues.

Corrective Action: No action is required.

CTO829E ALLOCATION OF CVT CUSTOMER ANCHORED BLOCK FAILED

Explanation:Control-O could not allocate a block of storage anchored to the z/OS communication vector table (CVT).

Even through the block of storage has not yet been allocated, Control-O could not allocate it.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action:Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

CTO82AW LOAD OF SMS INTERFACE MODULE FAILED: CSA GETMAIN FAILED

Explanation: During the Control-O monitor initialization, Control-O failed to GETMAIN the storage in E/CSA, which is required for the CTOACS module, and as a result the Control-O/DFSMS interface is disabled.

Corrective Action: Contact your systems programmer for assistance. Control-O requires about 1024 bytes. If the problem is not resolved, call BMC Customer Support for assistance and provide the step name indicated in the message.

CTO82BW LOAD OF SMS INTERFACE MODULE FAILED: LOAD TO CSA FAILED

Explanation: During the Control-O monitor initialization, Control-O failed to load the CTOACS module into E/CSA, and as a result the Control-O/DFSMS interface is disabled.

Corrective Action: Contact your systems programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

CTO82CW UNABLE TO REGISTER WITH SMS INTERFACE: NO PROPER ENTRY IN SSTABLE

Explanation:This warning message indicates that Control-O detected an internal problem. The Control-O/DFSMS interface is disabled.

Corrective Action: Contact BMC Customer Support.

CTO830I DEACTIVATION OF SMS SUPPORT STARTED

Explanation:This information message indicates that Control-O started deactivating an SMS interface.

Corrective Action: No action is required.

CTO831I SUBSYSTEM REGISTRATION REMOVED FROM SMS INTERFACE

Explanation: This information message indicates that Control-O removed its registration from the SMS interface.

When a Control-O subsystem is not registered with the SMS interface, it cannot receive SMS events from the SMS interface.

Corrective Action: No action is required.

CTO832I SMS INTERFACE MODULE REMOVED

Explanation: This information message indicates that Control-O removed the SMS interface module from storage.

The last Control-O subsystem removed unloads the SMS interface module.

Corrective Action: No action is required.

CTO833I DEACTIVATION OF SMS SUPPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that SMS support for the current Control-O subsystem was removed successfully.

Corrective Action: No action is required.

CTO834W DEACTIVATION OF SMS SUPPORT FAILED

Explanation: An error occurred when Control-O tried to remove the SMS interface module.

The following system actions result:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO835W SMS INTERFACE MODULE NOT INSTALLED

Explanation: Control-O could not find the SMS interface module to delete it.

Control-O detected an environment that supports the SMS interface. However, it could not find the SMS interface module that should have been installed during initialization.

The following system actions result:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO836W SUBSYSTEM NOT REMOVED FROM SMS INTERFACE: LOCK CANNOT BE OBTAINED

Explanation: Control-O could not remove its subsystem name from the SMS interface because Control-O could not get the SMS interface lock that it needs to remove its registration.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO837W SUBSYSTEM NOT REMOVED FROM SMS INTERFACE: SUBSYSTEM NOT FOUND

Explanation: Control-O could not remove its subsystem name from the SMS interface because the name of the current Control-O subsystem is not registered in the SMS interface.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO83AI INITIALIZATION OF AUTOOPERATOR SUPPORT STARTED

Explanation: This information message indicates that Control-O started initializing AutoOPERATOR support.

Corrective Action: No action is required.

CTO83BW UNABLE TO REGISTER WITH AUTOOPERATOR INTERFACE: LOCK CANNOT BE OBTAINED

Explanation: Control-O could not register with the AutoOPERATOR interface during initialization because Control-O could not obtain the AutoOPERATOR interface lock that it needs for registration.

The following system actions occur:

AUTOOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Restart the current Control-O monitor. If the problem persists, call your INCONTROL administrator.

CTO83CI AUTOOPERATOR INTERFACE MODULE SUCCESSFULLY LOADED

Explanation: This information message indicates that Control-O successfully loaded the AutoOPERATOR interface module.

Corrective Action: No action is required.

CTO83DW UNABLE TO REGISTER WITH AUTOOPERATOR INTERFACE: NO PROPER ENTRY IN SSTABLE

Explanation: Control-O could not register with the AutoOPERATOR interface during initialization because Control-O could not locate its entry in the INCONTROL internal subsystems table.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Restart the current Control-O monitor. If the problem persists, call your INCONTROL administrator.

CTO83EI SUBSYSTEM REGISTERED WITH AUTOOPERATOR INTERFACE

Explanation: This information message indicates that the current Control-O subsystem registered itself with the AutoOPERATOR interface.

Corrective Action: No action is required.

CTO83FI INITIALIZATION OF AUTOOPERATOR SUPPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that Control-O initialization of the AutoOPERATOR support ended successfully.

Corrective Action: No action is required.

CTO83GE INITIALIZATION OF AUTOOPERATOR SUPPORT FAILED

Explanation: An initialization error occurred when Control-O tried to initialize the AutoOPERATOR interface.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

CTO83HW LOAD OF AUTOOPERATOR INTERFACE MODULE FAILED: LOAD TO PRIVATE FAILED

Explanation: Control-O could not load the AutoOPERATOR interface module because it could not load the module into its own private region.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure. The following are possible causes:

The region allocated for Control-O is too small.
The CTOAAO module is not in the Control-O STEPLLIB library.

CTO83IW LOAD4 OF AUTOOPERATOR INTERFACE MODULE FAILED: CSA GETMAIN FAILED

Explanation: Control-O could not load the AutoOPERATOR interface module because it could not get the storage in the Common Service Area (CSA) that it needs for the AutoOPERATOR interface module.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure.

CTO83JW LOAD OF AUTOOPERATOR INTERFACE MODULE FAILED: LOAD TO CSA FAILED

Explanation: Control-O could not load the AutoOPERATOR interface module because it could not load the AutoOPERATOR interface module to the Common Service Area (CSA).

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure.

CTO83KI DEACTIVATION OF AUTOOPERATOR SUPPORT STARTED

Explanation: This information message indicates that Control-O started deactivating the AutoOPERATOR interface.

Corrective Action: No action is required.

CTO83LW AUTOOPERATOR INTERFACE MODULE NOT INSTALLED

Explanation: Control-O could not find the AutoOPERATOR interface module to delete it. Control-O detected an environment that supports the AutoOPERATOR interface. However, it could not find the AutoOPERATOR interface module that is usually installed during initialization.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO83MW SUBSYSTEM NOT REMOVED FROM AUTOOPERATOR INTERFACE: LOCK CANNOT BE OBTAINED

Explanation: Control-O could not remove its subsystem name from the AutoOPERATOR interface because Control-O could not get the AutoOPERATOR interface lock that it needs to remove its registration.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO83NW SUBSYSTEM NOT REMOVED FROM AUTOOPERATOR INTERFACE: NO PROPER ENTRY IN SSTABLE

Explanation: When Control-O tried to remove the AutoOPERATOR interface module it could not find its entry in the internal INCONTROL subsystem table.

Control-O termination continues.

Corrective Action: Check earlier messages to determine the cause of the error.

CTO83OI SUBSYSTEM REGISTRATION REMOVED FROM AUTOOPERATOR INTERFACE

Explanation: This information message indicates that Control-O unregistered the AutoOPERATOR interface.

Corrective Action: No action is required.

CTO83PI AUTOOPERATOR INTERFACE MODULE REMOVED

Explanation: This information message indicates that Control-O removed the AutoOPERATOR interface module from Common Service Area (CSA).

Corrective Action: No action is required.

CTO83QI DEACTIVATION OF AUTOOPERATOR SUPPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that the Control-O deactivation of the AutoOPERATOR support ended successfully.

Corrective Action: No action is required.

CTO83RW DEACTIVATION OF AUTOOPERATOR SUPPORT FAILED

Explanation: An error occurred when Control-O tried to remove the AutoOPERATOR interface module.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO83SI REQUESTS WILL BE ACCEPTED FROM AUTOOPERATOR SUBSYSTEM `subsystem-name`

Explanation: This information message indicates that Control-O will accept requests from the specified AutoOPERATOR subsystem.

Corrective Action: No action is required.

CTO840E INITIALIZATION OF SUBSYSTEM TABLE FAILED: LOAD OF CTOSSI FAILED

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems if they were not already defined. During the definition process, the Control-O interface was not successfully loaded.

Control-O terminates with a return code of 8.

Corrective Action:Ensure that the Control-O STC is using the correct STEPLIB library, then restart Control-O.

CTO841I MAINVIEW INTERFACE MODULE SUCCESSFULLY LOADED

Explanation: This information message indicates that a Control-O subsystem loaded the MAINVIEW interface module into storage.

The first Control-O subsystem to initialize itself loads the MAINVIEW interface.

Corrective Action: No action is required.

CTO842I SUBSYSTEM REGISTERED WITH MAINVIEW INTERFACE

Explanation: This information message indicates that the current Control-O subsystem registered itself with the MAINVIEW interface.

Control-O subsystems must be registered with the MAINVIEW interface to receive MAINVIEW events from it.

Corrective Action: No action is required.

CTO843I INITIALIZATION OF MAINVIEW SUPPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that MAINVIEW support for the current Control-O subsystem was installed successfully.

Control-O requires MAINVIEW exit routines to trigger rules based on MAINVIEW events.

Corrective Action: No action is required.

CTO844W LOAD OF CAB ALLOCATOR MODULE FAILED

Explanation: Control-O could not load IOACAB.

Control-O needs the IOACAB program to install the MAINVIEW interface module.

The following system actions result:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check the IOA load library.

CTO845W UNABLE TO REGISTER WITH MAINVIEW INTERFACE: LOCK CANNOT BE OBTAINED

Explanation: Control-O could not register with the MAINVIEW interface during initialization because Control-O could not get the MAINVIEW interface lock that it needs for registration.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Restart the current Control-O monitor. If the problem persists, call your INCONTROL administrator.

CTO846W LOAD OF MAINVIEW INTERFACE FAILED: LOAD TO PRIVATE FAILED

Explanation: Control-O could not load the MAINVIEW interface module because Control-O could not load the MAINVIEW interface module into its own private region.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check earlier messages to determine the cause of failure. The following are possible causes:

The region allocated for Control-O is too small.
The CTOACS module is not in the Control-O STEPLLIB library.

CTO847E INITIALIZATION OF MAINVIEW SUPPORT FAILED

Explanation: An initialization error occurred when Control-O tried to install the MAINVIEW interface.

The following system actions result:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

CTO848I SUBSYSTEM ALREADY REGISTERED WITH MAINVIEW INTERFACE

Explanation: This information message indicates that the current Control-O subsystem did not register with the MAINVIEW interface because it was already registered.

A possible cause is that a previous Control-O subsystem did not end correctly.

MAINVIEW interface initialization continues.

Corrective Action: No action is required.

CTO84AI INITIALIZATION OF MAINVIEW SUPPORT STARTED

Explanation: This information message indicates that Control-O started initializing MAINVIEW support.

Corrective Action: No action is required.

CTO84BI DEACTIVATION OF MAINVIEW SUPPORT STARTED

Explanation: This information message indicates that Control-O started deactivating an MAINVIEW interface.

Corrective Action: No action is required.

CTO84CI SUBSYSTEM REGISTRATION REMOVED FROM MAINVIEW INTERFACE

Explanation: This information message indicates that Control-O removed its registration from the MAINVIEW interface.

When a Control-O subsystem is not registered with the MAINVIEW interface, it cannot receive MAINVIEW events from the MAINVIEW interface.

Corrective Action: No action is required.

CTO84DI MAINVIEW INTERFACE MODULE REMOVED

Explanation: This information message indicates that Control-O removed the MAINVIEW interface module from storage.

The last Control-O subsystem removed unloads the MAINVIEW interface module.

Corrective Action: No action is required.

CTO84EI DEACTIVATION OF MAINVIEW SUPPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that MAINVIEW support for the current Control-O subsystem was removed successfully.

Corrective Action: No action is required.

CTO84FW DEACTIVATION OF MAINVIEW SUPPORT FAILED

Explanation: An error occurred when Control-O tried to remove the MAINVIEW interface module.

The following system actions result:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO84GW MAINVIEW INTERFACE MODULE NOT INSTALLED

Explanation: Control-O could not find the MAINVIEW interface module to delete it.

Control-O detected an environment that supports the MAINVIEW interface. However, it could not find the MAINVIEW interface module that should have been installed during initialization.

The following system actions result:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO84HW SUBSYSTEM NOT REMOVED FROM MAINVIEW INTERFACE: `rsn`

Explanation: Control-O could not remove its subsystem name from the MAINVIEW interface.

Possible values of rsn are:

SUBSYSTEM NOT FOUND - The name of the current Control-O subsystem is not registered in the MAINVIEW interface.
LOCK CANNOT BE OBTAINED - Control-O could not get the MAINVIEW interface lock that it needs to remove its registration.

The following system actions result:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

CTO84IE INITIALIZATION OF SUBSYSTEM TABLE FAILED: CSA GETMAIN FAILED

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems if they were not already defined. During the definition process, the Control-O failed to GETMAIN in CSA.

Control-O terminates with a return code of 8.

Corrective Action:Ensure that Control-O has sufficient storage. Control-O requires about 50K in CSA. It might be necessary to restart the system.

CTO84JE INITIALIZATION OF SUBSYSTEM TABLE FAILED: LOCK CANNOT BE OBTAINED

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems if they were not already defined. During the definition process, the Control-O failed to obtain LOCK.

Control-O terminates with a return code of 8.

Corrective Action:The error might be a Control-O internal error. Try to start Control-O again. If the same error occurs, contact BMC Customer Support.

CTO84KE INITIALIZATION OF SUBSYSTEM TABLE FAILED: TOO MANY SUBSYSTEMS

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems, if they were not defined previously. During the definition process, the Control-O failed to define the subsystem, because the number of Control-O and Control-M Event Manager (CMEM) environments defined on the LPAR exceeded the maximum of 20.

Control-O terminates with a return code of 8.

Corrective Action:Stop all active Control-O and CMEM monitors, run the IOACABPR (Emergency CAB Control Block Disconnect) utility, and then restart the Control-O and CMEM monitors.

CTO84LW UNABLE TO REGISTER WITH MAINVIEW INTERFACE: NO PROPER ENTRY IN SSTABLE

Explanation: Control-O could not register with the MAINVIEW interface during initialization because Control-O could not locate its entry in the INCONTROL internal subsystems table.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Restart the current Control-O monitor. If the problem persists, call your INCONTROL administrator.

CTO84MW LOAD OF MAINVIEW INTERFACE FAILED: CSA GETMAIN FAILED

Explanation: Control-O could not load the MAINVIEW interface module because Control-O could not get the storage in the Common Service Area (CSA) that it needs for the MAINVIEW interface module.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Make sure that at least 8KB are allocated for the CSA and restart Control-O.

CTO84NW LOAD OF MAINVIEW INTERFACE FAILED: LOAD TO CSA FAILED

Explanation: Control-O could not load the MAINVIEW interface module because Control-O could not load the MAINVIEW interface module into the Common Service Area (CSA).

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check earlier messages to determine the cause of failure.

CTO84OW SUBSYSTEM NOT REMOVED FROM MAINVIEW INTERFACE: NO PROPER ENTRY IN SSTABL

Explanation: When Control-O tried to remove the MAINVIEW interface module it could not find its entry in the internal INCONTROL subsystem table.

Control-O termination continues.

Corrective Action: Check earlier messages to determine the cause of failure.

CTO8A0I Control-O IS NOT ACTIVE. NO RULES LOADED

Explanation: This information message indicates that the Rule Status screen is empty because the Control-O subsystem is not active. When the Control-O subsystem in inactive, no rules are loaded.

No records are shown.

Corrective Action: Check why the subsystem is inactive.

CTO8A1E SUBSYSTEM FAILURE - REASON `rsn`

Explanation: An error in the subsystem was found while trying to access the subsystem tables. The value of rsn indicates what happened.

Possible values of rsn are:

08 - Subsystem name incorrectly defined
16 - GETMAIN failed
24 - Load of executor failed
28 - Invalid parms

The program is terminated.

Corrective Action: Notify your INCONTROL administrator.

CTO8A2I STATUS SCREEN REBUILT DUE TO RELOADING OF RULES

Explanation: This information message indicates that, after pressing a key that returns control to the program (PFKey, Enter, and the like.), the list of rules was rebuilt according to the information currently residing in the subsystem data lists.

After control returns to the Rule Status screen program (CTOTARF), the program checks to see if it is necessary to rebuild the Active Rule List. If rules have been ordered since the last time control was returned, the rule table is reloaded, and the screen is rebuilt according to the new information.

The Rule Status screen is rebuilt.

Corrective Action: No action is required.

CTO8A3E "TO" VALUE MUST BE EQUAL/GREATER THAN "FROM" VALUE, OR BLANK

Explanation: A FROM value larger than a TO value was specified. In the Show Window, you can specify ranges of values for filtering the displayed Active Rule List. The TO value must be larger than the FROM value, or either or both values must be blank. A blank in the FROM field indicates the minimum valid for that field. A blank in the TO field indicates the maximum for that field.

The Show Window is not exited until a valid range is defined.

Corrective Action: Specify a valid range in the TO and FROM fields.

CTO8A4E MAXIMUM VALUE OF COUNTER EXCEEDED

Explanation: An ACTIVATION# range greater than, or equal to, 231 was entered in the Show Window. The maximum value allowed for this counter is 1 less than 231.

The Show Window is not exited until a valid range is entered.

Corrective Action: Set the ACTIVATION# range to a value less than 231.

CTO8A5I NO INFORMATION AVAILABLE

Explanation: This information message indicates that an option was specified for a rule which no longer exists in the Active Rule List. An option was requested for a rule appearing in the screen, but the rule was deleted, or the rule table was reloaded, before the request was processed.

The option is not performed.

Corrective Action: Reorder the rule if necessary.

CTO8ABE CANNOT PERFORM "HOLD" OPTION WHEN RULE IS EXECUTING

Explanation: A HOLD request was specified for a rule with status EXECUTING. A rule with status EXECUTING cannot be HELD. This status indicates that the rule is executing, and waiting for the completion of an event that is external to Control-O, such as, a TSO or KSL statement in Wait mode, or a DO COMMAND statement in Command-Response mode.

The option is not performed.

Corrective Action: Wait until the rule no longer has a status of EXECUTING before specifying the HOLD request.

CTO8ACI RULE `ruleName` TABLE `tableName` LIBRARY `lib` action

Explanation: This information message indicates that the action specified in the message has been performed on rule ruleName which is found in table tableName of library lib.

Corrective Action: No action is required.

CTO8ADI RULE `ruleName` TABLE `tableName` action

Explanation: This information message indicates that the action specified in the message was performed on rule ruleName, which is found in table tableName. A longer message (CTO8ACI) is written to the IOA Log. Message CTO8ACI also contains the Rule library name.

Corrective Action: No action is required.

CTO8AEE RULE NOT SUSPENDED. 'RESUME' REQUEST IGNORED

Explanation: The line command R (RESUME) was entered in the Rule Status screen for a rule that is not in SUSPEND mode. This is invalid because only a suspended rule can be resumed. A rule becomes suspended when its threshold is reached.

The RESUME request is not performed.

Corrective Action: No action is required.

CTO8AFE "CANCEL" OPTION SUPPORTED ONLY WHEN RULE IS EXECUTING

Explanation: The user attempted to cancel a rule whose present status is not EXECUTING. CANCEL is supported only for rules in status EXECUTING.

The line command is ignored.

Corrective Action: No action is required.

CTO8AGE CTOTARF ABENDED `abend-rsn`, ESTAE IS TAKEN

Explanation: Program CTOTARF has abended with system abend code abend reason rsn.

Screen Rule Status terminates.

Corrective Action: Retry entering screen Rule Status again; if the problem persists, take an SVC DUMP of the Control-O monitor and contact BMC Customer Support.

CTO8B9E MONITOR REQUEST BUFFER IS FULL, TRY AGAIN LATER

Explanation: An S (Show), X (Exclude) or R (Reset) line command was specified, but cannot be executed because the Control-O monitor request buffer is full. Line commands are stored in the Control-O monitor request buffer.

The line command is not executed.

Corrective Action: Reattempt the line command after a few seconds. If Control-O is not active, start the Control-O monitor so that it may process the previous requests.

CTO8BAE LEFT AND RIGHT ARE INACTIVE WHEN WRAP IS ON

Explanation: While viewing the Control-O Message Statistics screen in wrap mode, the LEFT (PF10 or PF22) or RIGHT (PF11 or PF23) commands were issued. The LEFT and RIGHT commands are not supported when the text is wrapped, because all the information is already displayed.

The display remains unchanged.

Corrective Action: No action is required.

CTO8BBE STATISTICS FILE IN USE, TRY AGAIN LATER

Explanation: The Control-O Message Statistics screen cannot currently be viewed or refreshed because the Statistics file is in use. Possible causes are:

The indices of the Statistics file are currently being updated by the Control-O monitor.
The Statistics file is currently being reformatted.

Corrective Action: Try again later.

CTO8BCE ERROR READING RECORD 0, UPDATE NOT PERFORMED

Explanation: The Control-O Statistics file cannot be updated due to an internal error.

The Statistics file is not updated.

Corrective Action: Contact BMC Customer Support.

CTO8BDE ERROR WRITING RECORD 0, UPDATE NOT PERFORMED

Explanation: The Control-O Statistics file cannot be updated due to an internal error.

The Statistics file is not updated.

Corrective Action: Contact BMC Customer Support.

CTO8BES ERROR OPENING STATISTICS FILE

Explanation: An error occurred while attempting to allocate or open the Control-O Statistics file. Possible causes are:

An incorrect prefix was defined for the Control-O Statistics file in CTOPARM (the STTPREF parameter).
The Statistics file was deleted, or has an incorrect format
No Statistics file was defined or formatted for this CPU.

The Message Statistics screen is not displayed.

Corrective Action: Do one of the following:

Define the prefix correctly in CTOPARM. For details, see the section on operational parameters in the Control-M chapter of the INCONTROL for z/OS Installation Guide.
Allocate and format a Control-O Statistics file for the CPU. For details, see the section that describes how to allocate and format a Control-O statistics files in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

Contact BMC Customer Support.

CTO8BFW RULES BEING LOADED, HIT ENTER TO UPDATE SCREEN

Explanation: This warning message indicates that, after pressing a key that returns control to the program, such as PFKey or ENTER, the list of rules is rebuilt, and therefore the screen must be refreshed to update the list.

Corrective Action: Press ENTER to update the screen. When the update is completed, the CTO8A2I message is displayed. It is advisable to press PF3 and re-enter 'OS' to display the updated rule list from the beginning.

CTO8C0E CTMMEM ERROR WHILE READING MEMBER `memName`, RC=`rc`

Explanation: The Automation Options main program failed while trying to access the memName menu definition member in the IOA PARMCMD library.

The requested menu is not displayed.

Corrective Action: Check the return code in the following list to determine the reason for the failure. Correct the problem and try again to activate the Automation Options facility.

Return Code	Explanation
8	Insufficient memory to continue; region is too small, or member is too large.
12	The member was not found in the library.
16	The specified data set is not a library.
20	The specified data set is not in fixed format.
24	The logical record length is not 80.
28	The specified data set is in use.
32	Internal error - the type is in the abend code field.
36	The specified data set was not found in the catalog.
40	Dynamic allocation failed.
44	Invalid request to CTMMEM.
48	Maximum lines or directory entries exceeded.
52	Error when opening or processing directory.
56	STAE intercepted an abend.
68	Format parameter is inappropriate for the library.

CTO8C1E GETMAIN ERROR WHILE READING MEMBER `memName`, RC=`rc`

Explanation: The Automation Options Program (AOP) failed to obtain storage. The Automation Options main program failed to obtain main storage while processing the memName menu definition member in the IOA PARMCMD library.

The requested menu is not displayed.

Corrective Action: If other options in the IOA Online Facility were active when this message was displayed, exit these options and try again. If the problem persists, increase the region size.

CTO8C2E INVALID CARD NUMBER `stmtNum`

Explanation: The Automation Options Program (AOP) detected an invalid menu statement. The stmtNum menu statement in the menu definition member for the requested menu does not follow AOP rules for syntax and order.

The menu is not displayed.

Corrective Action: Correct the error in the menu definition member. For more information on correct syntax for menu member definition, see the description of customization of automation options in the INCONTROL for z/OS Administrator Guide.

CTO8C3E EXCESSIVE CONTINUATION IN CARD NUMBER `stmtNum`

Explanation: The Automation Options Program (AOP) detected an excessive number of continuation statements. The menu statement number stmtNum surpassed the allowed number of continuation statements.

The menu is not displayed.

CTO8C4E OPTION IN CARD NUMBER `stmtNum` IS DUPLICATE

Explanation: The Automation Options Program (AOP) detected a duplicate option name in the menu definition. No two options in an AOP menu can share the same name.

The menu is not displayed.

Corrective Action: Correct the error in the menu definition member.

CTO8C5E "DESC" IS MISSING, DUPLICATE OR OUT OF SEQUENCE

Explanation: The Automation Options Program (AOP) detected an invalid DESC statement. A DESC (Description) statement must be specified immediately after each option statement. This message indicates that a DESC statement is either missing, or does not conform to AOP menu definition syntax.

The menu is not displayed.

Corrective Action: Correct the error in the menu definition member, and restart the action. For more information on correct syntax for menu member definition, see the description of customization of automation options in the INCONTROL for z/OS Administrator Guide.

CTO8C6E "LINECMD" IS MISSING, DUPLICATE OR OUT OF SEQUENCE

Explanation: The Automation Options Program (AOP) detected an invalid or missing LINECMD statement. The LINECMD statement does not follow AOP rules.

The menu is not displayed.

CTO8C7E "PROGRAM" IS MISSING, DUPLICATE OR OUT OF SEQUENCE

Explanation: The Automation Options Program (AOP) detected an invalid or missing PROGRAM statement. The PROGRAM statement specifies the program to be invoked when an option is selected. The program for the requested option does not follow AOP rules.

The menu is not displayed.

CTO8C8E TOO MANY "PROMPT" CARDS, OR "PROMPT" CARDS OUT OF SEQUENCE

Explanation: The Automation Options Program (AOP) detected too many PROMPT statements, or PROMPT statements coded out of order. Not more than 14 PARM statements in a row can be specified.

The menu is not displayed.

CTO8C9E "RETURNS" IS DUPLICATE, OR OUT OF SEQUENCE

Explanation: The Automation Options Program (AOP) detected an invalid RETURNS statement. Either the RETURNS statement is listed twice in the menu definition or the RETURNS statement is not in the position dictated by AOP rules.

The menu is not displayed.

CTO8CAE "FORMAT" IS DUPLICATE, OR OUT OF SEQUENCE

Explanation: The Automation Options Program (AOP) detected invalid FORMAT statement. Either the FORMAT statement is listed twice in the menu definition or the FORMAT statement is not in the position dictated by AOP rules.

The menu is not displayed.

CTO8CBE "OPTLIST" IS DUPLICATE, OR OUT OF SEQUENCE

Explanation: The Automation Options Program (AOP) detected invalid OPTLIST statement. Either the OPTLIST statement is listed twice in the menu definition or the OPTLIST statement is not in the position dictated by AOP rules.

The menu is not displayed.

CTO8CCE INVALID ACTION FOR OPTION

Explanation: The program called by the specified Automation Option was invoked with an invalid action. If the option is supported by a user-written Client Program, that program is probably in error. Otherwise, this is an internal error.

Valid actions are:

GETLINES
ACTCMD
END

The requested option is not performed.

Corrective Action: If the problem is in a user-written Client Program, correct the program. Otherwise, contact BMC Customer Support.

CTO8CDE INVALID LDB IN PROGRAM `pgm`

Explanation: The pgm Automation Options Program was passed an invalid LDB control block. If the pgm program is a user-written Client Program, it is probably in error. Otherwise, this is an internal error.

The selected option is not performed.

Corrective Action: If the problem is in a user-written Client Program, then correct the program. Otherwise, contact BMC Customer Support.

CTO8CEE INVALID OPTION

Explanation: The requested option was not defined as a valid LINECMD (line command) in the menu definition member.

The invalid line command is ignored.

Corrective Action: Specify a valid line command.

CTO8CFE GETMAIN ERROR IN PROGRAM `pgm`

Explanation: The pgm Automation Option program failed to obtain main storage to process its request. A return code is returned by GETMAIN.

The pgm program is terminated.

Corrective Action: Increase the region size.

CTO8D0E PROGRAM `pgm` NOT FOUND

Explanation: The pgm Client Program could not be found. The program specified in the menu definition for this option could not be located by means of STEPLIB or DALOAD.

The pgm program is not invoked. The main menu remains displayed on the screen.

Corrective Action: Correct the error and restart the action.

CTO8D1E ERROR `rc` IN OPTION

Explanation: The Client Program ended with an error. The return code of the Client Program (rc) is included in this message.

Corrective Action: If the name of the failed program begins with CTO or IOA, contact BMC Customer Support. If not, contact your system programmer.

CTO8D2E PROGRAM `pgm` MUST RUN UNDER ISPF

Explanation: Client Program pgm can only run under ISPF. A selection was made to a program that must run under ISPF. ISPFENV was specified. However, the call was not made under ISPF.

The pgm program is not invoked.

Corrective Action: Correct the error, and restart the action.

CTO8D3E TSO CMD ERROR, R15=`val`, RET-CODE=`rc`, RS-CODE=`rsn`, AB-CODE=`abCode`

Explanation: A TSO-command Client Program ended with an error. TSOCP was specified.

The variables in this message are:

val - the value in general register 15
rc - the program return code
rsn - the program reason code
abCode - the program abend code

Corrective Action: For information regarding the error, refer to TSO manuals, and take appropriate corrective action.

CTO8D5E LOAD OF EXIT(S) `exitNames` FAILED. SECURITY CHECK BYPASSED

Explanation: The security exits specified in this message could not be loaded. These security exits were not found in the STEPLIB DD statement.

No security checks are performed.

Corrective Action: Check why security exits are not found in the STEPLIB DD statement.

CTO8D6E ACCESS DENIED BY SECURITY EXIT

Explanation: The selected Automation Option cannot be performed because security exit CTOSE03 detected a security violation.

The option is not performed.

Corrective Action: Check the security definitions with your IOA Security Administrator.

CTO8D7E AUTOEDIT ERROR, R15=`rc`, REASON- CODE=`rsn`

Explanation: An AutoEdit error was encountered in the PARM statement of the menu definition member for the selected option.

The option is not performed.

Corrective Action: For a description of rc and rsn, see the following table. Correct the PARM statement accordingly.

Return 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 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, and 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.
	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.

CTO8D8E INVALID PARAMETER. ONLY SINGLE PROMPT ALLOWED

Explanation: A TSOCP program was defined with multiple PROMPT statements in an Automation Options menu definition. TSOCP programs cannot be invoked with more than one prompt statement.

The option is not performed.

Corrective Action: Correct the menu definition for this option. Define either a single PROMPT statement, or use a PARM statement to build the single parameter for the TSOCP program.

CTO8D9E PROG=`pgm` ABEND CODE=`Scode/Ucode` OFFSET=`offset` R15=`val`

Explanation: An Automation Options Client Program abended. This message displays the abend information.

The variables in this message are:

pgm - the program name
Scode - the system code
Ucode - the user code
offset - the offset
r15 - the value in general register 15

The option that calls this Client Program cannot be selected.

Corrective Action: If the problem is in a user-written Client Program, correct the program. Otherwise, contact BMC Customer Support.

CTO8DAE INVALID APF ENVIRONMENT FOR OPTION <`option` >

Explanation: The user has no APF authorization for the selected Automation Option (where < option > is the specific option selected by the user). The LOAD library used by this option (DD name DALOAD) should be APF authorized.

The option is not performed.

Corrective Action: Check the APF authorization of the DALOAD library.

CTO8DBE CONTROL-O MUST BE ACTIVE FOR OPTION <`option` >

Explanation: The user selected an Automation Option (where < option > is the specific option selected by the user) requiring the Control-O monitor but the monitor is inactive. The selected Automation Option needs services provided by the Control-O monitor.

The option is not performed.

Corrective Action: Verify that the Control-O monitor is active before selecting this option.

CTO8DCE INVALID PARAMETER PASSED TO OPTION <`option` >

Explanation: Automation Option (where < option > is the specific option selected by the user) was invoked with invalid parameters.

The option is not performed.

Corrective Action: Check and correct the PARM and PROMPT parameters specified in the menu definition for this option.

CTO8DEE COSMOS WAS NOT INSTALLED - CHECK CTOPARM

Explanation: The user tried to enter screen OC, but COSMOS was not installed. The definition in CTOPARM is COSMOS=N

The system rejects the request.

Corrective Action: Record the message code and message. Contact your INCONTROL administrator to check if Control-O/COSMOS is properly installed.

CTO8E0E INTERNAL ERROR: ONLY ACTIONS "GETLINES" OR "END" ARE SUPPORTED

Explanation: The CTOTGES Automation Options program was invoked with an invalid action. This message indicates an internal error.

The option is not performed.

Corrective Action: Contact BMC Customer Support.

CTO8E2E INVALID TIMING PARAMETER. SPECIFY Y OR N

Explanation: An incorrect value was specified for the TIMING parameter in the ENQINFO option. Valid values are Y (Yes) and N (No).

The option is not performed.

Corrective Action: Specify a valid value for the TIMING parameter.

CTO8E6E CONTROL-O MUST BE ACTIVE FOR TIMING=Y

Explanation: Value Y (Yes) was specified for the TIMING parameter in the ENQINFO option when the Control-O monitor was inactive. When the ENQINFO option is specified with TIMING set to Y, it needs the services of the Control-O monitor.

The option is not performed.

Corrective Action: Verify that the Control-O monitor is active before using this option.

CTO8E9I {CONTROL-O | CTMCMEM} LOADER TASK STARTED

Explanation: In Control-O, this information message indicates that the task responsible for loading rules and Global variables has begun.

In Control-M, this information message indicates that the task responsible for loading CMEM rules has begun.

Corrective Action: No action is required.

CTO8EAE CTORFR DETECTED AN INVALID CHAIN STRUCTURE

Explanation: Control-O detected invalid structure for internal control blocks.

This message indicates an internal error.

The Control-O monitor terminates.

Corrective Action: Contact BMC Customer Support.

CTO8EBI {CONTROL-O | CTMCMEM} LOADER TASK ENDED

Explanation: In Control-O, this information message indicates that the task responsible for loading rules and Global variables has terminated successfully.

In Control-M, this information message indicates that the task responsible for loading CMEM rules has terminated successfully.

Corrective Action: No action is required.

CTO8ECS ERROR ATTACHING CTOCPS - GLOBAL VARIABLES COMPRESSION FEATURE INACTIVE

Explanation: The CTOCPS program, which is responsible for automatic compression of the Global AutoEdit library, could not be loaded.

The Automatic Compression Facility is not activated.

Corrective Action: Check associated MVS messages for the reason and for possible corrective actions, such as wrong load library concatenation, or region too small).

CTO8EDS GLOBAL VARIABLES LIBRARY IS NOT IN EXPECTED FORMAT

Explanation: The CTOCPS program detected an error while verifying that the previous LOADGLOBAL/WRITEGLOBAL action ended successfully.

When automatic compression is activated, the $$COMPST member in the Global AutoEdit library is checked to see if the previous compress ended successfully. An error was detected by the program that performs the check on the $$COMPST member. This message is preceded by messages that describe the cause of the error.

The LOADGLOBAL/WRITEGLOBAL operation that prompted the verification process is terminated.

Corrective Action: Check preceding messages for the cause of the error and possible corrective actions.

CTO8EES ERROR COMPRESSING GLOBAL VARIABLES LIBRARY

Explanation: Compression of the Global AutoEdit library failed.

This message is preceded by messages describing the cause of the error.

The compression process is terminated.

Corrective Action: Check preceding messages for the cause of the error and possible corrective actions.

CTO8EFS `cmd` COMMAND FAILED

Explanation: The CTORFR program detected an error while executing the cmd command.

This message can result from problems while loading variables or tables, or while writing variables to the Global AutoEdit library. This message is preceded by messages describing the cause of the error.

The command specified in this message is terminated.

Corrective Action: Check preceding messages for the cause of the error and possible corrective actions.

CTO8F1S CTOTSRV INTERNAL ERROR - `rsn`

Explanation: An internal error was detected when Option SERVERS was activated.

The option is not performed.

Corrective Action: Contact BMC Customer Support.

CTO8F3E SERVER `srvr` IS ALREADY `status`

Explanation: The user tried to change the server status, by means of a line command, but the server already had the requested status.

The line command is ignored.

Corrective Action: No action is required.

CTO8F4E IMMEDIATE SERVER CANNOT BE STARTED

Explanation: The user tried to start an Immediate server by means of a line command in the Option Servers screen. An Immediate server is started by Control-O only when a DO KSL/TSO/SHELL statement with IMMEDIATE Y is performed.

The line command is ignored.

Corrective Action: No action is required.

CTO8F5E SERVER `svr` IS NOT IN USE, CANCEL IGNORED

Explanation: Line command C (CANCEL) was specified for a server that is not active.

The line command is ignored.

Corrective Action: No action is required.

CTO8F7I SERVER `svr cmd` WAS REQUESTED

Explanation: This information message indicates that command cmd was specified for server svr.

Control-O performs the specified command.

Corrective Action: No action is required.

CTO8F8E INVALID SERVER TYPE - ONLY S,G,I ARE SUPPORTED

Explanation: An invalid server type was specified in the server selection window. Valid options are S (Special), G (General), I (Immediate), and blank (All).

The Server Selection Window remains displayed.

Corrective Action: Specify a valid server type.

CTO8F9W NO SERVERS MATCH THE SELECTION CRITERIA

Explanation: Option SERVERS was requested with selection criteria that did not match any server presently defined to Control-O.

The Server Selection Window remains displayed.

Corrective Action: Change the selection criteria if necessary.

CTO8G1W NO GLOBAL VARIABLE POOLS FOUND

Explanation: The user specified a Global variable pool name or mask that did not match any of the existing Global variable pools.

The Option GLOBALS selection window is redisplayed.

Corrective Action: Change the selection criteria if necessary.

CTO8G3W FUNCTION NOT SUPPORTED

Explanation: The requested function that was specified online is not supported.

Corrective Action: Check the validity of the value specified in the option field.

CTO8G8E INTERNAL ERROR TYPE REQUEST=`requestInfo`

Explanation: Option GLOBALS encountered an internal error.

The GLOBALS display is terminated.

Corrective Action: Contact BMC Customer Support.

CTO8GCE NO MATCHING GLOBAL VARIABLE POOL FOUND

Explanation: Option GLOBALS was selected with selection criteria not matched by any Global Variable Pool.

The GLOBALS selection window remains displayed.

Corrective Action: Change the selection criteria if necessary.

Messages CTO900 through CTO9xx

This group includes messages for the Control-O product.

CTO910W PARAMETER NUMCONS IN CTOPARM FORCED TO '0', DUE TO OPERATING SYSTEM RESTRICTIONS

Explanation: Control-O changes the NUMCONS parameter, in the CTOPARM member, to zero.

The Control-O startup process continues.

Corrective Action: If the CTOPARM member is only used for Control-O set NUMCONS=0 in the CTOPARM member.

CTO912S ERROR IN CONTROL-`x` INSTALLATION PARAMETERS - INVALID DAYTIME

Explanation: Invalid format of Control- x Installation DAYTIME parameter. DAYTIME is the start time of the Control-M work day in your installation. Valid formats are +hhmm or -hhmm.

For more details see the section that describes installation parameters in the chapter for the appropriate products in the INCONTROL for z/OS Installation Guide.

The requested function terminates.

Corrective Action: Call your system programmer to correct the DAYTIME parameter in the CT xPARM member.

CTO913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a print file failed.

Possible causes are:

The DD statement SYSPRINT is missing.
The data set described by DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

CTO915S ERROR IN CONTROL-O INSTALLATION PARAMETERS

Explanation: During the startup of the Control-O monitor, an error is encountered in the Control-O installation parameters. The nature of the error is detailed in an accompanying message or messages.

The Control-O monitor terminates.

Corrective Action: Contact your INCONTROL administrator.

CTO916S ERROR OCCURRED DURING CONTROL-O INITIALIZATION

Explanation: During the startup of the Control-O monitor, an error occurred during Control-O initialization. The nature of the error is detailed in an accompanying message or messages.

The Control-O monitor terminates.

Corrective Action: Contact your INCONTROL administrator.

CTO917W PARAMETER JCMDSSN SHOULD DIFFER FROM SSNAME; REPLACED WITH BLANKS

Explanation: During the startup of the Control-O monitor, the values of the JCMDSSN and the SSNAME parameters were found to be identical.

The JCMDSSN parameter identifies the JES2 command suppression subsystem name, and is in the CTOPARM member.

The SSNAME parameter identifies the IOA subsystem, and is in the IOAPARM parameter.

The value of the JCMDSSN parameter is replaced with blanks. Monitor startup continues.

Corrective Action: Contact your INCONTROL administrator.

CTO918S INSUFFICIENT MEMORY TO RUN CONTROL-O. COMPONENT: `component` LENGTH=`getmain_length`

Explanation: The Control-O component could not be initialized because the getmain in length getmain_length failed.

The specified monitor will shut down.

Corrective Action: Increase the REGION size of the specified monitor.

CTO919E `monitor_type name` FROM VERSION `version` IS USING SUBSYSTEM `subsys`. BRING IT DOWN BEFORE STARTING THIS MONITOR

Explanation: During Control-O or CMEM monitor initialization, it was discovered that the existing subsys subsystem is already activated for the version version of the monitor. The active monitor is shut down.

Corrective Action: Determine which monitor (the active one or the newly started) should use the subsystem and act accordingly.

CTO91CW RQC ELEMENTS NUMBER CANNOT BE CHANGED WHILE MONITOR SWITCHING. VALUE `xxxx` USED.

Explanation:The RQC# parameter in the CTOPARM member was changed, and a new Control-O/CMEM was started over a running one. The new RQC# value is not used.

xxxx - the old RQC# from the previous Control-O execution

Corrective Action:Shut down Control-O/CMEM.

After the started task ends, start a new Control-O/CMEM. Verify that the new RQC# is being used by examining the started task job log.

Messages CTOC00 through CTOCxx

This group includes messages for the Control-O product.

CTOC02E INTERNAL ERROR, RC=`rc`. TD MESSAGE INTERCEPTION STOPPED

Explanation: The Control-O CICS Interface cannot intercept new CICS Transient Data (TD) messages due to a Control-O CICS Interface internal error.

Transient Data message interception is stopped.

Corrective Action: Contact BMC Customer Support.

CTOC04I CTO SUBSYSTEM `subsys` INACTIVE. TD MESSAGES NOT PROCESSED

Explanation: This information message indicates that the Control-O CICS Interface was activated but cannot process Transient Data (TD) messages because the Control-O monitor is not active. The Control-O CICS Interface can automate Transient Data messages only when the Control-O monitor is active.

Processing of Transient Data messages is discontinued. It will be resumed when Control-O becomes active.

Corrective Action: Start the Control-O monitor.

CTOC05I CTO SUBSYSTEM `subsys` IS NOW ACTIVE. TD MESSAGES ARE PROCESSED

Explanation: This informative message indicates that the processing of Transient Data (TD) messages resumes because the Control-O monitor has been activated. The Control-O CICS Interface can automate Transient Data messages only when the Control-O monitor is active.

Processing of Transient Data messages resumes.

Corrective Action: No action is required.

CTOC06E INTERNAL ABEND= (`systemCode,userCode`)

Explanation: The Control-O CICS Interface detected an internal abend, where systemCode is the system abend code, and userCode is the user abend code. This is the header message for messages CTOC07I, CTOC08I, CTOC09I, and CTOC10I which provide information about the abend.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface, and processing of the current Transient Data (TD) message is stopped. Subsequent Transient Data messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC07E CICS FUNCTION `func` RESOURCE `res` ERROR RESPONSE `resp1 resp2.`

Explanation: The Control-O CICS initialization interface module initialization of the IOA environment failed due to a CICS service error.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Notify the CICS or INCONTROL administrator.

CTOC07I PSW AT TIME OF ABEND=`psw` CTOCTDF EP=`add1` CTOEXEC EP=`add2`

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. It describes the PSW at the time of the abend, and the entry points of the related Control-O modules. This message follows message CTOC06E and precedes messages CTOC08I, CTOC09I, and CTOC10I.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface, and processing of the current Transient Data (TD) message stops. Subsequent Transient Data messages are processed.

CTOC08I REGISTERS AT TIME OF ABEND (R0 - R15):

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. This message is a header for messages CTOC09I and CTOC10I which detail the contents of the registers at time of abend. This message is follows messages CTOC06E and CTOC07I.

CTOC09I register0 `register1 ... register7`

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. The header for this message is message CTOC08I. This message details the contents of registers 0 - 7 at time of abend. It is precedes message CTOC10I, which details the contents of registers 8 - 15.)

CTOC0AE BLDL/LOAD FAILED FOR MODULE `modName`

Explanation: The Control-O CICS interface initialization module CTOCTDT failed to load the modName module.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Do the following:

Verify that the IOA load library is concatenated to CICS STEPLIB. If it is not, do the following, in sequence:
- Add the IOA load library to the CICS STEPLIB.
- Stop and restart the CICS.
Restart the Control-O CICS interface.

CTOC0BE CONTROL-O IS NOT INSTALLED. IOAPARM MUST BE SET TO CTO=Y.

Explanation: The Control-O CICS interface module initialization of the IOA environment failed because Control-O is not installed, that is, CTO is not set to Y.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Notify the INCONTROL administrator.

CTOC0CE CTOPARM WAS NOT INITIALIZED. CHECK ERROR MESSAGES ON THE JOBLOG/SYSLOG.

Explanation: The Control-O CICS interface module initialization of the IOA environment failed because CTOPARM is not initialized.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Notify the INCONTROL administrator.

CTOC10I register8 register9 ... register15

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. This message follows messages CTOC08I and CTOC09I. This message details the contents of registers 8 - 15 at time of abend.

CTOC11I CONTROL-O CICS INTERFACE INITIALIZATION COMPLETED FOR SUBSYSTEM

Explanation: This information message is issued upon successful completion of the Control-O CICS Interface initialization for the specified subsystem.

Corrective Action: No action is required.

CTOC12E ERROR IN SEND TO CICS TERMINAL. EIBRESP=`errCode`

Explanation: The Control-O CICS Interface could not send a message to the terminal during initialization or termination. Command EXEC CICS SEND failed with error code errCode.

Corrective Action: Check the error code. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC13E RELEASE MISMATCH. THIS VERSION OF PROGRAM CTOCTDT DOES NOT SUPPORT CICS RELEASE `release`

Explanation: An installation error due to a release mismatch occurred. Possible errors:

The wrong version of the CTOCTDT module was copied to the DFHRPL CICS library.
A CICS release earlier than Release 1.7 is installed.
CICS was upgraded without upgrading the Control-O CICS Interface.

The Control-O CICS Interface is not initialized.

Corrective Action: Copy the version of the CTOCTDT module that corresponds to the CICS release to the DFHRPL CICS library. For details, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC14E ERROR WHILE TRYING TO DETERMINE CICS LEVEL. EIBRESP=`error_code`

Explanation: The Control-O CICS Interface could not determine the level of the CICS release. Command EXEC CICS INQUIRE SYSTEM RELEASE failed with error code errCode.

The Control-O CICS Interface is not initialized.

Corrective Action: Check the error code, and correct accordingly. If necessary, contact BMC Customer Support.

CTOC15E ERROR IN RECEIVE FROM TERMINAL. EIBRESP=`error_code`

Explanation: The Control-O CICS Interface could not receive from the terminal during initialization or termination. Command EXEC CICS RECEIVE failed with the error code errCode.

The Control-O CICS Interface is not initialized or terminated.

CTOC16W INIT REQUEST INVALID. INTERFACE ALREADY INITIALIZED

Explanation: An initialization request was issued, but the Control-O CICS Interface is already initialized.

The request is not processed.

Corrective Action: No action is required.

CTOC17E "PGMIDERR" ERROR IN LOADING CTOCTDF

Explanation: Load of the CTOCTDF program failed due to a program ID error. The EXEC CICS LOAD command failed. The probable cause of the error is that the CTOCTDF program is not defined in the CICS tables.

The Control-O CICS Interface is not initialized.

Corrective Action: Make sure that the CTOCTDF program was defined and copied correctly to CICS. For details, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC18E UNAUTHORIZED TO LOAD CTOCTDF

Explanation: Load of the CTOCTDF program failed because the user is not authorized to load the program.

The Control-O CICS Interface is not initialized.

Corrective Action: Perform the necessary CICS customization, or see your CICS security administrator.

CTOC19E "PGMIDERR" ERROR IN LOADING CTOCTDP

Explanation: Load of the CTOCTDP program failed due to a program ID error. The EXEC CICS LOAD command failed. The probable cause of the error is that the CTOCTDP program is not defined in the CICS tables.

The Control-O CICS Interface is not initialized.

Corrective Action: Make sure that the CTOCTDP program was defined and copied correctly to CICS. For details, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC20E UNAUTHORIZED TO LOAD CTOCTDP

Explanation: Load of the CTOCTDP program failed because the user is unauthorized to load the program.

The Control-O CICS Interface is not initialized.

Corrective Action: Perform the necessary CICS customization, or see your CICS security administrator.

CTOC21I CONTROL-O CICS INTERFACE INITIALIZATION STARTED

Explanation: This informative message is issued at the start of the Control-O CICS Interface initialization.

Corrective Action: No action is required.

CTOC24E ERROR IN EXTRACT EXIT FOR CTOCTDX. EIBRCODE(BYTES 1-2)=`errCode`

Explanation: The EXEC CICS EXTRACT command failed with error code errCode.

The Control-O CICS Interface is not initialized.

Corrective Action: Check the error code and correct the problem accordingly; then try to initialize the interface again. If necessary, contact BMC Customer Support.

CTOC25E INTERFACE NOT INITIALIZED. SHUT REQUEST INVALID

Explanation: A SHUT request was issued, but it was invalid since the Control-O CICS Interface was not initialized.

The request is not processed.

Corrective Action: No action is required.

CTOC26I CONTROL-O CICS INTERFACE SHUTDOWN STARTED FOR SUBSYSTEM

Explanation: This information message is issued at start of the Control-O CICS Interface shutdown for the specified subsystem.

Corrective Action: No action is required.

CTOC27I CONTROL-O CICS INTERFACE SHUTDOWN COMPLETED FOR SUBSYSTEM

Explanation: This information message is issued upon completion of the Control-O CICS Interface shutdown.

Corrective Action: No action is required.

CTOC29E "PGMIDERR" ERROR IN RELEASING CTOCTDF

Explanation: The EXEC CICS RELEASE command failed due to a program ID error.

The Control-O CICS Interface is not shut down.

Corrective Action: Activate and deactivate the Control-O CICS Interface. If the problem persists, contact BMC Customer Support.

CTOC30E UNAUTHORIZED TO RELEASE CTOCTDF

Explanation: The EXEC CICS RELEASE command failed because the user is unauthorized to release the CTOCTDF program.

The Control-O CICS Interface is not shut down.

Corrective Action: Perform the necessary CICS customization so that the user authorized to release the CTOCTDF program, or contact your CICS security administrator.

CTOC31E "PGMIDERR" ERROR IN RELEASING CTOCTDP

Explanation: The EXEC CICS RELEASE command failed due to a program ID error.

The Control-O CICS Interface is not shut down.

Corrective Action: Activate and deactivate the Control-O CICS Interface. If the problem persists, contact BMC Customer Support.

CTOC32E UNAUTHORIZED TO RELEASE CTOCTDP

Explanation: The EXEC CICS RELEASE command failed because the user is unauthorized to release the CTOCTDP program.

The Control-O CICS Interface is not shut down.

Corrective Action: Perform the necessary CICS customization so that the user is authorized to release the CTOCTDF program, or contact your CICS security administrator.

CTOC33E UNRECOGNIZED REQUEST

Explanation: A request was not recognized. The probable cause is a syntax error in a Control-O CICS Interface command issued by the user.

The command is not processed.

Corrective Action: Re-issue the request correctly. For further information, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC35E ERROR IN ENABLING CTOCTDX FOR XTDOUT EXIT. EIBRCODE(BYTES 1-2)=`errCode`

Explanation: Command EXEC CICS ENABLE failed with error code errCode.

The Control-O CICS Interface is not initialized.

Corrective Action: Check the error code and correct the problem accordingly; then try to initialize the interface again. If necessary, contact BMC Customer Support.

CTOC36E ERROR IN DISABLING CTOCTDX FOR XTDOUT EXIT. EIBRCODE(BYTES 1-2)=`errCode`

Explanation: Command EXEC CICS DISABLE failed with the error code errCode.

The Control-O CICS Interface is not shut down.

Corrective Action: Check the error code and correct the problem accordingly; then try to initialize the interface again. If necessary, contact BMC Customer Support.

CTOC37I PSW AT TIME OF ABEND=`psw` CTOCTDX EP=`add` CTOEXEC EP=`add2`

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. The message details the PSW at time of abend, and the entry points of the related Control-O modules.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface. Processing of the current Transient Data (TD) message is stopped. Subsequent Transient Data messages are processed.

CTOC38E INTERFACE NOT INITIALIZED. DBG REQUEST INVALID

Explanation: A DBG request was issued, but it was invalid since the Control-O CICS Interface was not initialized.

The request is not processed.

Corrective Action: No action is required.

CTOC39I DBG REQUEST ACCEPTED

Explanation: Informative message issued in response to DBG request.

Corrective Action: No action is required.

Messages CTOF00 through CTOFxx

This group includes messages for the Control-O product.

CTOF90S OPEN OF DDCARD `ddName` FAILED

Explanation: Open for the ddName DD statement pointing to the password member failed.

Possible causes are:

The ddName DD statement is missing.
The file allocated to the ddName DD statement is not a sequential file nor a member in a PDS.

Authorization to access the product is denied.

Corrective Action: Correct the JCL statement for the procedure or the allocations for the CLIST.

CTOF91S PASSWORD MEMBER TOO LARGE (DD `ddName`)

Explanation: Password member (or sequential data set) has too many lines.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Remove unnecessary lines from the member.

CTOF92S SYNTAX ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A syntax error was found in the password member. When this message is issued by the monitor, it is generally followed by message CTOF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTOF93S VALUE ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A field in the password member contains invalid data. When this message is issued by the monitor, it is generally followed by message CTOF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTOF94S PASSWORD INVALID, PLEASE RECHECK PASSWORD MEMBER (DD `ddName`)

Explanation: Data in the password member was not consistent with the specified password.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from BMC Customer Support. If it checks, contact the representative.

CTOF95S PASSWORD FOR CONTROL-`x` IS ABOUT TO EXPIRE IN `n` DAYS

Explanation:Highlighted, unrollable message.

Password expiration period is about to end.

An expiration date is specified in the password member for the product.

Corrective Action: Contact BMC Customer Support for a new password.

CTOF96S PASSWORD FOR CONTROL-`x` HAS EXPIRED

Explanation:Highlighted, unrollable message.

Password expiration period has ended.

An expiration date is specified in the password member for the product.

Authorization to access the product is denied.

Corrective Action: Contact BMC Customer Support for a new password.

CTOF97S INTERNAL ERROR OCCURRED ON DD `ddName`, PLEASE NOTIFY THE IOA ADMINISTRATOR

Explanation: An internal error has occurred while analyzing the password member pointed to by the ddName DD statement.

Authorization to access the product is denied.

Corrective Action: Notify the IOA administrator.

CTOF98S OBLIGATORY FIELD MISSING FROM PASSWORD MEMBER (DD `ddName`)

Explanation: An obligatory field is missing from the password member.

In this message, ddName is the identity of the DD statement that points to the password member. The PROD, START, CPUID, PASS and TYPE fields should appear at least once in a password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from your INCONTROL administrator.

CTOF9AS PASSWORD FOR CONTROL-`x` NOT DEFINED IN MEMBER (DD `ddName`)

Explanation: The member pointed to by the ddName DD statement does not contain the password for the appropriate product.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this product.

CTOF9BS AUTHORIZATION PERIOD HAS NOT STARTED YET (DD `ddName`)

Explanation: The start date of the password has not yet arrived.

In this message, ddName is the identity of the DD statement that points to the password member. The START field contains the starting date of the password.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this period.

CTOF9CS CPUID/MODEL NOT FOUND IN AUTHORIZED CPU LIST (DD `ddName`)

Explanation: The current CPU is not defined in the CPU list.

In this message, ddName is the identity of the DD statement that points to the password member. Each entry in the CPU list in the password member contains the CPUID of the CPU and its model.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this CPU.

CTOF9DS CARD = `text`

Explanation: This message supplies additional information for a previous error message.

This message may appear after message CTOF92S or CTOF93S which indicates an error has occurred in one of the lines of the password member. Message CTOF9DS displays the erroneous line.

Corrective Action: See messages CTOF92S or CTOF93S.

CTOF9ES PASSWORD DDCARD `ddName` POINTS TO A NON EXISTING MEMBER (ABEND S013-18)

Explanation: The ddName DD statement is allocated to a non-existing member in a PDS file.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the name of the member in the DD statement or create a member with the specified name.

CTOF9FS PASSWORD FOR CONTROL-`x` EXPIRED, TEMPORARY AUTHORIZATION GRANTED

Explanation: The password for Control- x has expired. Nonetheless, Control- x can be run on the current date.

Despite password expiration, Control-x can be run on the 28th, 29th, 30th, 31st, 1st, 2nd, and 3rd days of each month for special purposes.

Control-x processing continues.

Corrective Action: Contact BMC Customer Support to obtain password renewal.

Messages CTOI00 through CTOIxx

This group includes messages for the Control-O product.

CTOI00I CTO SUBSYSTEM `subsys` NOW ACTIVE. IMS AOI MESSAGE PROCESSED

Explanation: This information message indicates that the Control-O subsystem subsys is now active and as a result the IMS Automated Operator Interface (AOI) messages can now be processed.

Corrective Action: No action is required.

CTOI02E CTO SUBSYSTEM `subsys` INACTIVE. IMS AOI MESSAGES NOT PROCESSED

Explanation: IMS Automated Operator Interface (AOI) messages cannot be processed because Control-O subsystem subsys is not active.

No segments of the current AOI message are processed.

Corrective Action: Activate Control-O.

CTOI03E CTO SUBSYSTEM `subsys` DETECTED AN ERROR WHILE PROCESSING AN IMS AOI MESSAGE

Explanation: An internal error occurred while processing an IMS Automated Operator Interface (AOI) message.

No segments of the current AOI message are processed.

Corrective Action: Contact BMC Customer Support.

CTOI04E CTO SUBSYSTEM `subsys` RETURNED AN INVALID RC FOR AN IMS AOI MESSAGE

Explanation: An internal error occurred while processing an IMS Automated Operator Interface (AOI) message.

No segments of the current AOI message are processed.

Corrective Action: Contact BMC Customer Support.

CTOI06E INTERNAL ABEND=(`systemCode,userCode`)

Explanation: The Control-O IMS Interface detected an internal abend, where systemCode is the system abend code, and userCode is the user abend code. This is the header message for messages CTOI07I, CTOI08I, CTOI09I, and CTOI10I which provide information about the abend.

A dump of the address space is produced on the first abend intercepted by the Control-O IMS Interface. Processing of the current IMS Automated Operator Interface (AOI) message is stopped. Subsequent AOI messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to IMS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOI07I PSW AT TIME OF ABEND=`psw` DFSAOUE0 EP=`add1` CTOEXEC EP=`add2`

Explanation: This information message indicates that the Control-O IMS Interface detected an internal abend. The message details the PSW at time of abend, and the entry points of the related Control-O modules. This message follows message CTOI06E and precedes messages CTOI08I, CTOI09I, and CTOI10I.

CTOI08I REGISTERS AT TIME OF ABEND (R0 - R15):

Explanation: This information message indicates that the Control-O IMS Interface detected an internal abend. This message is a header for messages CTOI09I and CTOI10I which detail the contents of the registers at time of abend. This message follows messages CTOI06E and CTOI07I.

CTOI09I `register0register1 ... register7`

Explanation: This information message indicates that the Control-O IMS Interface detected an internal abend. The header for this message is message CTOI08I. This message details the contents of registers 0 - 7 at time of abend. (It is followed by message CTOI10I, which details the contents of registers 8 - 15.)

CTOI10I `register8register9 ... register15`

Explanation: This information message indicates that the Control-O IMS Interface detected an internal abend. This message follows messages CTOI08I and CTOI09I. This message details the contents of registers 8 - 15 at time of abend.

CTOI11E FREEMAIN OF ADDRESS `add` FAILED

Explanation: A FREEMAIN request by the Control-O IMS Interface failed. The probable cause is an internal error.

Corrective Action: Contact BMC Customer Support.

CTOI12I CONTROL-O IMS/ `ims_region` INTERFACE INITIALIZATION COMPLETED FOR SUBSYSTEM `subsys` IMS

Explanation: This information message indicates that initialization of the DFSAOE00 Control-O IMS module is complete for the IMS DB/DC, DCCTL, or DBCTL address space.

The DFSAOE00 Control-O IMS interface module is ready for requests.

Corrective Action: No action is required.

CTOI13W START REQUEST INVALID. INTERFACE ALREADY STARTED

Explanation: This warning message indicates that a /CTO START command was issued to start or restart the Control-O IMS interface, but the interface is already active.

The START request is rejected.

Corrective Action: No action is required.

CTOI15I CONTROL-O IMS/`ims_region` INTERFACE STOPPED FOR SUBSYSTEM `subsys` IMS

Explanation: This information message indicates that the Control-O IMS interface stopped in response to a /CTO STOP command.

Corrective Action: To reactivate the interface, issue the command /CTO START.

CTOI17I TRACE REQUEST ACCEPTED

Explanation: This information message indicates that a /CTO TRACE=ON command to start the Control-O / IMS trace messages was issued and accepted.

TRACE messages may be issued by the DFSAOE00 Control-O IMS interface module.

Corrective Action: To stop the trace, issue the command /CTO TRACE=OFF

CTOI18I `text`

Explanation: This is an echo message. It shows the text of a /CTO command as received from IMS by the DFSAOE00 interface module.

Corrective Action: No action is required.

CTOI19E INVALID COMMAND - COMMAND IGNORED

Explanation: An invalid /CTO command was issued to Control-O IMS interface. The text of the command appears in the previously issued message CTOI18I.

The command is rejected.

Corrective Action: Correct the command and reissue it.

CTOI20E START REQUEST INVALID. INTERFACE WAS PREVIOUSLY CANCELED

Explanation: The command /CTO START was issued to restart the Control-O / IMS interface, but the interface rejects the command because /CTO CANCEL has already been issued, and this prevents the interface from reactivating.

The request is rejected.

Corrective Action: To restart the Control-O IMS interface, stop IMS, then restart it again.

CTOI21I CONTROL-O IMS/ `ims_region` INTERFACE CANCELED FOR SUBSYSTEM `subsys`

Explanation: This information indicates that the Control-O IMS interface stopped in response to a /CTO CANCEL command. The interface between IMS and Control-O using IOA subsystem subsys cannot be reactivated for this IMS region.

Corrective Action: To restart the Control-O IMS interface, stop IMS and restart it again.

CTR messages

This group includes messages for the Control-M for z/OS ,Control-M -M/Assist, Control-M /Links for z/OS , and Control-M /Restart products.

Messages CTR0 through CTR0xx

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.

CTR001I CONTROL-M/RESTART, REL `releaseMaint` STARTED FOR JOB `jobName`

Explanation: This information message is issued by the CONTROLR step to indicate that Control-M/Restart processing of the jobName job started.

Corrective Action: No action is required.

CTR002S INTERNAL ERROR IN CONTROL-M/RESTART MODULE `modName`

Explanation: The CONTROLR step detected an internal error in one of its modules. This message usually follows messages describing the specific error.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Have your system programmer call BMC Customer Support.

CTR003I processName OF JOB `jobName` ENDED SUCCESSFULLY

Explanation: This information message indicates that the Control-M/Restart process for the jobName restarted job (for example, ended OK, abended) is not known at this point.

Corrective Action: No action is required.

CTR004I processName `processType` OF JOB `jobName` ENDED

Explanation: When processType is SIMULATION, this information message indicates that Control-M/Restart, working in simulation mode, finished the simulation of the restart (when processName is RESTART) or prevent NCT2 (when processName is NONCAT2) for this job.

When processType is REGISTRATION (and processName is blank), this information message indicates that Control-M/Restart finished the collecting of cross-reference statistics for job - data sets.

The job is terminated after the CONTROLR step.

Corrective Action: No action is required.

CTR005S CONTROL-M/RESTART STEP MUST BE THE FIRST STEP OF THE JOB

Explanation: The CONTROLR step is not the first in this job. The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Correct the JCL. The CONTROLR step should always be the first one in the job.

CTR006S INTERNAL ERROR - INVALID CONTROL-M/RESTART PARAMETERS

Explanation: The parameters passed to Control-M/Restart in the EXEC statement or in the DAPARMIN DD statement are invalid. The specific errors are generally described in the preceding messages.

Corrective Action: If the job was run manually, correct the parameters in error and resubmit the job. If the job was submitted through the Control-M restart or prevent NCT2 processing, have your system programmer call BMC Customer Support for assistance.

CTR007S SYNTAX ERRORS IN `processName` CONTROL-STATEMENT(S)

Explanation: One or more of the control statements specified in a Restart or Prevent NCT2 Control Parameters member has an invalid syntax. The specific errors are generally described in the preceding messages.

The member in error is either the $DEFAULT member or the one indicated by the MEMNAME subfield in the PARM field of the Control-M/Restart step. The library is the one allocated to the DACTRCTL DD statement.

Corrective Action: Correct the member in error, and rerun the job.

CTR008I PROCESSING PARAMETERS: `parms`

Explanation: This information message shows the contents of the parameters passed to the CONTROLR step either through the EXEC statement or in the DAPARMIN DD statement.

Corrective Action: No action is required.

CTR009S `processName` PROCESSING TERMINATED BY THE USER EXIT `exitName`. RC= `rc`

Explanation: The Control-M/Restart User Exit CTRX001 returned a return code which signified to Control-M/Restart to stop process processing.

Corrective Action: No action is required.

CTR010S `processName` PROCESSING TERMINATED DUE TO AN INVALID RC= `rc` FROM `exitName` EXIT. FUNCTION - `func`

Explanation: Exit exitName was called to perform function. The return code rc passed back to Control-M/Restart was not one of the expected return codes. Each Control-M/Restart exit has a defined set of expected return codes. Exit exitName returned a code which is not in the set of allowed codes.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter. The job terminates after the CONTROLR step.

Corrective Action: Correct the exit code in error. Refer to the INCONTROL for z/OS Administrator Guide for a description of exit exitName and the list of expected return codes.

CTR011S UNCONDITIONAL SYSOUT READING IS REQUESTED, BUT ERRORS WERE ENCOUNTERED DURING SYSOUT PROCESSING

Explanation: The CONTROLR step, running with SYSOPT parameter R, encountered errors during sysout processing. The specific errors are generally described in the preceding messages.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR012W SYSOUTS FROM PREVIOUS RUNS OF JOB ORDER `jobOrder` WERE NOT FOUND. READING IS BYPASSED

Explanation: The CONTROLR step, running with SYSOPT parameter C, encountered errors during sysout processing. The specific errors are generally described in the preceding messages.

The CONTROLR step continues processing, but will not uncatalog data sets, perform GDG adjustment, and the like.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR013S JOB `jobName` IS NON RESTARTABLE

Explanation: Some necessary conditions mandatory for the restart of the job were not met. The specific errors are generally described in the preceding messages.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR014S MISSING CONTROL-M/RESTART REQUIRED PARAMETERS

Explanation: One of the mandatory Control-M/Restart parameters is missing.

Corrective Action: If the job was run manually, correct the parameters in error and resubmit the job. If the job was submitted through Control-M restart or prevent NCT2 processing, have your system programmer call BMC Customer Support for assistance.

CTR015I CONTROL-M/RESTART STEP IS NOT THE FIRST STEP OF THE JOB. ALL STEPS PREVIOUS TO Control-M/RESTART STEP ARE IGNORED

Explanation: This message informs the user that Control-M/Restart was not the first step in the job. Control-M/Restart will ignore all steps prior to Control-M/Restart steps, which means that Control-M/Restart will not analyze any steps prior to the Control-M/Restart step.

Corrective Action: Validate that the steps prior to the Control-M/Restart step were only environment steps or real steps.

CTR017E MISSING PARAMETER IN THE EXCLUDE STATEMENT

Explanation: An obligatory parameter was not specified in the EXCLUDE DSN statement.

Corrective Action: Correct the EXCLUDE DSN statement. Refer to the Control-M/Restart User Guide for the description of the EXCLUDE DSN restart control statement.

CTR018E INVALID DSN LENGTH - CONTROL- `stmt`

Explanation: The data set name specified in the EXCLUDE DSN control statement has an invalid length.

Corrective Action: Correct the EXCLUDE DSN statement. Refer to the Control-M/Restart User Guide for a description of the EXCLUDE DSN control statement.

CTR019E INVALID TRACE LEVEL VALUE. PLEASE ENTER UP TO EIGHT NUMBERS OF RANGE (1-8), SEPARATED BY COMMAS.

Explanation: An error occurred in the Control-M/Restart step of the job. The user tried specified more than 8 numbers when turning on the trace for that specific job in the Control-M/Restart PARM library, with the TRCREST parameter applied for restart and the TRCNCT2 parameter for NCT2.

Example: In MEMBERNAME in Control-M/Restart PARM library add statement for RESTART and NCT2.

TRCREST 1,2,3,4,5,6,7,8

TRCNCT2 1,2,3

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Correct the member with the member name in the Control-M/Restart PARM library according to the above example.

CTR020W `processName` CONTROL-MEMBER `memName` IS EMPTY

Explanation: The process Control-MEMBER was found in the library specified by the DACTRCTL DD statement, but it does not contain any process CONTROL statements.

CONTROLR step continues processing.

Corrective Action: No action is required.

CTR021S MISSING "OPERATION TYPE" PARAMETER

Explanation: The obligatory OPERATION TYPE parameter was not specified in the CONTROLR step parameters.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the parameters passed to the CONTROLR job step. Refer to the Control-M/Restart User Guide for a description of the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR022S INVALID LENGTH OF THE POSITIONAL PARAMETER - `parm`

Explanation: One of the positional parameters passed to the CONTROLR step has an invalid length.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the parameters passed to the CONTROLR step. Refer to the Control-M/Restart User Guide for a description of the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR023S INVALID PROCESSING MODE - " `type`"

Explanation: The PROCESSING MODE positional parameter specified in the parameters for the CONTROLR step is not a valid type of restart.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the RESTART TYPE parameter passed to the CONTROLR job step. See the Control-M/Restart User Guide for the description of the Control-M/Restart PROCESSING MODE parameter.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR024W MISSING " `processName` CONTROL-MEMBER" NAME PARAMETER

Explanation: The process Control-PARAMETERS member name was not specified in the parameters passed to the CONTROLR step.

CONTROLR step continues processing. The control statements from the $DEFAULT member are used for the current job.

Corrective Action: No action is required.

CTR025S MISSING "RECAPTURE CODES/STEP ADJUSTMENT" PARAMETER

Explanation: The mandatory Recapture Codes or Step Adjustment parameter was not specified in the CONTROLR step parameters.

Corrective Action: Add to the JCL the Recapture Codes or Step Adjustment parameter passed to the CONTROLR job step.

CTR026W MISSING "ORDERID" PARAMETER

Explanation: The ORDERID was not specified in the parameters passed to the CONTROLR step.

If the READ SYSOUT INDICATOR is R, then the CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step. If the READ SYSOUT INDICATOR is not R, processing continues.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the parameters passed to the CONTROLR job step. See the Control-M/Restart User Guide for a description of the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR027S INVALID "RECAPTURE ABEND/CONDITION CODE" INDICATOR - val

Explanation: The Recapture Abend or Condition Code indicator specified in the parameters for the CONTROLR step does not contain a valid value.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the ABNDTYP Control-M/Restart installation parameter in CTRPARM. The job stops after the CONTROLR step stops.

Corrective Action: Correct in the JCL the value of the Recapture Codes or Step Adjustment parameter passed to the CONTROLR job step.

CTR028S MISSING "READ SYSOUT INDICATOR" PARAMETER

Explanation: The obligatory READ SYSOUT INDICATOR parameter was not specified in the CONTROLR step parameters.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR029S INVALID "READ SYSOUT INDICATOR" - `type`

Explanation: The value of the READ SYSOUT INDICATOR positional parameter specified in the parameters for the CONTROLR step is not valid.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR030S MISSING "FROM PROCSTEP.PGMSTEP" PARAMETER

Explanation: The obligatory FROM PROCSTEP.PGMSTEP parameter was not specified in the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR031S INVALID "PROCSTEP.PGMSTEP" COMBINATION USED

Explanation: The PROCSTEP.PGMSTEP positional parameter passed to the CONTROLR step has an invalid syntax.

If the CONTROLR step has been added to the job by Control-M, contact BMC Customer Support for assistance.

CTR032E REDUNDANT PARAMETER IN THE "EXEC" PARM OF THE RESTART STEP

Explanation: More positional parameters than necessary were specified in the CONTROLR step parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR033S ORDERID IS OBLIGATORY WHEN READ SYSOUT INDICATOR IS SET TO "C" OR "R"

Explanation: Reading of all the sysouts of previous runs of the job was requested, but ORDERID was not specified in the CONTROLR step parameters.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the CONTROLR step parameters. Refer to the Control-M/Restart User Guide for the description of the Control-M/Restart READ SYSOUT INDICATOR and ORDERID parameters.

If the CONTROLR step was added to the job by Control-M, contact BMC Customer Support for assistance.

CTR034S INVALID OPERATION TYPE - `opn`

Explanation: The OPERATION parameter in the PARM field of the CONTROLR step has an invalid value (opn).

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

If the CONTROLR step was added to the job by Control-M, notify BMC Customer Support.

CTR035S READ SYSOUT OPTION IS INCOMPATIBLE WITH OPERATION TYPE. NONCAT2 IS PERFORMED WITHOUT SYSOUT PROCESSING

Explanation: The combination of READ SYSOUT and TYPE parameters is invalid. The operation requested was NONCAT2 and the READ SYSOUT requested was one of the codes specifying that SYSDATA is to be read. The Prevent NCT2 function does not use the SYSDATA from previous runs.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: If the JCL for the CONTROLR step was created manually, correct the CONTROLR step parameters. See the Control-M/Restart User Guide for the description of the OPERATION subparameter of the MODE parameter and the READ SYSOUT parameter.

If the CONTROLR step was added to the job by Control-M, notify BMC Customer Support.

CTR036S UNKNOWN DATASET DISPOSITION - `val`

Explanation: The Control-M/Restart adjustment facility encountered an invalid data set disposition. This message precedes message CTR038I, which describes the data set name.

Corrective Action: Contact BMC Customer Support for assistance.

CTR037S MISSING INPUT DATASET(S). JOB IS NOT EXECUTABLE

Explanation: At least one of the input data sets for the job is missing. It cannot be located. The job may fail during execution. The name of any missing data set is in an earlier part of the CONTROLR step output.

Corrective Action: Look for previous messages that describe data sets that could not be found. One of the following may be done for each data set:

If you want to bypass the checking for this data set, use the Restart Control member and the EXCLUDE DSN statement.
If the data set is needed as input to the job, find out why it is missing, correct the situation, and rerun the job.

CTR038I DSN= `dsn` DD= `ddName` STEP= `stepName` PROCSTEP= `procStep`

Explanation: This information message details a data set name and its location in the job. The message always appears after another message that describes the actual problem relating to this data set.

Corrective Action: Refer to the previously displayed message in order to determine the problem.

CTR039I `processName` STEP ADJUSTMENT PERFORMED. NEW `processName` STEP `stepName` PROCSTEP `processStepName`

Explanation: This information message indicates that the Control-M/Restart automatic step adjustment facility for processName ended successfully. The job will be restarted from the specified step and procstep.

Corrective Action: No action is required.

CTR040W "NEW" DISPOSITION IS REQUESTED FOR DATASET, BUT IT IS ALREADY CREATED BY A PREVIOUS STEP OF THE JOB

Explanation: The data set is specified with a NEW disposition although it is created by a previous step of the job and it is not deleted during the step. This could cause a JCL failure during job execution.

Corrective Action: Check the original JCL.

CTR041I DATASET WILL BE SCRATCHED FROM VOLUME `volser`

Explanation: This information message indicates that the data set will be scratched from the volume to prevent the failure of the job in duplicate data sets on the same volume.

The data set will be scratched from the volume in the execution phase of the CONTROLR step.

Corrective Action: No action is required.

CTR042I DATASET WILL BE UNCATALOGED

Explanation: This information message indicates that the data set will be uncataloged during the catalog adjustment phase in order to prevent the NOT CATLGD 2 error.

The data set will be uncataloged in the execution phase.

Corrective Action: No action is required.

CTR043E DATASET DOES NOT EXIST FOR THE STEP. STEP ADJUSTMENT IS ATTEMPTED

Explanation: A step that should run in the restarted job contains a data set that does not exist. Control-M/Restart will try to perform a step adjustment. It will find a previous step that creates the required data set, and restart the job from that step.

Corrective Action: No action is required.

CTR044I TAPE DATA SET REFERENCES A VOLUME OF A PREVIOUS STEP. STEP ADJUSTMENT IS ATTEMPTED.

Explanation: Control-M/Restart performs step adjustment to resolve the DD card for a tape data set whose volume is specified by a backward reference (VOL=REF in DD card) to a previous step that is not to be executed during Restart.

The message is followed by message CTR038I, which describes the data set name.

Corrective Action: To make Control-M/Restart avoid step adjustment in case of a VOL=REF referring to a step prior to the Restart step, specify the parameter IGNVOLRF = Y in the CTRPARM member. Then Control-M/Restart attempts to resolve the VOLSER and avoids JCL errors without step adjustment.

CTR045S "NEW" DISPOSITION IS REQUESTED, BUT THE SPACE PARAMETER IS NOT SPECIFIED IN THE JCL

Explanation: The CONTROLR step or the job will have to allocate the data set with a NEW disposition, but the space parameter was not specified in the JCL.

For non-SMS environments, the CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step. Under SMS, the message is not produced.

Corrective Action: Change the disposition of the data set in the JCL, for example from NEW to MOD, and/or add the space parameter.

CTR046W DATASET IS ALREADY CATALOGED BY A PREVIOUS STEP OF THE JOB

Explanation: The data set has to be cataloged, but is already cataloged by a previous step of the job. The message is followed by a CTR038I message that describes the data set name.

Corrective Action: No action is required.

CTR048W "CATALG" DISPOSITION IS SPECIFIED, BUT DATASET IS ALREADY CATALOGED ON OTHER VOLUMES

Explanation: The data set has to be cataloged on a specific volume, but it is already cataloged on another volume. The message is followed by message CTR038I which describes the data set name.

Corrective Action: No action is required.

CTR04AS MISSING INPUT DATA SET `dsn`

Explanation: An error occurred in the job with a Control-M/Restart step because of missing input data set in the job JCL

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Check which data set is missing, correct the job JCL, or allocate the missing file, then rerun or restart the job.

CTR050W "UNCATLG" IS REQUESTED FOR DATASET, BUT THE DATASET IS NOT CATALOGED

Explanation: The data set has to be uncataloged, but it is not cataloged. The message is followed by message CTR038I which describes the data set name.

Corrective Action: No action is required.

CTR051E JOB IS NOT AUTHORIZED TO ACCESS DATASET: `dsn` (DDNAME: `ddName`)

Explanation: An error occurred in the job with Control-M/Restart step. When the CHKSEC parameter is set to Y in the CTRPARM member in the IOA PARM library, Control-M/Restart calls Security Exit IOASE032 to validate whether the job has authorization to access the data set. This message shows that the problematic job is not authorized to access the data set.

Corrective Action: Consult with your system security administrator, add the correct authorization, and rerun or restart the job.

CTR054S OPEN OF DDNAME `ddName` FAILED

Explanation: Open of the ddName data set failed. Possible causes are:

The ddName DD statement is missing.
The data set DCB characteristics are not as expected by the CONTROLR step.

Corrective Action: Look in the job log for additional system messages that explain the cause of the failure. If the DD statement is missing, correct the Control-M/Restart procedure.

CTR055S `processName` OF JOB `jobName` ENDED WITH ERRORS

Explanation: Errors were detected during Control-M/Restart processing. The specific errors are generally described in the preceding messages.

Corrective Action: Check the preceding messages and take the recommended steps.

CTR056S INVALID LENGTH OF THE EXEC PARM DATA

Explanation: The restart parameters data is longer than 255 characters. This might happen only when Control-M/Restart is called internally by another program.

Corrective Action: Correct the parameters passed to Control-M/Restart.

CTR057S STARTED TASKS PROCESSING IS NOT SUPPORTED YET

Explanation: The CONTROLR step was activated for a started task, and restart of a started task is not supported.

Corrective Action: Do not use Control-M/Restart for started tasks.

CTR059I ANALYZE PHASE STARTED

Explanation: This information message is issued by the CONTROLR step when starting the analyze phase. In this phase Control-M/Restart analyzes what should be done.

Corrective Action: No action is required.

CTR060I EXECUTION PHASE STARTED

Explanation: This information message is issued by the CONTROLR step the execution phase starts. In this phase Control-M/Restart executes the special restart or prevent NCT2 adjustment required (for example, delete data sets, perform GDG adjustments).

Corrective Action: No action is required.

CTR061I EXECUTION SIMULATION PHASE STARTED

Explanation: This information message is issued by the CONTROLR step when starting the execution phase under simulation mode. In this phase Control-M/Restart issues only the messages related to the special restart or prevent NCT2 adjustment required, without actually performing the adjustments.

Corrective Action: No action is required.

CTR062I `processType` OF JOB `jobName` STARTED

Explanation: This information message is issued by the CONTROLR step when starting the simulation (if processType is SIMULATION) or collecting of cross-reference statistics for job - data sets (if processType is REGISTRATION) of a job.

Corrective Action: No action is required.

CTR063S CONTROL-M/RESTART IS NOT APF AUTHORIZED

Explanation: The CONTROLR step is not APF authorized.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Ensure that the STEPLIB for the CONTROLR step is on the APF authorization list in SYS1.PARMLIB.

CTR064S INVALID FUNCTION CALL `func` TO MODULE `modName`

Explanation: Internal Control-M/Restart error. This message is followed by other messages detailing the nature of the error.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Notify BMC Customer Support.

CTR065S CONTROL-M/RESTART INITIALIZATION FAILED ON PHASE `phase`

Explanation: Internal Control-M/Restart error. This message is preceded by other messages detailing the nature of the error.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the value set for the ABNDTYP Control-M/Restart installation parameter. The job terminates after the CONTROLR step.

Corrective Action: Examine the preceding messages and take any corrective action associated with those messages. If the problem persists, notify BMC Customer Support.

CTR066I OID= `orderId` NUMBER OF SKIPPED STEPS `nnnn` WITH A TOTAL ELAPSED TIME `hh.mm` CPU TIME `mmm` MIN `ss.cc`SEC

Explanation: This information message indicates the elapsed and CPU time saved by skipping the indicated number of steps during the restart. This message is issued to the job syslog during Control-M/Restart step termination.

The variables in this message are:

nnnn - the number of skipped steps
hh.mm - the elapsed time saved, in hours (hh) and minutes (mm)
mmm ss.cc - CPU time saved, in minutes (mmm), seconds (ss) and hundredths of seconds (cc)

Corrective Action: No action is required.

CTR067I SIMULATION MODE WAS FORCED BY INSTALLATION PARAMETERS

Explanation: This information message indicates that the CTRSTAT Control-M/Restart installation parameter was set to ONLY. Control-M/Restart has been configured to issue statistics only, not to perform any actions.

Corrective Action: No action is required.

CTR070S DSN `dsn` SHOULD BE EXCLUDED, BUT IS NOT FOUND IN THE JOB

Explanation: A specific, non-generic, EXCLUDE DSN statement was specified for the dsn data set, but this data set was not referenced in any of the JCL DD statements in the job.

Control-M/Restart assumes that the data set is referenced in the JCL.

Corrective Action: Check the JCL and remove the EXCLUDE DSN statement. Another solution is to change the EXCLUDE DSN statement to a generic statement.

CTR071W MEMBER `member` DOES NOT EXIST IN CONTROL-M/RESTART PARM LIBRARY

Explanation: The $EXCLUDE or $KEEP member was not found in the Control-M/Restart PARM library. As both members exist in the PARM library as delivered, the member was renamed or deleted.

Corrective Action: Restore the $EXCLUDE or $KEEP member that was renamed or deleted.

CTR072I DSN `dsn` IN PROCEDURE `processName`, STEP `stepName`, DDNAME `ddName` HAS BEEN EXCLUDED FROM RESTART DECISION.

Explanation: The DD name that is defined in the $EXCLUDE member was excluded from Control-M/Restart restart processing. The $EXCLUDE member contains the definitions of DD names and data set names to be excluded from Control-M/Restart processing.

Corrective Action: No action is required.

CTR073I DSN `dsn` HAS BEED EXCLUDED FROM RESTART DECISION.

Explanation: This message informs the user that the data set that was defined in the $EXCLUDE member was excluded from Control-M/Restart restart processing. See message CTR072I.

Corrective Action: No action is necessary.

CTR074I DSN `dsn` HAS BEEN EXCLUDED DUE TO ITS TYPE

Explanation: The data set is excluded from Control-M/Restart processing because of its type, based on installation parameter EXCLVSAM=Y or EXCLPDS=Y. It is either a VSAM data set, with EXCLVSAM=Y defined, or a PDS or PDSE data set, with EXCLPDS=Y defined.

Corrective Action: No action is required.

CTR075S ONLY CONTROLR STEP IS PRESENT IN THE JOB `jobName`

Explanation: The job contains only the CONTROLR step. This could be the result of the AutoEdit translation or the Control-M submit exit.

Corrective Action: Check the job and find out why there are no other steps in the job.

CTR076S `processName` WAS REQUESTED FROM PGMSTEP `stepName` PROCSTEP `stepName` BUT THE STEP WAS NOT FOUND IN THE JOB

Explanation: Control-M/Restart was requested to process the job from a specific step, but this step was not found in the job.

Corrective Action: Check the job step names against the restart parameters (against DO IFRERUN in Control-M), or against the manual restart decision. Correct them, and rerun the job.

CTR077S `processName` WAS REQUESTED TO PGMSTEP `stepName` PROCSTEP `stepName` BUT THE STEP WAS NOT FOUND IN THE JOB

Explanation: Control-M/Restart was requested to restart the job until a specific step, but this step was not found in the job.

Corrective Action: Check the job step names against the restart parameters (against DO IFRERUN in Control-M), or against the manual restart decision. Correct it, and rerun the job.

CTR078S "TO" STEP APPEARS BEFORE THE "FROM" STEP IN THE JOB

Explanation: Control-M/Restart was requested to restart the job from a specific step until another step, but the TO step appears in the job before the FROM step.

Corrective Action: Check the job step names against the restart parameters (against DO IFRERUN in the Control-M), or against the manual restart decision. Correct it, and rerun the job.

CTR079S DUPLICATE "FROM/TO" STEP NAMES FOUND IN THE JOB

Explanation: The CONTROLR step found more than one FROM or TO steps in the job, and could not determine the restart step.

Corrective Action: Change the job step names to avoid duplicate step names in the job.

CTR080I CONDITION CODE `code` WAS RESET FOR STEP `stepName`

Explanation: This information message indicates that a condition code was reset to zero by Control-M/Restart. Steps in the restarted job can refer to a reset condition code of zero from a step that is not executed in the restarted job. The CONTROLR step can use that condition code to affect the execution of the restarted job.

Corrective Action: No action is required.

CTR081I CONDITION CODE `code` IS RECAPTURED FOR STEP `stepName`

Explanation: This information message indicates that a condition code was recaptured by Control-M/Restart. Control-M/Restart captures the condition codes of the steps from the previous run or runs of the job. Steps in the restarted job can refer to a recaptured condition code from a step that is not executed in the restarted job. The CONTROLR step can use that condition code to affect the execution of the restarted job.

Corrective Action: No action is required.

CTR082I OID= `orderId` RESTARTING FROM STEP `stepName` TO STEP `stepName`

Explanation: This information message indicates the Control-M/Restart final restart decision. After all the required adjustments, the restarted job will execute in the specified range of steps.

Corrective Action: No action is required.

CTR083S DATASET ADJUSTMENT PROCEDURE FAILED

Explanation: The restarted job required data set adjustments like uncatalog or scratch a data set. For some reason the adjustment operation failed. This could be because the user exit failed the request, or the operation was failed by the operating system, or because of internal errors in Control-M/Restart.

Corrective Action: If you cannot locate the reason for the failure in previous messages, call BMC Customer Support for assistance.

CTR084E SCRATCH OF DATASET `dsn` FAILED

Explanation: The data set must be scratched in order to prevent duplicate data set errors, but the scratch operation failed.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Look in the job log or in the CONTROLR step messages for messages that will clarify the reason for the failure. Correct it, and rerun the job.

CTR085I DATASET `dsn` SCRATCHED FROM VOL= `volser`

Explanation: This information message indicates the data set is scratched from the volume in order to prevent duplicate data set errors when the job is restarted.

The data set is scratched from the volume.

Corrective Action: No action is required.

CTR086E "UNCATALG" OF DATASET `dsn` FAILED

Explanation: The data set must be uncataloged in order to prevent NOT CATLGD 2 situations, but the uncatalog operation failed.

Corrective Action: Look in the job log or in the CONTROLR step messages for messages that clarify the reason for the failure. Correct it, and rerun the job.

CTR087I DATASET `dsn` HAS BEEN UNCATALOGED

Explanation: This information message indicates that the data set is uncataloged in order to prevent NOT CATLGD 2 situations when the job is restarted.

The data set is uncataloged.

Corrective Action: No action is required.

CTR088E "CATALG" OF DATASET `dsn` FAILED

Explanation: The data set must be cataloged in order to prevent DATASET NOT FOUND errors when the job is restarted.

Corrective Action: Look in the job log or in the CONTROLR step messages for messages that will clarify the reason for the failure. Correct it, and rerun the job.

CTR089I DATASET `dsn` HAS BEEN CATALOGED ON VOLUME `volser`

Explanation: This information message indicates that the data set is cataloged in order to prevent DATASET NOT FOUND errors when the job is restarted.

The data set is cataloged.

Corrective Action: No action is required.

CTR090I CORRECTING REFERENCE OF GDG DATASET TO "`dsn`" FROM:

Explanation: This information message is followed by message CTR038I which describes the GDG name before adjustments. The GDG bias numbers must be reversed so that the relative references to them, within the restarted job, will refer to the correct generation of the data set.

The reference to the GDG data set is corrected.

Corrective Action: No action is required.

CTR091E REQUESTED VOLUMES `vols` ARE NOT MOUNTED

Explanation: The volumes containing the data set to be scratched were not mounted.

Corrective Action: Make sure that the listed volumes are mounted, and rerun the job.

CTR092E "SCRATCH" FAILED. RC="`rc`"

Explanation: An unusual condition was encountered on one or more volumes while scratching a data set.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

CTR093E INVALID VOLUME LIST `volList`

Explanation: An invalid volume list was used to scratch a data set. This is probably due to an internal error in Control-M/Restart, but it may also happen when attempting to run the job in a computer other than the one in which it abended.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

CTR094I CHANGING VOLUME(S) FOR DATASET TO - `volser`

Explanation: This information message precedes message CTR038I, which describes the data set name. The data set was cataloged to prevent DATASET NOT FOUND errors, and now resides on another volume. This is done because the data set name in the JCL of the job is not followed by a VOLSER, and the data set was not cataloged in the previous run of the job.

The internal MVS volume reference to the data set is corrected.

Corrective Action: No action is required.

CTR095I `func` FAILED. RC= `rc` REASON= `rsn`

Explanation: This information message indicates that a specified function was not performed for a data set. In the case of a severe error, this message precedes message CTR084E, which indicates the data set name causing the problem.

Corrective Action: No action is required.

CTR096W MODEL DSCB ATTRIBUTES WERE NOT USED FOR `dsn`. REASON `rsn`

Explanation: Control-M/Restart could not find MODEL DSCB attributes. While performing a GDG adjustment for a file (dsn), Control-M/Restart checks whether the DD statement for the GDG file refers explicitly to a MODEL DSCB. If so, Control-M/Restart tries to locate this MODEL DSCB. If for some reason the DSCB cannot be located, Control-M/Restart issues this warning message, accompanied by message CTR038I, and continues processing.

Possible values for reason: NOTFOUND or TYPEERR.

Corrective Action: No action is required.

CTR097I NCT2 HAS BEEN PREVENTED FOR DATASET

Explanation: This information message indicates that Control-M/Restart prevented the cataloging of the data set because the data set was already cataloged. This message precedes message CTR038I, which specifies the data set name.

Corrective Action: No action is required.

CTR098S JCL ERROR. DATASET " `dsn` " HAS A NAME OF ALIAS

Explanation: The JCL for the job contains a DD statement that specifies a data set dsn whose name is the same as the name of an alias in the catalog. A data set name cannot be the same as the name of an alias in the catalog, because it causes a JCL error when the job is run.

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on CONTROLR installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Correct the JCL of the job by specifying a unique data set name, and rerun or restart the job.

CTR099S THE FOLLOWING GDG BASE DOES NOT EXIST IN CATALOG `ctlg`

Explanation: The JCL for the job contains a DD statement that specifies a GDG data set whose GDG base name does not exist in the ctlg catalog. Any GDG data set specified in the job JCL should have a GDG base name defined in the catalog.

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on CONTROLR installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Define a GDG base name in the catalog by means of the IDCAMS utility, or correct the JCL of the problematic job. Specify the GDG data set with a GDG base name that exists in the catalog.

Messages CTR100 through CTR1xx

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.

CTR100I ABEND CODE `code` IS RECAPTURED FOR STEP `procStep. pgmStep`

Explanation: This information message indicates that the CONTROLR step recaptured an abend code from a previous run of the job. This code may affect execution of the restarted job. The steps of the restarted job can refer to (COND=EVEN or COND=ONLY) abends in steps that are not executed in the restart run.

Corrective Action: No action is required.

CTR101I NONCAT2 FROM STEP `procStep. pgmStep` TO STEP `procStep. pgmStep`

Explanation: This information message indicates the range of steps which will be executed in a Prevent NCT2 run.

Corrective Action: No action is required.

CTR102I CLEANUP FROM STEP `step.procStep` TO STEP `step.procStep`

Explanation: This information message indicates that the Control-M/Restart Data Set Cleanup Facility (CLIST CTRCCLN) was used to perform data set adjustment, without performing the actual restart. Data Set Cleanup Facility is used to restore the steps in the specified step range to their initial state. The CONTROLR step performs data set adjustment, deleting all new cataloged files, adjusting GDG bias numbers, and so on, without executing other steps of the job.

Corrective Action: No action is required.

CTR103I `job` [`procedure`] `step` - STEP NOT EXECUTED - DUE TO RESTART DECISION

Explanation: This information message indicates the step that is being skipped during the restarted run of a job. The job step was not executed because restart was requested by a From Restart Step statement from a later step.

Corrective Action: No action is required.

CTR104S ALL STEPS WILL BE FLUSHED DUE TO PREVIOUS CODES

Explanation: Restart resulted in flushing all remaining steps in the job. A request was made to Control-M/Restart to recapture step completion codes. This request will cause all remaining steps not to be executed, because of condition codes specification.

All the job steps are not executed.

Corrective Action: If recapturing of completion codes is required, mark the job as ended OK using the FORCE OK command, or restart the job without the step recapturing option.

CTR105I 'NCT2' IS RECAPTURED FOR STEP `stepName.procStep`

Explanation: This message informs the user that Control-M/Restart recaptured the NCT2 codes for a specific step and specific procstep. Control-M will use this information during post-processing analysis of the results of the job.

Corrective Action: No action is necessary.

CTR106I `jobName processName stepName - complCode systemAbCode/userAbCode nct2_sign`

Explanation: This message appears for every step in the job. It is used by Control-M during the Post-processing analysis of the results of the job.

Corrective Action: No action is necessary.

CTR107I ABEND CODE `code` IS RESET FOR STEP `procStep. pgmStep`

Explanation: This information message indicates that Control-M/Restart reset the abend code for the specified step and reset the step to a "not abended" state with a zero condition code.

This code might affect execution of the restarted job.

Corrective Action: No action is necessary.

CTR120E READING OF THE SYSOUT OF PREVIOUS RUN(S) OF ORDERID `orderId` FAILED

Explanation: Severe errors were encountered during processing of the sysouts from the previous run or runs of the job. The preceding messages explain the problem in detail.

Depending on the Read Sysout Indicator, Control-M/Restart either terminates or continues processing.

If R was specified as a value for READ SYSOUT INDICATOR then the CONTROLR step terminates with a nonzero condition code or with an abend code, depending on the setting of the ABENDTYP Control-M/Restart installation parameter in CTRPARM. The job terminates after the CONTROLR step.

If C was specified as a value for Read Sysout Indicator then Control-M/Restart continues processing.

Corrective Action: Check the combination of CONTROLR step parameters MEMNAME and ORDERID. If the combination is valid, try to find out why the compressed data sets containing the sysouts of the previous run for the job were deleted.

CTR121E IMPORTANT SYSOUT OF JOBID `jobId` FROM ORDERID `orderId` IS MISSING. RESTART IMPOSSIBLE

Explanation: Control-M/Restart did not find some or all of the archived SYSDATA for the orderId order ID during the restart run CONTROLR step. The SYSDATA pointers that Control-M/Restart received pointed to archived SYSDATA that was deleted before the restart run was executed. Control-M/Restart cannot perform a restart without this data.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the setting of the ABENDTYP Control-M/Restart installation parameter. The job terminates after the CONTROLR step.

Corrective Action: Determine the cause of deletion of the needed SYSDATA, and ensure that all SYSDATA needed by Control-M/Restart for restart are available at the time the restart is performed.

CTR126W PROBLEMS READING ARCHIVED SYSOUT DATA BASE. DSN=`dsn`

Explanation: Control-M/Restart encountered problems while attempting to read archived SYSDATA from the archived SYSDATA database. This message is accompanied by other messages that define the exact problem.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Notify BMC Customer Support.

CTR128S SYSOUT(S) OF THE PREVIOUS RUN(S) DO NOT CONTAIN USEFUL INFORMATION. NUMBER OF CARDS READ `nnnn`

Explanation: SYSDATA read by Control-M/Restart did not contain the data necessary to complete processing properly.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Notify BMC Customer Support.

CTR131E INCORRECT DSN SPECIFICATION - `dsn`

Explanation: The dsn data set specified in the RESTART or PREVENT NCT2 Control-STATEMENT has an invalid syntax.

Corrective Action: Correct the RESTART or PREVENT NCT2 Control-statement. Refer to the Control-M/Restart User Guide for the description of the RESTART or PREVENT NCT2 Control-statement.

CTR132I PARAMETER MISSING IN THE DEBUG LEVEL STATEMENT

Explanation: This information message indicates that parameter DEBUGLEVEL was specified in the CTRPARM member, but no value was supplied.

The program ignores the parameter and continues processing.

Corrective Action: Enter the value from 1 to 255 for the DEBUGLEVEL parameter in the CTRPARM member.

CTR133I INVALID DEBUG LEVEL VALUE

Explanation: This information message indicates that an invalid value was specified in the DEBUGLEVEL parameter in the CTRPARM member.

The program ignores the parameter and continues processing.

Corrective Action: Correct the value specified in the DEBUGLEVEL parameter in the CTRPARM member to a number from 1 to 255.

CTR134E INVALID SPECIFICATION OF NONRESTARTABLE STEP [`procStep.pgmStep`]

Explanation: The NONRESTARTABLE_STEP parameter in the olprefa.CTR library was specified incorrectly.

The program aborts the CONTROLR step with an error code.

Corrective Action: Correct the format of the NONRESTARTABLE_STEP parameter to [PROCSTEP. PGMSTEP] and restart the job.

CTR135E INVALID SPECIFICATION OF NONRESTARTABLE PGM `programName`

Explanation: The NONRESTARTABLE_PGM parameter in the olprefa.CTR library was specified incorrectly.

The program aborts the CONTROLR step with an error code.

Corrective Action: Correct the format of the NONRESTARTABLE_PGM parameter to PGM and restart the job.

CTR141S MVS/JES TABLE `tableName` CANNOT BE LOCATED

Explanation: Control-M/Restart cannot locate the specified operating system table for retrieving necessary information.

Corrective Action: Contact BMC Customer Support for assistance.

CTR142S TOKEN TRANSLATION FOR TABLE `tableName` FAILED. TOKEN= `token`. RC= `rc`

Explanation: Failure in request by Control-M/Restart for MVS SWA Manager translation service. Values of table, token, and return-code are provided for problem determination purposes.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: Notify BMC Customer Support.

CTR143S UNIT NAME NOT FOUND: `unitName`

Explanation: Unit name unitname was not recognized by Control-M/Restart. The unit name is either incorrect or missing from the Control-M/Restart Unit Table.

The job terminates with error.

Corrective Action: Specify a correct unit name in the Control-M/Restart Unit Table.

CTR146S "MOD" DISPOSITION IS REQUESTED, BUT THE SPACE PARAMETER IS NOT SPECIFIED IN THE JCL

Explanation: The data set that was specified with a MOD disposition could not be found, and therefore a new one must be allocated. However, the space parameter is missing.

Corrective Action: Add the SPACE parameter to the data set with the MOD disposition, and rerun the job.

CTR147I REFERENCE TO GDG DATASET WILL BE ADJUSTED TO `dsn1` FROM: `dsn2`

Explanation: This information message indicates that the GDG adjustment phase will change the data set name because the generation number was updated by the job during a previous run. Usually the change will be to return to the previous generation data set.

The data set name will be changed. The JCL of the job remains unchanged. Only the real job references the new data set name during execution.

Corrective Action: No action is required.

CTR148E DATASET NOT FOUND IN CATALOG. STEP ADJUSTMENT IS ATTEMPTED

Explanation: A step that should run in the restarted job contains a data set that is not found in the catalog.

Control-M/Restart tries to do a step adjustment, find a previous step that creates the required data set, and restart from that step.

Corrective Action: No action is required.

CTR149W "NEW" DISPOSITION IS REQUESTED FOR A DATASET USED BY A PREVIOUS JOB STEP

Explanation: A job step must allocate a data set as if DISP was set to NEW, but Control-M/Restart determined that a previous step in the job references the same data set name with a disposition other than DELETE.

Processing continues normally.

Corrective Action: No action is required.

CTR150I `exitName` USER EXIT WILL BE INVOKED TO `func` DATASET

Explanation: This information message indicates that the CTRX001 Control-M/Restart Exit will replace Control-M/Restart data set adjustment processing. This exit is installed during Control-M/Restart Installation. It overrides CATALOG, UNCATALOG, DELETE (SCRATCH), LOCATE and SCANDS functions originally performed by Control-M/Restart.

For more information concerning Control-M/Restart user exits, see the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

CTR151W ERRORS OCCURRED WHILE COLLECTING JOBS/DATASETS CROSS-REFERENCE STATISTICS

Explanation: Errors occurred during Control-M/Restart PREVENT NCT2 processing while statistics were being collected for the Job Dataset Cross Reference report.

Control-M/Restart continues PREVENT NCT2 processing, and Control-M continues processing of the job, but the Job Dataset Cross Reference report statistics relating to this job are not collected.

Corrective Action: Retain the whole sysout of the problematic job execution, and contact BMC Customer Support.

CTR152I JOBS/DATASETS CROSS-REFERENCE STATISTICS COLLECTED SUCCESSFULLY

Explanation: During Control-M/Restart PREVENT NCT2 processing, statistics for the Job Dataset Cross Reference report were collected successfully.

Corrective Action: No action is required.

CTR160E INVALID "EXEC" CARD FOUND - `stmt`

Explanation: An unknown type of EXEC statement was found during sysout processing.

Corrective Action: Check the problematic EXEC statement and if appropriate, correct it. If everything appears in order, contact BMC Customer Support.

CTR161S "SUBSTITUTION JCL" CARD NOT FOUND FOR JCL LINE " `lineNum`"

Explanation: Substituting JCL message (IEF653I) had been expected for the JCL line number line-number but it was not found in the sysout. This is probably an internal error in Control-M/Restart. Control-M/Restart tries to analyze the JCL of the previous executions of the job. This message means that Control-M/Restart could not resolve some internal references of the sysout of the job.

The CONTROLR step ends with a non-zero condition code or with an abend code, depending on the Control-M/Restart Installation parameter ABNDTYP in CTRPARM. The job ends after the CONTROLR step.

Corrective Action: Check the problematic sysout, and correct the JCL of the job. If everything appears in order, contact BMC Customer Support for assistance. Provide a printout of the sysout of the previous execution of the job that failed, and the complete sysout of the job run that produced this message.

CTR162S UNKNOWN SYSOUT STRUCTURE OF JOBID `jobId`

Explanation: Severe failure during sysout processing. Control-M/Restart is unable to process the sysout from the previous run of the job (JOBID jobId). Control-M/Restart encountered a job SYSJCL or SYSMSG structure with which it is not familiar. It is probably an internal error of Control-M/Restart.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart Installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step.

Corrective Action: Contact BMC Customer Support for assistance. Provide a printout of the sysout of the previous execution of the job that failed, and the complete sysout of the job run that produced this message.

CTR163I MISPLACED "JCL" STATEMENT - `jclStmt`

Explanation: This information message indicates that a JCL statement was found in the message area of the job sysout from the previous run.

CONTROLR step continues processing. This JCL statement is ignored.

Corrective Action: Check why the specified JCL statement was found in the improper area of the sysout. If everything appears in order, contact BMC Customer Support.

CTR164I MISPLACED SYSOUT STATEMENT - `sysout stmt`

Explanation: This information message indicates that the specified sysout statement was found in an improper area of the job sysout from the previous run.

CONTROLR step continues processing, and the sysout statement is ignored.

Corrective Action: Check why the specified sysout statement was found in the improper area of the sysout of the previous run of the job. If everything appears in order, contact BMC Customer Support for assistance.

CTR165E ERRORS WHILE PROCESSING SYSOUT. SENSE= `sense`

Explanation: Control-M/Restart encountered an error in the structure of a SYSDATA statement from a previous run. The SYSDATA contained data that was in an invalid format. The value of sense is an internal code that helps in problem analysis. This message is accompanied by message CTR167I, which contains the content of the statement in error.

Control-M/Restart continues the restart process.

Corrective Action: Notify BMC Customer Support.

CTR166I CURRENT JOB JCL IS DIFFERENT FROM JCL OF PREVIOUS RUN(S)

Explanation: This information message indicates that differences were found between current job JCL and the JCL or JCLs of the job from previous run or runs of the job.

CONTROLR step continues processing.

Corrective Action: No action is required.

CTR167I UNKNOWN CARD STRUCTURE - `sysoutData`

Explanation: This information message contains the data that caused the error indicated in the preceding CTR165S message.

Corrective Action: No action is required.

CTR168I ANALYZE {STAGE2 | CHKSTG2} INFORMATION FOR STEP=STEP= `stepName` PROCSTEP= `procStepName`

Explanation: This information message provides additional information for messages CTR164I and/or CTR038I.

The program continues normal error processing.

Corrective Action: Supply BMC Customer Support with the sysout of the original run of the job, and the sysout and Control-M/Restart output of all restarted attempts of the job.

CTR169I {JESJCL | SYSMSG} `ddName dsn gdgLevel`

Explanation: This information message provides additional information for messages CTR164I and CTR038I.

The program continues normal error processing.

Corrective Action: Supply BMC Customer Support with the sysout of the original run of the job, and the sysout and Control-M/Restart output of all restarted attempts of the job.

CTR171S `processName` FROM CONTROL-M/RESTART STEP IS NOT SUPPORTED

Explanation: Control-M/Restart was requested to perform process starting with the CONTROLR step itself. A RESTART or NONCAT2 run must start processing at some step other than the CONTROLR step itself. The request to begin at the CONTROLR step may have been generated manually, either in the Control-M Restart Window or by manual creation of the JCL, or automatically as the result of a prior run abending in the CONTROLR step.

The CONTROLR step terminates with a non-zero condition code or with an abend code (depending on the Control-M/Restart installation parameter ABNDTYP). The job terminates after the CONTROLR step.

Corrective Action: If the FROM step was manually specified on the Control-M Restart Window, specify a subsequent step in the job as the starting step. If the JCL for the RESTART or NONCAT2 run was created manually, correct the JCL to point to a subsequent step.

If the FROM step was generated automatically, the restart step must be overridden manually in the Control-M Restart Window to point to a later step in the RESTART or NONCAT2 run.

CTR180E DSN `dsn` IS LOCATED ON MORE THAN ONE VOLUME - CANNOT RESTART

Explanation: During restart of a job that was executing when the system crashed, Control-M/Restart found data set dsn on more than one disk volume. After a system crash, Control-M/Restart must determine where new data sets that did not specify a specific volume were allocated. The system crashed before the data sets were cataloged. At restart, Control-M/Restart found more than one data set with the same name.

This message precedes a series of CTR181E messages that list the volumes on which data set dsn was found.

The CONTROLR step terminates with a non-zero condition code or with an abend code, depending on the Control-M/Restart installation parameter ABNDTYP. The job terminates after the CONTROLR step.

Corrective Action: If it can be determined from the CTR181E messages which data set was the one created when the system crashed, delete all others with the same data set name and retry the restart.

If it is not possible to determine which data set is the correct one for restart, delete all data sets with data set name dsn, and when restarting, manually ensure that the restart step occurs before the step that created dsn.

An alternative is to modify the JCL for the job so that a specific volume is requested for data set dsn. This permits restart to proceed. In this case, delete dsn from all other volumes on which it appears.

CTR181E DSN `dsn` IS LOCATED ON VOLUME `vol`

Explanation: This message accompanies message CTR180E and indicates on which volumes the duplicate data sets reside.

Corrective Action: No action is required.

CTR182I STEP ADJUSTMENT REQUIRED BUT "NOSTEPADJUST" WAS SPECIFIED. RESTART PROCESSING TERMINATED

Explanation: This information message indicates that restart processing terminated because a required step adjustment could not be performed due to a NOSTEPADJUST specification. Control-M/Restart determined that step adjustment was required to perform the restart correctly. However, control statement NOSTEPADJUST, which prevents automatic step adjustment, was specified.

Restart processing is terminated and the job is not executed.

Corrective Action: No action is required.

CTR183I STEP `step` PROCSTEP `procStep` NON RESTARTABLE BY REQUEST `(reason)`. STEP ADJUSTMENT ATTEMPTED

Explanation: This information message indicates that the step is non-restartable, as requested by the user. Therefore, Control-M/Restart attempts step adjustment, that is, to restart the job from the previous step.

If a reason appears for why the step is non-restartable, it can be one of the following:

DD – The step includes the CTRNORST DD statement.
STEP – The step is specified in the NONRESTARTABLE_STEP or NONRESTART_STEP parameter.
PGM – The step executes the program specified in the NONRESTARTABLE_PGM or NONRESTART_PGM parameter.

Corrective Action: No action is required.

CTR184S JOB IS NON RESTARTABLE BY REQUEST

Explanation: Job could not be restarted because Control-M/Restart attempted to perform the restart from the first step, but the user specified the CTRNORST DD statement within that step or there is a NONRESTARTABLE statement that prevents the step from running.

If Control-M/Restart attempts restart from a step that is non-restartable, Control-M/Restart then attempts restart from the previous step.

Control-M/Restart attempts step adjustment.

When Control-M/Restart attempts restart from the first step, but the CTRNORST DD statement is specified for that step or there is a NONRESTARTABLE statement that prevents the step from running, there is no previous step from which the restart can be attempted, so the restart fails.

Corrective Action: No action is required.

CTR185E ERROR IN PROCESSING OF "IF/THEN/ELSE" JCL CARD FOR STEP `stepName` PROCSTEP `procStepName`

Explanation: An internal error occurred during Control-M/Restart analysis of the ‘IF/THEN/ELSE’ job JCL statements.

Corrective Action: Report the problem to BMC Customer Support.

CTR186E ERROR ACCESSING CTR PARM LIBRARY

Explanation: Control-M/Restart encountered an error while trying to read the $DEFAULT parameter file member or the Restart Parm Member Name (by default, the Job MEMNAME).

Corrective Action: Try to verify the members. If no issue is found, report the problem to BMC Customer Support.

Messages CTR200 through CTR2xx

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.

CTR220E ENQ OF DATASET `dsn` FAILED

Explanation: Control-M/Restart attempted to enqueue a data set, but the enqueue failed because the data set was already enqueued by another MVS task.

Control-M/Restart terminates the job.

Corrective Action: Determine which other tasks in the system are using the data set. Have it relinquish control of the data set, and restart the job.

CTR230S INVALID "STEP ADJUSTMENT" INDICATOR - `val`

Explanation: The Step Adjustment indicator specified in the parameters for the CONTROLR step does not contain a valid value.

The CONTROLR step terminates with a non-zero condition code or with an abend code depending on the Control-M/Restart installation parameter ABNDTYP in CTRPARM. The job terminates after the CONTROLR step has terminated.

Corrective Action: Correct in the JCL the value of the Step Adjustment parameter passed to the CONTROLR job step.

CTR235I `opn` REQUEST FROM PROCSTEP `procStep` PGMSTEP `pgmStep` TO PROCSTEP `procStep` PGMSTEP `pgmStep`

Explanation: This information message indicates that the input parameters of the job step EXEC statement were interpreted, and the FROM and TO procedure and program steps were determined by Control-M/Restart.

The operation identified in the message, could be RESTART, NCT2, or CLEANUP. The FROM pgmstep is always present while the other steps may be blank. If the TO procstep is present, the TO pgmstep is also present. If the steps specified by the user were symbolic, for example, $FIRST, in the message the names of the steps will be the actual JCL steps determined by Control-M/Restart.

Corrective Action: No action is required.

CTR241I =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
CTR242I = CONTROL-M/RESTART - PRELIMINARY STEP ANALYSIS =
CTR243I STEP PROC-STEP RESTART ANALYSIS

Explanation: Header messages of the Control-M/Restart Non-Restartable Steps Report, which is controlled by Installation parameters STEPLIST and STEPLOUT.

Corrective Action: No action is required.

CTR244I `stepName` `procstepName` Non-Restartable – `reason`

Explanation: Part of the Control-M/Restart Non-Restartable Steps Report, which is controlled by Installation parameters STEPLIST and STEPLOUT. The message displays a job step that was found to be non-restartable according to a preliminary analysis of the job JCL and Control-M/Restart parameters. The reason can be one of the following:

NONRESTARTABLE_STEP statement — a NONRESTARTABLE_STEP statement is defined for the step/procstep name in the corresponding CTR PARM definition.
NONRESTARTABLE_PGM statement — a NONRESTARTABLE_PGM statement is defined for the step program name in the corresponding CTR PARM definition.
Special DD name — The step uses a special DD statement that indicates a Non Restartable step. For more information, see the description of the NONRSTDD parameter in the INCONTROL for z/OS Installation Guide: Customizing.
Forwarded temporary dataset — The step (or any following step) uses a temporary data set created by any of the preceding steps.

Corrective Action: No action is required.

CTR245I `stepName` `procstepName`

Explanation: Part of the Control-M/Restart Non-Restartable Steps report , which is controlled by Installation parameters STEPLIST and STEPLOUT. The message displays a job step that was NOT found to be non-restartable according to a preliminary analysis of the job JCL and Control-M/Restart parameters.

Corrective Action: No action is required.

Messages CTR300 through CTR3xx

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.

CTR301I `varName`

Explanation: This information message passes information from the original run of a job to subsequently restarted runs. It is not intended to provide information to the user. When Control-M/Restart optional installation feature WR0204 is enabled, one or more of these information messages may appear in the JES system output or the console hardcopy log. These messages only appear in job runs that were not restarted. The contents of the message is variable.

Corrective Action: No action is required.

CTR302W GETMAIN ERROR IN CTRSTAT

Explanation: Insufficient memory to perform enhanced GDG handling. This message can only occur if optional installation feature WR0204 is enabled. The message does not occur for restarted jobs. If this message occurs, subsequent reruns of the job may be adversely affected because GDG adjustment could be incorrect.

The CONTROLR step continues running, but subsequent restarted jobs may perform GDG adjustment incorrectly.

Corrective Action: Increase the REGION size parameter on the JCL JOB or EXEC statement. If the job must be restarted and if GDG adjustment must be performed, the WR0204 feature should be disabled until the rerun is complete.

CTR303I POST-SYSTEM CRASH ANALYSIS: SCAN ALL DASD TO SEARCH FOR UNCATALOGED DATASETS FROM THIS JOB?

Explanation: This information message indicates that a system crash occurred during the original run of this restarted job, and asks if a DASD scan should be performed. Message CTR304I requests a reply regarding the scan.

Corrective Action: Reply to WTOR message CTR304I.

CTR304I REPLY ''YES'' TO SCAN, ''NO'' TO BYPASS SCAN, OR ''CAN'' TO CANCEL THE JOB

Explanation: This information message follows message CTR303I.

The system waits for the user response.

Corrective Action: Enter one of the following:

YES - Scan all DASD to search for uncataloged data sets for this job.
NO - Bypass the scan. Control-M/Restart will not search for uncataloged data sets but this may cause problems while running the job.
CAN - Cancel the job.

CTR305I NCT2 CONDITION DETECTED - JOB FLUSHED

Explanation: This information message indicates that CONTROLR detected an NCT2 problem for a job scheduled with NCT2 option F (FLUSH). If parameter NCT2 is set to F in a job scheduling definition, then the job is not executed when CONTROLR detects an NCT2 condition for the job.

The CONTROLR step terminates with a nonzero condition code or with an abend code, depending on CONTROLR installation parameter ABNDTYP. The job terminates after the CONTROLR step

Corrective Action: Manually DELETE and UNCATALOG data sets that cause the NCT2 condition, or change parameter NCT2 from F to Y so that CONTROLR will DELETE and UNCATALOG such data sets. Then, rerun the job.

CTR306I REMOVE VOL=REF REFERENCE FROM THE DD CARD.

Explanation: IGNVOLRF = Y is specified in the CTRPARM member. Control-M/Restart does not do step adjustment to resolve the DD card for a tape data set whose volume is specified by a backward reference (VOL=REF in DD card) to a previous step that is not to be executed during Restart. The message is followed by message CTR038I, which describes the data set name.

In the first DD card of a restarted step that allocates a tape volume specified by a backward reference, Control- M/Restart removes the backward reference, that is, the VOL=REF parameter. If a volume name was resolved or extracted (from history or JCL), then Control-M/Restart adds the VOL=SER parameter using the resolved or extracted volume name and issues message CTR094I.

In subsequent DD cards pointing to the same volume (by a VOL=REF backward reference), Control- M/Restart changes the reference so that it points to an executed DD card (that is, a DD card belonging to a restarted step) allocating the same volume. For every such subsequent DD card, Control-M/Restart issues message CTR307I.

If the volume name was not found and the first executed DD that allocates this volume has a label number greater than one, then Control-M/Restart changes the label number to one (it assumes that the restart run uses another volume) and shifts the LABEL numbers of subsequent DD cards points to the same volume, respectively. For every DD card whose LABEL was changed, Control-M/Restart issues message CTR308I.

Corrective Action: To make Control-M/Restart always do step adjustment to resolve the DD card for a tape data set whose volume is specified by a backward reference (VOL=REF in DD card) to a previous step that is not to be executed during Restart, keep the parameter IGNVOLRF = N (default) in the CTRPARM member.

CTR307I CHANGE VOL=REF REFERENCE TO THE FIRST DD ALLOCATED DURING THE JOB RUN - DD= `ddName`, STEP= `stepName. procstepName`.

Explanation: IGNVOLRF = Y is specified in the CTRPARM member. See the description of message CTR306I for more information. The message is followed by message CTR038I, which describes the data set name.

Corrective Action: No action is required.

CTR308I CHANGE LABEL= PARAMETER VALUE FOR TAPE DATASET FROM `oldLabelNumber` TO `newLabelNumber.`

Corrective Action: No action is required.

CTR309I CHANGE THE DISPOSITION OF THE DATASET TO DISP=OLD

Explanation: The DD card (specifying the NEW data set) fits the definition in the $KEEP member of CTR PARM library. Therefore, Control-M/Restart handles the DD card or data set as a Checkpoint data set. See the Control-M/Restart User Guide for more information regarding the $KEEP member. The message is followed by message CTR038I, which describes the data set name.

The Checkpoint data set is not deleted by Control-M/Restart. To prevent JCL error and NCT2 problems, Control-M/Restart may change the disposition in the DD card specifying a Checkpoint data set.

If the JCL of a job contains a DD statement in which the parameter DISP is set to NEW, and the corresponding Checkpoint data set already exists when Control-M/Restart is invoked, Control-M/Restart automatically changes the value of the DISP parameter to OLD.

Corrective Action: No action is required.

Messages CTR500 through CTR5xx

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.

CTR555S OID= `orderId` INSUFFICIENT STORAGE. INCREASE THE REGION SIZE

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

Messages CTR900 through CTR9xx

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.

CTR913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a print file failed.

Possible causes are:

The DD statement SYSPRINT is missing.
The data set described by the DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

Messages CTRC00 through CTRCxx

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.

CTRC001 ARCHIVED FILE NOT FOUND

Explanation: The archived file required to perform a Control-M/Restart Simulation or Data Set Cleanup could not be found. To perform a RESTART or NCT2 Simulation (CLIST CTRCSIM) or Data Set Cleanup (CLIST CTRCCLN), Control-M/Restart must locate the archived file corresponding to the member name of the job and unique order ID of the job.

This file could not be located for one of the following reasons:

The order ID specified in the main panel of CTRCSIM or CTRCCLN is not the correct order ID for the specified member name.
The specified member name does not exist on the AJF.
Although the simulated job still exists on the AJF, its corresponding archived file was deleted manually.

If the relevant entry is deleted from the AJF, the archived file is deleted automatically during the running of the Control-M New Day procedure.

Corrective Action: Identify the cause of the problem, and then correct it, as follows:

Check whether or not the specified order ID is the correct one, by issuing command ORDERID (PF12 or PF21) in the Active Environment screen. The order ID for each entry is displayed in the STATUS field.
Verify that the specified member name matches the member name of the job to be simulated or cleaned-up.
If the relevant job entry still exists on the AJF, and the New Day procedure did not delete the archived file, the file may have been manually deleted by mistake. In this case, simulation or cleanup cannot be performed.

CTRC002 CONTROL-M/RESTART ARCHIVED FILE FOR THIS JOB WAS PROBABLY DELETED

Explanation: The system attempted to access an archived sysout associated with the Active Job file entry being processed, but could not find it. Further processing of the job is impossible.

The job is not processed.

Corrective Action: Manual intervention is required to restart the job.

Messages CTRX00 through CTRXxx

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.

CTRX01E ERROR OPENING FILE, DDNAME `sysprint`

Explanation: An error opening file occurred in the CTMJDS utility. The CTMJDS utility is invoked when necessary to create data set cross-reference records in statistic file.

Corrective Action: Add the SYSPRINT DD statement to the CTMJDS utility, and rerun the job.

CTRX02E SYSTEM INTERFACE ERROR

Explanation: An error occurred in the CTMJDS utility. The error occurs when the return codes from the IBM TIME macro are not zero.

Corrective Action: Contact BMC Customer Support for assistance.

CTT messages

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

Messages CTT0 through CTT0xx

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

CTT001S INTERNAL ERROR - REASON = `rsn`. NOTIFY THE IOA ADMINISTRATOR

Explanation: Processing failed due to internal error for the specified reason.

The program stops executing.

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

CTT002S TASK `taskName` WAS CANCELED BY OPERATOR

Explanation: The specified task was canceled by an operator MVS CANCEL command.

The job or started task stops executing.

Corrective Action: No action is required.

CTT003S CONTROL-M/TAPE REAL-TIME ENVIRONMENT IS NOT ACTIVE

Explanation: The Control-M/Tape real-time environment exists but its status is not active, for example, SUSPEND or DORMANT. This message is issued by every component that requires an active environment to perform its function.

The requested Control-M/Tape function is not performed.

Corrective Action: Activate Control-M/Tape by starting the CTTINIT procedure with a PARM=RESUME statement before using this function.

CTT004S UNABLE TO LOCATE CONTROL-M/TAPE REAL-TIME ENVIRONMENT TABLE

Explanation: Control-M/Tape was not initialized in this CPU. The message is issued by every component that requires an active environment to function.

The requested Control-M/Tape function is not performed.

Corrective Action: Initialize Control-M/Tape by starting the CTTINIT procedure before using this function.

CTT005W LOAD OF USER EXIT `exitName` FAILED. EXIT DISABLED

Explanation: Loading of the specified user exit by Control-M/Tape failed.

This could be due to one of the following:

The installation is not using this user exit and erased the default exit supplied with Control-M/Tape.
IOA Load library is not in the load modules search list of the job (STEPLIB and Linklist).
There is insufficient storage to load the exit.
Another system-oriented reason. Check the MVS system log.
A security violation was attempted.

No user checking is performed for the rule order.

Corrective Action: Notify your INCONTROL administrator.

CTT006E MEMBER `memName` NOT FOUND IN LIBRARY `lib`

Explanation: The requested member is not found in the requested library. This message may occur when the CTTINIT procedure tries to load the rules according to the rules order list specified by the DARULLST DD statement.

The requested rule is not loaded.

Corrective Action: Correct the member or library name in the rules order list, and restart the CTTINIT procedure.

CTT007S INSUFFICIENT STORAGE IN (EXTENDED) CSA

Explanation: There is insufficient storage available in the Extended Common Service Area (CSA) to load Control-M/Tape modules or tables.

If the problem occurs during the initialization process, initialization stops. If the problem occurs during a reload function, Control-M/Tape will continue to work with the existing module or table.

Corrective Action: Check why there is insufficient CSA. You may need to contact your systems programmer. After correcting the problem, reload the table or restart Control-M/Tape as necessary.

CTT008W `dsn` DATASET FREESPACE SHORTAGE - `nn` % UTILIZATION

Explanation: The number of free records in the file is below the specified utilization nn% threshold that was set at installation.

Normal processing continues.

Corrective Action: Depending on the specified data set either:

Enlarge the file for the Media Database (MDB) or Stacking Database.
Run the MDB backup utility to recycle the space for the Trace file.

CTT009S TRC DATASET FULL - MDB BACKUP REQUIRED

Explanation: The Trace file is full; therefore, no Media Database (MDB) updates are allowed.

The Trace file keeps every update to the MDB, mainly for recovery purposes. When the Trace file becomes full, updates to the MDB are not allowed, since they may cause data to be lost. However, when a backup is made to the MDB, the Trace file data is no longer critical, so new MDB updates can overwrite old records in the Trace file.

The currently executing function stops.

Corrective Action: Run the MDB backup utility, then rerun the failed job.

CTT010E MEDIA `media` DOES NOT EXIST IN CTTPARM

Explanation: The specified media is not defined. All media names must be defined in the CTTPARM installation member.

The function that is currently executing stops.

Corrective Action: Either specify a media already defined in the CTTPARM member, or add the media name to CTTPARM.

CTT011I TRACE LEVEL IS TURNED OFF

Explanation: This information message indicates that the debug level of Control-M/Tape was turned off as a result of the TRACELVL=0 parameter.

Normal processing continues.

Corrective Action: No action is required.

CTT012S `action` FAILED FOR MODULE `modName`

Explanation: The specified action (LOAD, BLDL, FIND) for the modName module failed. During the Dynamic Interface Process, the modName module was not found in the STEPLIB library nor in SYS1.LPALIB.

The currently executing function stops.

Corrective Action: Ensure that the module exists in the STEPLIB or SYS1.LPALIB library.

CTT013S FUNCTION CATALOG NOT SUPPORTED IN THIS MVS RELEASE

Explanation: An attempt was made to catalog the data sets of an external volume, but the MVS release does not support IEFEB4UV. Cataloging of the data set failed because Control-M/Tape performs online cataloging of a data set of an external volume by means of the look up value of the unit name. IEFEB4UV, which retrieves this information, was not available in early versions of the operating system.

The ENTER command was issued to add an external volume to the Media Database. In addition, Y was entered in the MVS CATALOG field to catalog the data sets of the external volume. The ENTER command triggers both cataloging and adding of the volume to the Media Database, but the cataloging is performed before adding the volume.

The data sets are not cataloged, and the external volume is not added to the Media Database.

Corrective Action: To add the external volume, change the value in the MVS CATALOG field from Y to N.

CTT014W INVALID UNIT NAME `unitName` FOR MEDIA `media`

Explanation: The specified unit name is not defined in MVS tables. The specified media is defined in the CTTPARM installation member as unit unitName.

Normal processing continues.

Corrective Action: Check the media definition in the CTTPARM member.

CTT015I TRACE JOB IS SET TO `jobName`

Explanation: This information message indicates that since CTTINIT was started with the TRACEJOB parameter, the trace job of Control-M/Tape was assigned the name jobName. The trace job sets the job name for which trace messages, printed by some Control-M/Tape components, are issued.

Corrective Action: No action is required.

CTT016E PRINT LABEL ROUTINE FAILED. RC: `rc`

Explanation: The print label routine failed. This message is issued after control returns from the print label routine. The print label routine calls User Exit 9, which formats the label.

The print label routine issues one of the following return code values:

4 - Invalid return code. User Exit 9 returned an rc other than 0 or 4.
8 - Invalid label width. User Exit 9 set a label width that does not meet the 1 through 72 byte width restriction.
12 - Invalid label size. User Exit 9 set a label width and depth combination that exceeds the maximum print buffer size (2048 bytes).

Processing continues. The label is not printed.

Corrective Action: No action is required.

CTT017W CONTROL-M/TAPE IS NOT ACTIVE IN THE SYSTEM

Explanation: The Control-M/Tape real-time environment was terminated by operator request and is no longer active in the system.

No Control-M/Tape processing takes place.

Corrective Action: Check why Control-M/Tape was brought down, and if appropriate, start the CTTINIT procedure.

CTT018E INVALID REPLY: `reply`

Explanation: Control-M/Tape received an invalid reply to a WTOR message from the operator.

The WTOR message is issued again.

Corrective Action: Check the possible responses for the issued WTOR message, and respond to this message accordingly.

CTT019E SMS SUBSYSTEM ERROR: RC=`rc`, REASON= `rsn`

Explanation: An error was encountered when Control-M/Tape tried to interface with DFSMS.

Message variables are:

rc -- The DFSMS subsystem return code.
rsn -- The DFSMS subsystem reason code.

The Control-M/Tape to DFSMS cannot retrieve information from DFSMS.

Corrective Action: Call your INCONTROL administrator for assistance.

CTT020E CTT/SMS INTERFACE NOT ACTIVE

Explanation: Control-M/Tape tried to access DFSMS information as requested by a rule, but the interface to DFSMS is not active.

The requested function is not performed.

Corrective Action: Either remove the DFSMS reference from the Control-M/Tape rules (delete all ON MGMTCLAS rules) and the Control-M/Tape MDB records, or activate the Control-M/Tape SMS interface by setting SMSINTR to Y in the Control-M/Tape TCT table.

CTT021E SMS MANAGEMENT CLASS NOT FOUND

Explanation: The Management Class of a data set was not defined to DFSMS, and was probably deleted after the data set was created. When a data set is created, a Management Class is assigned to it.

Control-M/Tape cannot determine the data set expiration date.

Corrective Action: Define the Management Class in DFSMS, or update the data set record in the Control-M/Tape Media Database (MDB) and assign a Management Class to it.

CTT022E RULE APPLICATION FAILED. RC= `rc`, REASON= `int_diag, ret_rc, vault_rc`

Explanation: Control-M/Tape attempted to apply a rule to a data set or volume but the specified retention or vaulting information in not consistent with the relevant records in the Media Database.

The variables in this message are:

rc -- Rule return code. Possible values:
- 8 -- Insufficient memory.
- 12 -- Attempt to apply retention or vaulting information failed.
int_diag -- Internal diagnostic flags.
ret_rc -- Retention information application return code. Possible values:
- 4 -- Expiration date type not supported.
- 12 -- Internal error.
- 16 -- Expiration date is non-numeric.
vault_rc -- Vaulting information application return code. Possible values:
- 4 -- Expiration date type not supported.
- 8 -- Insufficient memory.
- 16 -- Expiration date is non-numeric.

If the message was issued by the Dynamic Dataset Stacking facility, the data set is not stacked. Otherwise, the retention and/or the vault pattern of the data set may be different from what was intended, because default retention may have been applied.

Corrective Action: Check the JCL EXPDT values for errors according to return codes, and do one of the following:

If the message indicates a memory problem, increase the region size for the job which issued the message.
If an invalid expiration date type was detected, check the values specified for the EXPDT parameter in the JCL DD statement.

If the problem persists, send a complete description of the problem to BMC Customer Support. Include the complete message, the job log of the problematic job, and a TI screen printout of the problematic volume and data set records.

CTT023E COULD NOT FIND FIELD `fieldName` FOR REQUESTED RECORD TYPE

Explanation: The user requested the display of an unrecognized field in the view definition of Media Database information on the z/OS console. Only fields that exist in the requested record type, volume or data set, can be specified. However, the specified field does not exist. The name may be misspelled.

The requested information is not displayed.

Corrective Action: Correct the field name in the view. For more information, refer to the Control-M/Tape chapter in the INCONTROL for z/OS Administrator Guide.

CTT046S BLDL/LOAD FAILED FOR THE MODULE " `modName` "

Explanation: Loading of the modName module failed.

Possible causes are:

The IOA Load library is not in the load modules search list (STEPLIB + Linklist).
There is insufficient memory.
There is some other system-oriented reason, which may be found in the syslog.

Execution might stop.

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

CTT050S UNABLE TO BUILD TCT, RC= `rc`

Explanation: The Control-M/Tape Control Table could not be built dynamically.

In this message, rc is one of the following:

8 - IOAPARM or CTTPARM load failed.
12 - GETMAIN failed.

The IOA Functional monitor is terminated.

Corrective Action: Do one of the following, depending on the return code:

If the return code is 8, check why the CTTPARM member or the IOAPARM member could not be loaded, and restart the Functional monitor.
If the return code is 12, increase the region size of the IOA Functional monitor, and restart the Functional monitor.

CTT051W STARTING TO READ RECORDS FROM END OF TRACE FILE

Explanation: The IOA Functional monitor did not find the check point for the last record that it processed from the Trace file.

This is normal when there were no actions recorded in the Trace file since the last request was processed, when the Trace file is empty, or it has been reformatted.

Processing of the IOA Functional monitor continues. Some of the last actions to be recorded in the Trace file before the error may not be performed.

Input records from the Control-M/Tape Trace file will be read starting from the last record in the Trace file.

Corrective Action: No action is required.

CTT070W ROUTINE `routineName` FAILED. RC= `rc`

Explanation: This message indicates that an internal error occurred in a certain routine. The significance of this error depends on the utility and the severity of the failure indicated by the return code (rc).

The variables in this message are:

routine -- Routine in which the error occurred.
rc -- Type of error.

Refer to the specific utility in the Control-M/Tape User Guide to determine whether processing continues or stops.

Corrective Action: Examine the return code of the utility when it stops, and proceed accordingly. If you cannot continue, refer the problem to the INCONTROL administrator.

CTT072I UTILITY `util` IS RUNNING IN {SIMULATION | R-SIMULATE} MODE

Explanation: This information message indicates that the specified Control-M/Tape utility is running in either simulation mode (SIMULATION) or simulation restart mode (R-SIMULATE).

Corrective Action: No action is required.

CTT073I *

Explanation: The asterisk in this message is positioned directly below the error in the previous CTT700I message to show the location of the error.

The utility stops.

Corrective Action: Remove or fix error and try again.

CTT074E SERVICE `svc` FAILED. RC= `rc`, REASON= `rsn`

Explanation: The specified external service called by the executing utility has failed. The executing utility returns return code rc and reason code rsn.

Possible values for the service (svc), return code (rc) and reason (rsn) are:

Value	Explanation
TCTLOAD
8	Cannot load CTTPARM or IOAPARM
12	Insufficient region
INITPARS
36	Insufficient region
INITINC
8	Insufficient region
36	Insufficient region
BLDINC
8	Too many INCLUDE statements
16	Invalid value passed in INCLUDE statement
20	<, > not allowed in this context
24	Invalid value for a date field
28	Invalid format in a date field
CTTRBD
4	RETRY scheduled
8	DD statement missing or open error
12	Load failed for one of the following modules: CTTX008, automated tape library interface exit (for example, if you set RBTTYPE to SMST/IBMT in the CTTPARM member, make sure exit CTTOAM has been compiled and exists in the IOA.load library)
14	Error returned from automated tape library interface exit
16	Internal. Contact BMC Customer Support
20	Internal. Contact BMC Customer Support
24	Error in ATL interface
28	Contradicting volume status in the media database
32	Internal. Contact BMC Customer Support
36	I/O error accessing media database
Other	Program or system error

The utility stops execution.

Corrective Action: Correct the problem according to the reason listed in the table above and rerun the utility. If you cannot correct the problem, contact BMC Customer Support.

CTT075E DUPLICATE USE OF {STATEMENT | KEYWORD} { `stmt|keywd` }

Explanation: A utility encountered duplicate use of a stmt statement or keywd keyword. The statement or keyword listed in the message can only be specified once.

The utility stops execution.

Corrective Action: Remove the extraneous statement or keyword.

CTT076E MANDATORY {STATEMENT | KEYWORD} { `stmt|keywd` } IS MISSING

Explanation: The stmt statement or keywd keyword is mandatory, but was not found in the input to the executing utility. The stmt statement or keywd keyword does not have a default, and must be specified to the utility.

The utility stops execution.

Corrective Action: Specify the required statement or keyword in the input to the utility.

CTT077E NO KEYWORDS FOUND

Explanation: A utility encountered a statement for which no keywords were specified. The statement listed in a previous message must have at least one keyword specified.

The utility stops execution.

Corrective Action: The statement was probably specified incorrectly. Check the syntax and make sure that the appropriate keywords are used for this statement.

CTT078E INVALID VALUE SPECIFIED FOR KEYWORD `keywd`

Explanation: An invalid value was specified for one of the keywords in the input to a utility.

In this message, keywd is the keyword with the problematic value

The utility stops execution.

Corrective Action: Fix the value of the specified keyword and rerun the utility.

CTT079E INVALID OR UNKNOWN {STATEMENT | KEYWORD}

Explanation: A utility encountered an invalid statement or keyword. The previous CTT700I message specifies the line in which the error occurs.

The utility stops.

Corrective Action: Check earlier messages for more information. Then, remove or fix the invalid statement or keyword, and try again.

CTT080W VOLUME (`volser`) EXCLUDED FROM OPERATION TO PREVENT MDB INTEGRITY ERRORS

Explanation: The CTTSPL utility encountered a request to COPY or MOVE a volume (the volser volume) that is part of a chain.

If a volume is removed from a chain, the MDB is corrupted. If the copied volume is MERGEd into another MDB, the MDB into which it is merged is also corrupted.

The volser volume is excluded from the COPY or MOVE operation. The utility continues processing.

Corrective Action: BMC recommends that you do one of the following:

When ordering a MOVE or COPY operation, ensure that you do not specify any volume that is part of a chain.
If you must perform a MOVE or COPY operation on a volume that is part of a chain, ensure that all the volumes in the chain are specified.

CTT084I NO REPORT STATEMENT SUPPLIED. REPORT NOT GENERATED.

Explanation: There is no REPORT statement for the utility.

The utility continues processing, but no report is displayed.

Corrective Action: No action is required.

CTT085I `num` RULES GENERATED

Explanation: This information message is displayed when the CTTSCA utility finishes processing. During the search for tape contentions, the CTTSCA utility generated num rules to prevent detected contentions from happening in the future. Rules created by the CTTSCA utility prevent data sets that should be processed simultaneously, from being stacked on the same volume.

For more information about the CTTSCA utility, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTT086I `num` POSSIBLE CONTENTIONS DETECTED

Explanation: This information message is displayed when the CTTSCA utility finishes processing. During the search for tape contentions, the CTTSCA utility detected num possible contentions. Any two data sets processed simultaneously are considered in possible contention, if at least one of them was opened for OUTPUT. This message is accompanied by message CTT085I.

For more information about the CTTSCA utility, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTT087I num STACKABLE DATASETS FOUND

Explanation: This information message is displayed when the CTTSTKR utility finishes processing. It indicates that num data sets were identified as stackable by the CTTSTKR utility.

For more information about the CTTSTKR utility, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTT088E INVALID OR UNKNOWN {STATEMENT | KEYWORD} ON LINE `lineNum`, COLUMN `col_num` OF ABOVE STATEMENT

Explanation: A utility encountered an invalid statement or keyword. This message follows message CTT700I, and specifies the line and column in which the error occurred.

The utility stops.

Corrective Action: Remove or fix the invalid statement or keyword and try again.

CTT096E SCRATCH VOLUME, BUT LAST LABEL NUMBER IS NOT ZERO

Explanation: A non-specific (scratch) request was made, but the volume that was mounted is unsuitable for one of the following reasons:

The volume already contains one or more active data sets.
The volume status is incorrectly set.
The last data set number on the scratch volume is greater than zero.

The specified volume is rejected and another volume is requested.

Corrective Action: Mount a scratch volume.

CTT098E TAKING LOCK OF ASVT BY FORCE

Explanation: An error was encountered while the Control-M/Tape real-time environment was trying to synchronize between subtasks of the same address space.

One of the subtasks of the address space is granted access to one of the Control-M/Tape control blocks without synchronizing this access with the other subtasks.

Corrective Action: Call your INCONTROL administrator for assistance.

Messages CTT100 through CTT1xx

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

CTT100A `msgText`

Explanation: A tape mount request was detected. This MVS message is displayed when waiting for a tape to be mounted. The tape can be specific or nonspecific (scratch). This message may contain additional information added by means of the MSGFMT parameter defined in the CTTPARM member.

The message ID was changed from the original MVS message ID by means of the CNGMSGID parameter in the CTTPARM member. The original IBM message ID was IEC101A, IEC501A/E, or IEF233A/D. See the appropriate IBM documentation for more information.

Corrective Action: Mount the requested tape.

CTT101A `msgText`

Explanation: A request was made to mount a scratch tape from a specific pool. This MVS message is displayed when waiting for a nonspecific (scratch) tape with the volser field containing a specific pool name, instead of SCRTCH or PRIVAT, to be mounted.

Corrective Action: Mount a tape from the requested pool.

CTT102A `msgText`

Explanation: A request was made to remove the specified volume from the tape device. This MVS KEEP message is displayed when the tape must be removed. This message may contain additional information added by means of the MSGFMT parameter defined in the CTTPARM member.

The message ID changed from the original MVS message ID by means of the CNGMSGID parameter in the CTTPARM member. The original IBM message ID was IEC111E, IEC502E, or IEF234E. See the appropriate IBM documentation for more information.

Corrective Action: Remove the specified volume from the tape device.

CTT103A `msgText`

Explanation: A request to mount a tape was detected. This JES3 message is displayed when waiting for a tape to be mounted. The tape can be specific or nonspecific (scratch). This message may contain additional information added by means of the MSGFMT parameter defined in the CTTPARM member.

The message ID was changed from the original JES3 message ID by means of the CNGMSGID parameter in the CTTPARM member. The original message ID was IAT5210.

Corrective Action: Mount the requested tape.

CTT104A `msgText`

Explanation: A request was made to mount a scratch tape from the specified pool. This JES3 message is displayed when waiting for a nonspecific (scratch) tape with the volser field containing a specific pool name, instead of SCRTCH or PRIVAT, to be mounted.

The message ID was changed from the original JES3 message ID by means of the CNGMSGID parameter in the CTTPARM member. The original message ID was IAT5210.

Corrective Action: Mount a tape from the requested pool.

CTT105A `msgText`

Explanation: A request was made to remove the specified volume from the tape device. This JES3 KEEP message is displayed when a tape must be removed. This message may contain additional information added by means of the MSGFMT parameter defined in the CTTPARM member.

The message ID was changed from the original JES3 message ID by means of the CNGMSGID parameter in the CTTPARM member. The original message ID was IAT5410.

Corrective Action: Remove the specified tape from the tape device.

CTT106S INTERNAL ERROR IN CONTROL-M/TAPE SVC. CODE: `rc`

Explanation: An internal error occurred during Control-M/Tape real-time processing.

The job or task is abended.

Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.

CTT107E `unit`, FILES WITH HIGHER SEQUENCE NUMBERS EXIST ON VOLUME `volser` (`ddName`, `seqNumber`)

Explanation: An attempt was made to write a file with sequence number seqNumber on a tape volume while another data set with a higher file sequence number exists on the volume.

The job is abended.

Corrective Action: Correct the JCL and rerun the job.

CTT108E `unit`, PREVIOUS FILE DOES NOT EXIST ON VOLUME `volser` (`ddName`, `seqNumber`)

Explanation: An attempt was made to write a file with a specified sequence number (seqNumber) on a tape volume but the preceding file sequence number does not exist on the volume.

The job is abended.

Corrective Action: Correct the JCL and rerun the job.

CTT109E `unit`, CONFLICT WITH MDB DSN: `dsn` (`volser, seqNumber`)

Explanation: An attempt was made to read a data set with a different name than the name (dsn) recorded in the Control-M/Tape MDB.

The job abends.

Corrective Action: Correct the JCL and rerun the job.

CTT110E `unit`, DATASET NOT FOUND IN MDB: `dsn` (`ddName`)

Explanation: An attempt was made to read a data set that is not in the Control-M/Tape database, and dynamic data set definition is not allowed (DYNDS is set to N in the CTTPARM member).

The job is abended.

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

CTT111E `unit`, JOB FAILED BY USER EXIT #3 (`ddName`)

Explanation: An abend was requested from local exit #3.

The job is abended.

Corrective Action: Notify your system programmer.

CTT112A `unit`, `jobName`, VOLUME `volser` NOT IN MDB. REPLY Y - DEFINE, E - EXTERNAL, I - IGNORE OR N - `action`

Explanation: A mount request was issued for a volume (VOLSER) that is unknown to Control-M/Tape. The specified volume is probably not on-site. This message is issued only if the DYNVOL parameter is set to P (Prompt) in the CTTPARM member.

The jobName job waits for a reply.

Corrective Action: Reply with one of the following values:

Y - Control-M/Tape dynamically defines the volume in its database.
E - Control-M/Tape dynamically defines the volume in its database. The volume will be marked as External.
I - This volume and its data sets should be ignored, as if EXPDT=98000 was specified in the JCL. This value is not available for the first volume in a chain and for single volumes which are not part of a chain.
N - If this is a specific tape request, the job is abended. If this is a nonspecific tape request, the volume is rejected and a new volume is requested.

CTT113A `unit`, `jobName`, VOLUME `volser` IN VAULT `vault`. REPLY U - USE OR A - ABEND

Explanation: The database indicates that the volume (volser) requested for mounting is in a remote vault, and the mount request is probably a user error.

Job jobName waits for a reply.

Corrective Action: Reply with one of the following values:

U - Control-M/Tape should allow the job to continue. Information will be recorded as usual, but the volume status remains vaulted.
A - The program should abend.

CTT114A `unit`, ENTER VOLSER FOR {NL | BLP} REQUEST

Explanation: A tape without a label is mounted on the specified unit. This message requires confirmation that the correct volume is mounted, since there is no label information.

Control-M/Tape waits for a reply.

Corrective Action: Specify the VOLSER of the volume mounted on the unit. If this is the same VOLSER as that specified in the user JCL, the job continues normally. Otherwise, after another confirmation, the volume is rejected and the correct volume is requested.

See the section that describes the NL and BLP options for volume processing in the chapter on organization and administration of the Control-M/Tape User Guide.

CTT115S INVALID RETURN CODE (`rc`) FROM USER EXIT `exit_num`

Explanation: An invalid return code was returned from the specified exit. The exit in this message can be Exit 3, 4, or 5. The return code (rc) was not in accordance with the documented interface.

If the invalid return code was sent by Exit 4, the job continues. If the invalid return code was sent by either Exit 3 or Exit 5, the job abends.

Corrective Action: Have your system programmer check the specified exit.

CTT116S ABEND IN USER EXIT `exit_num`

Explanation: The exit_num user exit abended.

The job is abended.

Corrective Action: Have your system programmer check the specified exit.

CTT117S ABEND IN MODULE `modName`, E.P: `add` OFFSET: `offset`

Explanation: An abend occurred in the Control-M/Tape real-time environment. This message identifies the module, its entry point, and the offset of the error.

The job is abended.

Corrective Action: Notify BMC Customer Support.

CTT118E `unit`, FILE ALREADY EXISTS: `dsn` (`ddName`)

Explanation: An attempt was made to overwrite an existing data set with a different name than its current name (dsn). A recreate was requested for a DSNAME on a label that has a different DSNAME than the requested DSNAME.

The job is abended.

Corrective Action: To recreate, correct the JCL and rerun.

CTT119E `unit`, RECREATE WITH DISP=NEW: `dsn` (`ddName`)

Explanation: An attempt was made to recreate an existing data set with DISP set to NEW. Recreate is permitted only with DISP set to OLD.

The job is abended.

Corrective Action: If recreate is desired, correct the JCL and rerun.

CTT120E `unit`, RECREATE ON A PERMANENT DATASET: `dsn` (`ddName`)

Explanation: An attempt was made to recreate a data set with Permanent retention. Recreate is permitted only with other types of retention.

The job is abended.

Corrective Action: If recreate is desired, change the retention specification of this data set.

CTT121I LAST CHKPT IN SVC: `svc` INTERCEPT: `id` RELEASE: `ver` LEVEL: `lev`

Explanation: This information message identifies the last checkpoint in the Control-M/Tape real-time environment module, and may be accompanied by additional messages.

The variables in this message are:

svc -- Last checkpoint reached before the service interruption.
id -- Function internal ID.
ver -- Version number of the currently installed Control-M/Tape.
lev -- Level number of the Control-M/Tape real-time environment module.

Corrective Action: Look for previous error or warning messages.

CTT122E `unit`, NON-POOL REQUEST RECEIVED VOLUME `volser` FROM POOL: `poolName`

Explanation: A nonspecific request (scratch request) received a volume from the indicated pool although the request was for a non-pool volume.

The volume is rejected and another volume is requested.

Corrective Action: Mount a scratch volume which is not part of a pool or check the DO POOL statement in the matching rule.

CTT123E `unit`, NON-POOL VOLUME `volser` FOR POOL REQUEST: `poolName`

Explanation: A nonspecific request (scratch request) for the specified pool received a volume that does not belong to any pool.

The volume is rejected and another volume is requested.

Corrective Action: Mount a scratch volume from the specified pool.

CTT124E `unit`, REQUEST FOR POOL `poolName` RECEIVED VOLUME `volser` FROM POOL `poolName`

Explanation: A nonspecific request (scratch request) for the specified pool received a volume from another pool.

The volume is rejected and another volume is requested.

Corrective Action: Mount a scratch volume from the correct pool.

CTT125E `unit`, `volser` NOT A SCRATCH VOLUME

Explanation: A nonspecific (scratch) request on the specified unit received a non-scratch volume.

The specified volume is rejected and another volume is requested.

Corrective Action: Mount a scratch volume.

CTT126E `unit`, `volser` MARKED DELETED

Explanation: A nonspecific request (scratch request) on the specified unit received a volume which is marked as deleted (out of service).

The specified volume is rejected and another volume is requested.

Corrective Action: Mount another scratch volume.

CTT127I `unit, volser`, TEMPORARY DATASET (`ddName`)

Explanation: This information message indicates that a temporary data set is being written on the specified volume.

Corrective Action: Return the volume to the scratch pool right after its use.

CTT128E `ddName` INVALID EXPDT VALUE `expdt`. RC: `rc`

Explanation: An invalid expiration date (EXPDT) was specified in the JCL. Usually this message is caused by setting EXPDT to 970 xx, which is not supported by Control-M/Tape.

The variables in this message are:

ddName - the DD statement that contains the invalid date
expdt - the invalid expiration date
rc - the return code

Possible values for rc are:

4 - expiration date type not supported
16 - expiration date in an invalid format, such as
nonnumeric
yy000
yyyy/000

The EXPDT value is ignored and the data set is given a default retention.

The EXPDT value is expressed in internal format.

Corrective Action: No action is required.

CTT129I `unit`, VOLUME `volser` IN {LOCAL VAULT: `vaultName`, SLOT: `slotNumber|` OUT LOCATION: `loc` }

Explanation: This information message indicates that the tape requested for mounting (volser) is located in the specified location.

Corrective Action: No action is required.

CTT130E `unit`, VOLUME `volser` NOT IN MDB

Explanation: The specified volume is not defined in Control-M/Tape's Media database. Possible causes are:

Dynamic Volume Definition is disabled (DYNVOL is set to N in the CTTPARM member).
N (Abend) reply to message CTT112A.

Corrective Action: Specify EXPDT=98000 in the JCL, or define the volume in the Media database using CTTDLD utility, and rerun the job.

CTT131W `unit`, VOLUME `volser` IN USE BY JOB `jobName`

Explanation: The indicated volser is marked in use by the specified job. Possible causes are:

A system or program crash left the 'in use' indicator turned on. This occurs when a data set being written does not go through a complete CLOSE process. In this case, the volume remains 'in use'. For example, in the case of a system abend 837, when a demount has occurred for a multi-volume data set but a new mount is disallowed because the file is on more than the maximum number of volumes, a full CLOSE will not occur, and the volume remains 'in use'. In most cases, a cancel command will cause CLOSE processing to occur, but it depends on exactly when the job was canceled. The IEC205I message in the job log will indicate that the job went through a full CLOSE process.
During online stacking processing, the 'in-use' bit is temporarily set to prevent other jobs from allocating the volume while online stacking is examining the specific volume.

Corrective Action: Do the following:

To reset this bit, run the CTTIDB utility in repair mode.
Then run the CTTMUP utility to perform the repair.

CTT132E `unit`, EDM TRYING TO WRITE ON NON-EDM VOLUME `volser`

Explanation: An EDM (External Data Manager) is trying to write a data set on a non-scratch volume which is not marked as an EDM Volume. An EDM can only write data on scratch volumes afterwards marked as EDM Volumes, or non-scratch volumes already marked as EDM Volumes.

The job is abended.

Corrective Action: Check the rules regarding EDM. Verify that they have not been changed in a way that caused this problem.

CTT133E `unit`, NON-EDM TRYING TO WRITE ON EDM VOLUME `volser`

Explanation: A job that is not an EDM (External Data Manager) is trying to write on a volume that is marked as an EDM Volume. Only an EDM is allowed to write on volumes that are marked as EDM Volumes.

The job is abended.

Corrective Action: Correct the job and rerun.

CTT134A `unit, jobName,` CONTROL-M/TAPE ENVIRONMENT DOES NOT EXIST. REPLY A - ABEND, R - RETRY OR U - CONTINUE

Explanation: A job is trying to process data on tape, while the Control-M/Tape real-time environment does not exist or is still initializing. Control-M/Tape real-time environment is started by the CTTINIT procedure. No tape processing is allowed while Control-M/Tape is down, unless Control-M/Tape MVS intercepts are disabled.

The job waits for a reply.

Corrective Action: Reply with one of the following values:

A -- Abend this job.
R -- Retry to find Control-M/Tape environment. This option enables you to start CTTINIT and then reply Retry.
U -- Bypass Control-M/Tape for the processing of this data set. In this case, Control-M/Tape does not record or protect any information affected by this job while processing this data set.

CTT135A `unit`, `jobName`, 98000 REQUEST FOR MDB VOLUME `volume`, REPLY ‘U’ - IGNORE, ‘A’ - ABEND OR ‘F’ - FORCE

Explanation: A job specified EXPDT=98000, Control-M/Tape bypass, for a controlled volume. Specifying EXPDT=98000 for a controlled volume is not recommended, because Control-M/Tape cannot enforce data integrity.

The job waits for a reply.

Corrective Action: Reply with one of the following:

U -- Continue. Ignore the bypass request.
A -- Abend the job.
F -- Bypass Control-M/Tape for processing of this data set. In this case, Control-M/Tape does not record or protect any information affected by this job while processing this data set.

CTT136E `unit`, `volser` MARKED IN AN OUT LOCATION

Explanation: The operator mounted a volume marked “out of the library” in response to a request to mount a scratch tape.

The volume is rejected. The operator is prompted to mount another volume.

Corrective Action: Mount a scratch tape.

CTT137S CSECT IN ERROR `csect`, EP: `add` OFFSET: `offset`

Explanation: An abend occurred in one of the Control-M/Tape real-time environment modules. This message identifies the CSECT in the module, its Entry Point, and the offset of the error. This message follows message CTT117S.

The job abends.

Corrective Action: Notify BMC Customer Support.

CTT138W `unit`, DATASET BYPASSED. REASON: `rsn` VOLUME: `volser`

Explanation: Control-M/Tape is bypassing the data set on the specified volume. As a result of this bypass, no information regarding this data set is recorded in the MDB.

Valid values for rsn are:

rsn	Explanation
LBL-ERR	An invalid label was used when accessing a SL tape in the Media Database (MDB). For example, a tape, identified as SL in the MDB, was accessed using BLP.
READBACK	The data set is read backward (READBACK processing).
RULE-REQ	A Control-M/Tape rule requested that this data set be bypassed by setting DO BYPASS to Y.
VOLMISS	The specified volume was not controlled by Control-M/Tape and either: the DYNVOL parameter is set to I (ignore) in either the CTTPARM member or a rule. or the user answered message CTT112A with I (ignore). This reason is also given if User Exit CTTX004 was used to temporarily override the setting for the DYNVOL parameter.
UX03	User Exit CTTX003 requested that this data set be bypassed.
UX05	User Exit CTTX005 requested that this data set be bypassed.

The job continues without Control-M/Tape involvement.

Corrective Action: No action is required.

CTT139I `unit`, VOLUME `volume` DYNAMICALLY DEFINED

Explanation: The specified volume was dynamically defined in the Media Database by Control-M/Tape. This volume was not known to Control-M/Tape before this job. The DYNVOL installation parameter determines whether or not such volumes will be defined dynamically.

The job continues.

Corrective Action: No action is required.

CTT140E `unit`, SPECIFIC REQUEST FOR SCRATCH VOLUME `volume` DENIED (`ddName`)

Explanation: A job attempted to access a scratch volume by specifying the volser of this volume. The SCRPROT Installation parameter determines whether a scratch volume is protected from specific access. This message may occur when VOL=REF= value is specified, or when a double open occurs in the same step that acts as a specific request, even though the JCL was for a nonspecific request.

The job is abended.

Corrective Action: Change the JCL as required. If a scratch volume is required, remove the parameter VOL=SER= value or VOL=REF= value.

CTT141E `unit`, RECREATE ON WRONG VOLUME `vol`

Explanation: A job attempted to recreate a data set that already exists on the vol volume, but the data set does not start on the volume. Data sets can only be recreated on the same volumes they were on before, and in the same order.

The job is abended.

Corrective Action: Change the JCL as required.

CTT142I IA= `instruction_addr` SVCA= `svc_addr` COMP CODE= `complected`

Explanation: This information message supplies additional details relating to the abend that occurred, and may be accompanied by additional messages.

The variables in this message are:

instruction_addr -address of the abend
svc_addr - Control-M/Tape real-time environment module address
complCode - abend code

Corrective Action: Look for previous error or warning messages.

CTT143E `jobName,` TASK IS ABENDED BY CONTROL-M/TAPE (`rsn`)

Explanation: Control-M/Tape abended the jobName task. The cause of the abend is explained in a message that precedes this message, which is indicated by the value of rsn.

The following are the possible values of the reason code (rsn), and the related preceding message for each:

rsn	Explanation
4	Invalid intercept code. See CTT106S.
8	ESTAE failed. See CTT106S.
12	GETAST failed. See CTT106S.
16	RBA of the volume is missing. See CTT106S.
20	RBA of data set is missing. See CTT106S.
24	Message routine failed. See CTT106S.
28	Previous file does not exist. See CTT108E.
32	Data set name conflict with MDB data set name. See CTT109E.
36	Volume not in MDB. See CTT130E.
40	Data set not in MDB. See CTT110E.
44	Job failed by User Exit 3. See CTT111E.
48	Open failed for MDB. See CTT200S.
52	Close failed for MDB. See CTT200S.
56	GETMAIN error.
60	Recreate with DISP set to NEW. See CTT119E.
64	Volume is in a remote vault. See CTT113A.
68	File already exists. See CTT118E.
72	Bad RC from user exit. See CTT115S.
76	Abend in user exit. See CTT116S.
80	Recreate on a permanent data set. See CTT120E.
84	Control-M/Tape environment does not exist. See CTT134A.
88	Control-M/Tape is suspended. See CTT150A.
92	Invalid file sequence. See CTT107E.
96	Retry after abend in test mode.
100	Volume is not scratch. See CTT125E.
104	DYNVOL is set to I (Bypass), but an attempt was made to access a controlled volume. See CTT149E.
108	9800 request denied. See CTT135A.
112	MDB error. See CTT200S.
124	EDM tries to write on non-EDM. See CTT132E.
128	Non-EDM tries to write on EDM. See CTT133E.
156	Specific request for a scratch volume. See CTT140E.
160	Recreate on the wrong volume. See CTT141E.
168	Job started before Control-M/Tape set active. See CTT144E.
172	Access denied by User Exit 6. See CTT145E.
180	An attempt was made to run a utility of Control-M/Tape 6.0.01 or later while an earlier version of Control-M/Tape was active.
192	Recreate disabled by installation. See CTT148E.
228	Volume not found during MVS/RESTART.

The task is abended. Control-M/Tape does not record any information on this tape data set.

Corrective Action: Do one of the following:

If rc = 56, increase the region size.
If rc = 180, stop the earlier version of Control-M/Tape, and rerun the 6.0.01 or later version of the utility.
If rc = 228, note the contents of the job log and contact BMC Customer Support.
In all other cases check the preceding message to understand why this message was issued, and proceed accordingly.

CTT144E `unit,` CONTROL-M/TAPE WAS NOT ACTIVE WHEN JOB STARTED

Explanation: Either Control-M/Tape was not active when the job started to run, or Control-M/Tape was brought down and up while the job was running. If there is any tape activity in the system, Control-M/Tape must be active.

The job is abended, unless Control-M/Tape is in Test mode.

Corrective Action: Rerun the job when Control-M/Tape is active.

CTT145E `unit`, ACCESS DENIED TO {VOL: `volser|` DS: `dsn` }

Explanation: Permission to access the specified volume or data set was denied by the Control-M/Tape security exit.

The job is abended.

Corrective Action: If you think you should have access to this volume or data set, contact your security administrator.

CTT146I `unit`, JOB CONTINUES DUE TO TEST MODE (`rsn`)

Explanation: This information message indicates that a job that probably would have abended in PROD or PHASED mode continues processing because the job is running in TEST mode. The cause of the abend is explained in a message that precedes this message, which is indicated by the value of rsn.

The following are the possible values of the reason code (rsn) and the related preceding message for each:

rsn	Explanation
4	Invalid intercept code. See CTT106S.
8	ESTAE failed. See CTT106S.
12	GETAST failed. See CTT106S.
16	RBA of the volume is missing. See CTT106S.
20	RBA of the data set is missing. See CTT106S.
28	Previous file does not exist. See CTT108E.
32	Data set name conflict with MDB data set name. See CTT109E.
36	Volume not in MDB. See CTT130E.
40	Data set not in MDB. See CTT110E.
44	Job failed by user exit 3. See CTT111E.
48	Open failed for MDB. See CTT200S.
52	Close failed for MDB. See CTT200S.
56	GETMAIN error.
60	Recreate with DISP=NEW. See CTT119E.
64	Volume is in a remote vault. See CTT113A.
68	File already exists. See CTT118E.
72	Bad RC from User Exit. See CTT115S.
76	Abend in user exit. See CTT116S.
80	Recreate on a permanent data set. See CTT120E.
92	Invalid file sequence. See CTT107E.
100	Volume is not scratch. See CTT125E.
112	MDB error. See CTT200S.
124	EDM tries to write on non-EDM. See CTT132E.
128	Non-EDM tries to write on EDM. See CTT133E.
156	Specific request for a scratch volume. See CTT140E.
160	Recreate on the wrong volume. See CTT141E.
168	Job started before Control-M/Tape set active. See CTT144E.
172	Access denied by User Exit 6. See CTT145E.
192	Recreate disabled by installation. See CTT148E.
228	Volume not found during MVS/RESTART.

The job continues processing, but Control-M/Tape does not record any more information related to the job.

Corrective Action: No action is required.

CTT147W `unit`, VOLUME `volser` MARKED DELETED. JOB CONTINUES

Explanation: The specified volume is marked as deleted might be a physically damaged volume.

Since the job specifically requested this volume, the job continues.

Corrective Action: Check why the volume is marked as deleted, and determine if you want the job to continue processing.

CTT148E `unit`, RECREATE DISABLED BY INSTALLATION PARAMETERS (`ddName`)

Explanation: An attempt was made to recreate a data set, and N was specified for the RECREATE installation parameter in the CTTPARM member.

The job is abended.

Corrective Action: If you wish to enable recreation of data sets, contact your INCONTROL administrator.

CTT149E `unit`, `jobName`, BYPASS ATTEMPT ON MDB VOLUME `volser` [{SCRATCH | ACTIVE},{R | W}]

Explanation: Job (jobName) tried to access a volume from the Media Database (MDB), while under a Control-M/Tape bypass. Control-M/Tape bypassed the first volume that the executing task accessed, because it was not in the MDB. When the executing task tried to access a later volume that was in the MDB, Control-M/Tape disabled access by the executing task to the volume, and issued this message.

For security reasons Control-M/Tape requires that when DYNVOL is set to I, if the first volume accessed by the task is not in the MDB, the rest of the volumes accessed by the task must not appear in the MDB either.

This message is issued when:

The DYNVOL parameter is set to I in CTTPARM, or User Exit 4 (Dynamic Definition exit) selected DYNVOL set to I;
The first volume accessed by the executing task is not in the MDB, and any volumes that the executing task accesses later are in the MDB.

The system action depends on how the volume was requested.

If the task requested this specific volume, the task is abended.
If the volume was mounted in response to a nonspecific mount request, it is rejected, and another scratch tape is requested instead.

Corrective Action: Do one of the following, depending on how the volume was requested.

If this is a request for this specific volume, verify that all or none of the volumes to be accessed are defined in the MDB.
If this is a nonspecific tape request, either mount a non-MDB volume, or have the job restarted using only MDB volumes.

CTT150A `unit, jobName,` CONTROL-M/TAPE ENVIRONMENT IS SUSPENDED. REPLY A-ABEND, R-RETRY OR B-BYPASS

Explanation: A job attempted to process data on a tape, while the Control-M/Tape real-time environment was suspended. The Control-M/Tape real-time environment was suspended by the MODE=SUSPEND statement in the CTTINIT procedure. While Control-M/Tape is suspended, no tape activity is allowed.

The job waits for a reply.

Corrective Action: Specify one of the following operator responses:

A - Abend the job or task.
R - Recheck the status of the real-time environment. This enables you to reset Control-M/Tape to status ACTIVE using statement MODE=RESUME in the CTTINIT procedure, before specifying this operator response. Before resetting the status of Control-M/Tape, determine why SUSPEND mode was requested and whether or not you can reset the mode at this time.
B - Bypass Control-M/Tape for the processing of this data set. In this case, Control-M/Tape does not record or protect any information affected by this job while processing this data set.

CTT151I `unit`, VOLUMES `volser1`, `volser2` CHAINED ON INPUT

Explanation: This information message indicates that a job successfully read a data set that spans volumes volser1 and volser2, but volume volser2 was a scratch tape.

Control-M/Tape automatically changes the status of the scratch tape (volser2) to ACTIVE and updates the necessary pointers in the volume record so that volser2 is joined in a multivolume chain to volser1.

Corrective Action: No action is required.

CTT152W `unit`, VOLUMES `volser1`, `volser2` ARE NOT FROM THE SAME GROUP

Explanation: A job is reading a data set from volumes volser1 and volser2 as if they belong to the same volume group. However these volumes are recorded in the Media Database as belonging to two different multivolume chains. The information recorded in the Media Database might not reflect the real status of the two volumes.

This error message may also occur while running Control-M/Tape in TEST mode, as a result of differences between Control-M/Tape and the other tape management system.

The job continues processing.

Corrective Action: Check the volumes specified in this message (volser1 and volser2) and their definitions in the Media Database to determine why this message was issued.

CTT153E `unit`, MOUNT REQUEST FOR VOLUME `volser` RECEIVED A VOLUME WITH SL-NAME `slName1` WHERE `slName2` EXPECTED

Explanation: The SL-NAMEs on the mounted tape (slName1) is different from the one listed in the Media Database for this volser (slName2). Probably a different tape from the one requested was mounted.

The tape is rejected.

Corrective Action: Mount the requested tape. The volser specified in this message should appear on the gummed (external) label.

CTT154I `unit`, RESTART IN PROGRESS FOR VOLUME `volser`

Explanation: This information message indicates that the job in process was restarted from volume volser by means of the MVS/RESTART feature.

Corrective Action: No action is required.

CTT155E `unit`, RESTART FAILED, SELECT A-ABEND, B-BYPASS

Explanation: During tape processing done under MVS/RESTART, Control-M/Tape encountered errors. Since MVS/RESTART is in process, the current status of the volumes or data sets may be different from the status expected by Control-M/Tape.

The errors encountered are described in the messages that precede this message.

The job waits for a reply.

Corrective Action: Reply with one of the following:

A - Abend the job or task.
B - Bypass Control-M/Tape for the processing of this data set. In this case, Control-M/Tape does not record or protect any information affected by this job for while processing this data set.

CTT156W `unit`, {IOA FUNCTIONS | SMS RULES} PROCESSING IS INHIBITED

Explanation: Control-M/Tape can no longer process IOA functions or SMS rules, due to a problem described in the messages preceding this message. IOA functions mentioned in the message refer to DO statements that call IOA functions, for example, DO COND, DO RESOURCE and DO SET.

The job continues without using the specified feature , which is IOA functions or SMS rules.

Corrective Action: Check preceding messages for the reason for this error and correct the problem accordingly.

CTT157W `unit`, AUTOMATIC CARTRIDGE LOAD DISABLED (`n` CONSECUTIVE REJECTS)

Explanation: Tapes mounted on the specified unit after a nonspecific mount request, were rejected n consecutive times. Control-M/Tape found that the mounted tape did not satisfy the request requirements. For example, the tape may not be from the requested scratch pool. As a result, it rejected the tape, and issued the mount message again. This process repeated itself n times, after which Control-M/Tape stopped the automatic load process on the specified unit.

Control-M/Tape disables the automatic load process for the specified unit until a tape that satisfies the mount request requirements is mounted manually.

Corrective Action: Have the operator mount tapes that satisfy the mount request requirements.

CTT158E `unit_addr`, DENSITY OF VOLUME `volser` IS NOT COMPATIBLE WITH THE DEVICE

Explanation: Volume volser that was mounted for output on unit_addr has a density that is not compatible with the device. This message is issued only when CNGDENS is set to Y in CTTPARM.

The specified volume is currently recorded with a density lower than the density about to be used by the device (for example, a 3480 volume mounted for output on a 3490E device). When CNGDENS is set to N in CTTPARM, Control-M/Tape allows higher density recording on the volume, making it no longer usable on lower density devices. However, since CNGDENS was set to Y in CTTPARM, Control-M/Tape does not allow higher density recording on the volume.

The volume is rejected from the device and a mount message is issued.

Corrective Action: Mount a scratch volume with a compatible density.

CTT159W `jobName`, PROCESS STOPPED DUE TO {CANCEL | DETACH | ABEND IN ANOTHER TASK}

Explanation: A task was running under the Control-M/Tape real time environment module, and Control-M/Tape needed to stop execution of the task. The reason is one of the following:

CANCEL - The job was canceled.
DETACH - A different task caused the Control-M/Tape task to DETACH.
ABEND IN ANOTHER TASK - A different task abended, and therefore the Control-M/Tape task abended as well.

Corrective Action: If the reason is CANCEL, ignore the message. Otherwise, use the dump to understand which task abended, since Control-M/Tape is not the reason for the abend.

Messages CTT200 through CTT2xx

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

CTT200S `operation` FAILED FOR `logical_ds` DATASET. RC= `rc`, REASON= `ic_rsn`

Explanation: The specified operation against the logical data set logical_ds failed.

Valid values for logical_ds are shown in the following table:

logical_ds	Description
MDBD	Media database data file
MDBI	Media database index file
STKD	Stacking database data file
STKI	Stacking database index file
TRACE	Trace file
SEQ	Any sequential file

The reason for the failure is indicated by ic_rsn, where ic is a 2-digit internal code, and rsn is the 4-digit reason code described in the following tables.

Logical Errors in Database Data File and Database Index Files

rsn	Description
0004	READ - key not found READNEXT - end of file reached READPREV - beginning of file reached
0008	Non-unique key (add)
0012	Invalid function
0016	Invalid record has been read or supplied
0020	Not enough memory
0024	Not enough storage in data file
0028	Not enough storage in index file
0030	Internal error: no message retriever found
0032	Missing parameters
0036	Invalid record type
0044	Invalid LRECL in data file
0048	Invalid KEYLEN in index file
0052	Simulation failed, restart
0056	Open for Trace file failed
0060	TCT address invalid (open)
0066	Invalid key change during update

Errors in Database DATA File

rsn	Description
1004	ADD - the file is full READNEXT - no more records READPREV - beginning of file reached
1006	Record not found
1008	Record not found--invalid extent number
1009	Record not found--invalid block number
1010	Internal error: Record not found--invalid extent number
1011	Internal error: Record not found--invalid block number
1012	Insufficient memory
1013	Open failed for the DD statement name
1016	The free record counter in the database is corrupt.
1018	Corrupted record
1019	Record is not active
1020	Invalid QNAME (open)
1021	Bad record in free list
1022	Invalid data set name in block 0
1024	Invalid function
1028	Load of IOAPARM failed
1032	Add failed, record too long
1036	I/O error
1044	EXCP initialization error
1046	Dual database file corrupted--not up to date, aborting
1048	Invalid data set name, or data set name too long
1050	Locate failed
1052	Dynamic allocation failed
1054	Dynamic allocation free failed
1056	Dual database file not up to date
1058	Dual database file corrupted--continue working with main database
1060	Failed to link IOADBF
1064	Failed to format new database file
1066	Cannot update block 0--block was not ENQed
1068	Update failed--record too long
1070	Failed to load IOADBSB#
1072	Cannot perform read with ENQ--another ENQ was already issued
1074	Cannot open database exclusively--database is in use
1076	Failed to update block 0--corrupted data
1078	Failed to update block 0--dual database flags changed without appropriate ENQ
1080	Buffering not initialized
1082	ENQ failed
1084	Compress/uncompress error
1086	Internal error--current EFCB does not match the RBA to be written
1090	Attempted to update database while it was open for read-only
1092	Open failed: read job file control block failed for the DD statement name.

Logical Errors in Database Index File

rsn	Description
2004	ADD - key already exists DELETE - record not found READ - record not found READNEXT - end of file reached READPREV - beginning of file reached
2008	Error accessing the file
2012	Not enough main storage
2016	Internal error
2018	The index tree structure is corrupted--an index on a higher level does not match the last index on a lower level.
2019	The index tree structure is corrupted--index was not found on the block.
2020	Invalid index function
2024	Invalid timestamp
2028	Invalid chain

Data Errors in Database Index File

rsn	Description
3004	ADD - file is full READNEXT - no more records READPREV - beginning of file reached
3006	Record not found
3008	Record not found--invalid extent number
3009	Record not found--invalid block number
3010	Internal error: Record not found--invalid extent number
3011	Internal error: Record not found--invalid block number
3012	Not enough memory
3013	Open failed for DD name
3016	The free record counter in the database is corrupt.
3018	Corrupted record
3019	Record is not active
3020	Invalid QNAME (open)
3021	Bad record in free list
3022	Invalid data set name in n block 0
3024	Invalid function
3028	Failed to load IOAPARM
3032	Add failed--record too long
3036	I/O error
3044	EXCP initialization error
3046	Dual database file corrupted--not up to date, aborting
3048	Invalid data set name, or data set name too long
3050	Locate failed
3052	Dynamic allocation failed
3054	Dynamic allocation free failed
3056	Dual database file not up to date
3058	Dual database file corrupted--continue working with main database
3060	Failed to link IOADBF
3064	Failed to format new database file
3066	Cannot update block 0--block was not ENQed
3068	Update failed--record too long
3070	Failed to load IOADBSB#
3072	Cannot perform read with ENQ--another ENQ was already issued
3074	Cannot open database exclusively--database is in use
3076	Failed to update block 0--corrupted data
3078	Failed to update block 0--dual database flags changed without appropriate ENQ
3080	Buffering not initialized
3082	ENQ failed
3084	Compress/uncompress error
3086	Internal error--current EFCB does not match the RBA to be written
3090	Attempted to update database while it was open for read-only
3092	Open failed: read job file control block failed for the DD statement name.

Errors in TRACE or SEQ Files

rsn	Explanation	Description
4004	READ	Record truncated because it was too long
	READ0	Record truncated because it was too long
4008	OPEN	Not enough memory
	READ	Record or block could not be read
	READ0	Record or block could not be read
	WRITE	Record or block could not be read
4012	OPEN	OPEN failed, or JFCB could not be obtained
	READ	Invalid RBA or EOF
	READ0	Invalid RBA or EOF
	WRITE	Record could not be written
	WRITE0	Record could not be written
4016	OPEN	Internal error--IOADBE initialization failed
	READ	Sequence error
	READ0	Sequence error
	WRITE	Sequence error
	WRITE0	Sequence error
4020	OPEN	Error reading record 0
	WRITE	Trace file is full
4024	OPEN	Trace file format is invalid
4028	OPEN	Trace file is full
4032	Internal error--invalid function for all TRACE or SEQ file operations.

Errors during sequential read of Media database

rsn	Description
5002	End of physical file (extent)
5004	End of file
5008	The file could not be opened. RDJFCB failed (probably no DD statement for the MDB).
5012	The file could not be opened. OPEN for MDB failed.
5016	Invalid dsname specified in DD statement referencing the MDB. Either name is too long or the name does not end with E000.
5020	Parameters error
5024	File attributes incorrect. File type incorrect.
5028	File attributes incorrect. Lrecl incorrect.
5032	File attributes incorrect. Blksize incorrect.
5036	File attributes incorrect. Dsname incorrect.

The currently executing function or utility stops.

Corrective Action: Notify your INCONTROL administrator.

CTT202I RECORD: `key`

Explanation: This information message follows another error message, and identifies the Media Database (MDB) record for which the operation identified in the earlier message failed.

Corrective Action: No action is required.

CTT203E CTTAPI FAILED. FUNCTION= `func` RC= `rc` RSN= `rsn` URC= `urc`

Explanation: The Control-M/Tape Application Program Interface (CTTAPI) has failed to perform one of its functions.

The variables in this message are:

func - the function that was not performed
rc - the return code
rsn - the reason code
urc - the utility return code, if a utility was run

The following table displays valid values for the return code and reason code, together with the relevant explanations:

Return Code	Reason Code	Explanation
8	200	No handler sent
204	GETMAIN failed
	208	No active query when query next
	212	Invalid call - invalid eye catcher
	216	No buffer when query
	220	Subtask error
	224	Open error from database. To identify the error that has occurred, use the value of `urc` as if it was the reason code in the CTT200S message.
	228	Close error from database. To identify the error that has occurred, use the value of `urc` as if it was the reason code in the CTT200S message.
	232	Load environment error
	236	Control-M/Tape real time environment is not active
	240	Allocate database error
	244	Free database error
	248	User not authorized
	252	Expiration management error
	256	MDB was not opened in update mode
	260	The program is not APF-authorized.
12	200	Function is not supported
	204	Path is invalid
	208	Relation is invalid
	212	Relation is inconsistent
	216	Mask is invalid
	220	Parsing error
	224	Invalid combination of where and path
	228	INCLUDE or EXCLUDE error
	232	Invalid options have been specified.
	236	A non-existent volume has been specified.
	240	The specified data set does not exist.
	244	The data set name specified does not match an actual data set name.
	248	The request is inconsistent with the current environment. An External Data Manager (EDM) attempted to mark as expired a volume not marked as under the control of that EDM.
16	200	Dynamic allocation error
	204	Dynamic free error
	208	Read error from database. To identify the error that has occurred, use the value of `urc` as if it was the reason code in the CTT200S message.
	212	Sort error
	216	More than two API parallel query tasks are not allowed.

Corrective Action: Use the information in this and any associated message to identify the problem, and take action accordingly.

CTT204W NUMBER OF FREE RECORDS IN `file` BELOW THRESHOLD

Explanation: The number of free records in the specified file has fallen below the installation default. The file indicated in this message is either MDB (the Media Database) or STK (the Stacking Database). This message is issued each time a record is added to the specified file while the situation persists.

Corrective Action: The size of the specified file should be examined and enlarged according to the current needs of the site. Refer to the INCONTROL for z/OS Administrator Guide.

CTT205S {MDB | STK} DATA FILE IS FULL

Explanation: An attempt was made to add a new record to the Media Database (MDB) or Stacking Statistic Database (STK), but the MDB/STK Data file has no free space left.

Processing stops.

Corrective Action: The MDB/STK Data file should be enlarged. Refer to the INCONTROL for z/OS Administrator Guide.

CTT206S {MDB | STK} INDEX FILE IS FULL

Explanation: An attempt was made to add a new record to the Media Database (MDB) or Stacking Statistic Database, but the MDB/STK Index file has no free space left.

Processing stops.

Corrective Action: The MDB/STK Index file should be enlarged. Refer to the INCONTROL for z/OS Administrator Guide.

CTT207S DATA FILE FORMATTED INCORRECTLY

Explanation: The format of the Media Database (MDB) Data file is incorrect. This message indicates that the LRECL of the Data file is not correct.

Processing stops.

Corrective Action: Refer to the Control-M/Tape chapter in the INCONTROL for z/OS Installation Guide and run the CTTDBF utility to format the MDB correctly.

CTT208S INDEX FILE FORMATTED INCORRECTLY

Explanation: The format of the Media Database (MDB) Index file is incorrect. This message indicates that the KEYLEN of the Index file is not correct.

Processing stops.

Corrective Action: Refer to Control-M/Tape chapter in the INCONTROL for z/OS Installation Guide and run the CTTDBF utility to format the MDB correctly.

CTT209E RECORD NOT FOUND. KEY= `key`

Explanation: A record with the indicated key was not found in the Media Database (MDB).

Corrective Action: Contact your INCONTROL administrator for assistance.

CTT210W MEDIA `mediaTypeDef` OF VOLSER `volser` NOT FOUND IN CTTPARM

Explanation: The CTTCDB utility cannot locate the media type definition for the volume specified in the CTTPARM member. The CTTCDB utility uses media definitions in the CTTPARM member to convert volume capacity information from feet to megabytes. Since the media assigned to volume volser is not defined in CTTPARM, the default capacity is used.

The variables in this message are:

mediaTypeDef -- the missing media type definition
volser -- the volume for which the CTTCDB utility tried to find the media type definition

The utility continues processing. The capacity for volume volser is set to the default for the utility.

Corrective Action: Define med_typ_def in CTTPARM and rerun the utility.

CTT250I TRC IS FORMATTED WITH `n1` BLOCKS, `n2` RECORDS, `n3` AVG RECORD LENGTH

Explanation: This information message is issued by the formatting program at the end of the Trace file format.

n1 -- Number of blocks
n2 -- Number of records
n3 -- Average record length

Corrective Action: No action is required.

CTT251E INDEX FILE IS NOT EMPTY

Explanation: The Index file contains active records.

The Index file must be empty before the issuing utility is started.

Processing of the utility stops.

Corrective Action: Do the following:

Use the IOADBF utility to format the Index file.
Rerun the utility.

CTT260E VOLUME `vol` NOT FOUND IN TMC FILE. DATASET `dsn`

Explanation: No volume record was found for the specified data set record in the database during conversion.

Conversion continues.

Corrective Action: No action is required.

CTT261I `num type recd_type` CONVERTED FROM REPORT `rpt_num`

Explanation: This information message indicates that the conversion program has finished converting a number of records of a specific type from the specified CA-TLMS report into Control-M/Tape format.

The variables in this message are:

num - The number of records converted.
type - The status of the specified records (ACTIVE or SCRATCH).
recd_type - The type of records converted (DATASETS or VOLUMES).
rpt_num - The number of the CA-TLMS report that was converted.

Corrective Action: No action is required.

CTT262S UNSUPPORTED TLMS `nnn` REPORT FORMAT

Explanation: This message indicates that the conversion program encountered a mismatched line in CA-TLMS report, where nnn indicates the report number and is either 004 or 010.

Execution is terminated.

Corrective Action: Produce a corrected CA-TLMS report and rerun the utility.

CTT263E VOLSER `volser` HAS NO FIRST VOLUME IN REPORT 004

Explanation: Due to an error in the CA-TLMS report 004, the conversion program has encountered a volser that is part of a chain of volsers, but which does not indicate a first volser.

The volser is assumed to be a single volume.

Corrective Action: Produce a corrected CA-TLMS report 004 and rerun the utility.

CTT264W VOLUME `volser` EXPIRATION DATE IS CHANGED TO PERMANENT

Explanation: The CA1 V4.9 conversion program identified a volume with EXPDT=99366. CA1 V4.9 saves expiration dates that are within keyword range, or whose year is 2000 or more, with EXPDT=99366. The conversion to Control-M/Tape cannot identify the exact expiration date.

The volume expiration date is set to permanent. The conversion program continues processing with the next record.

Corrective Action: Contact BMC Customer Support.

CTT265W UNKNOWN `fieldName` IN EPIC-RBA: `epic_rba`. VALUE: `unknown_value`

Explanation: The EPIC conversion program (CTTCEPC) processed the EPIC record in the specified epic_rba, and found an unknown value for the specified field name.

Possible values of fieldName are:

REC-TYPE - EPIC record type
LBL_TYPE - label type
DENSITY - density
UNT_TYPE - unit type

If the fieldName is REC-TYPE, the whole record is ignored and is not converted. In all other cases, the record containing the unknown field is converted to the Control-M/Tape Media Database using a default value for the problematic field.

Corrective Action: If the field name is known to you, consider modifying the CTTCEPC EPIC conversion program to support the field.

CTT266E UNEXPECTED DSN. RBA: `epic_rba`. DSN: `dsn`

Explanation: The EPIC conversion program (CTTCEPC) found that the specified data set name in the EPIC detail record located in the specified epic_rba is not the same as the data set name in the associated EPIC master record. This message indicates an integrity error in the EPIC database. The data set name in the EPIC master record must be identical with the data set name in the EPIC detail record.

The variables in this message are:

epic_rba -- the address of the problematic detail record in the EPIC database
dsName -- the data set name in the detail record which was inconsistent with data set name in the EPIC master record.

The conversion program terminates.

Corrective Action: Verify the integrity of the EPIC database and restart the conversion process.

CTT267W FIELD NOT NUMERIC: `fieldName` RBA: `epic_rba` VOL: `volser`

Explanation: The EPIC conversion program (CTTCEPC) processed the record associated with the specified volser, which is located in the listed RBA, and found a non-numeric value where a numeric value was expected in the specified field.

The variables in this message are:

fieldName - the name of the field containing the problematic value

Possible values for rc from CTVUPGDB, and their meanings, are:

rc	Explanation
OK	OK
4	End of file. Key not found.
8	Error processing the files
12	Invalid function
16	An invalid record was read.
20	Not enough storage
24	Not enough storage in the GIR file
28	Not enough storage in the GIRI file
32	There is no DBO block.
40	Invalid LRECL or KEYLEN in the data or index file. Invalid logical record in DEFGIT
48	SETPATH was not issued.
100 through 199	DBS error codes
200 through 299	DBI error codes

Possible fields are:
- FILE_SEQ - File sequence (label number).
- BLK_SIZE - Block size (BLKSIZE).
- REC_SIZE - Logical record length (LRECL).
- BLK_CNT - Block count.
- SLOT - Slot number.
- TUSE_CNT - Tape use count.
- MCYCLE - Retention cycle limit.
- RET_DAYS - Retention number of days.
epic_rba - Address of the EPIC detail record in which bad value was detected.
volser - Volume whose associated record field contains the problematic value.

The record containing the problematic field is converted to the Media Database but a default value of zero is substituted for the problematic value.

Corrective Action: Either fix the problematic field in the EPIC database and repeat the conversion process, or fix that field in the Media Database by means of the CTTMUP utility.

CTT268W NEXT VOLUME NOT FOUND FOR VOLUME: `volser`, DSN: `dsName`

Explanation: A volume chaining error was detected in the EPIC database. The specified data set name (dsName) resides on the specified volume (volser) and continues on another volume. However, the conversion program was unable to locate the continuation volume.

The conversion program continues. However, the volume chaining error will probably be propagated to the Control-M/Tape Media Database.

Corrective Action: Either fix the volume chaining error in the EPIC database and rerun the conversion program, or fix the error directly in the Control-M/Tape Media Database using the CTTMUP utility.

CTT269E CHAIN ERROR IN EPIC DATA. VOLSER: `volser` CUR_RECD: `epic_rba`

Explanation: A volume group chaining error was found in the EPIC database. The EPIC conversion program (CTTCEPC) could not create a multivolume group chain for volume volser located at record address epic_rba in the EPIC database.

The variables in this message are:

volser -- Volume ID
epic_rba -- Address of the volume record in the EPIC database

Conversion continues. However, the group chaining error found in the EPIC database is propagated to the Control-M/Tape database.

Corrective Action: Do one of the following:

Fix the chaining error in the EPIC database, and repeat the conversion process.
Fix the chaining error directly in the Control-M/Tape database using the CTTMUP utility.

CTT270E REQUEST PATH IS { `data_set`|`volume` } BUT `stmt` PARAMETERS CONTAIN FIELDS FROM { `volume`|`data_set` }

Explanation: Fields that are used as parameters in the INCLUDE, EXCLUDE or FIELDS statements are not valid with the specified path. Only data set fields can be used with the PATH=DATASET statement. Only volume fields can be used with the PATH=VOLUME statement.

The report is not produced.

Corrective Action: Remove the fields used as parameters that conflict with the selected path, or change the path.

CTT271E NEW EXTRACT STATEMENT IS NOT ALLOWED WHILE THE PREVIOUS ONE IS NOT CLOSED

Explanation: A new EXTRACT statement was specified before a REPORT statement was specified for the previous EXTRACT statement. A new EXTRACT block cannot be started before closing the previous EXTRACT block with a REPORT statement.

The report is not produced.

Corrective Action: Close the previous EXTRACT statement with a REPORT statement before specifying a new EXTRACT statement.

CTT275E INCLUDE/EXCLUDE STATEMENTS MUST FOLLOW AFTER `stmt` STATEMENT

Explanation: At least one INCLUDE or EXCLUDE statement specified for the CTTRTM or CTTVTM utility did not immediately follow the specified statement.

In the CTTRTM and CTTVTM utility, at least one INCLUDE or EXCLUDE statement must follow the TYPERET and TYPEVLT statements, respectively.

The utility stops execution.

Corrective Action: Place an INCLUDE or EXCLUDE statement immediately after the TYPERET or TYPEVLT statement. Rerun the utility.

CTT276I VOLUME `vol` IN USE

Explanation: This information message indicates that retention processing or vault processing is requested for the volume, but the volume is in use.

If the message is issued during retention processing, the CTTRTM utility skips the volume. If the message is issued during vault processing, the CTTVTM utility skips the volume and, if the volume is part of a multi-volume chain, the whole chain is skipped.

Corrective Action: No action is required.

CTT277E INVALID EXPDT VALUE. RC: `rc`

Explanation: An invalid Expiration Date as defined by the EXPDT parameter was specified in the user JCL.

The EXPDT value is ignored and the data set is given a default retention.

Corrective Action: No action is required.

CTT278I VAULT `vault` IN VOLUME `vol` IS `nn` IN PATTERN

Explanation: This information message indicates that the specified vault was found to be the nnth vault in the vault pattern for the specified volume.

Corrective Action: No action is required.

CTT279W CONTROL-M/TAPE IS ACTIVE, RESULTS ARE UNPREDICTABLE

Explanation: The Control-M/Tape real-time environment remained active while the CTTCDB utility was running. The Media Database records created by CTTCDB might include integrity problems.

The CTTCDB utility continues processing.

Corrective Action: If this message is issued while you are running this utility for test purposes, ignore it.

If this is a production execution of the CTTCDB utility, bring Control-M/Tape down and rerun the utility.

See the step that describes conversion of the Control-M/Tape Media Database in the Control-M/Tape chapter of the INCONTROL for z/OS Installation Guide.

CTT280W VOLUME `vol` DEVICE `dev` IGNORED. NO CORRESPONDING MEDIA IN MEDIA TABLE

Explanation: The Media Table (the DADEVICE DD statement) did not contain an entry for the device specified in the message.

The current record is ignored.

Corrective Action: If this device should be defined in the Media Table, add an entry for it. Otherwise, consider this message as an information message.

CTT281I `num` VOLUME/DATASET RECORDS WERE CREATED

Explanation: This information message indicates the number of records written by the Conversion From MVS Catalog utility.

Corrective Action: No action is required.

CTT282W DUPLICATE DATASET `dsn` (VOL: `volser`, LABEL: `lbl`) DISCARDED

Explanation: A duplicate entry was detected for the specified data set during conversion of tape management data from an MVS catalog. While scanning the MVS catalog, the catalog conversion utility detected a more recent entry with the same volume and label number.

The data set with the latest creation date is taken. The referenced data set is dropped.

Corrective Action:

If the entry is obsolete, then ignore the message and continue.
Otherwise, resolve the conflict by updating your MVS catalog and rerun the conversion process.

CTT283W OBSOLETE DATASET `dsn` (VOL: `volser` LBL: `lbl`) DISCARDED.

Explanation: An obsolete entry was detected for the specified data set during conversion of tape management data from an MVS Catalog. A data set with a more recent creation date and a lower label number exists on the specified volume making the current entry obsolete.

The variables in this message are:

dsn -- The data set name of the obsolete catalog entry.
volser -- Volume serial number of the obsolete catalog entry.
lbl -- Volume label of the obsolete catalog entry.

The specified catalog entry is ignored. The conversion program continues normally.

Corrective Action: No action is required.

CTT286E SPECIFIED VOLSER `volser` CANNOT BE {INITIALIZED | ERASED} RSN= `rsn`

Explanation: The CTTTPI utility determined that the specified target volser cannot be initialized or erased.

Possible values of rsn:

ACTIVE IN MDB - The specified volser is in the Media Database and its status is not SCRATCH.
ADD=N - The specified volser is not in the Media Database. The ADD=N and MDBUPDAT=Y statements were specified in the TYPERUN statement.
OPER SKIPPED - The operator responded to a program prompt with a request to skip the initialization or erasure of this volume.
OPER CANCELED - The operator responded to a program prompt with a request to cancel the execution of the CTTTPI utility.

The specified volser is not initialized or erased. Execution terminates unless the reason is OPER SKIPPED, in which case processing continues with next volser or with the next control statement.

Corrective Action: If the reason was either OPER SKIPPED or OPER CANCELED, no action is necessary.

If the reason was ACTIVE IN MDB or ADD=N examine the status of the volume in the Media Database and the parameters specified in the TYPERUN control statement. Change the settings for these if necessary.

CTT287E TAPE INITIALIZATION FAILED. PROG= `pgm`

Explanation: The pgm program returned a nonzero return code while trying to write a label on a tape volume. The specified program was called by the CTTTPI utility. This message is also issued if the operator responds ‘S’ (SKIP) to the IBM IEHINITT utility.

The CTTTPI utility is terminated.

Corrective Action: Examine the report produced by the pgm program, and take appropriate action.

CTT288E MOUNTED VOLUME `volser` CANNOT BE USED. RSN= `rsn`

Explanation: The CTTTPI utility determined that it could not write a new label on the mounted volume (volser).

Possible values for rsn:

ACTIVE IN MDB - The specified volser is in the Media Database, and its status is not SCRATCH.
OPER REJECTED - The operator responded to a program prompt with a request to not use the mounted volume for the requested initialization.
INVALID VOLSER - The mounted volume is not the requested volume.

The CTTTPI utility unloads the mounted volume, and requests that another volume be mounted for the initialization of the same specified target volser.

Corrective Action: Do the following:

Remove the unloaded volume from the drive.
Either mount a new volume to continue the initialization process, or check the status of the volume in the Media Database and the parameters specified in the TYPERUN control statement, and change the settings if necessary.

CTT289A MOUNT VOLUME TO BE INITIALIZED AS `volser` ON `unit_num`

Explanation: The CTTTPI utility is requesting the mounting of a volume to be initialized on the specified device number (unit_num).

The message is scrolled off the screen and is followed by an ordinary MOUNT message (from MVS or from Control-M/Tape) for file CTTTPI.UTIL.INIT. volser on device number unit_num.

Corrective Action: Do the following:

Mount the volume to be initialized as volser on the desired tape drive.
Verify that the volume is not write-protected. It is recommended that the volume be already externally labeled with the correct serial number.

CTT290E OPEN FAILED FOR TAPE DD `ddName`

Explanation: The CTTTPI utility was unable to access the designated tape drive using the ddName DD statement.

The CTTTPI utility is terminated.

Corrective Action: Examine the JCL printout of the job, input JCL, job console log, and the allocated device. Correct all errors and rerun the CTTTPI utility.

CTT291A CONFIRM {ERAS | INIT} `unit / volser1` OLDV= `volser2` (`status`) D= `dsn` : Y/UNLOAD/SKIP/CANCEL

Explanation: The CTTTPI utility is requesting operator approval to initialize or erase the volume mounted on unit unit. If the user response is Y (Yes) the new label (volser1) is written over the old one (volser2). The status (status) of volser2 is displayed in parentheses.

If no label previously existed for the volume, volser2 appears as NO-LBL in this message.

If volser2 is a standard label volume, the first data set name of the volume is shown in the message (dsn). Otherwise, the first data found on the tape (if any) is displayed in its place.

Possible values of volser2 are:

ACTIVE!! -- volser2 is ACTIVE in the Media Database.
SCRATCH -- volser2 is SCRATCH in the Media Database.
NON-MDB -- volser2 is not found in the Media Database.
???????? -- Status of the mounted volume is unknown.

If the CTTTPI utility cannot read any data from the volume, the volume may never have been written, or the volume was written by another device.

The utility waits for the user response, after which it continues processing accordingly.

Corrective Action: Enter one of the following:

Y -- Confirm the operation.
UNLOAD -- Reject the mounted volume volser2. The CTTTPI utility proceeds to request another volume to be initialized as volser1.
SKIP -- Reject the mounted volume and the specified target volser1. The CTTTPI utility proceeds with the next volser or the next control statement.
CANCEL -- Terminate the CTTTPI utility. If the status of the volser is ACTIVE!!, use this option to end the operation, unless it is certain that the volser match between the mounted volume and the other active volume in the Media Database is coincidental.

No abbreviations are allowed for the UNLOAD, SKIP, or CANCEL responses.

CTT292I INITIALIZED LABEL `volser1` ON OLD VOLUME `volser2`

Explanation: This information message indicates that the CTTTPI utility successfully completed initialization of a volume. Label volser1 was written on a volume whose previous label was volser2. When PROTECT=NOREAD is specified, volser2 appears as UNKNWN in this message.

The CTTTPI utility continues processing with the next volser or with the next control statement.

Corrective Action: No action is required.

CTT293A VOLUME `volser` IS NOT IN MDB. REPLY ‘Y’ - DEFINE, ‘E’ - EXTERNAL, ‘I’ - IGNORE, ‘SKIP’ OR ‘CANCEL’

Explanation: This WTOR message is issued by the CTTTPI utility before it adds a volser to the Media Database (MDB).

The utility waits for the user’s response. It then continues processing accordingly.

Corrective Action: Enter one of the following:

Y - Add the new volume to the MDB.
E - Add the new volume to the MDB and mark it as External.
I - Ignore the addition, and initialize the tape without adding the volume to the MDB.
SKIP - Reject the specified target volume (volser). The CTTTPI utility proceeds with the next volser or the next control statement. SKIP cannot be abbreviated.
CANCEL - Terminate the CTTTPI utility. CANCEL cannot be abbreviated.

CTT294E SYNTAX ERROR IN CTTTPIV PARAMETER

Explanation: The CTTTPI utility encountered a syntax error in the value specified for the PARM in the JCL EXEC statement or in the first value passed to it by an invoking program.

The CTTTPI program terminates.

Corrective Action: Correct the error and rerun the CTTTPI utility.

CTT295I VOLUME `volser1` ERASED. OLD VOLUME `volser2`

Explanation: This information message indicates that the CTTTPI utility successfully completed erasing information on a volume.

The variables in this message are:

volser1 - the identity of the volume that was erased
volser2 - the identity of the volume label that read from the tape

The CTTTPI utility continues processing the next volser or the next control statement.

Corrective Action: No action is required.

CTT296E TAPE I/O ERROR. ECB: `ecb_add`

Explanation: A tape I/O operation that was issued by the CTTTPI utility failed.

In this message, ecb_add is the Event Control Block of the unsuccessful I/O operation.

If the CTTTPI utility was erasing a tape (TAPERAS) or initializing a tape (INITT), it stops processing.

If the CTTTPI utility was mapping a tape (TAPEMAP), it repeatedly tries to perform the I/O until it reaches the I/O error limit specified in the NUMERR parameter of the TAPEMAP statement.

Corrective Action: If the CTTTPI utility stops, rerun the job or started task using a different tape unit.

Messages CTT300 through CTT3xx

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

CTT301I VOLUME `vol` BECAME SCRATCH

Explanation: This information message indicates that the CTTRTM utility deleted all data sets and changed the status of the volume to SCRATCH.

The utility continues executing.

Corrective Action: No action is required.

CTT302I DATASET `dsn` (VOLSER=`volser`) SCRATCHED ON THE MDB

Explanation: This information message indicates that the specified data set was marked SCRATCH by the CTTRTM utility according to the expiration criteria for the data set.

Corrective Action: No action is required.

CTT303I DATASET `dsn` (VOLSER=`volser`) HAS ENTERED ITS GRACE PERIOD

Explanation: This information message indicates that although the expiration date of a data set has been reached, the data set has not been expired, because a grace period was defined. However, when the grace period is over, the data set will be expired.

The variables in this message are:

dsn - the name of the data set that has entered its grace period
volser - the volume serial number of the volume containing dsn

Grace periods are defined by the GRACECAT and GRACECYC parameters in CTTPARM. For more information on these parameters, see the Control-M/Tape chapter in the INCONTROL for z/OS Installation Guide.

The utility continues processing normally.

Corrective Action: No action is required.

CTT304E DATASET `dsn` (VOLSER=`volser`) IS NOT UNCATALOGED. RC=`rc`

Explanation: The CTTRTM utility could not uncatalog the data set. The data set could not be uncataloged because the MVS Catalog is not available or an I/O error occurred in catalog volume.

The CTTRTM utility skips the data set record and continues executing.

Corrective Action: Notify your system programmer of the value of rc.

CTT305I DATASET `dsn` (VOLSER=`volser`) HAS BEEN UNCATALOGED.

Explanation: The CTTRTM utility successfully uncataloged the data set that was scratched just now.

The message is issued only when UNCATMSG=YES in the CTTRTM TYPERET statement.

Corrective Action: No action is required.

CTT306I DATASET `dsn` (VOLSER=`volser`) IS NOT CATALOGED.

Explanation: The CTTRTM utility found that the dataset that was scratched just now is not cataloged. Therefore, CTTRTM does not attempt to uncatalog the dataset.

The message is issued only when UNCATMSG=YES and UNCTLG=YES (the default) are set in the CTTRTM TYPERET statement.

Corrective Action: No action is required.

CTT307E INCONSISTENCY BETWEEN REPORT NAME AND UTILITY MODE

Explanation: In the input parameters of the CTTRTM utility, there is an inconsistency between the values of the MODE parameter in the TYPERET statement, and the values of the REPORT NAME parameter. For example, MODE is set to REGULAR in the TYPERET statement for the RECALC report.

The utility stops executing.

Corrective Action: Correct the values of the TYPERET MODE parameter and the REPORT NAME, and rerun the utility.

CTT308E THERE ARE NO DATASETS ON VOLUME `vol`

Explanation: Volume vol is an active volume, but no data sets from the Media Database were found on the volume. This message indicates a logical error in the Media Database.

The CTTRTM utility continues processing.

Corrective Action: Notify your database administrator.

CTT309E NUMBER OF {VOLUMES | DATASETS} TO BE SCRATCHED (`num`) EXCEEDED THE LIMIT. CHANGES WERE NOT PERFORMED IN MDB

Explanation: More than the maximum number of volumes or data sets specified by the MAXVOLNO parameter or the MAXDSNO parameter, respectively, were marked for expiration during a run of the CTTRTM utility. Before scratching data sets or volumes, the CTTRTM utility checks how many volumes or data sets will be scratched in the current run of the utility.

In this message, num is the number of volumes or data sets that would have been marked for expiration by this run of the utility.

No volumes or data sets are scratched. The CTTRTM utility produces a Scratch report that describes the volumes and data sets that would have been scratched if the specified maximum were not exceeded.

Corrective Action: Determine why so many data sets were marked as expired and, if necessary, increase the limit for the maximum number of volumes or data sets that can be marked for expiration in the MAXVOLNO parameter or the MAXDSNO parameter.

CTT320I `rba` : `fileType` OF `recordType entity action`

Explanation: This information message indicates that a record was processed by the CTTMER or CTTSPL utilities.

The variables in this message are:

rba-- RBA of the record in the MDB.
fileType-- Either DATA or INDEX.
recordType-- Type of MDB record processed (for example D for data set, V for volume).
entity-- Identifier, data set name for a data set record, volser for a volume record.
action-- Any of the following:
- NOT-DELETED (RESTART)
- DELETED
- ADDED
- RESTART-DELETED

Corrective Action: No action is required.

CTT321E VOLSER OF RECORD TO BE MERGED EXISTS IN MDB. RBA: `rba` VOLSER: `volser`

Explanation: The CTTMER utility tried to merge a record that already exists in the Media Database. The records that CTTMER was merging into a target Media Database were split off from another Media Database by the CTTSPL utility. These records can only be merged into the target Media Database if they, that is, their volsers, do not already exist there. However, the volser of the record identified in the message already exists in the target Media Database.

CTTMER ignores this record, and does not merge it to the Media Database. The original record in the source Media Database remains unchanged. CTTMER continues to process the rest of the records.

Corrective Action: Check why the record to be merged already exists in the target Media Database.

CTT330E INVALID SILO TYPE - `type`

Explanation: An invalid silo type was specified in the CTTPARM member.

Valid values of type are:

NONE -- No silo installed.
3495 -- IBM 3495 Automated Tape library.
STK -- StorageTek Silo.

Corrective Action: Specify a valid silo type (if desired).

CTT331E INVALID SILO FUNCTION - `func`

Explanation: The CTTRBM utility was invoked with an invalid silo function input parameter.

The following silo functions (func) are valid when invoking the CTTRBM utility:

CUASCR -- Set a volume use attribute to SCRATCH.
EJECT -- Eject a volume from the Automated Tape library.

Corrective Action: Correct the procedure used to invoke the CTTRBM utility.

CTT332I REPORT FILE DOES NOT CONTAIN RELEVANT DATA

Explanation: This information message indicates that the report file passed to the CTTRBM utility does not match the requested silo function.

Corrective Action: If desired, either request the CUASCR silo function for the SCRATCH or FULLSCR report of the Retention Management Utility (CTTRTM), or request the EJECT silo function for the DISTRIB report of the Vault Management Utility (CTTVTM).

CTT333I VOLUME `volser` NOT IN AUTOMATED LIBRARY. (INTERFACE MODULE IS `modName`)

Explanation: This information message indicates that a robot function requested for the specified volume failed because the volume cannot be found in the Automated Tape library.

In this message, mod_nam is one of the following Automated Tape library Interface module names:

CTTSTK -- Interface to a StorageTek silo.
CTTOAM -- Control-M/Tape interface to an automated tape library controlled by an OAM such as IBM ATL or IBM VTS.
CTTMMRX -- Interface to a SUTMYN robotic tape library.
CTTEMAS v Interface to an EMAS robotic tape library.
CTTFUJI -- Interface to a Fujitsu robotic tape library.

Possible system actions:

If modName specifies the last library to be searched, CTTRBM continues processing with the next volume.
If modName specifies a library other than the last library to be searched, CTTRBM searches for the same volume (volser) in the next tape library.

Corrective Action: To suppress this message, see the description of user exit CTTX008 in the Control-M/Tape Implementation Guide.

CTT334E FUNCTION `func` FAILED. VOLSER=`volser`, OPCODE=`opc`, RC=`rc`, REASON=`rsn`, INTERFACE=`modName`

Explanation: The silo function requested for a volume failed.

The software of the robotic tape library returns the operation code opc, the return code rc in decimal format, and the reason rsn in hexadecimal format.

In this message, modName is one of the following Automated Tape library Interface module names:

CTTRSTK -- Control-M/Tape interface to a StorageTek silo.
CTTRCSC -- Control-M/Tape interface to a StorageTek silo managed by CSC
CTTOAM -- Control-M/Tape interface to an automated tape library controlled by an OAM such as IBM ATL or IBM VTS.
CTTMMRX -- Control-M/Tape interface to a Memorex Telex robotic tape library.
CTTHACC -- Control-M/Tape interface to an ADIC robotic tape library.
CTTFUJI -- Control-M/Tape interface to a Fujitsu robotic tape library.

Possible system actions:

If modName indicates the last library to be searched, the CTTRBM utility continues processing with the next volume.
If modName indicates a library other than the last library to be searched, the CTTRBM utility searches for the same volume (volser) in the next tape library.

Corrective Action: Refer to the messages and codes documentation for your tape robot or silo for a description of the codes returned in this message.

CTT335E REPORT TYPE `type` IS IRRELEVANT FOR AUTOMATED TAPE LIBRARY

Explanation: The report file passed to the CTTRBM utility is inappropriate for the requested silo function. The report passed to the CTTRBM utility was neither a SCRATCH report nor a DISTRIB report.

The CTTRBM utility is terminated.

Corrective Action: Do one of the following:

Pass a CTTRTM SCRATCH report to the CTTRBM utility, while specifying the CUASCR silo function.
Pass a CTTVTM DISTRIB report to the CTTRBM utility, while specifying the EJECT silo function.

CTT336E SILO INTERFACE `modName` LOAD FAILED

Explanation: The CTTRBM utility was unable to load the specified interface module.

In this message, modName is one of the following Automated Tape library Interface module names:

CTTSTK - Control-M/Tape interface to a StorageTek silo.
CTTOAM -- Control-M/Tape interface to an automated tape library controlled by an OAM such as IBM ATL or IBM VTS.
CTTMMRX - Control-M/Tape interface to a Memorex Telex robotic tape library.
CTTEMAS - Control-M/Tape interface to an EMAS robotic tape library.
CTTFUJI - Control-M/Tape interface to a Fujitsu robotic tape library.

The specified interface is not used. The CTTRBM utility continues processing with the other interfaces (if any are loaded). If no other interfaces are loaded, the CTTRBM utility is terminated.

Corrective Action: If the specified interface is not needed, remove it from the specification for the RBTTYPE parameter in the CTTPARM member. If the specified interface is needed, add the appropriate module to one of the STEPLIB or LINKLIST libraries.

CTT337E {SCRATCH | ACTIVATE} FOR VOLUME `volser` FAILED DUE TO CONTRADICTING STATUS IN THE MDB

Explanation: Control-M/Tape initiated a SCRATCH or ACTIVATE operation on the specified volume (volser) in the database of the robot. However, the current status of this volume in the Media Database is incompatible with the attempted operation. The status of each volume in the Media Database and the robot database must be the same.

There was probably a delay between the issuance and execution of the robot request. During which the status of the specified volume was changed in the Media Database.

In this message, volser is the volume whose status update attempt is not compatible with its status in the Media Database.

The status of the volume is not changed in the robot database.

Corrective Action: Do one of the following:

If the volser was directly accessed as a scratch volume (SCRPROT set to N in CTTPARM) before Control-M/Tape was able to access the robot, ignore this message.
In all other cases, determine why the status update attempt for the volume in the robotic library contradicts its status in the Media Database. If necessary, correct the volume status in the Media Database using the Inquire Update Screen, the CTTMUP utility, or the robotic library using the standard robotic library update utility.

CTT338I RETRY `retry_ctr` (OUT OF `max_retry`) FOR VOLUME `volser` INITIATED

Explanation: This information message indicates the current retry number for an action requested of a robotic tape library. This message is generated each time the action is retried.

Control-M/Tape requested an action from a robotic tape library. The action failed and is being retried. Each time the action is attempted, the retry number is incremented. The action is not retried if the action is successfully performed, or if the specified maximum number of retries is exceeded.

Message variables are:

retry_ctr -- Retry number of the current attempt.
max_retry -- Maximum number of retries allowed for a robot operation on the specified volume.
volser -- Volser of the volume on which the requested action is to be performed.

Processing continues normally.

Corrective Action: Verify that the retry was completed successfully.

CTT339I FUNCTION `func` FOR VOLUME `volser` PERFORMED SUCCESSFULLY USING INTERFACE `robot_int`

Explanation: The robotic library function func that was requested by means of the robot_int robotic interface module was successfully performed for the volser volume.

See message CTT333I for a list of interface modules and the robotic libraries with which they are associated.

Corrective Action: No action is required.

CTT33AE INVALID PARAMETER OKMSG VALUE SPECIFIED. ONLY YES OR NO ALLOWED.

Explanation: Incorrect value specified for the optional parameter OKMSG. Only YES or NO are allowed. CTTRBM terminates.

Corrective Action: Specify a correct value and rerun CTTRBM.

CTT340I VTS EXPORT COMMAND ISSUED SUCCESSFULLY. EXPORT LIST VOLUME `volser`

Explanation: This information message indicates that the CTTVEXP utility successfully issued the EXPORT command to the Virtual Tape Server (VTS) and the export list volume is volser. The EXPORT command ejects physical tapes from the VTS so that logical VTS volumes can be put into external vaults. CTTVVM created volser earlier.

CTTVEXP waits for messages from OAM indicating that export processing is finished.

Corrective Action: No action is required.

CTT341E EXPORT FROM VTS FAILED. EXPORT LIST VOLUME `volser`

Explanation: The CTTVEXP utility could not export tapes from the Virtual Tape Server (VTS).

Possible reasons are:

The EXPORT command of the CBRXLCS service failed.
The EXPORT command did not fail, but OAM issued error messages.

CTTVEXP stops.

Corrective Action: Do one of the following:

The CTT074E message that precedes CTT341E shows the return code and the reason code of the CBRXLCS EXPORT command. Check these codes in IBM documentation for details and fix the error.
Search the system log for IBM messages CBR3857I, CBR3858I and CBR3863I, or for similar messages. Then, check IBM documentation for explanations and fix the error.

CTT342I `util` IS RUNNING IN SIMULATION MODE

Explanation: This information message indicates that the CTTVVM or CTTVEXP utility is running in simulation mode. When CTTVTM runs in simulation mode (TYPERUN MODE is set to SIMULATION), CTTVTM notifies CTTVVM and CTTVEXP, so that they also run in simulation mode.

In simulation mode, CTTVVM does not create the Export List volume or the Import List volume and CTTVEXP does not perform any EXPORT command.

Corrective Action: To export tapes from the VTS, run CTTVTM with TYPERUN MODE set to NORMAL.

CTT343I VOLSER `volser` SKIPPED BECAUSE OF TEST MODE

Explanation: This information message indicates that a volume with serial number volser was not exported because Control-M/Tape processed it in test mode. Test mode is set with the expression MODE=TEST in CTTPARM, or by a rule specifying MODE TEST. Control-M/Tape does not export a volume from the VTS (Virtual Tape Server) that it processed in test mode.

CTTVVM does not include the volser in the Export List File.

Corrective Action: If you intend to export a volume, make sure Control-M/Tape is not in test mode when it processes the volume.

CTT344E VOLSER `volser` NOT EXPORTED BECAUSE OF PREVIOUS ERROR

Explanation: Volume with serial number volser was not exported because of an earlier error. Control-M/Tape does not export a volume serial number if an error occurred while Control-M/Tape was processing it.

CTTVVM does not include the volser in the Export List File.

Corrective Action: Check the error message before CTT344E, fix the problem and try again.

CTT345E MAINTENANCE FOR VENDOR TAPE MANAGEMENT SYSTEM SUPPORT HAS NOT BEEN APPLIED TO EXLM

Explanation: The StorageTek ExLM level does not support vendor tape management systems. Control-M/Tape uses the StorageTek ExLM vendor tape management systems support to interface with ExLM.

ExLM processing terminates.

Corrective Action: See the section that describes the Robotic Tape Library Interface in the Control-M/Tape Implementation Guide for the minimum ExLM level required for the interface.

CTT346E LOCATION CANNOT EXCEED THE TENTH VAULT

Explanation: The CTTVVM utility was invoked with the expression MODE=ALLVLT to export a volume with a vaulting pattern that has more than ten vaults, and the next requested vault is beyond the tenth.

When the CTTVVM utility exports volumes from the Virtual Tape Server (VTS) based on the complete vaulting pattern (MODE=ALLVLT), it supports a maximum of ten vaults in each vaulting pattern. Since the next vault of the volume specified in the CTT344E message that accompanies this message is beyond the tenth vault, CTTVVM cannot export this volume.

CTTVVM issues message CTT344E, which specifies the volser for the volume that caused this error. This volume is not included in the Export List file created by this run.

Corrective Action: Use the CTTVVM utility with MODE set to FIRSTVLT to export the volume based on the first vault only.

CTT347I `func` LIST VOLUME CREATED ON VOLSER `volser`

Explanation: This information message indicates that the CTTVVM utility successfully created an Import or Export List volume.

Message variables are:

func -- Whether an Import or an Export List volume was created.
volser -- Volume serial number of the new volume.

If CTTVVM created an Export List volume, CTTVVM passes its volser to CTTVEXP by means of DD card VVMVOL and CTTVEXP issues the EXPORT command.

Corrective Action: If CTTVVM created an Import List volume, check that the physical volumes that contain the logical volumes to be imported are in the library. Then, issue the IMPORT command.

CTT348E INVALID EXPORT STATUS FILE IDENTIFIER

Explanation: The CTTVEXP utility could not read the Export Status File to produce a status report, because Control-M/Tape does not support the Export Status file identifier.

CTTVEXP stops without issuing a report.

Corrective Action: Check that Export processing finished successfully, and that OAM messages indicate that an Export Status file was created. If necessary, notify your INCONTROL administrator.

CTT349I EXPORT FOR LOGICAL VOLSER `log_volser`, STATUS CODE=`stat_code` {PHYSICAL VOLSER IS `phys_volser`, DESTINATION IS `dest`| REASON IS `rsn`}

Explanation: This information message indicates the results of the CTTVEXP export operation. The information is based on the Export Status File records, where log_volser is the serial number of the logical volume, and stat_code is the export status code.

If the export operation succeeded, phys_volser specifies the serial number of the physical volume to which the logical volume was exported and dest specifies the destination.

If the export operation ended with an error, rsn describes the nature of the error.

Corrective Action: Refer to IBM documentation to resolve errors during processing of logical volumes.

CTT350I DYNAMIC STACKING ON VOLUME `vol` PERFORMED FOR:

Explanation: This information indicates that dynamic stacking was successfully performed on the specified volume. This message is followed by message CTT351I, which contains details about the stacked data set.

Corrective Action: No action is required.

CTT351I JOBNAME=`jobName` DDNAME=`ddName` DSN=`dsn`

Explanation: This information message follows message CTT350I. It provides details about the data set that will be added to the volume specified in CTT350I.

Corrective Action: No action is required.

CTT352S STACKING PROCESSING STOPPED FOR JOB `jobName` - REASON:

Explanation: An error was encountered during the stacking process for job jobName.

This message is followed by another message that has details about the error.

Stacking stops for this job.

Corrective Action: Check the accompanying error message for details about the error.

CTT353S INSUFFICIENT STORAGE FOR STACKING PROCESSING

Explanation: This message follows message CTT352S when there is insufficient storage for stacking processing.

Stacking processing stops for this job.

Corrective Action: Notify your INCONTROL administrator.

CTT354S INTERNAL ERROR IN STACKING PROCESSING - CODE=`code`

Explanation: This message follows message CTT352S when an internal error in encountered during stacking processing.

Stacking processing stops for this job.

Corrective Action: Notify your INCONTROL administrator.

CTT355S ABEND S`xxx` IN MODULE `modName` OFFSET=X‘`offset` ’ (LOAD - POINT=`load_point`)

Explanation: This message follows message CTT352S when an internal abend occurs in stacking processing.

The message contains details about the abend: abending module name, abending load module load point, and offset of the abending instruction in the module.

Stacking processing stops for this job and a system dump is produced.

Corrective Action: Format and save the dump, and notify your INCONTROL administrator.

CTT356W STACKING STOPPED FOR DATASET `dsn`

Explanation: Control-M/Tape could not satisfy the stacking requirements for the dsn data set.

This message is followed by a message describing why the data set could not be stacked and why the stacking requirements could not be satisfied.

Stacking stops for the specified data set. The job continues without stacking for the dsn data set. The data set is written to a scratch volume.

Corrective Action: See later messages for details about the error and correct the problem.

CTT357W REACHED SEARCH LIMIT FOR STACKABLE VOLUME, LIMIT=`limit`

Explanation: The search limit for a stackable volume has been reached. This message follows message CTT356W, which specifies the data set for which stacking has stopped.

Stacking stops for the data set. The job continues without stacking for this dsn. The search for the next stackable volume begins from the volume reached in this search.

Corrective Action: Check and, if necessary, adjust the search limit for stackable volumes, defined in the STKSRCHL parameter in the CTTPARM member.

CTT358W MATCHING RULE SPECIFIED ‘DO RETENTION=EDM’

Explanation: DO RETENTION=EDM is specified in the matching rule. Stacking cannot be performed for EDM-controlled data sets.

This message follows message CTT356W, which specifies the data set for which stacking stopped.

Stacking stops for the data set. The job continues without stacking for this dsn.

Corrective Action: Use the Rule Simulation Facility to find matching rules for the data set. Check matching rules for conflicts between stacking definitions and other definitions (for example, retention definitions).

CTT359W MATCHING RULE SPECIFIED ‘TEST’ MODE

Explanation: TEST mode is specified in the matching rule. Stacking is not performed for data sets matched by rules with mode TEST.

This message follows message CTT356W which specifies the data set for which stacking has stopped.

Stacking stops for the data set. The job continues without stacking for this dsn.

CTT360W MATCHING RULE CONTAINS VAULT ENTRIES

Explanation: The matching rule contains vault entries, and the stacking algorithm specified by the STKMODE parameter in the CTTPARM member does not allow vault matching.

This message follows message CTT356W, which specifies the data set for which stacking stopped.

Stacking stops for the data set. The job continues without stacking for this DSN.

Corrective Action: Do the following:

Use the Rule Simulation Facility to find the matching rules for the data set.
Verify that the matching rule does not conflict with the stacking algorithm defined by means of the STKMODE parameter in the CTTPARM member.

To use vault matching in the stacking algorithm set STKMODE to R or A.

CTT361W NO STACK RECORD FOR DATASET

Explanation: The data set to be stacked is not in the Stacking Database, and a default size value is not specified. The search process must locate the data set record in the Stacking Database to determine its average size.

This message follows the CTT356W message, which specifies the data set for which stacking stopped.

Stacking stops for the data set. The job continues without stacking for this data set.

Corrective Action: Do one or more of the following:

Run the CTTSTK utility to collect statistical information for the Stacking Database.
Use the STKDEFSZ parameter in the CTTPARM member to specify a default size for data sets not defined in the Stacking Database.
Use the DO STKDEFSZ option in a Control-M/Tape rule to specify a default size for data sets not defined in the Stacking Database.

CTT362W DATASET IS NOT STACKABLE

Explanation: The specified data set record is marked NOT STACKABLE in the Stacking Database. Stacking cannot be performed for NOT STACKABLE data sets.

This message follows message CTT356W which specifies the data set for which stacking stopped.

The data set record was marked NOT STACKABLE for one of the following reasons:

The data set was opened with DIPS=MOD specified in the JCL.
The data set was recreated on the volume.
The data set was opened by a job step that specified //NOSTACK DD.

Stacking stops for the data set. The job continues without stacking for this dsn.

Corrective Action: No action is required.

CTT363W POOL `pool` IS NOT DEFINED

Explanation: The matching rule specifies a pool not defined to Control-M/Tape.

This message follows message CTT356W, which specifies the data set for which stacking stopped.

Stacking stops for the data set. The job continues without stacking for this dsn.

Corrective Action: Do the following:

Use the Rule Simulation Facility to find the matching rules for the data set.
Either define the pool name by means of screen TP, or replace the pool name in the rule with the name of a previously defined pool.

CTT364W INVALID POOL FOUND IN MEMORY

Explanation: The pool name in the matching rule has an invalid pointer in memory. It points to an area in memory that cannot be identified as a pool block.

This message follows message CTT356W, which specifies the data set for which stacking stopped.

Stacking stops for the data set. The job continues without stacking for this dsn.

Corrective Action: Reload the pool table into memory with the following operator command: S CTTINIT,PARM=‘RELOAD,TBLT=POOL’

CTT365W NO ELIGIBLE VOLUME FOR STACKING IN POOL `pool`

Explanation: All volumes in all ranges of the specified pool were searched, and none satisfied the search process requirements. The search process searches all volumes in the specified pool for a stackable volume. The search starts at the last found volser, and checks volsers one at a time until the first searched volser is encountered (that is, until a loop is detected).

This problem is probably due to one of the following reasons:

Incorrectly defined pool ranges.
The wrong pool was requested by the job.
Invalid stacking criteria were defined.

This message follows message CTT356W which specifies the data set for which stacking stopped.

Stacking stops for the data set. The job continues without stacking for this dsn.

Corrective Action: Determine the reason for this error and correct the problem.

CTT366W NO MEDIA ENTRIES WERE DEFINED IN CTTPARM

Explanation: The search process found that no Media entries were defined in CTTPARM. The search process uses the values specified for the Media parameters in CTTPARM to calculate the remaining size on a volume.

This message follows message CTT356W which specifies the data set for which stacking stopped.

Stacking stops for the data set. The job continues without stacking for this dsn. No data set stacking can be performed until this problem is corrected.

Corrective Action: Define Media parameters in CTTPARM, as explained in the Control-M/Tape chapter of the INCONTROL for z/OS Installation Guide. Definition of these parameters only takes effect after Control-M/Tape is brought down and restarted.

CTT367I DDNAME `ddName` OF JOB `jobName` CHANGED TO DEFERRED MOUNT

Explanation: This information message indicates that the specified immediate request for a scratch tape was changed to a deferred request by Control-M/Tape.

Under JES3, dynamic data set stacking is performed only in deferred mode. When a job is interpreted by JES3, Control-M/Tape searches the job for created data sets that are candidates for stacking. If any of the scratch requests for tapes for these candidate data sets are in immediate mode, Control-M/Tape changes them to deferred mode so that stacking can be performed.

The variables in this message are:

ddName -- A data set DD name that is a candidate for stacking.
jobName -- The name of the job interpreted by JES3 that created the data set referenced by ddName.

The job continues. The DD allocation is deferred so that stacking can be performed.

Corrective Action: No action is required.

CTT368W SEARCH STOPPED BY EXIT 10

Explanation: User Exit CTTX010 requested that stacking search processing be stopped for the data set. The exit request causes a halt in the stacking process for the data set specified in message CTT356W which follows this message.

Stacking stops for the data set. The job continues and a scratch volume is requested for the data set.

Corrective Action: No action is required.

CTT369W FUNCTION `func` FAILED. VOLSER=`volser`, OPCODE=`opc`, RC=`rc`, REASON=`rsn`, INTERFACE=`modName`

Explanation: The silo function requested for a volume ended with a warning.

The software of the robotic tape library returns the operation code opc, the return code rc in decimal format, and the reason rsn in hexadecimal format.

In this message, modName is one of the following Automated Tape library Interface module names:

CTTRSTK - Control-M/Tape interface to a StorageTek silo.
CTTOAM -- Control-M/Tape interface to an automated tape library controlled by an OAM such as IBM ATL or IBM VTS.
CTTMMRX - Control-M/Tape interface to a Memorex Telex robotic tape library.
CTTHACC - Control-M/Tape interface to an ADIC robotic tape library.
CTTFUJI - Control-M/Tape interface to a Fujitsu robotic tape library.

If modName indicates the last library to be searched, the CTTRBM utility continues processing with the next volume. If modName indicates a library other than the last library to be searched, the CTTRBM utility searches for the same volume (volser) in the next tape library.

Corrective Action: Refer to the messages and codes documentation for your tape robot or silo for a description of the codes returned in this message.

CTT370E VOLSER `volser` HAS NO VAULTING PATTERN

Explanation: CTTVVM cannot process the volume whose serial number is volser, because it has no vaulting pattern. The CTTVVM utility groups logical volumes by their vaulting patterns. No vaulting pattern is an integrity error in the Media Database (MDB).

The CTTVEXP utility issues error message CTT344E and does not include the volser volume serial number in the Export List file.

Corrective Action: Use the CTTIDB utility to check the integrity of the MDB. Then, fix the errors.

CTT371I LOGICAL VOLSER `log_volser`, IS TO BE IMPORTED FROM PHYSICAL VOLSER `phys_volser`

Explanation: This information message specifies the serial numbers for a logical volume (log_volser) that should be imported, and the physical volume (phys_volser) from which it should be imported. The CTTVVM utility determines when a logical volume should be imported back to the Virtual Tape Server (VTS) .

The CTTVVM utility produces an Import List File for the volume with the specified serial number.

Corrective Action: Issue an IMPORT command. Refer to the previous CTT347I message for the serial number of the Import List volume.

CTT372E `util` CAN NOT RUN WHEN CONTROL-M/TAPE IS NOT ACTIVE

Explanation: The CTTVVM or CTTVEXP utility could not run because Control-M/Tape is not active. Control-M/Tape intercepts OAM messages about completion of the export operation in a real-time environment. For this reason, Control-M/Tape must be active when the CTTVVM and CTTVEXP utilities run.

The specified utility stops.

Corrective Action: Start Control-M/Tape and rerun CTTVVM and CTTVEXP.

CTT373W FUNCTION `func` FOR VOLUME `volser` FAILED - VOLUME IS IN USE

Explanation: Control-M/Tape tried to perform the func function on the volser volume in the robotic tape library, but the robotic tape library returned an error because the tape is currently being used by the robotic tape library.

The utility continues processing. The IOA Functional Monitor will later automatically retry the func function on the volser volume.

Corrective Action: No action is required.

CTT374W CLEANUP FOR {VOLUME `vol`| LABEL `vol label`} COMPLETED WITH AN ERROR. REASON=`rsn`

Explanation: An error occurred during "volume cleanup" or "label cleanup."

Volume cleanup is the deletion from the Media database of all data set records of a volume.

Label cleanup is the deletion from the Media database of a database record.

Cleanup occurs when

a scratch volume is used for a mount requestControl-M/Tape must delete all the old data set records of the volume from the Media database before the new data sets are tracked into the Media database.
a volume is deleted from the Media databaseControl-M/Tape must delete all the data set records of the volume before deleting the volume record.

The variables in this message are:

vol - the identity of the volume
label - the identity of the database record
rsn - a 4-digit reason code

Possible values of rsn, and their explanations, are shown in the following table:

rsn	Explanation
0001	No data set record for L-Index
0002	Attempt to remove an active data set
0003	Active data set on a non-active volume
0004	Record of the first volume of the data set not found
0005	The first volume of the multi-volume chain differs from the first volume of the data set
0006	Non-active volume in an active multi-volume chain
0007	The volume update function failed for a volume
0008	The update function failed for a volume
0009	A data set that had already been found could not be read at deletion time
0010	Data set deletion failed
0011	Next volume expected but not found
0012	A volume other than the first in a multi-volume chain could not be read
0013	A volume other than the first in an active multi-volume chain is not active
0014	The volume update function failed for a volume other than the first in a multi-volume chain
0015	The first volume in a multi-volume chain differs from the first volume of a data set (other than the first)
0016	The update function failed for a volume other than the first in a multi-volume chain
0017	Database access error while reading the L-index
0018	The expected L-index was not found
0019	The L-index has a non-matching RBA
0020	An attempt to delete the L-index failed
0022	The update function failed for a data set (DDSVOLS#)

The cleanup process is performed only for the current volume in the multi-volume chain of which it is part. Processing continues normally.

Corrective Action: Use the CTTIDB utility to check the logical integrity of the Media database, and correct all errors that are reported by the utility. For more information, see the description of verifying Media database integrity in the Control-M/Tape Implementation Guide.

CTT380I JOBNAME DSN C-OBS C-SIZE N-OBS N-SIZE MAXSIZE MINSIZE S-DEV

Explanation: This information message is a column header for message CTT381I.

This message is followed by message CTT381I.

Corrective Action: No action is required.

CTT381I `jobName dsn c_obs c_size n_obs n_size max_size min_size s_dev`

Explanation: This information message contains summary information on each data set for which statistical calculations regarding average data set size have been performed.

This CTT381I message follows the CTT380I message, which provides column headers for the information in this CTT381I message.

The variables in this message are:

jobName - the name or user ID of the job which created the data set
dsn - the name of the data set
c_obs - the number of observations used for statistical calculations before the present run
c_size - the data set average size, calculated on the basis of c_obs
n_obs - the number of observations used for statistical calculations (including the present run) This number differs from c_obs by the number of valid runs of jobName and dsn since the previous run of the CTTSTK utility
n_size - the data set average size, calculated on the basis of n_obs
max_size - the data set maximum size encountered in the present run This value is meaningful only if more than one new observation has been encountered for the jobName and dsn statistics
min_size - the data set minimum size encountered in the present run This value is meaningful only if more than one new observation has been encountered for the jobName and dsn statistics
s_dev - the standard deviation for the average size of the data set, calculated on the basis of n_obs

Corrective Action: No action is required.

CTT390S FAILED TO OPEN DDNAME `ddName`.

Explanation: Open of the ddName DD statement 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.

CTT394S INVALID PARAMETER - `parm`

Explanation: An invalid parameter was specified.

If this message was issued during execution of the CTMBLT utility, it is followed by message BLT895I and/or BLT896I, which identify the problematic job, keyword, and value.This message may also be issued by the CTMBUPD utility.

The report or utility stops executing with a condition code of 08 or 12.

Corrective Action: For the syntax of the parameter for the report or utility, see either the INCONTROL for z/OS Administrator Guide or the INCONTROL for z/OS Utilities Guide, as appropriate.

Messages CTT400 through CTT4xx

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

CTT400S INVALID RETURN CODE FROM SORT = `rc`. CHECK THE SORT MANUAL

Explanation: A sort program that has been activated internally ended with an unexpected return code (rc).

The program stops executing with a condition code higher than 08.

Corrective Action: Refer to documentation for the sort program and to the sort messages of the job to clarify the reason.

CTT401S INTERNAL ERROR, REASON: `rsn`

Explanation: Control-M/Tape failed during the dynamic installation process for MVS Tape Label Processing Exits.

The started task of Control-M/Tape real-time environment is stopped.

Corrective Action: Contact BMC technical support.

CTT402S INCONSISTENCIES FOUND IN MODULE `mod`: {LENGTH | V-CONSTANT} MISMATCH

Explanation: Control-M/Tape failed during the dynamic installation process for MVS Tape Label Processing Exits. Control-M/Tape found an inconsistency between the modules in the LPA and in the SYS1.LPALIB library.

The started task in the Control-M/Tape real-time environment is stopped.

Corrective Action: Make sure the module in error is match between the LPA and SYS1.LPALIB. If you have recently applied the IBM PTF to the SYS1.LPALIB library, then perform an IPL or add the LPALIB DD statement to the CTTINIT procedure that points to the SYS1.LPALIB library before applying the IBM PTF.

CTT403E CSVDYNEX REQUEST=`request` FOR MODULE CTTHCKE FAILED. RC=`rc` RS=`rs`

Explanation: The Add/Delete action for Control-M/Tape exit routine CTTHCKE of the HZSADDCHECK exit ended with an unexpected return code and reason code.

Control-M/Tape continues to initialize/terminate normally.

The Control-M/Tape check is not added to or deleted from IBM Health Checker.

Corrective Action: To clarify the reason for this issue, refer to the IBM documentation for IBM Health Checker and the CSVDYNEX macro.

CTT404E HZSCHECK REQUEST=`request` FAILED. RC=`rc` RS=`rs`

Explanation: The specified requested action (either ADDNEW or DELETE) for a Control-M/Tape check by IBM Health Checker ended with an unexpected return code and reason code.

Control-M/Tape continues to initialize/terminate normally.

The Control-M/Tape check is not added to or deleted from IBM Health Checker.

Corrective Action: To clarify the reason for this issue, refer to the IBM documentation for IBM Health Checker and the HZSCHECK macro.

CTT405E CONTROL-M/TAPE FAILED TO REGISTER A CHECK TO THE HEALTH CHECKER. RC=`rc`

Explanation: Control-M/Tape was unable to add its check to IBM Health Checker.

Possible RC values are:

08 – CSVDYNEX ADD request for CTTHCKE exit routine of HZSADDCHECK exit failed.
12 – HZSCHECK ADDNEW request for Control-M/Tape check to IBM Halth Checker failed.
16 – CSVDYNEX DELETE request for CTTHCKE exit routine of HZSADDCHECK exit failed.
20 – HZSCHECK DELETE request for Control-M/Tape check to IBM Halth Checker failed.
24 – Control block CTTHZS not found.
28 – Control block CTTTCT not found.
32 – GETMAIN failed.
36 – Running under z/OS lower than 2.2.

Corrective Action: For more information, refer to the IBM documentation for IBM Health Checker and for the CSVDYNEX and HZSCHECK macros.

CTT420I MODULE: `modName` CSECT: `csect`

Explanation: This information message follows other messages concerning the dynamic intercept process and identifies the module and CSECT in error.

Corrective Action: No action is required.

CTT421S VERIFY REJECTED. INTERCEPT: `i_id` VER-ID: `v_id`

Explanation: One of the dynamic intercepts failed verification. Verification of an MVS module failed. The verification is done against the module in memory (LPA). The module or CSECT names are identified by CTT420I.

The dynamic intercept process is terminated. The failing CSECT is dumped into the data set pointed to by the DADUMP DD statement.

Corrective Action: Make sure that the intercepts are not already applied. Keep the dump of the failing CSECT. Contact BMC Customer Support.

CTT422S MODULE `modName` NOT FOUND IN LPA/MLPA/FLPA

Explanation: One of the dynamic intercept modules was not found in the Active LPA Queue (FLPA or MLPA) or in PLPA. The module is searched in the LPA, MLPA, or FLPA of the current active system.

The dynamic intercept process is terminated.

Corrective Action: Contact BMC Customer Support.

CTT423S CSECT `csect` NOT FOUND IN MODULE `modName`

Explanation: One of the dynamic intercept CSECTs was not found in the modName module. The CSECT is searched in the specified module that resides in your STEPLIB libraries or in the cataloged SYS1.LPALIB library.

The dynamic intercept process is terminated.

Corrective Action: Contact BMC Customer Support.

CTT424S CTTIDYN INTERNAL ERROR. CODE: `rc` REASON: `rsn`

Explanation: An internal error occurred in the dynamic intercept process.

The dynamic intercept process is terminated. All the intercepts already processed are rejected. The module or CSECT names are identified by CTT420I.

Corrective Action: Contact BMC Customer Support.

CTT425S {ALLOC | UNALLOC} FAILED FOR DDNAME `ddName`

Explanation: The specified action failed for the specified DD statement.

The dynamic intercept process is terminated.

Corrective Action: Contact BMC Customer Support.

CTT426W LENGTH MISMATCH. MODULE: `modName` CSECT: `csect`

Explanation: There is a difference in length between the memory copy (in LPA) and the disk copy (in SYS1.LPALIB) of a specified module. This situation indicates a problem in the environment.

The dynamic intercept process continues.

Corrective Action: No action is required.

CTT427S SVC UPDATE FAILED FOR `modName`. RC: `rc`

Explanation: The SVCUPDTE function failed with the specified return code. The Control-M/Tape SVC could not be installed.

The dynamic intercept process is terminated.

Corrective Action: Contact BMC Customer Support.

CTT428I REMOVE PROCESSING STARTED

Explanation: This information message indicates that the dynamic intercept process is reversed and the MVS intercepts are being removed.

This message is the result of one of the following:

Starting the CTTINIT utility with the MODE parameter set to REMOVE.
A failure during the dynamic intercept process.

If the reason for this message is failure of the dynamic intercept process, after the intercepts are removed, the currently executing utility (CTTINIT or CTTHSMP) terminates.

Corrective Action: No action is required.

CTT429S ZAP: `zap` REP: `rep_num` NOT IN PLACE. ADDR: `add`

Explanation: Removal of Control-M/Tape intercepts failed. The expected intercept code was not found.

The Dynamic Intercepts Removal Process stops.

Corrective Action: Notify BMC Customer Support.

CTT430S INCONSISTENT FMID FOUND. MOD=`mod`

Explanation: The input to the CTTHSMP utility contains information on MVS MOD entries that belong to more than one FMID. The CTTHSMP utility cannot operate on input that contains several FMIDs.

The program terminates with a return code of 12.

Corrective Action: Provide input to the CTTHSMP utility in a single FMID MOD group.

CTT431S UMID/RMID BUFFER OVERFLOW

Explanation: Too many UMID or RMID entries were added to the work area in the CTTHSMP utility. The utility cannot process more than 20,000 entries.

The program terminates with a return code of 16.

Corrective Action: Call BMC Customer Support.

CTT432W WARNING: MOD=`mod` HAS UMID=`umid`

Explanation: The CTTHSMP utility detected a UMID in an IBM MOD entry. IBM MODs do not normally have UMIDs. The detected UMID can indicate the existence of an IBM APAR fix or a hook applied for another product.

The program continues processing but ends with a return code of 4.

Corrective Action: Check which modifications apply to the relevant module and change accordingly.

CTT433W OPTIONAL COMPONENT `opt_cpnt` CANNOT BE INSTALLED, COMPONENT DISABLED

Explanation: Control-M/Tape could not locate the elements necessary to install optional component opt_cpnt. Possible causes are:

The component requirements are incompatible with the release of MVS installed at this site.
Another product uses the same resources that are needed for installation of this component.
An internal error.

Control-M/Tape continues operation without optional component opt-cpnt.

Corrective Action: Contact BMC Customer Support.

CTT440S INTERNAL ERROR IN CTTIWTO. CODE: `int_code` REASON: `rsn`

Explanation: An error occurred while trying to install or remove the Control-M/Tape WTO Intercept.

The dynamic intercept process is terminated.

Corrective Action: Call BMC Customer Support.

CTT441S SVC `svcNumber` INTERCEPT LEVEL ERROR

Explanation: The CTTWTOI module in the Control-M/Tape Load library does not contain the expected header.

The dynamic intercept process is terminated.

Corrective Action: Call BMC Customer Support.

CTT442S SVC `svc_num` INTERCEPT NOT FOUND. REMOVE NOT PERFORMED

Explanation: As part of the Control-M/Tape termination process, when trying to remove the Control-M/Tape WTO Intercept, the current WTO module (SVC 35) was not identified as the Control-M/Tape Intercept.

The dynamic intercept process is terminated. A snap of the current WTO SVC is provided under the DADUMP DD name.

Corrective Action: Check if some other program product at your site is interfering with MVS WTO and installing its own WTO Intercept. If not, call BMC Customer Support.

CTT450W VOLUME `vol` NOT MOVED. VOLUME STATUS WAS CHANGED.

Explanation: The CTTVTM utility initiated the movement of the vol volume to a new location, but the status of the volume was changed by another job before the volume record was updated in the Media database.

The volume is not moved to a new location, although the movement appears in the utility output report.

Corrective Action: Do not move the volume. Ignore the vol entry in the CTTVTM utility output report.

CTT451E LOCATION `loc` FOR VOLUME `vol` NOT FOUND IN RULE. VOLUME MARKED MANUALLY VAULTED

Explanation: During a run of the CTTVTM utility with MODE set to CONVERT, the specified volume was marked vaulted but its current location was not found in the vault pattern of the matching rule of the volume data set.

The CTTVTM utility moves the volume to MAINLIB in the Distribution Report and marks it as a potential vault.

Corrective Action: Check the vault pattern of the rule that matches the volume’s data set and change it to include the current location name. Then rerun the CTTVTM utility.

CTT452E RULE NOT FOUND FOR DATASET ON VOLUME `volser`. VOLUME MARKED MANUALLY VAULTED

Explanation: No rule was found for the data set used to determine the vaulting pattern for volume volser. Possible causes are:

MODE was set to CONVERT for the CTTVTM utility, no rule exists for the data set, and the data set resides on a volume marked as VAULTED.
MODE was set to RECALC for the CTTVTM utility, and no rule exists for a volume which is already marked as MANUALLY VAULTED.

This message is accompanied by message CTT202, which supplies the name of the data set used to determine the vaulting pattern for this volume.

If MODE was set to CONVERT, the volume is marked as MANUALY VAULTED.

In both CONVERT and RECALC modes, the volume is assigned the current location, and the expiration date of the data set that is used to determine the vaulting pattern of the volume.

Corrective Action: If a rule should have existed for the data set, define this rule and rerun CTTVTM with MODE set to RECALC.

CTT453E RESLOT=YES IS INVALID WITH MODE={SLOTBLD | BOXBLD}

Explanation: The RESLOT parameter and SLOTBLD or BOXBLD mode were specified for the CTTVTM utility. The RESLOT=YES and MODE=SLOTBLD or MODE=BOXBLD expressions cannot be both specified for the same run of the CTTVTM utility.

CTTVTM stops execution.

Corrective Action: If you want to run the CTTVTM utility with RESLOT=YES, change the mode of the utility to REGULAR or RECALC; otherwise, remove the RESLOT=YES option.

CTT454E BOX `boxName` (`boxRecordNum`) NOT FOUND IN MDB

Explanation: The CTTVTM utility detected a logical error while processing the Media Database (MDB). CTTVTM accesses the volumes in a box by locating all its associated records. In this case, the box record number identified in the message cannot be located in the MDB. As a result, the data accessed for this box might be incomplete.

CTTVTM continues processing.

Corrective Action: If it is important to obtain precise data for the box in question, run CTTVTM in the BOXBLD mode.

CTT455E BOX COUNT `boxId` (`count`) INCONSISTENT WITH NUMBER OF VOLUMES (`num`)

Explanation: The CTTVTM utility detected that the number of volumes in the box found in the box record differs from the number of volumes actually in the box (count), based on information from the volume records (num). The two values should match.

The utility continues processing.

Corrective Action: Contact your IOA database administrator.

CTT456E BOX `boxId` VOLUME LIST IS INCONSISTENT WITH VOLUMES BELONGING TO THIS BOX

Explanation: The CTTVTM utility detected that the list of volumes in the box detailed in the box record, does not match the volumes that are actually found in the box, based on the information in the volume records. The two lists should match.

The utility continues processing.

Corrective Action: Contact your IOA database administrator.

CTT457E LOCATION `vol_loc` OF VOLUME `volser` DIFFERS FROM LOCATION `box_loc` IN BOX `boxId`

Explanation: The CTTVTM utility detected that the location of the volume (vol_loc) is different than the location of the box in which the volume is contained. The two locations should match.

The utility continues processing.

Corrective Action: Contact your IOA database administrator.

CTT458E NO BOX DEFINITION RECORDS IN MDB

Explanation: The CTTVTM utility did not find any box definition records in the Media Database (MDB), but found volumes that should be vaulted by box. Box records must be defined so vaulting by boxes can take place. To build box records, first the box must be defined and then the CTTVTM utility must be executed with the BOXBLD parameter.

The utility continues processing.

Corrective Action: If vault by boxes is required, define the box records and rerun CTTVTM. If the volumes need not be vaulted by box, change the Vault By Box parameter in the Rule Definition screen (screen TR) to ‘N.’

CTT459E BOX `boxId` IS NOT DEFINED IN MDB

Explanation: The CTTVTM utility found that the record of box (boxId), does not exist in the Media Database (MDB), although at least one volume in the MDB is marked as being in the box.

The utility continues processing.

Corrective Action: Contact your IOA database administrator.

CTT460E EMPTY BOXES ARE NOT AVAILABLE FOR MEDIA `media`

Explanation: The CTTVTM utility cannot find an empty box for the media specified to be used for vaulting by boxes. Volumes in the media specified in the message are marked to be vaulted by boxes. This cannot be carried out, since no more empty boxes are available for this media.

The utility continues processing.

Corrective Action: Check that all the boxes that are supposed to be available for this media are in fact available. If no problem can be found in the availability of the boxes, then define more boxes for this media.

CTT461I THE FOLLOWING VOLUMES FROM BOX `boxId` IN LOCATION `location` NOT MOVED:

Explanation: The CTTVTM utility was unable to move all volumes belonging to the box. The volumes that cannot be moved are listed in CTT202I messages that follow this message.

The utility continues processing without updating the new location of the volumes listed in CTT202I. Therefore, these volumes should be ignored even though they are listed in the CTTVTM report.

Corrective Action: See the previous error message.

CTT462E BOX PREFIX `box_prfx` (MEDIA `media_type`) IS DEFINING DUPLICATE BOX ID/IDS

Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but the box ranges defined in the MAINLIB library with prefix box_pref and media media_type overlap each other, causing duplicate box IDs. Each box ID must be unique.

The utility terminates with no action taken. No box is defined.

Corrective Action: Check and correct the box definitions. Rerun the CTTVTM utility with the BOXBLD parameter.

CTT463E MODE=BOXBLD IS INVALID WITH SIMULATION RUN

Explanation: MODE was set to BOXBLD in a simulation run of the CTTVTM utility. MODE cannot be set to BOXBLD in a simulation run of the CTTVTM utility.

The utility does not start processing.

Corrective Action: If you would like to define new boxes or to change existing box definitions, remove the SIMULATION option and rerun CTTVTM.

CTT464E BOX `boxId` IS IN USE BUT HAS NO DEFINITION

Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but the specified box ID is in use and was not defined. All boxes presently in use must be included in the box definitions in the MAINLIB library.

The utility terminates with no action taken (no box is defined).

Corrective Action: Check the box definitions. Verify that all boxes in use have correct definitions. Rerun the CTTVTM utility with the BOXBLD parameter.

CTT465E BOX `boxId` IS IN USE BUT DEFINED WITH A NEW MEDIA TYPE

Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but a box already in use was defined with a media type different from the one specified in its previous definition. Attributes of a used box cannot be changed.

CTTVTM terminates with no action taken. No box is defined.

Corrective Action: Specify the correct media type for this box, or range of boxes. Rerun the CTTVTM utility with the BOXBLD parameter.

CTT466E BOX `boxId` IS IN USE BUT DEFINED WITH A NEW BOX SIZE

Explanation: The CTTVTM utility was invoked with the BOXBLD parameter, but a box already in use was defined with a new box size. Attributes of a box in use cannot be changed.

The utility terminates with no action (no box is defined).

Corrective Action: Specify the correct size for this box or range of boxes. Rerun the CTTVTM utility with the BOXBLD parameter.

CTT467W VOLUME `volser` HAS MAINLIB IN ITS VAULT PATTERN AND CANNOT BE VAULTED BY BOX

Explanation: The volume (volser) has been marked for vault by box, but MAINLIB is one of the locations specified in its vault pattern. A volume cannot be vaulted by a box if it has MAINLIB as one of the locations in its vault pattern.

The utility continues processing.

Corrective Action: Remove the mark from the volume so that it is not vaulted by box, or remove MAINLIB from the volume vault pattern.

CTT468W UPDATE FOR VOLUME `volser` REJECTED BY CTTX006. INTEGRITY PROBLEMS MIGHT OCCUR

Explanation: Exit CTTX006 rejected a Media Database (MDB) update of the specified volser that was requested by the utility. The utility tried to update the specified volume information in the MDB. Database. However, the update operation was rejected by Exit CTTX006. This may cause an integrity error in the MDB.

The utility continues. The specified volume information is not updated.

Corrective Action: Make sure an integrity error was not created due to the rejected update. Consider modifying Exit CTTX006 in case of unexpected rejections. Ignore this message if the rejection is expected.

CTT469E INCLUDE/EXCLUDE CANNOT BE SPECIFIED WITH MODE={SLOTBLD | BOXBLD}

Explanation: An attempt has been made to run the CTTVTM utility in SLOTBLD or BOXBLD mode, but with at least one INCLUDE or EXCLUDE statement in the input statements of the utility.

The utility stops processing.

Corrective Action: Remove all INCLUDE and EXCLUDE statements from the input statements of the utility and rerun the utility.

CTT470I STATUS OF VOLUME `volser` HAS BEEN SET TO {IN ATL | NOT IN ATL}

Explanation: The automated tape library residence status of the specified volume was set by the CTTSYNC utility in the Media Database (MDB). The CTTSYNC utility synchronizes the automated tape library residence status of MDB volumes according to the actual residence in the automated tape library.

The status of the volume in the MDB was changed to represent its actual status. The utility continues processing.

Corrective Action: No action is required.

CTT471I VOLUME `volser` HAS BEEN MARKED AS IN ATL LIBRARY `newLib` (`oldLib`)

Explanation: The automated tape library name of the specified volume was set by the CTTSYNC utility in the Media Database (MDB). The CTTSYNC utility synchronizes the automated tape library name of the MDB volumes from the name that was previously recorded in the MDB (oldLib) to the library name where the volumes actually reside (newLib).

The status of the volume in the MDB was changed to represent its actual status. The utility continues processing.

Corrective Action: No action is required.

CTT472I ATL NOTIFIED OF STATUS {SCRATCH | ACTIVE} FOR VOLUME `volser`

Explanation: The status of the indicated volume in the automated tape library was set by the CTTSYNC utility according to its status in the Media Database (MDB). The CTTSYNC utility synchronizes the status of volumes in the automated tape library with the equivalent status in the MDB.

The status of the volume in the automated tape library was changed to agree with its status in the MDB. The utility continues processing.

Corrective Action: No action is required.

CTT473I VOLUME `volser` HAS BEEN MARKED AS IN ATL INTERFACE `atl_intfce`

Explanation: This information message indicates that the CTTSYNC utility synchronized the automated tape library with the Media Database (MDB) and found that the volume resides in the automated tape library. The CTTSYC utility then updated the MDB.

The utility continues processing.

Corrective Action: No action is required.

CTT474I TYPE OF VOLUME `volser` HAS BEEN MARKED AS {LOGICAL | PHYSICAL}

Explanation: This information message indicates that the CTTSYNC utility synchronized the automated tape library type with the Media Database (MDB), determined the volume type, and updated the MDB accordingly.

The utility continues processing.

Corrective Action: No action is required.

CTT475I SMS STORAGE GROUP OF VOLUME `volser` HAS BEEN SET TO `storage-group-name`

Explanation: This information message indicates that the CTTSYNC utility retrieved the DFSMS Storage Group of the volume from the automated tape library database, and updated the Media database accordingly.

The utility continues processing.

Corrective Action: No action is required.

CTT476E VOLUME `volser` NOT DEFINED IN MEDIA DATABASE

Explanation: The volser is controlled by DFSMShsm or Control-V, but it is not defined in the Control-M/Tape Media database.

Normal processing continues.

Corrective Action: Check why the volume is not defined in the Media database. If the volume should be defined in Control-M/Tape Media database, then use the CTTMUP utility to add the volume and its datasets to the Media database.

CTT477E VOLUME `volser` STATUS SHOULD BE {ACTIVE | EDM-CONT} IN MEDIA DATABASE

Explanation: The volser is controlled by DFSMShsm or Control-V, but its status in the Media database is not active or not it is not under EDM control.

Normal processing continues.

Corrective Action: Use the CTTMUP utility to update the volume record in the Media database to its correct status.

CTT478E VOLUME `volser` NOT CONTROLLED BY {DFSMSHSM | CONTROL-V}

Explanation: The volser is not controlled by DFSMShsm or Control-V, but it is marked as active and under EDM control in Control-M/Tape Media database.

Normal processing continues.

Corrective Action: Verify that the volume is really not controlled by any of the External Data Managers (for example DFSMShsm, CA-Disk, or ExHPDM) used at your site, and scratch the volume in the Media database using the CTTMUP utility.

CTT479W NO ROBOTIC TAPE LIBRARIES DEFINED IN THE CTTPARM

Explanation: The RBTTYPE parameter is set to NONE in the CTTPARM. The CTTSYNC utility cannot perform synchronization with any automated tape library.

The Utility ends.

Corrective Action: Specify the necessary ATL in the RBTTYPE parameter and rerun the utility.

CTT47AI VOLUME volser HAS BEEN MARKED AS {WORM | NON-WORM}

Explanation: The automated tape library WORM status of the specified volume was set by the CTTSYNC utility in the Media Database (MDB).

The status of the volume in the MDB was changed to represent its actual status, and the utility continues processing.

Corrective Action: No action is required.

CTT481E `stmt` STATEMENT WAS NOT SUPPLIED OR IS NOT FIRST

Explanation: Control-M/Tape did not detect a valid statement at the beginning of the SYSIN file. The SYSIN file for the utility must begin with a valid statement. The SYSIN file is empty or the first control statement is invalid.

The utility stops executing.

Corrective Action: Correct the statements in the SYSIN file, and rerun the utility.

CTT486E RESTART OF UTILITY `util` IS REQUIRED. RUN TIME `dd /mm /yyyy hh :mm :ss`

Explanation: The CTTIDB utility detected that the previous run of the specified Control-M/Tape utility abended.

In this message, dd/ mm/ yyyy is the date of the abending execution of the utility, and hh: mm: ss is the abending execution time.

The CTTIDB utility continues processing.

Corrective Action: Locate and correct the cause of the error. Rerun the utility.

CTT487I PHASE `n /m` OF UTILITY `util` {ENDED | STARTED}

Explanation: This information message indicates that phase n out of m phases of the specified utility started or ended. This message can help in estimating the execution time of the specified utility.

If this message does not indicate the end of the last phase of the utility, the specified utility continues processing.

Corrective Action: No action is required.

CTT488I `n` PERCENT OF `rcrd_type` RECORDS WERE PROCESSED

Explanation: This information message indicates that a Control-M/Tape utility has processed n percent of the records of the specified record type. This message can help in estimating the execution time of the utility.

The utility continues processing.

Corrective Action: No action is required.

CTT489I `n rcrd_type` RECORDS WERE PROCESSED

Explanation: This information message indicates that a Control-M/Tape utility has processed n records of the specified record type. This message can help in estimating the execution time of the utility.

The utility continues processing.

Corrective Action: No action is required.

CTT490E INVALID MULTI-VOLUME GROUP. REASON=`rc`, VOLSER=`volser`, FIRST=`first_vol`

Explanation: Control-M/Tape discovered that the volser belongs to an invalid multivolume group in the Media Database (MDB). The first_vol variable indicates the first volume in the volume group.

Possible values of rc are:

01 - Invalid first volume in the group.
02 - The group does not contain the selected volume.
03 - Invalid PREV and/or NEXT pointers in the volume record.
04 - Volser in DATA differs from INDEX.
05 - Volume number is out of sequence.
06 - Invalid Scratch Timestamp in the volume record.
07 - Invalid volume status.
08 - Loop is detected within the group.
09 - I/O error.
10 - Volume record is not found.

Control-M/Tape stops processing the invalid multivolume group.

Corrective Action: Use the CTTMUP utility to correct invalid fields in volume records within the multivolume group.

CTT492I RECORD CHANGED. REC=`record`

Explanation: This information message indicates that a Control-M/Tape task was about to update a Media Database (MDB) record but discovered that the record was changed by another task.

The record is not updated in the current task.

Corrective Action: If the update was requested from the Online Facility, check the record, and if the update is still required, repeat the request.

CTT493I RETENTION INFORMATION UPDATED SUCCESSFULLY

Explanation: This information message indicates that the CTTRTM utility updated retention information in volume and data set records when running in either CONVERT or RECALC mode.

This message is followed by message CTT202I, which shows the Media Database (MDB) record being handled.

Corrective Action: No action is required.

CTT494I RECORD ELIGIBLE FOR SELECTION

Explanation: This information message indicates that the user was running the CTTRTM utility, and specified INCLUDE or EXCLUDE statements to select Media Database (MDB) records.

This message is followed by message CTT202I which shows the Media Database (MDB) record being handled.

Corrective Action: No action is required.

CTT495I RESTART CANCELLED DUE TO USER REQUEST

Explanation: A previous run of the CTTRTM utility or the CTTVTM utility abended. The current utility run includes the Automatic Restart mode. However, the user set RESTART to NO in the TYPERUN statement to prevent restarting the utility.

The utility continues running without restarting.

Corrective Action: No action is required.

CTT496E TOO MANY RETENTION FACTORS. EXTRANEOUS FACTORS DISCARDED

Explanation: When applying retention criteria to a Media Database (MDB) data set record, Control-M/Tape discovered that more than three retention factors were specified for a data set. Data set retention information is stored in data set records by either the real-time environment when creating a data set, or by the CTTRTM utility in either RECALC or CONVERT mode.

Extraneous retention factors are ignored. Message CTT202I showing the Media Database (MDB) record being handled, is issued after this message.

Corrective Action: Check the matching Control-M/Tape rule, using the Rule Definition screen (Screen TR), and the JCL EXPDT parameter for the data set, and remove any extra retention factors.

CTT497I TASK IS NOT APF AUTHORIZED. CHANGES WERE NOT PERFORMED IN ATL

Explanation: After modifying the Media Database (MDB) records, Control-M/Tape tried to make the equivalent changes in databases of the robot systems (automated tape libraries). To be able to update databases of the robot systems such as StorageTek or IBM 3495, the Control-M/Tape task must be APF-authorized, since this is required by interfaces to the robot systems.

The robot system databases are not updated.

Corrective Action: Contact your system programmer to make the Control-M/Tape task APF-authorized.

CTT498W JCL EXPDT WAS NOT SUPPLIED. INSTALLATION DEFAULT RETENTION USED (`ddName`)

Explanation: According to the matching rule, Control-M/Tape requires that retention criteria for a data set be provided by the JCL EXPDT parameter when creating the data set. However, the JCL EXPDT parameter was not supplied in the JCL. The message is issued by one of the following:

By the real-time environment when creating a data set.
By the CTTRTM utility running in either the RECALC or CONVERT mode.
By the CTTMUP utility when adding new dataset record.

If the message is issued by the Control-M/Tape real-time environment, the ddName parameter will be displayed. In other cases, the message will be followed by message CTT202I, which shows the Media Database (MDB) record being handled.

Installation default retention criteria are applied to the data set record.

Corrective Action: Supply the JCL EXPDT parameter in the DD statement when creating a data set. To change the retention criteria of the data set record that was created using the default retention criteria, use the CTTMUP utility.

CTT499E SLOT CAPACITY RECORD NOT FOUND. VAULT=`vault`, MEDIA=`media`

Explanation: Control-M/Tape has updated a vaulted volume, and has unsuccessfully tried to update the appropriate Slot Definition record, to synchronize its data with the newly updated Volume record.

The Slot Definition records are created by the CTTVTM utility, according to the vault definitions that the user specifies in the Control-M/Tape Vault Definition screen (Screen TV).

The Slot Definition record is not updated.

Corrective Action: Check vault definitions using the Vault Definition screen (Screen TV), and then run the CTTVTM utility in mode SLOTBLD to synchronize the Slot Definition records with the Volume records.

Messages CTT500 through CTT5xx

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

CTT501E PLEASE FILL IN TABLE NAME OR OMIT RULE

Explanation: A rule name was specified without a table name. A rule name cannot be specified without a table name.

Corrective Action: Either specify the table name, or omit the rule name, in order to receive a list of tables in the library.

CTT510E INVALID "ON". USE A, D, J, ME, MG, P, UC, US OR V

Explanation: An invalid option was specified in the ON field.

The ON field is used to specify criteria which must be met before Control-M/Tape performs actions. The option specified identifies certain criteria from the active environment.

Valid options in the ON field are:

A (Account)
D (Data set)
J (Jobname)
ME (Media)
MG (MGMTCLAS)
P (Pgm)
UC (UCB)
US (User ID)
V (VOLSER)

Corrective Action: Correct the entry by specifying a valid ON option.

CTT511E VOLSER RANGE IS INVALID

Explanation: An invalid volser range was specified in ON VOLSER fields. The ON VOLSER field enables specifying a range of volsers. For a volser range to be valid, the first value in the specified range must be less than or equal to the second value.

Corrective Action: Correct the entry by specifying a valid range.

CTT512E VALID RETENTION TYPES ARE CA,CY,DAT,DAY,ED,J,L,P,R,M

Explanation: An invalid retention type was specified in a DO RETENTION statement. The DO RETENTION statement is used to specify a duration for which a data set or volser is kept. The retention type specified identifies how the duration is calculated. There may be a single retention type specified, or a combination of up to three different retention types using the AND/OR field.

Valid retention types are:

CA (MVS Catalog)
CY (Cycles)
DAT (Date)
DAY (Days)
ED (EDM)
J (JCL EXPDT)
L (Last access)
P (Permanent)
R (Return from vault)

Corrective Action: Correct the entry by specifying a valid retention type.

CTT513E THERE MAY BE ONLY ONE RETENTION PERIOD PER "ON" BLOCK

Explanation: An attempt was made to open a DO RETENTION statement in a rule that already contains a DO RETENTION statement. The DO RETENTION statement specifies a duration for which a data set or volser is kept.

To avoid conflicting duration periods for the criteria defined in the ON block, there may be only one DO RETENTION statement per ON block.

Corrective Action: Instead of opening a second DO RETENTION statement, specify a combination of retention periods in one DO RETENTION statement using the AND/OR parameter.

CTT514E INVALID RETENTION COMBINATION

Explanation: An attempt was made to specify a retention period that does not correspond to previous retention periods in the DO RETENTION statement. The DO RETENTION statement has up to three different retention periods to specify a duration for which a data set or volser is kept.

To avoid conflicting duration periods, the combination of retention periods specified in one DO RETENTION statement must be logical. For example, a retention period of PERMANENT may not be combined with any other retention periods.

Corrective Action: Specify a valid retention combination.

CTT515E PERMANENT RETENTION IN VAULT. ADDITIONAL VAULTS CANNOT BE SPECIFIED

Explanation: An attempt was made to specify an additional vault or an additional retention period in a DO VAULT statement that already contains a retention period of PERMANENT. If a volume is to be kept permanently, it cannot be transferred to an additional vault, and no more retention periods can be specified.

Corrective Action: Clear the additional VAULT parameter or AND/OR parameter, if the volume is to be kept permanently, or change the retention period from PERMANENT to another retention period.

CTT516E RETENTION TYPE MUST BE FILLED IN

Explanation: A retention line was opened, but no retention type was specified. The retention period in a DO RETENTION, ABENDRET, or VAULT statement specifies a duration for which a data set or volser is kept. The retention type determines how the duration is calculated. There may be a single retention type, or a combination of up to three different retention types using the AND/OR field.

Valid retention types are: CA (MVS Catalog), CY (Cycles), DAT (Date), DAY (Days), ED (EDM), EX (EXPIRE), J (JCL EXPDT), L (Last access), P (Permanent), R (Return from vault), and V (VAULT DAYS). Some retention types are not valid for all retention periods in the different statements.

Corrective Action: Specify a valid retention type, or clear the preceding AND/OR field (or DO field in the case of a single retention) if no further retention criteria are required.

CTT517E VALID WHEN TYPES ARE A,CH,CL,K,M,O

Explanation: The WHEN type was specified in the WHEN field of a DO statement was invalid or absent. The WHEN parameter determines when the DO statement that contains the WHEN parameter is performed.

Valid WHEN types are:

A (Close after abend)
CH (Check in volumes)
CL (Close)
K (Keep)
M (Mount)
O (Open)

Corrective Action: Correct the entry by specifying a valid WHEN type.

CTT518E ONLY ONE POOL NAME PER "ON" BLOCK MAY BE SPECIFIED

Explanation: An attempt was made to open a DO POOL statement in an ON block that already contains a DO POOL statement. The DO POOL statement specifies the pool from which a scratch volume is taken.

To avoid conflicting data when mounting a scratch tape, there may be only one DO POOL statement per ON block.

Corrective Action: Delete the second DO POOL statement by clearing the DO field.

CTT519E ONLY ONE PRINT LABEL OPTION PER "ON" BLOCK MAY BE SPECIFIED

Explanation: An attempt was made to open a DO LABEL statement in an ON block that already contains a DO LABEL statement. The DO LABEL statement specifies whether or not a label is to be printed when a data set is written on a volume.

To avoid conflicting data when deciding whether or not to print a label, there may be only one DO LABEL statement per ON block.

Corrective Action: Delete the second DO LABEL statement by clearing the DO field.

CTT51AE INVALID VALUE. SPECIFY A NUMERIC VALUE (bottom_limit-upper_limit)

Explanation: An invalid value was specified.

Corrective Action: Specify a numeric value in the range between bottom_limit and upper_limit.

CTT520E ONLY ONE STACK OPTION PER "ON" BLOCK MAY BE SPECIFIED

Explanation: An attempt was made to open a DO STACK statement in an ON block that already contains a DO STACK statement. The DO STACK statement specifies whether or not stacking of data sets is performed on a certain volume.

To avoid conflicting data when deciding whether or not to stack data sets on a volume, there may be only one DO STACK statement per ON block.

Corrective Action: Delete the second DO STACK statement by clearing the DO field.

CTT521E ONLY ONE VAULT CYCLE PER "ON" BLOCK MAY BE SPECIFIED

Explanation: An attempt was made to open a DO VAULT statement in a rule that already contains a DO VAULT statement. The DO VAULT statement determines in which vaults, if any, a volume is to be kept.

To ensure that a volume is specified in the correct sequence of vaults, there may be only one DO VAULT statement per ON block. However, a sequence of vaults may be specified in a DO VAULT statement. An empty VAULT entry is opened whenever a new vault is specified in a DO VAULT statement.

Corrective Action: Instead of opening a second DO VAULT statement, specify a sequence of vaults in the DO VAULT statement using the empty VAULT entry at the end of the statement.

CTT522E A BLOCK WITH FILLED "DO" STATEMENTS AND NO "ON" STATEMENTS IS INVALID

Explanation: The rule does not contain any ON statements. Every rule must have at least one ON statement that identifies under what conditions to perform the DO statements.

The rule is not saved.

Corrective Action: Add an ON statement to the rule.

CTT523E AT LEAST ONE CYCLE MUST BE SPECIFIED

Explanation: In a DO RETENTION, ABENDRET, or VAULT statement, a value of zero was specified in the CYCLES field of a retention period. The CYCLES retention type determines the number of cycles that a volume or data set is to be kept. A cycle of a data set relates to the creation of a copy of the specified data set. A retention period of zero is invalid since it means there is no duration.

Corrective Action: Specify a valid number of CYCLES or change the retention type.

CTT524E ONLY ONE OWNER PER "ON" BLOCK MAY BE SPECIFIED

Explanation: An attempt was made to open a DO OWNER statement in an ON block that already contains a DO OWNER statement. The DO OWNER statement determines the owner of a volume data set. There may be only one owner for a volume or data set. Therefore, there may be only one DO OWNER statement per ON block.

Corrective Action: Delete the second DO OWNER statement by clearing the DO field.

CTT525E DATE ALREADY IN PREVIOUS VAULT RANGE

Explanation: A retention type of DATE was specified for a vault. However, the date specified overlaps the duration of the same volume in a previous vault.

The DO VAULT statement enables a volume to be kept in a sequence of vaults. Each vault may have its own retention period. A volume is transferred from one vault to the next vault in the sequence at the end of its duration field. Overlapping of dates is invalid. The calculated duration for the retention of a volume or data set in a vault must only begin at the end of the retention period of the previous vault.

Corrective Action: Modify the retention date to a date after the retention period of the previous vault.

CTT526E ONLY ONE "ON DATASET" STATEMENT PER RULE MAY BE SPECIFIED

Explanation: An attempt was made to add an ON DATASET statement in a rule that already contains an ON DATASET statement. The ON DATASET statement specifies the data set or data set prefix that must be matched for Control-M/Tape to perform actions defined in the rule. This is the basic search criterion. Therefore, only one ON DATASET statement is allowed.

Corrective Action: Delete one of the ON DATASET statements. A mask containing * and ? may be used instead of a data set name.

CTT527E VALID RETENTION TYPES ARE CA,CY,DAT,DAY,EX,J,L,P,V,M

Explanation: An invalid retention type was specified in a retention period of a DO VAULT statement. The DO VAULT retention period specifies a duration for which a data set or volser is kept in a vault. The retention type specified identifies how the duration is calculated. There may be a single retention type, or a combination of up to three types using the AND/OR field.

Valid retention types are:

CA - MVS Catalog
CY - Cycles
DAT - Date
DAY - Days
EX - EXPIRE
J - JCL EXPDT
L - Last access
P - Permanent
V - VAULT DAYS
M - MVS Catalog

Corrective Action: Correct the entry by specifying a valid retention type.

CTT528E VALID RETENTION TYPES ARE CA,CY,DAT,DAY,ED,J,L,P,M

Explanation: An invalid retention type was specified in a retention period of a DO ABENDRET statement. The DO ABENDRET retention period specifies a duration for which a data set or volser is kept in case of an abend. The retention type specified identifies how the duration is calculated. There may be a single retention type, or a combination of up to three types using the AND/OR field).

Valid retention types are:

CA -- MVS Catalog
CY -- Cycles
DAT -- Date
DAY -- Days
ED -- EDM
J -- JCL EXPDT
L -- Last access
P -- Permanent
M -- MVS Catalog

Corrective Action: Correct the entry by specifying a valid retention type.

CTT529E INVALID DO STATEMENT WAS SPECIFIED

Explanation: An invalid DO statement was specified in a Control-M/Tape rule (screen TR). DO statements specify actions to be performed by Control-M/Tape when scheduling and selection criteria for a rule are satisfied. For more information about DO statements, see the description of ON and DO statements in the rule parameters chapter of the Control-M/Tape User Guide.

The rule definition cannot be saved.

Corrective Action: Either delete the invalid DO statement or replace it with a valid DO statement.

CTT530E POOL ASSIGNMENT IS INVALID AFTER "ON VOLUME" OR "ON MEDIA" ARE SPECIFIED

Explanation: A POOL assignment was requested by means of a DO field in a rule that previously contains ON VOLUME or ON MEDIA statements. The POOL assignment is only meaningful when scratch tapes may be requested. If a volume or media appears as criteria for executing the rule, scratch tapes cannot be requested.

Corrective Action: Correct the entry by deleting the POOL assignment.

CTT531E THE PREFIX FIELD ON CYCLE RETENTIONS MUST BE THE SAME

Explanation: An attempt was made to define a cycle retention type with a prefix that does not match the prefix of another cycle retention type. The prefix of the cycle retention types for the DO RETENTION and DO ABENDRET statements must be the same. The prefix of the cycle retention types within the DO VAULT statement must also be the same.

Corrective Action: Correct the entry.

CTT532E STACK=Y IS INVALID AFTER "ON {VOLUME | MEDIA | UCB} " IS SPECIFIED

Explanation: A STACK=Y statement was specified in a rule that previously contained an ON VOLUME, ON MEDIA, or ON UCB statement. STACK=Y processing takes place before media, volume or UCB information is available. Therefore, rules that are triggered by volume, media or UCB information cannot request dynamic stacking.

Correct the rule by deleting the STACK=Y statement or use a different ON statement.

Corrective Action: No action is required.

CTT533E UCB RANGE IS INVALID

Explanation: The UCB range specified in the TR screen is invalid. The FROM or TO value is not a valid UCB address (hexadecimal value) or the FROM value is larger than the TO value.

The rule cannot be saved until the range is specified correctly.

Corrective Action: Specify a valid UCB range and save the rule.

CTT534E ONLY ONE `do_stmt` STATEMENT PER RULE CAN BE SPECIFIED

Explanation: The specified DO statement (do_stmt) was included more than once in a Control-M/Tape rule. Only one DO statement of the specified type can be included in each Control-M/Tape rule.

The rule definition cannot be saved.

Corrective Action: Delete the duplicate DO statement, leaving only one DO statement of the specified type. See the section on ON and DO blocks in the chapter on rule parameters of the Control-M/Tape User Guide for more information about the specified DO statement.

CTT535E VALID SCOPES ARE DSN OR VOL

Explanation: An invalid value was specified for the SCOPE subparameter in a DO STACK statement in the Rule Definition screen (screen TR).

Valid SCOPE values:

DSN -- Do not stack the current copy of the data set.
VOL -- Do not stack the current copy of the data set. Mark the volume on which it is created as non-stackable.

The rule definition cannot be saved.

Corrective Action: Specify a valid SCOPE value.

CTT536E "DO STKRULE" IS VALID ONLY IF "DO STACK=Y"

Explanation: A DO STKRULE statement was specified in a Control-M/Tape rule that does not include a DO STACK=Y statement. A DO STKRULE statement can only be specified if a STACK=Y statement is specified earlier in the rule.

The rule definition cannot be saved.

Corrective Action: Either specify a DO STACK=Y statement earlier in the rule or remove the DO STKRULE statement.

CTT537E SPECIFY A JOBNAME, DSN, OR BOTH

Explanation: No value was specified for subparameters JOB and DSN in a DO STKRULE statement of a Control-M/Tape rule. The DO STKRULE statement describes data sets or jobs that create data sets, which should not be stacked with the data set whose access triggered the rule. Therefore, a value must be specified for at least one of these subparameters.

The rule definition is not saved.

Corrective Action: Specify the required jobname, data set name, or both, in DO STKRULE and save the rule.

CTT538E VALID OPTIONS FOR THIS FIELD ARE YES OR NO

Explanation: An invalid value was specified for the current field in a Control-M/Tape rule. This field must have a value of either YES or NO.

The rule definition cannot be saved.

Corrective Action: Specify either YES or NO and save the rule.

CTT539E VALID DYNVOL OPTIONS ARE I, E, N, P, OR Y

Explanation: An invalid value was specified in a DO DYNVOL statement of a Control-M/Tape rule.

Valid values for a DO DYNVOL statement are:

I - Ignore the volume.
E - Define the volume dynamically in the Media Database as an external tape.
N - Do not define the volume in the Media Database. Specific request cases abend the job. Nonspecific (scratch) requests are rejected.
P - Prompt the operator to determine whether or not to dynamically define the volume.
Y - Define the volume dynamically in the Media Database.

The rule definition cannot be saved.

Corrective Action: Either specify a valid value for the DO DYNVOL statement, or delete the statement.

CTT540E VALID RECREATE OPTIONS ARE YES, NO, OR PERMANENT

Explanation: An invalid value was specified in a DO RECREATE statement of a Control-M/Tape rule.

Valid values for a DO RECREATE statement are:

YES - Data sets (except permanent data sets) can be recreated.
NO - Data sets cannot be recreated.
PERMANENT - Data sets (including permanent data sets) can be recreated.

The rule definition cannot be saved.

Corrective Action: Either specify a valid value for the DO RECREATE statement or delete the statement.

CTT541E VALID STKMODE OPTIONS ARE SIMPLE, VAULT, RETENTION, OR ALL

Explanation: An invalid value was specified in a DO STKMODE statement of a Control-M/Tape rule. A DO STKMODE statement determines the algorithm used to search for a volume on which to stack the current data set. These searches are performed on the same pool as the eligible candidate volumes for stacking.

Valid values for a DO STKMODE statement are:

SIMPLE - Searches for volumes regardless of retention date and vaulting pattern.
VAULT - Searches for volumes that have a vaulting pattern similar to the stacked data set.
RETENTION - Searches for volumes which have a similar or later retention date.
ALL - Satisfies the requirements of both the Vault and Retention search criteria.

The rule definition cannot be saved.

Corrective Action: Specify a valid value for the DO STKMODE statement, or delete the statement.

CTT542E KEEP EVENT IS INVALID AFTER "ON PGM" IS SPECIFIED

Explanation: A DO statement at KEEP event was specified in a rule that previously contained an ON PGM statement. KEEP processing takes place when the PGM name is no longer available. Therefore, rules that are triggered by a PGM name cannot request an IOA service at a KEEP event.

Control-M/Tape does not save the rule definition.

Corrective Action: Correct the entry by deleting the KEEP event, or use a different ON statement.

CTT543E VALID FASTPOS OPTIONS ARE YES, NO, OVERRIDE, OR TEST

Explanation: An invalid fast positioning option was specified in a DO FASTPOS rule statement. The DO FASTPOS statement specifies the mode of operation for fast positioning.

Valid fast positioning options are:

Y - Yes
N - No
O - Override
T - Test

Control-M/Tape does not save the rule definition.

Corrective Action: Correct the entry by specifying a valid fast positioning option.

CTT544E REDUNDANT RETENTION AFTER AN EMPTY AND/OR OPTION

Explanation: A value was specified in a RETENTION field but the AND/OR relationship to the value in a previous RETENTION field was left blank.

If values are specified in more than one RETENTION field, a value must be inserted into the AND/OR field relating to each of the RETENTION fields, except the last, to avoid inconsistency.

The definition is rejected.

Corrective Action: Correct the definition, either by deleting the current RETENTION value, or by inserting an AND/OR relationship between the current RETENTION and the previous RETENTION.

CTT545E STACK=Y ALONG WITH NONSPECIFIC VAULT RETENTION IS INVALID

Explanation: A Control-M/Tape rule definition is invalid. The definition included both of the following:

the statement DO STACK=Y
a DO VAULT statement with UNTIL set to "MVS CATALOG" or "CYCLES" or "LAST ACCESS"

Dynamic stacking cannot be performed for data sets with an unpredictable return date from the vault. All stacked data sets on the volume must have the same return date from the vault.

The rule definition cannot be saved.

Corrective Action: Do one of the following:

Remove the statement DO STACK=Y.
Change the DO VAULT return criteria.

CTT548E SEVERE ERROR IN CALENDAR OR YEAR NOT FOUND IN CALENDAR

Explanation: Either the year is not defined in the calendar, or the calendar was incorrectly modified.

The rule is not ordered.

Corrective Action: Check the contents of the rule order and the calendar. Correct accordingly, and reorder the rule.

CTT551E VALID CAPACITY TYPES ARE "S" (SLOT) OR "B" (BOX)

Explanation: An invalid capacity type was specified. Valid capacity types are slots and boxes.

Corrective Action: Specify a valid capacity type.

CTT552E PLEASE FILL IN TABLE NAME OR OMIT VAULT NAME

Explanation: A vault name was specified without a table name. A vault name cannot be specified without a table name.

Corrective Action: Either specify the table name or omit the vault name.

CTT553E THIS FIELD MUST BE NUMERIC AND GREATER THAN ZERO

Explanation: The field contains the value 0. It must hold a numeric value greater than 0.

Corrective Action: Correct the value in the field.

CTT554E A VALID CALCULATED BOX ID IS 2 - 6 CHARS LONG

Explanation: The combination of the box ID and Capacity parameters creates a calculated box ID that exceeds six characters.

Corrective Action: Change either the box ID or Capacity parameters, or both, so that their combination does not exceed six characters.

CTT555S INSUFFICIENT STORAGE. INCREASE THE REGION SIZE

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

CTT556I CHANGE OF VAULT MAY CAUSE CHANGES IN CAPACITY TYPE BOX

Explanation: The vault name has been changed by the user from MAINLIB to a different name, and therefore all box definitions are automatically changed to box capacity definitions. Be aware that box definitions are allowed only under the definition of vault name MAINLIB.

Corrective Action: No action is required.

CTT557E DUPLICATE DEFINITION

Explanation: The same media capacity is already defined under the same vault, or the same box ID with the same media is already defined under the vault name MAINLIB.

Corrective Action: Do one of the following:

Use a different media name.
Use a different box ID.
Delete the line.

CTT567E USER NOT AUTHORIZED

Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.

Corrective Action: Check with your system security administrator.

CTT567I COND `cond` ODATE `odate` {ADDED | DELETED | FOUND} BY USER `userId` / `jobName` (`jobId`)

Explanation: This information message indicates that the ADD, DELETE, or CHECK option completed successfully and the cond condition with the odate original scheduling date was added to or deleted from, or found in the IOA Conditions file.

In this message, odate is the date on which the message is issued. If the ADD, DELETE, or CHECK option is run by the IOACND utility in batch mode, the user ID (userId), job name (jobName), and job ID (jobId) of the batch file are also displayed.

Corrective Action: No action is required.

CTT570E VOLUME RANGE MUST BE DEFINED

Explanation: No volume range is defined.

Corrective Action: Specify the volume range.

CTT571E VOLUME RANGE IS INVALID

Explanation: Volume range is invalid. The first value in a valid volume range must be less than or equal to the second.

Corrective Action: Specify a valid range.

CTT572E PLEASE FILL IN TABLE NAME OR OMIT POOL NAME

Explanation: A pool name was specified without a table name. A pool name must have a table name.

Corrective Action: Either specify the table name or omit the pool name.

CTT585W A DSN=** STATEMENT IGNORED. RULE MUST BE DEFINED MANUALLY

Explanation: During the conversion of EPIC vaulting rules into Control-M/Tape rules, an EDM rule was found. EDM rules cannot be converted automatically. They must be defined manually.

The rule is not converted.

Corrective Action: Define the EDM rule manually by means of screen TR.

Messages CTT600 through CTT6xx

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

CTT601E SPECIFY DSNAME OR REMOVE CREATION DATE

Explanation: A creation date is specified on the Inquire/Update Entry Panel without a data set name. A creation date may be specified only when a data set is defined.

Corrective Action: Specify a data set name or mask on the Inquire/Update Entry Panel or remove the creation date.

CTT602E INVALID RECORD TYPE. USE "V","D","VD" OR "DV"

Explanation: The specified record type on the Inquire/Update Entry Panel is invalid.

Valid record types on the Inquire/Update Entry Panel are:

V -- Volume
D -- Data set record
VD -- Volume followed by Data set
DV -- Data set followed by Volume

Corrective Action: Specify a valid record type value.

CTT604E OPTION VALID FOR VOLUMES ONLY

Explanation: An option was requested for a data set that is valid only for volumes.

Corrective Action: Refer to the Control-M/Tape User Guide for a list of valid line options for volumes.

CTT605E OPTION INVALID FOR THE CURRENT STATUS OF `dsn /vol`

Explanation: An option that is not valid for the current status of the data set or volume is specified. For more information about status field values, see the description of the Inquire/Update facility in the Control-M/Tape User Guide.

Corrective Action: Specify an option that is valid for the current status of the data set or volume.

CTT606E RECORD IN USE BY ANOTHER USER

Explanation: Option specified for a data set or volume is in use by another user or job.

Corrective Action: Try the option again later.

CTT607E NO INFORMATION FOUND IN MEDIA DATABASE

Explanation: The requested information was not found in the Media database.

Corrective Action: No action is required.

CTT608E YOU ARE NOT AUTHORIZED TO USE THIS OPTION

Explanation: An option was requested for which there is no authorization. The INCONTROL administrator can authorize or deny use of certain options for certain users.

Corrective Action: To get authorization to use the option specified, contact your INCONTROL administrator.

CTT609E EXTEND INVALID FOR THE EXPIRATION TYPE OF `vol /dsName`

Explanation: The Extend option is requested for a volume or data set entry that cannot be extended. Extend is valid only for an entry with expiration type D (actual Date). Expiration types that are not specific, like MVS CATALOG, cannot be extended.

The Extend option fails.

Corrective Action: Use the Extend option only for a volume or data set entry with expiration type D.

CTT610I VOLUME `vol` WAS SENT TO `loc`

Explanation: This information message indicates that the requested CHECKOUT, VAULT, or RECALL operation, to transfer a volume to a different location, was executed successfully.

Corrective Action: No action is required.

CTT611I VOLUME `vol` WAS RETURNED FROM `loc`

Explanation: This information message indicates that line option BACK-IN-LIB was executed successfully. When option BACK-IN-LIB is specified for a volume, the volume location is immediately set to MAINLIB.

Corrective Action: No action is required.

CTT612I VOLUME `vol` WAS `operation`

Explanation: This information message indicates that the requested line option (CLEAN, DELETE, UPDATE, or EXPIRE) was successfully executed on the volume.

Corrective Action: No action is required.

CTT613I DATASET `dsn` WAS `operation`

Explanation: This information message indicates that the requested line option (UPDATE, EXPIRE, or EXTEND) was successfully executed on the data set.

Corrective Action: No action is required.

CTT615E {GROUP | SUBLINES} NOT ALLOWED ON THIS LEVEL

Explanation: Either line option G (GROUP) or S (SUBLINES) to open a third level of sublines is specified for the current line. Only two levels of sublines are allowed for each line in screen TI.

Corrective Action: Do not specify option G or S for the current line.

CTT616E THERE ARE NO SUBLINES FOR THIS ENTRY

Explanation: Either line option G (GROUP) or S (SUBLINES) is specified to open sublines for a line on screen TI, but the line does not contain sublines.

Corrective Action: Do not specify option G or S for the current line.

CTT617E RECORD CHANGED. TRY AGAIN

Explanation: A line option was requested for a record whose displayed data was no longer current. An option was requested for a line on screen TI, but between the time the screen was displayed and the time the request was made, the corresponding record on the Media Database changed. The request may have been based on outdated data.

The requested line option is not executed.

Corrective Action: Press the Enter key to refresh the screen with current data, and repeat the request again if desired.

CTT618E OPTION NOT SUPPORTED FOR MULTI-VOLUME GROUP

Explanation: Line option E (EXPIRE) was requested for a volume that is a part of a multivolume group. The EXPIRE option is supported for a single volume only.

Corrective Action: Do not specify option E for the current line.

CTT619E OPTION SUPPORTED FOR DATASETS ONLY

Explanation: Line option X (EXTEND) was requested for a volume. The EXTEND option is supported for a data set only.

Corrective Action: Do not specify option X for the current line.

CTT620E UNABLE TO UNCATALOG DATASETS

Explanation: In response to a request for option E (immediate expiration) for a volume, all data sets on the volume were deleted, but the Online Facility cannot uncatalog the data sets from the MVS Catalog. The probable cause of the problem is that the MVS Catalog is not available.

Corrective Action: Call your system programmer for assistance.

CTT621E SILO REQUEST FAILED

Explanation: In response to a request for option E (immediate expiration) for a volume, the volume was scratched in the Media Database and the corresponding SCRATCH request was sent to a Silo Interface. However, the Silo request failed. Error message CTT334E, containing return and reason codes, in the MVS SYSLOG accompanies this message.

Corrective Action: Check the MVS SYSLOG for the return and reason codes in message CTT334E. Proceed accordingly.

CTT623E SLOT `slot` WAS NOT RELEASED. RC=`rc`, VAULT=`vault`, MEDIA=`media`

Explanation: A volume expiration request was issued for a vaulted volume. Control-M/Tape cannot release the slot that was assigned to the volume.

Possible values for rc (causes for the failure) are:

04 -- Slot Definition Records not in Media Database (MDB) for specified vault.
08 -- Internal program error.
12 -- Not enough memory.
16 -- I/O error.
20 -- The specified media was not defined for the specified vault.
32 -- The CTTVTM utility is currently running, and updating the Slot Definition Records.

The currently executing function continues. The requested volume becomes scratch in the MDB.

Corrective Action: For a return code of 12 or 16, do one of the following:

If rc is 12, increase the region size for the executing job’s online procedure.
If rc is 16, notify your INCONTROL administrator.

In all other cases, check the vault definition using the Vault Definition screen (screen TV), and then run the CTTVTM utility in mode SLOTBLD to synchronize the Slot Definition records with the Volume records.

CTT624E BOX CANNOT BE VAULTED MANUALLY

Explanation: Option VAULT was requested in the Inquiry/Update Media DB screen (screen TI) for a volume that is located in a box. This is not permitted since the volume was not previously recalled from a vault. Option VAULT is valid for a volume from a box only if the box was previously recalled from a vault to the MAINLIB.

Corrective Action: No action is required.

CTT625E INVALID DATASET GENERATION QUERY

Explanation: An invalid format was used for data set generation in the DSNAME field in Screen TI, the Control-M/Tape Inquire/Update entry panel. To request data set generation, specify zero or a negative number in parentheses appended to the data set name in the DSNAME field, for example, data set (-1).

No data is displayed until data set generation is specified correctly.

Corrective Action: Correctly specify the data set generation value. For more information, see the DSNAME field in the section that describes entry panel fields in the chapter on online facilities of the Control-M/Tape User Guide.

CTT626E INVALID SORT COMMAND SYNTAX. USE ‘SORT FIELD-NAME A/D’

Explanation: The syntax for the SORT command on the TI screen, the Control-M/Tape Inquire/Update screen, is invalid.

The valid syntax for the SORT command is SORT field [{A|D}] where:

A means sort in ascending order
D means sort in descending order

For more information about this command, see the section that describes the commands of the Inquire/Update screen in the chapter on online facilities of the Control-M/Tape User Guide.

The SORT command is ignored.

Corrective Action: Specify the command with valid syntax.

CTT627E SORT FIELD UNKNOWN, OR INVALID WITH {VOLUME | DATASET} RECORDS

Explanation: The SORT command contains an invalid sort field. Either the specified sort field is unknown or it is not in the current display. This command is used in the Inquire/Update screen (Screen TI).

If data set records are currently displayed, only data set fields can be used to sort displayed records. If volume records are currently displayed, only volume fields can be used to sort displayed records.

The SORT command is ignored.

Corrective Action: Specify a valid sort field. Valid field names are listed under the heading External names in tables in the appendix that describes logical field names for the Control-M/Tape repository in the INCONTROL for z/OS Administrator Guide, or the column headers on the TI screen.

CTT630E LOCATION NOT FOUND IN THE VAULT PATTERN

Explanation: During update of a vaulted volume record using the Volume Update screen, the value specified in the LOCATION field did not match any of the VAULT NAME fields.

Corrective Action: Synchronize LOCATION and VAULT NAME fields.

CTT631E DATE CANNOT BE LESS THAN PREVIOUS VAULT ENTRY DATE

Explanation: During an attempt to update a vaulted volume record using the Volume Update screen, one of the Entry Date fields was specified for a date earlier than the previous entry date.

Corrective Action: Correct the erroneous Entry Date field.

CTT632E INVALID TYPE `retention`. VALID RETENTION TYPES ARE CA,CY,DAT,EX,L,P,VA,VO,M

Explanation: An invalid UNTIL type specifies the retention period in a DO VAULT statement. The UNTIL type specifies the retention period for which a volser is kept in a vault, and how the period is calculated. A single UNTIL type, or a combination of up to three types, can be specified using the AND/OR field.

See the UNTIL subparameter of DO VAULT in the chapter on rule parameters of the Control-M/Tape User Guide for a description of valid UNTIL types.

Corrective Action: Correct the entry by specifying a valid retention type.

CTT633E INVALID TYPE `retention`. VALID RETENTION TYPES ARE CA,CY,DAT,ED,L,P,R,S,M

Explanation: An invalid RETENTION type was specified in a DO RETENTION statement. The DO RETENTION statement specifies a duration for which a data set is kept. The retention type specified identifies how the duration is calculated. A single retention type, or a combination of up to three different retention types may be specified using the AND/OR field.

For a description of valid RETENTION types, see the RETENTION subparameter of DO VAULT in the rule parameters chapter in the Control-M/Tape User Guide.

Corrective Action: Correct the entry by specifying a valid retention type.

CTT634W VAULT PATTERN HAS MORE THAN THREE ENTRIES

Explanation: The user was attempting to update a vaulted volume record using the Volume Update screen, but the volume record contains more than three vault entries in the vault pattern. It is impossible to update such a vault pattern.

All vaulting related fields, such as LOCATION and MOVE DATE, are displayed but cannot be edited.

Corrective Action: No action is required.

CTT635E INVALID DATE `date`

Explanation: An invalid date was specified in the Volume/Dataset Update screen. The date format is set according to installation parameters and may be either ddmmyy, mmddyy, or yymmdd. Other date fields may be four digits (omit the yy year values) or eight digits (include a four digit year: ddmmyyyy, mmddyyyy or yyyymmdd).

Corrective Action: Specify a valid date.

CTT636E INVALID VALUE `value`. FIELD SHOULD BE NUMERIC

Explanation: A nonnumeric value was specified in a numeric field.

Corrective Action: Fill in a numeric value.

CTT637E INVALID VALUE `value`

Explanation: An invalid value was specified in a field in the Volume/Dataset Update screen.

Corrective Action: Correct the invalid value according to the field contents.

CTT638E `fld` VALUE EXCEEDED MAXIMUM

Explanation: The specified field value exceeded the maximum value.

Valid values for fld are:

fld	Explanation
ACTIVE-DS#	Active data set number. The maximum value is 65535.
LAST-LABEL	Last label on volume. The maximum value is 65535.
V-DATASET	Vaulting data set number. The maximum value is 65535.
RET-DATASET	Retention data set number. The maximum value is 65535.

Corrective Action: Specify a valid value below the maximum.

CTT639E INVALID VALUE `value.` VALID UNITS ARE KB,MB,GB,TB

Explanation: An invalid value was specified in the capacity type units fields in the Volume/Dataset Update screen. KB, MB, GB, and TB stand for kilobytes, megabytes, gigabytes, and terabytes.

Corrective Action: Correct the invalid value according to the field contents.

CTT63AE MAXIMUM VALUE IS 2047 TB

Explanation: A value greater than the maximum was specified in the capacity value fields in the Volume/Dataset Update screen.

Corrective Action: Correct the invalid value.

CTT645I `utility` IS RUNNING IN RESTART MODE

Explanation: This information message indicates that the previous run of the specified utility abended and the utility is now running in RESTART mode. The utility is RTM (for CTTRTM), VTM (for CTTVTM), or MER (for CTTMER).

Corrective Action: The corrective action depends on the utility:

MER: Run in RSIMULATE mode.
RTM or VTM: No action is required.

CTT646I INVALID `fileName`. RESTART CANCELED

Explanation: The specified file is invalid. RESTART mode cannot continue. Restart is based on information in the specified file. Because the file is invalid, the utility cannot run in RESTART mode.

RESTART mode is canceled. The utility continues in NORMAL mode.

Corrective Action: No action is required.

CTT647I RESTART OF {`rtm`|`vtm`} ENDED SUCCESSFULLY

Explanation: This information message indicates that the CTTRTM utility (or the CTTVTM utility) finished processing successfully in Automatic Restart mode.

Corrective Action: No action is required.

CTT648E BOX `boxId` IS IN ERROR

Explanation: An error occurred when the CTTVTM utility was handling a Box Definition record while running in Automatic Restart Mode.

This message follows one of the following messages, which detail the error that occurred: CTT200E, CTT209E, CTT459E, or CTM555S.

Control-M/Tape stops handling the Volume records of the problematic Box Definition record. The utility continues processing.

Corrective Action: Correct errors that are detailed in the preceding messages.

Messages CTT700 through CTT7xx

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

CTT700I `text`

Explanation: This information message displays one of the following:

a control statement read from SYSIN
a parameter specified in a JCL EXEC statement
information to accompany another message

Corrective Action: No action is required.

CTT701S INCLUDE/EXCLUDE STATEMENT ERROR. FUNCTION=`func`, RC=`rc`. EXECUTION WILL TERMINATE

Explanation: A syntax error occurred in an INCLUDE/EXCLUDE statement.

The variables in this message are:

func - the name of the function in which the error occurred
rc - the return code that indicates the type of error for that function

Valid values for func and rc, and their explanations, are displayed in the following table:

Function	Return Code	Explanation
INIT	08	Insufficient memory
	36	Internal error
BUILD	08	The number of INCLUDE/EXCLUDE statements exceeds the limit of 1000 statements.
	12	The statement is not of the INCLUDE/EXCLUDE type.
	16	One of the following problems occurred: The parameter specified exceeds 44 characters. No parameter was specified. The keyword in invalid. It is not in the dictionary. The parameter specified is not allowed (not in the dictionary).
	20	The > (greater than) or < (less than) relation is not allowed in the specified format.
	24	The date value is not numeric.
	28	The date value is neither 6 nor 8 digits.
	32	Internal error
	36	The value is neither numeric nor hexadecimal.
SELECT	8	An INCLUDE/EXCLUDE block is empty.
	32	Internal error
	40	The field being used for comparison contains an invalid numeric value.

Execution stops.

Corrective Action: Correct the statement and rerun the utility.

CTT702S STATEMENT PARSING ERROR. REASON=`rsn`. EXECUTION WILL TERMINATE

Explanation: A parsing error occurred in one or more control statements. The reason code (rsn) in the message text indicates the type of error that occurred, as shown in the following table:

Utility	rsn	Explanation
All Utilities	4	No keywords were found
	8	Continuation statement is missing
	12	Operation code not found. No keywords parsed.
	16	No keywords found in the parsed record, or a mandatory keyword was not found.
	20	Redundant data in a parsed record.
	24	Internal error. Missing parameter name in command definition.
	28	More than 255 characters to parse.
	48	More than 31 input parameter lines.
CTTDLD	32	Range is invalid. FROM volser is higher than TO volser or volser range does not provide logical sequencing.
	52	Continuation statement missing.
CTTIDB	28	Invalid MODE parameter or more than 255 characters to parse.
	32	Invalid relation in statement.
CTTMER	50	OPCODE not found.
	54	Relation in statement is missing or invalid.
	58	Parameter is too long.
	62	DBGLEVEL is not numeric.
	70	Too many MERGE statements.
	74	MERGE statement is missing.
	78	Invalid MODE parameter.
CTTSPL	50	OPCODE not found.
	54	Relation in statement is missing or invalid.
	58	Parameter is too long.
	62	DBGLEVEL is not numeric.
	70	Too many SPLIT statements.
	74	SPLIT statement is missing.
	78	Invalid MODE parameter.
	82	Invalid FUNCTION parameter.

Execution is terminated.

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

CTT703I `recd_type` RECORDS `action = num`

Explanation: This message is generated to provide additional information from a Control-M/Tape utility.

Message variables are:

rec_type -- The type of records that have been processed.
action -- The action that was performed on the records, for example, read, written, updated, or dropped.
num -- The number of records processed.

Corrective Action: No action is required.

CTT704I CONTROL-M/TAPE UTILITY `utility` STARTED

Explanation: This information message indicates that a Control-M/Tape utility has started execution.

Corrective Action: No action is required.

CTT705I CONTROL-M/TAPE UTILITY `utility` ENDED RC=`rc`

Explanation: This information message indicates that a Control-M/Tape utility has ended with return code rc.

Corrective Action: No action is required.

CTT707S PARAMETERS `parm1` AND `parm2` ARE MUTUALLY EXCLUSIVE

Explanation: The specified parameters passed to the utility are mutually exclusive and therefore cannot be specified together.

The utility does not start processing.

Corrective Action: Specify either one of the parameters, but not both.

CTT708S UNRECOGNIZED POSITIONAL PARAMETER `parm`

Explanation: The specified positional parameter passed to the utility is unrecognized.

The utility does not start processing.

Corrective Action: Refer to the utility description in the INCONTROL for z/OS Utilities Guide for information regarding parameters which can be passed to the utility.

CTT709S POSITIONAL PARAMETER `parm` APPEARED MORE THAN ONCE

Explanation: The positional parameter was specified more than once as input to the utility.

The utility does not start processing.

Corrective Action: Specify this parameter only once. Refer to the utility description in the INCONTROL for z/OS Utilities Guide for more information regarding parameters that can be passed to the utility.

CTT710S STATEMENT VALIDATION ERROR IN KEYWORD `keyName`, EXECUTION WILL TERMINATE

Explanation: Validation error in scanning parameters of the specified keyword.

Execution is terminated.

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

CTT711I `num` RECORDS COPIED

Explanation: This information message indicates that the CTTACP utility copied the specified number of records.

Corrective Action: No action is required.

CTT712I `num` STATEMENTS READ FROM SYSIN

Explanation: This information message specifies how many control statements SYSIN has read.

Corrective Action: No action is required.

CTT713I `format` TYPE RECORDS - PROCESSED = `n1`, SELECTED = `n2`

Explanation: This information message indicates that the Stacking Database was built as shown.

The variables in this message are:

format - the track recording format
n1 - the number of records read from input
n2 - the number of records selected due to INCLUDE/EXCLUDE statements

Corrective Action: No action is required.

CTT714I TOTAL OF `n1` RECORDS READ `n2` DUPLICATE RECORDS WERE DROPPED

Explanation: This information message indicates that the Stacking Database was built as shown.

The variables in this message are:

n1 - the total number of records read from input
n2 - the total number of records ignored because they appeared in a previous execution of the utility

Corrective Action: No action is required.

CTT715S ROUTINE `routineName` FAILED. RC=`rc`

Explanation: A severe internal error occurred in the specified routine.

The variables in this message are:

routine - the routine in which the error occurred
rc - the return code of the routine

Execution is terminated.

Corrective Action: Check accompanying messages.

CTT716S {RETENTION | VAULTING} PROCEDURE ENDED WITH ERRORS

Explanation: Due to logical errors on the Media Database (MDB), a retention or a vaulting procedure ended with errors. This message follows other messages that indicate the exact nature of the problem.

The procedure terminates with errors.

Corrective Action: Check the accompanying error messages, and proceed accordingly.

CTT717E INVALID EXPIRATION DATA. RECORD KEY=`key`

Explanation: The data set or volume record contains invalid expiration information.

The CTTRTM (CTTVTM) utility skips the bad record and continues executing.

Corrective Action: Contact your database administrator.

CTT718I ANOTHER CTT UTILITY IS USING THE MDB. TRY AGAIN LATER

Explanation: This information message indicates that the requested utility requires, but cannot access, the Media Database, which is in use by another utility. Simultaneous access to the Media Database by these utilities might corrupt the data. Therefore, only one of the utilities at a time can access the database.

Corrective Action: Run the requested Control-M/Tape utility after the previous utility has ended.

CTT719E {POOL | RULE | VAULT} DEFINITION LOAD FAILED

Explanation: Control-M/Tape cannot load the Pool, Rule, or Vault definition into memory, for one of the following reasons:

The member is not in the Control-M/Tape PARM or RULE library.
There was an invalid allocation of the Control-M/Tape PARM or RULE library.
There is some other definition problem.

Execution stops.

Corrective Action: Examine the job log and the IOA log for messages relating to this error, and take appropriate corrective action.

CTT720E VAULT `vault` NOT FOUND. VOLUME=`vol`

Explanation: Control-M/Tape did not find the vault name vault in the vault definition.

Control-M/Tape moves the volume to the vault, and continues processing.

Corrective Action: Add the vault to the vault definition using the Vault Definition screen.

CTT721E INVALID LOCATION `loc` FOR VOLUME `vol`

Explanation: Volume was marked as vaulted, but the current vault name (location) is not in the volume vault list.

The CTTVTM utility skips the volume, and continues executing.

Corrective Action: Contact your INCONTROL administrator.

CTT722E INTERNAL ERROR IN DATA. RECORD=`key`

Explanation: Control-M/Tape detected one of the following errors in the indicated record:

The creation date on a data set record is either invalid or not specified (DDSCDT).
An invalid last access operation on a data set record (DDSLACS).
The last read or write date is not defined (DDSRDT or DDSWDT).
The last data set label number is not specified on a volume record (DVLLBLNM).
No data set found for an active volume.

This message is issued by the Online Facility, by the CTTRTM utility, or by the CTTVTM utility.

Execution continues with another record from the Media Database.

Corrective Action: Notify your database administrator.

CTT723E CHAIN ERROR ON VOLUME `vol`

Explanation: A Control-M/Tape utility detected a multivolume chain error. Possible causes are:

A volume record was found that has a first, next or previous VOLSER specification, but the related VOLSER was not found in the Media Database.
A multivolume chain with no data sets was found. The specified volume is a member of this multivolume chain.

This message is accompanied by other messages that provide additional information about the problematic record.

Corrective Action: No action is required.

CTT724I VOLSER=`volser` ; RBA=`rba` ; {FIRST | NEXT | PREV} = `volser` ; {LABEL = `lbl`| DSN = `dsn` }

Explanation: This information message provides information about a volser that caused an error. It accompanies error messages issued by other utilities.

Corrective Action: No action is required.

CTT725W CHAIN INCOMPLETE BECAUSE OF INCLUDE/EXCLUDE SELECTION OR CHAIN ERROR

Explanation: The CTTVTM utility detected an incomplete multivolume chain. Possible causes are:

The INCLUDE/EXCLUDE specification does not contain all the volsers of the chain.
A volume record was found that has a first, next or previous VOLSER specification, but the related VOLSER was not found in the Media Database.

This message is accompanied by message CTT724I, which provides additional information (VOLSER and RBA) about the problematic/missing record.

Corrective Action: No action is required.

CTT726E VOLUME `vol` NOT IN SEQUENCE (`seqNumber`)

Explanation: A Control-M/Tape utility detected that the seq_no sequence number in the vol volume is out of sequence in the volume chain. This problem generally relates to the conversion process.

Corrective Action: No action is required.

CTT727E CTTRPT FAILED. RC=`rc`, STATEMENT={FIELDS | SORTBY | BREAK}, PARM=`parmName`, ROW=`row_id`

Explanation: The CTTRPT utility, invoked directly or called internally by another utility, failed due to an invalid value in the parmName parameter.

In this message, row_id is the ROWID specified in a BREAK or SORTBY statement. The type of error is indicated by the return code (rc), as follows:

rc	Explanation
08	Missing DD statements or open error occurred.
12	Control card error.
16	Operation code not found.
20	Invalid operation code.
24	Syntax error in REPORT, FIELDS or SORTBY statement.
28	Field name specified in FIELDS or SORTBY list is undefined.
32	Same parameter specified more than once.
36	Field name exceeds maximum length.
40	Invalid relation specified (must always be an equal sign).
44	Report NAME is undefined.
48	BRK not specified for the preceding field in the SORTBY list.
52	FIELDS statement not specified.
56	Total of all field lengths requested in the FIELDS statement exceeds the line size.
60	Continuation card expected but not received.
64	Invalid numeric value.
68	Option in the FIELDS or SORTBY statement already specified.
72	ROWID specified in the BREAK or SORTBY statement.
76	EDIT parameter in the ATTR statement is invalid for the specified FIELDS.
80	EDIT mask is not valid.
84	Specified number not in permitted range. For example, the end column of a MARGIN statement exceeds the LINESIZE, or a column in a FIELDS statement is outside the margins of the report.
88	Column option (/C) not specified in the preceding field.
92	One of the following has occurred: No column is specified in the current FIELDS statement. The specified column in a FIELDS statement is inconsistent with the column specified in another FIELDS statement
108	Insufficient memory.
112	All fields specified for the primary and secondary line have the BRK attribute
200	Fields in the FIELDS or SORTBY statements do not fit the PATH parameter of the EXTRACT statement.

The utility is stopped.

Corrective Action: Depending on the return code, check and correct the appropriate parameters or DD statements.

CTT728I CONTROL-M/TAPE UTILITY `util` IS RUNNING. MDB UPDATES DELAYED

Explanation: This information message is issued upon the start of an IDB utility, which checks and analyzes Media Database integrity.

The message is highlighted and unrollable until the utility has finished accessing the Media Database.

Corrective Action: No action is required.

CTT729E CONTINUATION RECORD NOT FOUND FOR VOLUME `volser`

Explanation: Control-M/Tape tried to expire a volume that has continuation records (DTR records) that are not in the Media Database. This message is issued by either the Online Facility or by the CTTRTM utility.

Corrective Action: Notify your database administrator.

CTT730E MAXIMUM CAPACITY EXCEEDED FOR MEDIA `type`

Explanation: The value specified in the CAPACITY USD field exceeded the maximum capacity value defined in CTTPARM for the type media type. An attempt was made to update the CAPACITY USD field on a volume record through screen TI.

Corrective Action: Decrease the value in the CAPACITY USD field.

CTT731E LAST LABEL NUMBER CANNOT BE BELOW NUMBER OF ACTIVE DATASETS

Explanation: The value in the LAST LABEL field is invalid.

This message is issued in one of the following circumstances:

Using Screen TI, an attempt was made to update either the ACTIVE DS# field or the LAST LABEL field on a volume record in a manner that would result in the LAST LABEL field value being less than the ACTIVE DS# field value.
There is an active data set with a label number that is higher than the value in the LAST LABEL field.

In the Control-M/Tape database:

the ACTIVE DS# field is called ACTIVEDS
the LAST LABEL field is called LBLNUM

Corrective Action: Adjust the value in the LAST LABEL field to a number equal to the highest label number of all the active data sets on the volume.

CTT732E VOLUME `vol` IS ACTIVE AND HAS NO DATASETS

Explanation: A utility detected a volume data record which is marked as active, but the volume has no associated data set.

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT733E NUMBER OF ACTIVE DATASETS CANNOT BE BELOW NUMBER OF EXISTING DATASETS

Explanation: The value in the FILES field cannot be less than the actual number of data sets which reside on the selected volume. An attempt was made to update the FILES field on a volume record through Screen TI.

Corrective Action: Increase the value in the FILES field so that it is not less than the actual number of data sets on the volume.

CTT734E DATASET `num` DOES NOT EXIST ON THE VOLUME

Explanation: The user tried to update the DATASET NUM field within Vaulting Information on a volume record, but a data set with label number num was not found on the selected volume.

Corrective Action: Correct the value in the DATASET NUM field.

CTT735E MAXIMUM PREFIX NAME LENGTH EXCEEDED

Explanation: An attempt was made to update the DSNAME PREF LTH field in Vaulting Information on a volume record with a value greater than 44. The maximum value for the DSNAME PREF LTH field is 44.

Corrective Action: Decrease the value in the DSNAME PREF LTH field to a value not greater than 44.

CTT736E DUPLICATE {VOLUME | DATASET}: `rkey`

Explanation: The CTTIDB utility detected two or more data records with the same key (rkey).

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT737E MAXIMUM NUMBER OF MEDIA BLOCKS EXCEEDED. VAULT `vault`

Explanation: The CTTVTM utility detected more than 10 different media types defined for the specified vault. No more than 10 media types can be defined for a vault.

Only the first 10 media types are considered by the CTTVTM utility. The utility continues processing.

Corrective Action: Decrease the number of media types in the vault definition through screen TV.

CTT738E VAULT `vault` NOT DEFINED

Explanation: The Media Database contains information about slot assignment in the specified vault, but that vault is not defined through screen TV.

The CTTVTM utility continues processing.

Corrective Action: If the vault should be defined, define it through screen TV. Otherwise, ignore the message.

CTT739E MEDIA `mediaName` NOT DEFINED FOR VAULT `vault`

Explanation: The mediaName media type is not defined for the vault through screen TV.

The CTTVTM utility continues processing.

Corrective Action: Define the media type for the vault from screen TV.

CTT740W VOLUME `vol` SKIPPED. RANGE INVALID

Explanation: The CTTDLD utility, with TYPERUN set to CONVERT, detected a volume with VOLSER set to vol that was not defined in a RANGE statement.

The specified volume is not converted.

Corrective Action: Correct the definition of the RANGE statement.

CTT742W DUPLICATE DATASETS ON SAME VOLUME - VOL=SER=`volser` LABEL=`lbl`. DATASET NOT ADDED

Explanation: The CTTDLD utility, with TYPERUN set to CONVERT, detected a volume (volser) with multiple data sets residing on the same label.

Only one data set is added to the Media Database (MDB).

Corrective Action: List the data sets of the volume and define the data sets on it manually.

CTT743W VOLUME `vol` IS NOT A SCRATCH VOLUME. VOLUME NOT DELETED

Explanation: The CTTDLD utility, with TYPERUN set to DELETE, detected a non-scratch volume to be deleted from the Media Database (MDB).

The volume is not deleted.

Corrective Action: Check the status of the volume and verify why it is not scratch.

CTT744S RETENTION TYPE NOT RECOGNIZED. TYPE=`type` RMFKEY=`key`

Explanation: During conversion from CA-TLMS RMF (Retention Master File), an invalid retention type was detected in the input.

The volumes that will contain the data set indicated in the RMFKEY are assigned a permanent retention type.

Corrective Action: Check and correct the data set retention type in the Control-M/Tape rule definition.

CTT745S CONDITIONS IN VAULT PATTERN CONTROL STATEMENT EXCEEDED. DSN=`dsName`

Explanation: The conversion program encountered too many vault control statements in the definition file being converted.

The extra conditions are ignored.

Corrective Action: Check your CA-1 vault management definition for valid conditions.

CTT746W control NOT SUPPORTED. DSN=`dsName`

Explanation: The control value specified for the data set name is not relevant for Control-M/Tape.

The control statement is ignored. Conversion continues.

Corrective Action: No action is required.

CTT747S INSTALLATION NOT IN UCC-1

Explanation: The conversion routine that converts CA-1 VMS or VPDS to Control-M/Tape rules discovered that the input parameters were set for a non UCC-1 installation. The CTTCVMS program checks the EXPDTYPE parameter in the CTTPARM, and issues this message if the parameter is not set to CA1.

Rule conversion is stopped.

Corrective Action: Change the EXPDTYPE in the CTTPARM to CA1, if you are converting from CA-1 to Control-M/Tape.

CTT748W EXPIRATION DATE: `date` NOT SUPPORTED. VOL=`vol`

Explanation: The CTTDLD utility, with TYPERUN set to CONVERT, detected an unrecognizable expiration date.

The specified volume with this expiration date is assigned a permanent expiration date.

Corrective Action: Check volume retention type and date. Redefine it in the Control-M/Tape Inquire/Update Entry Panel if permanent status is incorrect.

CTT749E INVALID COMBINATION OF FIRST,LAST AND RENAME FIELDS

Explanation: An invalid combination of FIRST, LAST and RENAME values was used in a RANGE statement. The length of the string specified for RENAME must not exceed the length of the corresponding part of the FIRST and LAST prefixes. The FIRST and LAST prefixes must be identical.

The CTTDLD utility is terminated.

Corrective Action: Correct the RANGE statement and rerun the CTTDLD utility.

Messages CTT800 through CTT8xx

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

CTT801I CONTROL-M/TAPE `rel` REAL-TIME ENVIRONMENT IS ACTIVE

Explanation: This information message indicates that the real-time environment was successfully established.

In this message, rel is the specific release of Control-M/Tape.

Corrective Action: No action is required.

CTT802E CONTROL-M/TAPE INITIALIZATION FAILED. RC `rc` IN PHASE `phase_num`

Explanation: The initialization of Control-M/Tape activated by the CTTINIT procedure failed due to an error. This message is preceded by a message that identifies the error that caused the initialization failure.

Initialization terminates and the already-created environment is removed from the system.

Corrective Action: Notify your INCONTROL administrator.

CTT803E STARTSTK IS NOT ALLOWED. CONTROL-M/TAPE WAS INITIALIZED WITH DYNSTK=N

Explanation: Dynamic stacking cannot be activated if Control-M/Tape was initialized without dynamic stacking, meaning that the DYNSTK parameter was set to N in CTTPARM.

STARTSTK is not performed. Control-M/Tape continues to work in NOSTACK mode.

Corrective Action: If you want to utilize dynamic stacking, do the following:

Change the value of the DYNSTK parameter in CTTPARM to Y.
Stop and restart the Control-M/Tape real time environment.

If you later want to stop dynamic stacking temporarily, use the CTTINIT setting MODE=STOPSTK. To stop it for a longer period, set DYNSTK to N.

CTT804I Control-M/TAPE `rel` REAL-TIME ENVIRONMENT DELETED

Explanation: This information message indicates that the real-time environment was successfully removed from the system. The CTTINIT procedure was activated with MODE set to TERM to delete the previously established environment.

In this message, rel is the specific release of Control-M/Tape.

The system operates now without Control-M/Tape.

Corrective Action: No action is required.

CTT805E `func` FAILED WITH RC `rc` REASON `rsn` FOR DATASET `dsn`

Explanation: The specified MVS function (LOCATE or OBTAIN) failed for a Control-M/Tape file. All the Control-M/Tape files are accessed by the CTTINIT procedure, and should exist on the CPU where each is activated. The LOCATE function could fail if the data set is not cataloged. The OBTAIN function could fail if it is cataloged on a wrong volume.

The return code in the message is a SVC99 MVS return code.

Initialization terminates.

Corrective Action: Check that the data set in the message matches the name specified in installation the DBPREF parameter in the CTTPARM member. Make sure that the data set exists and is cataloged on the correct volume.

CTT806E UCBSCAN FAILED WITH RC `rc` FOR VOL `vol`

Explanation: The specified volume could not be located in the system.

Initialization terminates.

Corrective Action: Check that the volume is accessible from the CPU where the CTTINIT procedure was activated.

CTT807E CONTROL-M/TAPE REAL-TIME ENVIRONMENT IS ALREADY ACTIVE

Explanation: The CTTINIT procedure was started with MODE set to either

INIT - to initialize Control-M/Tape environment
VERIFY - to verify Control-M/Tape interfaces could be applied

while the INIT/VERIFY process reveals that the Control-M/Tape real-time environment was already active in this CPU.

The INIT/VERIFY process is not started.

Corrective Action:Either use the existing Control-M/Tape environment or delete the existing one before trying to INIT/VERIFY a new one.

CTT808W CONTROL-M/TAPE OPERATES IN `op_mode` MODE

Explanation: The Control-M/Tape operation mode is set to one of the following modes: TEST, ACTIVE, SUSPEND, DORMANT, STACKING, or NO-STACK.

Control-M/Tape operates according to the mode, as follows:

TEST - Information is recorded in the Media Database (MDB); however, there is no intervention in the running of jobs (shadow mode).
ACTIVE - All functions are under Control-M/Tape control.
SUSPEND - All media access is suspended.
DORMANT - All media access is performed without Control-M/Tape control. No information is recorded in the MDB.
STACKING - Dynamic stacking is performed.
NO-STACK - Dynamic stacking is not performed.

Corrective Action: No action is required.

CTT809I CONTROL-M/TAPE `func` STARTED

Explanation: This information message indicates that the Control-M/Tape initialization or termination process was started by the CTTINIT procedure.

Corrective Action: No action is required.

CTT810I CONTROL-M/TAPE RELOAD `modName` /`tbl_typ` ENDED. RC=`rc`

Explanation: This information message indicates that the reload function for a module (for example, user exit) or tables (rules, pools or vaults) was performed. When Control-M/Tape is activated in the system, certain components can be reloaded (refreshed with a new copy). Reload can be performed for the following:

Modules - Mainly user exits but also Control-M/Tape internal modules.
Rules - All the rules (as specified in the RULLIST member) are reloaded.
Pools - All the defined rules (as specified in the DAPOOLS member) are reloaded.
Vaults - All the defined vaults (as specified in the DAVLTS member) are reloaded.

Upon successful completion, the system operates with the new modules or tables.

Corrective Action: No action is required.

CTT811I CONTROL-M/TAPE DYNAMIC `component func` SUCCESSFULLY

Explanation: This information message indicates that the specified dynamic installation component function was successfully performed (for example, applied, removed).

The dynamic installation function can be optionally performed according to installation parameters for each of the following components:

SVC - Control-M/Tape SVC; controlled by the DYNSVC parameter.
WTO Interface - WTO intercept; controlled by the DYNWTO parameter.
VOLSTAT INTR - VOLSTAT interface; no available parameter.
O/C/E Exits - MVS Tape Label Processing Exits; controlled by the DYNINTR parameter.
FAST-POSITION - fast position feature; no available parameter.
IEFDB401 Exit - MVS IEFDB401 Exit; controlled by the STKALCD parameter.

Corrective Action: No action is required.

CTT812E CONTROL-M/TAPE DYNAMIC INSTALLATION FAILED. RC=`rc`

Explanation: The dynamic installation function (for example, APPLY, REMOVE) failed with the specified return code (rc). This function can also be performed according to installation parameters on operating system interfaces, the SVC, and the WTO intercept. This message follows a message about a failure to a component.

Processing terminates immediately.

Corrective Action: Check preceding error messages for details about the error and notify your INCONTROL administrator.

CTT813E CONTROL-M/TAPE SVC NUMBER (`svc_num`) IS BEING USED BY ANOTHER PRODUCT

Explanation: SVC number svc_num is already defined for another purpose not related to Control-M/Tape. The SVC number that was specified for Control-M/Tape during installation time in the CTTPARM member is already defined in the system. Control-M/Tape does not replace it with its own SVC.

Dynamic installation of the SVC fails, and the currently executing function is terminated.

Corrective Action: Either change the SVC number in the CTTPARM member to an unused number, or remove the older definition from the system.

CTT814W CONTROL-M/TAPE SVC (`svc_num`) IS NOT INSTALLED

Explanation: SVC svc_num is not installed in the system. The SVC is used by all Control-M/Tape real-time functions. Therefore, as part of the initialization process, the existence of the SVC is checked. This message indicates that although the dynamic SVC installation was not required (DYNSVC was set to N in the CTTPARM member), the SVC is not properly defined.

The currently executing function continues without defining the SVC since dynamic definition was not requested.

Corrective Action: Check why the SVC was not properly defined, or change the installation parameters to perform dynamic SVC installation (set DYNSVC to Y).

CTT815E CONTROL-M/TAPE SVC (`svc_num`) IS ALREADY INSTALLED

Explanation: The APPLY option of Control-M/Tape could not install SVC svc_num, because it was already in the system. Before installing the specified SVC, the CTTINIT procedure of Control-M/Tape checks to see if it already exists in the system.

The SVC may be already in the system for one of the following reasons:

This SVC was already installed by some method other than Control-M/Tape.
Another Control-M/Tape installed this SVC and did not remove it, either because the other Control-M/Tape is still running, or because a severe error occurred and it did not shut down properly.

The attempt to install the SVC stops, and the initialization process stops.

Corrective Action: Check earlier errors, or do one of the following:

If no other release of Control-M/Tape is running, check that the DYNSVC installation parameter in the CTTPARM member is specified correctly.
If another release of Control-M/Tape is already running, use the PARALLEL installation parameter.

For more information, refer to the INCONTROL for z/OS Upgrade Guide.

CTT816E CONTROL-M/TAPE SVC (`svc_num`) `func` FAILED. RC=`rc`

Explanation: SVC svc_num could not be dynamically installed or removed from the system.

The SVC is not installed or removed. The currently executing function stops.

Corrective Action: Check preceding error messages for details. Notify your INCONTROL administrator.

CTT817W CONTROL-M/TAPE `interceptName` INTERCEPT IS NOT INSTALLED

Explanation: Although dynamic installation was not required, the specified intercept is not installed or properly defined in the system. As part of the initialization process, the existence of the intercept is checked.

Valid values for interceptName are WTO or VOLSTAT.

The currently executing function continues without installing the intercept.

Corrective Action: Check why the intercept was not properly installed, or change the installation parameters to perform dynamic installation.

CTT818E CONTROL-M/TAPE `interceptName` INTERCEPT IS ALREADY INSTALLED

Explanation: The APPLY option of Control-M/Tape could not install the specified intercept because it was already in the system. Before installing the specified intercept, the CTTINIT procedure of Control-M/Tape checks to see if it already exists in the system.

The intercept may be already in the system for one of the following reasons:

This intercept was already installed by some method other than Control-M/Tape.
Another Control-M/Tape installed this intercept and did not remove it, either because the other Control-M/Tape is still running or because a severe error occurred and it did not shut down properly.

Valid values for interceptName are WTO or VOLSTAT.

The attempt to install the intercept stops.

Corrective Action: Check earlier errors or do one of the following:

If no other release of Control-M/Tape is running and interceptName is WTO, check that the DYNWTO installation parameter in the CTTPARM member is specified correctly.
If another release of Control-M/Tape is already running, use the PARALLEL installation parameter.

Consult the INCONTROL for z/OS Upgrade Guide.

CTT819E CONTROL-M/TAPE `interceptName` INTERCEPT `func` FAILED. RC=`rc`

Explanation: The specified intercept could not be dynamically installed or removed from the system. Possible values of interceptName are WTO or VOLSTAT.

The specified intercept is not reinstalled or removed. The currently executing function is terminated.

Corrective Action: Check preceding error messages for details about the error. Notify your INCONTROL administrator.

CTT81AW THE PARAMETER CTVINTR HAS BEEN FORCED TO 'NONE'

Explanation: The real-time value of the parameter CTVINTR has been changed to 'NONE'.

Control-M/Tape changes the real-time value of CTVINTR to 'NONE' and continues to run.

Corrective Action: No response required.

CTT81BW CONTROL-M/TAPE OPERATES WITH ACTIVATED CONTROL-V INTERFACE

Explanation: The real-time value of the parameter CTVINTR is other than 'NONE'.

Control-M/Tape continues to use the current value of the CTVINTR parameter.

Corrective Action: Change the Control-M/Tape CTVINTR parameter in the member CTTPARM to 'NONE'. Then issue the following command, which updates the system with the new value:

S CTTINIT,PARM='MODE=RELOAD,TBLT=PARM'

CTT820W CONTROL-M/TAPE `component` NOT APPLIED

Explanation: One of the following situations occurs:

If the component is FAST-POSITION, then Control-M/Tape finds that the fast position intercept is already applied and therefore bypasses its installation.
If the component is O/C/E EXITS and the DYNINTR parameter is set to N, then the MVS Tape Label Processing Exits are not applied in the system, since their installation is not required. The MVS Tape Label Processing Exits are used by all Control-M/Tape real-time functions. Therefore, as part of the initialization process, the existence of these interfaces is checked.
If the component is O/C/E EXITS and the DYNINTR parameter is set to Y, then the MVS Tape Label Processing Exits were already applied in the system, since their installation was required. The MVS Tape Label Processing Exits are used by all Control-M/Tape real-time functions. Therefore, as part of the initialization process, the existence of these interfaces is checked.

The currently executing function continues without installation of the specified component

Corrective Action: No action is required.

CTT821E CONTROL-M/TAPE `component` ALREADY APPLIED

Explanation: The APPLY option of Control-M/Tape could not install the specified component because it is already in the system. Before installing the specified component, the CTTINIT procedure of Control-M/Tape checks to see if it already exists in the correct place in the system.

The component may be already in the system for one of the following reasons:

It was already installed statically using ICE via SMP/E user mode.
Another Control-M/Tape installed it and did not remove it, either because the other Control-M/Tape is still running or because a severe error occurred and it did not shut down properly.

The attempt to install the interfaces stops, and the initialization process stops.

Corrective Action: Check earlier errors or do one of the following:

If no other release of Control-M/Tape is running, check that the DYNINTR installation parameter in the CTTPARM member is specified correctly.
If another release of Control-M/Tape is already running, use the PARALLEL installation parameter.

Consult the INCONTROL for z/OS Upgrade Guide.

CTT822E CONTROL-M/TAPE `componentfunc` FAILED. RC=`rc`

Explanation: The component could not be dynamically installed or removed from the system.

The component is not installed or removed. The currently executing function is terminated.

Corrective Action: Check preceding error messages for details about the error.

CTT823S INITIALIZATION OF SUBSYSTEM `subsys` FAILED. RC=`rc`

Explanation: Due to internal error, activation of a Control-M/Tape subsystem failed.

The initialization process stops and the already created environment is removed from the system.

Corrective Action: Notify your INCONTROL administrator.

CTT824E CONTROL-M/TAPE TERMINATION HALTED. THE FOLLOWING JOBS ARE ACTIVE:

Explanation: Termination of Control-M/Tape cannot continue because Control-M/Tape detected active jobs that use removable media in the system. When active jobs that use removable media are still active, Control-M/Tape cannot stop. This message is followed by one or more CTT825I messages that identify the active jobs.

Control-M/Tape does not terminate.

Corrective Action: No action is required.

CTT825I JOBNAME: `jobName` JOBID: `jobId`

Explanation: This information message identifies the name and ID of an active job in the system that uses removable media.

This messages accompanies message CTT824E. There is one CTT825I message for each active job that uses removable media. The last CTT825I message is followed by message CTT826A.

Corrective Action: No action is required.

CTT826A TO CONTINUE CONTROL-M/TAPE TERMINATION, REPLY ‘R’- RETRY, ‘A’- ABORT, OR ‘F’- FORCE

Explanation: There was an attempt to terminate Control-M/Tape while there are still active jobs in the system that use removable media.

This message asks what to do next, as follows.

R (Retry) -- Check again for active jobs.
A (Abort) -- Fail the termination request and continue processing.
F (Force) -- Continue the termination request regardless of the active jobs status.

This message follows message CTT825I.

The CTTINIT procedure waits for the operator reply.

Corrective Action: Reply to the message.

Using the FORCE option is not recommended. If you use this option, the removable media used by the active jobs will not be updated in the Control-M/Tape repository, and jobs might abend. Also, other unpredictable situations could occur, that sometimes might be resolved only by IPL.

CTT827S UNABLE TO REMOVE `component`. ENTERING DORMANT MODE

Explanation: Termination of Control-M/Tape failed because Control-M/Tape was unable to remove the specified component. Since termination cannot continue, Control-M/Tape enters DORMANT mode.

This message follows a specific error message, which identifies the error.

Termination of Control-M/Tape stops. Control-M/Tape enters DORMANT mode.

Corrective Action: Look for previous Control-M/Tape messages and check why Control-M/Tape failed to remove the specified component. Then proceed accordingly.

CTT828I TERMINATION ABORTED BY OPERATOR. PROCESSING CONTINUES

Explanation: This information message indicates that the operator instructed Control-M/Tape to abort termination, probably because termination of Control-M/Tape was in progress when Control-M/Tape informed the operator about active jobs in the system.

This message follows message CTT826A.

Normal processing continues.

Corrective Action: No action is required.

CTT829E CTTINIT CANNOT PROCEED BECAUSE ANOTHER CTTINIT IS ALREADY ACTIVE

Explanation: A CTTINIT operation was attempted while another was already operating. The current run of the CTTINIT utility cannot proceed until the old one ends.

The new CTTINIT is ended.

Corrective Action: Restart the CTTINIT utility after the conclusion of the current run of the CTTINIT utility.

CTT830S PASSWORD CHECK FAILED

Explanation: The CTTINIT utility discovered an error in the Control-M/Tape password.

This messages follows other messages that detail the error and password.

The CTTINIT procedure stops.

Corrective Action: Check the job log of CTTINIT for previous messages that refer to this failure, and proceed accordingly.

CTT831W CONTROL-M/TAPE TRACE FILE AND MDB BOTH RESIDE ON THE SAME VOLUME (`vol`)

Explanation: The Media Database (MDB) and the Trace (TRC) file are on the specified volume.

This message is issued during initialization of Control-M/Tape, when both the data component of the MDB (MDBD) and the TRC file are on the same volume. If the MDB is damaged, the CTTRCV utility can recover it using the TRC file as input. If the TRC file is also damaged, recovery fails. Keeping the TRC file on the same volume as the MDBD increases the danger of both being damaged simultaneously, with a resulting inability to recover.

Control-M/Tape initialization continues.

Corrective Action: As soon as possible, move the TRC file to a different volume from the one holding the MDB. Control-M/Tape must be inactive when the file is moved.

CTT832E CONTROL-M/TAPE SUBSYSTEM IS NOT DEFINED

Explanation: A Control-M/Tape subsystem was not statically defined. Because the TSSALLOC parameter in the CTTPARM member was set to N, Control-M/Tape does not dynamically define its subsystem during initialization.

The Control-M/Tape real time environment is not initialized.

Corrective Action: Either change the value of the TSSALLOC parameter in the CTTPARM member to Y, or define the Control-M/Tape subsystem statically.

For more information, see the description of the TSSALLOC parameter in the Control-M/Tape chapter of the INCONTROL for z/OS Installation Guide.

CTT833I CONTROL-M/TAPE IS UNABLE TO RELEASE THE RULES BECAUSE THEY ARE IN USE BY ANOTHER PROCESS

Explanation: When Control-M/Tape reloads rules following operator request RELOAD,TBLT=RULE, it first loads the new set of rules into memory and makes them active. Then, after several seconds, it releases the old set of rules, unless there are active processes using these old rules. This message indicates that there is at least one active process still using the old set of rules.

This message is followed by message CTT834A.

Corrective Action: Implement one of the options specified in message CTT834A.

CTT834A TO CONTINUE, REPLY 'R'- RETRY OR 'F'- FORCE

Explanation: In the situation described by message CTT833I, the user has the following response options:

F--Control-M/Tape retries releasing the old set of rules immediately.
R--Control-M/Tape retries releasing the old set of rules after a short delay.

Corrective Action: Implement the appropriate option.

CTT835S DYNAMIC INSTALLATION FOR EXIT `exitName` FAILED. RC=`rc` REASON=`rsn`

Explanation: During Control-M/Tape real time environment initialization, the dynamic installation for the exitName exit failed.

Control-M/Tape real-time environment initialization is terminated.

Corrective Action: Refer to IBM documentation along with the return code and reason code displayed in the message to understand why Control-M/Tape could not dynamically install the exit.

CTT840E KEY CHANGED. UPDATE FAILED FOR RECORD `rcrd_type`

Explanation: When updating a record using function RECUPD, an attempt was made to change the record key, (for example, the VOLSER in the volume record).

Execution of the RECUPD function is terminated, and the record is not updated.

Corrective Action: The record key cannot be updated directly. Instead, first delete the record, and then add a new one with the required key. If you inadvertently try to change the key by specifying an invalid offset in the REP statement, correct the control REP statement accordingly.

CTT841E VOLSER `volser` DOES NOT MATCH POOL `poolName`

Explanation: When trying to add a data set to the Media Database (MDB) using the DSNADD function, the selected pool specified in the corresponding Control-M/Tape rule did not contain the volser in which the data set resides.

The variables in this message are:

poolName - the pool specified in the corresponding Control-M/Tape rule
volser - the volser in which the data set resides

Execution of the DSNADD function is terminated. The data set is not added.

Corrective Action: Synchronize the DSVOLSER parameter with the pool definition.

CTT842W CTTVTM SHOULD RUN IN MODE={SLOTBLD | BOXBLD} AFTER UPDATING THE VOLUME

Explanation: The CTTMUP utility issues this message when volume record fields that are related to vaulting are modified. When vaulting related fields are modified in a volume record, the corresponding vault, slot and box records need to be modified to reflect the changes made in the volume record. The CTTVTM utility performs the necessary synchronization in the indicated mode.

The CTTMUP utility continues.

Corrective Action: Run the CTTVTM utility in SLOTBLD or BOXBLD mode as indicated by the message.

CTT850S RULE ORDER LIST IS EMPTY. DDNAME="DARULLST"

Explanation: Open of a rule list data set failed (the DARULLST DD statement).

Possible causes are:

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

The CTTINIT procedure stops.

Corrective Action: Correct the JCL and restart the CTTINIT procedure.

CTT851S INVALID DATA IN RULE ORDER LIST CARDS

Explanation: Invalid data has been found in the rule order list.

The CTTINIT procedure stops.

Corrective Action: Check the format of the rule order list in the PARM library; correct and restart the CTTINIT procedure.

CTT852S ORDER OF TABLE `tableName` RULE `ruleName` FAILED

Explanation: The order of rule ruleName from table tableName failed. This message is preceded by messages which explain why the rule table could not be ordered.

The rule is not ordered.

Corrective Action: Check earlier messages for reasons the rule order failed. Correct as necessary and reorder the rule table.

CTT853S ERROR IN RULE DATA. MANDATORY `stmt_type` STATEMENT IS EITHER MISSING OR NOT IN THE CORRECT ORDER

Explanation: A stmt_type statement is either missing or in the wrong order in a rule definition member. The rule definition data may have manually been changed incorrectly. The data does not conform to a valid Control-M/Tape format.

The rule is not ordered.

Corrective Action: Restore the table to its original state (from a backup copy) and reorder the rule table.

CTT854S INVALID SCHEDULING DATE - `date`

Explanation: An invalid scheduling date format was used in the rule list or in an order or force request.

Valid date formats are:

ddmmyy -- Day, month, and year
mmddyy -- Month, day, and year
* -- Current Control-M/Tape working date

The requested table order fails.

Corrective Action: Correct the date; reorder the rule table.

CTT855S ** ERROR IN RULE STATEMENTS. CHECK THE FOLLOWING STATEMENTS *

Explanation: The rule definition has been corrupted and the data does not conform to a valid Control-M/Tape format.

This message is followed by one or more CTT856S messages describing all statements belonging to the damaged rule. An asterisk (*) appears in the line under the erroneous data.

The rule is not ordered.

Corrective Action: Restore the table to its original state by means of the Online Viewing Facility, or by editing the member, then reorder the rule table.

CTT856S STATEMENT = `stmt`

Explanation: The rule definition is corrupt.

This message follows message CTT855S, and displays each statement in the damaged rule. An asterisk * appears in the line under a damaged statement.

The CTTMRLL program terminates with a condition code of 08.

Corrective Action: Restore the table to its original state.

CTT857I RULE `ruleName` TABLE `tableName` LIBRARY `lib` ODATE `odate` LOADED

Explanation: This is the normal message when a rule order is successfully loaded by the CTTINIT procedure. The rule is now active and will be used by the Control-M/Tape real-time process.

Corrective Action: No action is required.

CTT858S SEVERE ERROR IN RULE DATA STATEMENTS

Explanation: A severe error was found in the rule definition data statements. This message is followed by additional messages regarding the error.

The rule table is not ordered.

Corrective Action: Check for additional messages concerning the errors. Correct the error and reorder the table.

CTT859W ORDER CANCELED BY USER EXIT: RULE `ruleName` TABLE `tableName` LIBRARY `lib`

Explanation: The specified rule order failed as a result of a user exit check.

The rule order is not ordered or loaded.

Corrective Action: Check for prior messages concerning the reason for failure and the Control-M/Tape EXIT 1.

CTT862E OPERATION CANCELED BY USER EXIT CTTSE01

Explanation: The operation was canceled because Control-M/Tape User Exit CTTSE01 ended with a return code higher than 0.

The operation is canceled.

Corrective Action: Check why the exit ended with a return code higher than 0, and proceed accordingly.

CTT863E RULE MEMORY BLOCK GETMAINED BELOW 16MB LINE (IN CSA)

Explanation: The rule loading program of the CTTINIT utility tried to allocate a block for rules in ECSA. Due to lack of memory, it received an area in CSA. Control-M/Tape does not allocate CSA areas for rule blocks when working in TEST mode.

Rule loading is stopped. The CTTINIT procedure terminates after freeing all memory blocks allocated thus far.

Corrective Action: Either increase the ECSA size defined in your system, or reduce the number of rules defined to Control-M/Tape. Restart the CTTINIT utility.

CTT864E UNABLE TO FREE RULE BLOCKS FROM MEMORY

Explanation: Control-M/Tape was unable to free rule blocks from memory. The rule loading program ended unsuccessfully. An error occurred during the process of freeing all rule blocks allocated thus far.

If the allocated blocks are in ECSA or CSA, they are not freed by Control-M/Tape. If the allocated blocks are in a private region, they will be freed at job end.

Corrective Action: If allocated blocks remained in ECSA or CSA, use a tool (for example, OMEGAMON, RESOLVE) to free these blocks. Blocks not freed by a tool will be freed automatically by the next IPL.

Use extreme caution when freeing blocks from ECSA or CSA manually.

CTT865S NO RULES WERE LOADED BECAUSE NONE MATCH SCHEDULING CRITERIA

Explanation: Control-M/Tape was unable to load any rules because no rules were scheduled for today.

Control-M/Tape does not load any rule, and execution stops.

Corrective Action: Use the TR screen to check your rule definitions and update the rule scheduling criteria so as to ensure that at least one rule will be scheduled for today.

CTT870E INSUFFICIENT CAPACITY FOR MEDIA `media`, VAULT `vault`

Explanation: The Slot Management Facility could not find an empty slot for a volume being moved to the vault specified in the message. If a capacity is defined for a vault, Control-M/Tape tries to assign a slot to each volume that comes to the vault.

The appropriate Slot Definition record is not updated.

Corrective Action: Increase the capacity of the vault using the Vault Definition screen (screen TV), or define the vault with no capacity. Then run the CTTVTM utility in SLOTBLD mode.

CTT871E SLOT `slot` ALREADY IN USE. MEDIA=`media`, VAULT=`vault`

Explanation: The Slot Management Facility tried to assign a slot to a volume according to the slot number specified in the volume record, but the slot is already occupied by another volume.

Control-M/Tape does not reassign the slot number, but continues with the next volume.

Corrective Action: Correct the slot number in the volume record using the Volume Update screen.

CTT872E CONTROL-M/TAPE IS STILL ACTIVE, UTILITY `util` CANNOT CONTINUE

Explanation: The util utility cannot run in the mode requested if Control-M/Tape is active. Some Control-M/Tape utilities cannot be run while the Control-M/Tape real-time environment is active.

The utility terminates.

Corrective Action: See the description of this utility in the INCONTROL for z/OS Utilities Guide.

CTT873E EXPECTED CONTINUATION NOT RECEIVED

Explanation: An input statement was continued to the next line, but no continuation line was supplied. A comma at the end of a line indicates a continuation line, but the input was exhausted before the continuation line was received.

The program stops executing.

Corrective Action: Either remove the comma or supply the missing line.

CTT874E INVALID CONTROL STATEMENT: `err`

Explanation: The current control statement is in error.

Possible values for err are:

err	Explanation
INVALID DATE - `date`	The date specified (`date`) is in an invalid date format or contains invalid values. Valid formats for the date are yyyymmdd or yymmdd.
INVALID EQUATE SPECIFIED - `equ`	The equate `equ` was used incorrectly. For the correct usage of equate, see the appendix that describes logical field names for the Control-M/Tape repository in the `INCONTROL for z/OS Administrator Guide`.
INVALID FUNCTION ISSUED	An invalid function was used. For a list of supported functions, see the documentation for the CTTMUP utility.
INVALID HEX VALUE SPECIFIED - `hex`	`hex` is an invalid hexadecimal value.
INVALID KEYWORD SPECIFIED - `kwd`	The keyword `kwd` was used incorrectly, perhaps on the wrong side of the relation symbol. For the correct keyword format, see the appendix that describes logical field names for the Control-M/Tape repository in the `INCONTROL for z/OS Administrator Guide.`
INVALID NUMERIC VALUE SPECIFIED	A non-numeric value was specified.
INVALID PARAMETER VALUE - `parm`= `val`	The value assigned to parameter `parm` is invalid. For a list of correct values, see the appendix that describes logical field names for the Control-M/Tape repository in the `INCONTROL for z/OS Administrator Guide.`
INVALID '`parm`=' SPECIFICATION	The value specified for the `parm` parameter is invalid.
INVALID RBA PARAMETER	An invalid value was given to an RBA field. The RBA format is X `hhhhhhhh`, where X is a constant and `hhhhhhhh` is a valid RBA found in the MDB.
INVALID RELATION IN KEYWORD - `keywd`	An invalid relation symbol was used. Only the “=” symbol can be specified.
INVALID RETENTION DATA - `rtn`	Incorrect retention data was specified. For the correct format of retention data, see the documentation for the CTTMUP utility.
INVALID STATEMENT CODE	The statement contained an invalid code, or was not correctly placed.
INVALID ZERO VALUE SPECIFIED	The value of zero is invalid.
KEYWORD NOT FOUND IN DICTIONARY - `keywd`	The keyword `keywd` is invalid. Check the spelling.
MANDATORY FIELDS NOT FOUND	At least one mandatory field is missing. For mandatory fields, see the documentation for the CTTMUP utility.
TYPERUN STATEMENT MISSING	The TYPERUN statement is mandatory. It was not specified.
VOLSER TOO LONG - `volser`	VOLSER should contain one through six characters only.
VALUE EXCEED MAXIMUM `parm`= `val`	The `parm` parameter has been set to a value (`val`) that exceeds the maximum.

Corrective Action: Correct the error and rerun the utility.

CTT875W RULE SEARCH IS NOT PERFORMED FOR DATASET `dsn`

Explanation: Rule search is not performed for the dsn data set that is being added. The CTTMUP utility was activated with RULEINFO set to YES (the default). The DSNADD function was requested, but the volume specified as dsvolser was not in the Media Database. A rule search cannot be performed without valid volume information.

The dsn record is added without application of rule information for this data set.

Corrective Action: Ensure that the correct volume keyword dsvolser was specified in command DSNADD. When adding a data set (DSNADD) and a volume (VOLADD) to contain the data set, it is recommended that commands be issued in the following order: VOLADD, DSNADD.

CTT876I FUNCTION `func` PERFORMED SUCCESSFULLY. RECORD=`key`

Explanation: This information message indicates that the specified function was performed successfully. The record key or the record type is indicated.

The CTTMUP utility continues to the next function.

Corrective Action: No action is required.

CTT877W VOLUME `vol` IS NOT EXPIRED. USE GROUP EXPIRATION FUNCTION

Explanation: The scratch action requested for the vol volume could not be performed because vol is a member of a multivolume chain, and expiration of a single volume of a multivolume chain is not allowed.

The CTTMUP utility continues to next function.

Corrective Action: Use function GRPSCR if you wish to expire the entire multivolume chain.

CTT878W MISMATCH BETWEEN DATASET LABEL AND HIGHEST LABEL OF VOLUME `volser`

Explanation: The data set label number does not match the number of the highest label specified on one of its volumes. All the volumes connected by a multivolume data set must have the same label number as the data set itself, except for the last volume, which can have a higher label number.

In this message, volser is the identity of the problematic volume.

The execution of the current function continues.

Corrective Action: Correct the data set label number using the DSNUPD function, or the highest label number of the volume using the VOLUPD function.

CTT879E VERIFY REJECT

Explanation: The RECUPD function discovered that the data specified in the VER statement does not correspond to the data in the selected record.

Execution of the RECUPD function is terminated.

Corrective Action: Correct the data in the VER statement according to that in the selected record.

CTT880S {POOL | VAULT} LOAD FAILED. NAME: {`poolName`|`vaultName` }

Explanation: The load of the pool or vault failed. This message is preceded by messages that explain why the pool or vault could not be loaded.

The pool or vault is not loaded.

Corrective Action: Check earlier messages for reasons the pool or vault load failed. Correct as necessary.

CTT881W {POOL | VAULT} FILE IS EMPTY. DDNAME: {DAPOOLS | DAVLTS}

Explanation: Open of the pool or vault data sets failed (the DAPOOLS or DAVLTS DD statement).

Possible causes are:

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

Processing continues. Control-M/Tape will not have a pool or vault defined to it.

Corrective Action: No action is required.

CTT882S ERROR IN {POOL | VAULT} DATA. MANDATORY `type` STATEMENT IS EITHER MISSING OR NOT IN THE CORRECT ORDER

Explanation: A statement of the type type is either missing or in the wrong order in a pool or vault definition member. The pool or vault definition data may have been manually changed incorrectly. The data does not conform to a valid Control-M/Tape format.

The pool or vault is not ordered.

Corrective Action: Restore the table to its original state from a backup copy. Reorder the pool or vault table.

CTT883I {POOL | VAULT} LOADED SUCCESSFULLY. NAME: `name`

Explanation: This information message indicates a pool or vault order was successfully loaded by the Control-M/Tape monitor.

The pool or vault is now in a Control-M/Tape WAIT SCHEDULE state.

Corrective Action: No action is required.

CTT884S ** ERROR IN {POOL | VAULT} STATEMENTS. CHECK THE FOLLOWING STATEMENTS *

Explanation: The pool or vault definition is corrupt, and the data does not conform to a valid Control-M/Tape format.

This message is followed by one or more CTT885S messages describing all statements belonging to the corrupted pool or vault order. An asterisk (*) appears in the line under the erroneous data.

The pool or vault is not ordered.

Corrective Action: Restore the table to its original state by means of the Online Viewing facility; then reorder the pool or vault table.

CTT885S STATEMENT = `stmt`

Explanation: The pool or vault definition is corrupt.

This message follows message CTT884S. It appears once for each statement in the corrupted pool or vault in the scheduling table, each occurrence displaying a different statement. An asterisk * appears in the line under an erroneous statement.

The CTTMPVL program terminates with a condition code of 08.

Corrective Action: Try to restore the table to its original state.

CTT886S SEVERE ERROR IN {POOL | VAULT} DATA STATEMENTS

Explanation: A severe error was found in the pool or vault definition data statements. It is followed by additional messages regarding the error.

The pool or vault table is not ordered.

Corrective Action: Check for additional messages concerning the errors in the systems and IOA Log. Correct the error and reorder the table.

CTT887S POOL RANGES OVERLAP: `pool1` AND `pool2`

Explanation: Two pools (pool1 and pool2) were defined with a range overlap. Therefore, some volumes may belong to both pools. Control-M/Tape requires that volume ranges be unique for all pools.

The initialization process terminates.

Corrective Action: Correct the pool definitions so that no volume is defined in more than one pool.

Messages CTT900 through CTT9xx

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

CTT900E VALID LABELS ARE SL/NL/NSL/AL

Explanation: An invalid label type was specified in the LABEL TYPE field. The LABEL TYPE field is used to specify the label type of the external volume to be added (or modified) to the Control-M/Tape Media Database (MDB).

Valid label types are:

SL - Standard label
NL - No label
NSL - Nonstandard label
AL - ANSI label

Corrective Action: Correct the entry by specifying a valid label type.

CTT901E VALID RETENTION TYPES ARE DAY/DAT/P/C/R/M

Explanation: An invalid retention type was specified in the RETENTION field. The RETENTION field specifies a period for which an external volume should be kept. Different retention types specify different ways to calculate the duration to retain an external volume before it may be used as a scratch volume.

Valid retention types are:

DAT - Date
DAY - Days
P - Permanent
C - MVS catalog
R - according to specified rules
M - MVS Catalog

Corrective Action: Correct the entry by specifying a valid retention type.

CTT902E INVALID DATA ON RETENTION LINE

Explanation: Either data were specified for a retention type that does not allow additional data, or a retention type was changed to a retention type for which additional data are not allowed. The RETENTION field is used to specify a period for which an external volume should be kept. Additional data are not valid for the PERMANENT and MVS CATALOG retention types.

Corrective Action: Correct the entry by clearing out the additional data after the RETENTION field.

CTT903E VOLSER `volser` ALREADY EXISTS IN MDB

Explanation: An attempt was made to add a volume (volser) to the Control-M/Tape Media Database (MDB), and the volume name already exists in the MDB. The MDB contains information about all the volumes known to Control-M/Tape. The SL-NAME field must contain a unique volume identification for Control-M/Tape.

The entry is not added to the MDB, nor is the existing record in the MDB modified by any of the fields in the Check-In Volume screen.

Corrective Action: If the existing entry in the MDB refers to the external volume specified, then exit the Check-In Volume screen, or add a different external volume.

If the existing entry does not refer to the external volume specified, and they happen to share the same identification, then do the following:

Specify a new unique identification in the SL-NAME field. This may be a brand new ID and is used by Control-M/Tape internally. This name is not physically written on the volume.
Specify in the VOLSER field the value that was previously specified in the SL-NAME field (the physical volser).

The SL-NAME and VOLSER fields should contain the same value, except in cases described above in which the SL-NAME is an ID given to Control-M/Tape for internal purposes and VOLSER is the physical ID of the volume. All references to this volume using Control-M/Tape should be done using the ID in the SL-NAME field.

CTT904I VOLSER `volser` ADDED TO MDB

Explanation: This information message indicates that external volume volser was successfully added to the Control-M/Tape Media Database (MDB).

Corrective Action: No action is required.

CTT905E PREVIOUS DATASET FIELD MUST BE SPECIFIED

Explanation: A data set name was specified in a DATASET # field, but no value was specified in the previous DATASET # field.

DATASET # fields specify a list of data set names that appear on the external volume. The list may not contain entries separated by an empty field. This information is automatically recorded in the Media Database (MDB) whenever the external volume is read under Control-M/Tape, but only after the external volume is added to the MDB.

Corrective Action: Correct the list of data set entries by filling in the blank field or by clearing all the entries following the empty data set entry.

CTT906E AT LEAST ONE DATASET SHOULD BE SPECIFIED TO ENABLE CATALOGING

Explanation: A request was made to catalog the data sets of an external volume but no data set names were specified in the DATASET # fields. A value of Y (yes) specified in the MVS CATALOG is a request to catalog all of the volume data sets specified. If no data set names are listed, cataloging cannot be performed.

Corrective Action: Specify at least one DATASET # value or change the value of the MVS CATALOG field to N (no).

CTT907E AT LEAST ONE DATASET SHOULD BE SPECIFIED TO ENABLE CATALOG RETENTION

Explanation: The retention period of the external volume was set to MVS CATALOG, but there were no data sets specified in the DATASET # fields.

Specifying a retention type of MVS CATALOG in the RETENTION field means keep the external volume as long as the data sets on the external volume are cataloged. If no data set names are listed, no data sets are cataloged and this retention period cannot be supported.

Corrective Action: Either specify at least one DATASET # value, or change the retention type of the external volume to a type other than MVS CATALOG.

CTT908S CATALOG OF `dsn` FAILED. RC=`rc`

Explanation: A request to add an external volume to the MDB using the ENTER command and a request to catalog the data sets of the external volume by specifying Y in the MVS CATALOG field both failed. The ENTER command triggers both requests. Cataloging is performed first.

The variables in this message are:

dsn - the name of the data set
rc - the return code

Possible values of rc, and their explanations are shown in the following table:

rc	Explanation
4	The required catalog does not exist or is not open.
8	The user is not authorized to perform the operation.
20	There is insufficient space on the catalog data set.
24	Either an attempt was made to catalog an improperly named generation data set, or the generation index is full and the named data set is older than any in the index.
28	An I/O error occurred.

The data sets are not cataloged. The external volume is not added to the MDB.

Corrective Action: Check the return code to see why the catalog attempt was unsuccessful. After the cataloging problem is resolved, try again.

CTT909E LABEL OF DATASET MUST BE HIGHER THAN `lbl_num`

Explanation: The label number specified in a DATASET# field is lower or equal to the previous label number. The label number of a data set must be higher than the label number of the preceding data set. The first data set in the list must have label number of 1 or higher.

Corrective Action: Correct the label number of the data set by entering a valid sequence of label numbers in the data set list.

CTT910E PREVIOUS MULTI-VOLUME SL-NAME MUST BE SPECIFIED

Explanation: An SL-NAME was specified in one of the multivolume SL-NAME fields but the previous SL-NAME field in the list was empty.

Multivolume SL-NAME fields specify a list of volumes that are spanned by the last specified data set. For example, the last data set in the list spans the SL-NAME that appears at the top of the screen as well as all the multivolume SL-NAMEs filled in at the bottom of the screen. The multivolume list may not contain two completed entries separated by a blank entry.

Corrective Action: Correct the list of multivolume SL-NAMEs either by filling in the blank entry or by clearing all the other SL-NAME fields following the blank entry.

CTT911E SL-NAME CANNOT BE SPECIFIED WITHOUT VOLSER

Explanation: An SL-NAME was specified in one of the multivolume SL-NAME fields but the corresponding VOLSER field in the list was not specified. If the SL-NAME field is specified, then the VOLSER field must also be specified. For more information, see the description of the SL-NAME concept in the section on volume processing in the Control-M/Tape User Guide.

Corrective Action: Correct the list of multivolume volsers by filling in the VOLSER field or removing the SL-NAME field.

CTT912E ADDITIONAL VOLSER `volser` ALREADY EXISTS IN MDB

Explanation: A volser was entered in one of the multivolume SL-NAME fields but this volser already exists in the Media Database.

Multivolume SL-NAME fields specify a list of volumes which are spanned by the last specified data set. For example, the last data set in the list spans the SL-NAME that appears at the top of the screen as well as all the multivolume SL-NAMEs filled in at the bottom of the screen. A unique value must be specified in the SL-NAME field; the volume cannot be identified with a non-unique identifier.

Corrective Action: Correct the list of multivolume SL-NAMEs by identifying the volume with a unique identifier (a new SL-NAME) which should be entered in the SL-NAME field. (In such a case, the VOLSER field should be used to hold the actual volume serial number which is not unique.)

CTT913I MULTI VOLUMES ADDED TO MDB STARTING WITH VOLSER `volser`

Explanation: This information message indicates that external multi volumes (volsers) were successfully added to the Control-M/Tape Media Database.

The Media Database contains information about all volumes known to Control-M/Tape. An attempt to add using command ENTER external multi volumes to the Media Database was successful. For example, the external multi volumes were entered as known volumes to the Media Database.

Corrective Action: No action is required.

CTT913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a print file failed.

Possible causes are:

The DD statement SYSPRINT is missing.
The data set described by the DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

CTT914E ADDITIONAL VOLSER `volser` HAS BEEN PREVIOUSLY SPECIFIED IN LIST

Explanation: A volser was entered in one of the multivolume SL-NAME fields but this volser already exists in one of the multivolume SL-NAME fields or in the first SL-NAME field.

Multivolume SL-NAME fields specify a list of volumes which are spanned by the last specified data set. For example, the last data set in the list spans the SL-NAME that appears at the top of the screen, as well as all the multivolume SL-NAMEs filled in at the bottom of the screen. A unique value must be specified in the SL-NAME field; the same value cannot appear twice in the same list.

Corrective Action: Correct the list of multivolume SL-NAMEs by eliminating SL-NAMEs that appear more than once in the list.

CTT915S DSN `dsn` ALREADY CATALOGED

Explanation: A request to add an external volume to the Media Database using the ENTER command and a request to catalog the data sets of the external volume by specifying Y in the MVS CATALOG field both failed. The ENTER command triggers both, but performs cataloging first. Cataloging of the data set failed, because one of the data sets (dsn) is already cataloged.

The data sets are not cataloged and the external volume is not added to the Media Database.

Corrective Action: Notify your system programmer. To add the external volume, change the value in the MVS CATALOG field from Y to N.

CTT916I CONTROL-M/TAPE IS NOT ACTIVE. IOA DO COMMANDS WILL HAVE NO EFFECT

Explanation: An attempt was made to process IOA DO commands with a WHEN CHECKIN statement or the RETENTION by RULES option while Control-M/Tape was not active.

IOA DO commands in matching rules are ignored. If RETENTION BY RULES is requested, no retention or vaulting pattern is set for any data set in the checked in volume.

Corrective Action: To perform IOA DO commands in matching rules, or to implement the retention and vaulting pattern defined in Control-M/Tape rules for the checked-in data sets, start Control-M/Tape by means of CTTINIT.

CTT917I RANGE OF EXTERNAL VOLUME REFERENCES BY PREFIX IS FULL

Explanation: The range of volume names using the external prefix is full. The External Volume Reference Prefix is defined in CTTPARM by the EXTRNVOL parameter. All volume names defined by this prefix are already defined in the Media Database (MDB).

The name of the volser will no longer be assigned automatically by Control-M/Tape.

Corrective Action: Fill in an alternate volser name.

CTT918I PRESS ENTER TO CONFIRM THE ADDITIONAL VOLSER LIST

Explanation: When the CTTPARM EXTRNVOL parameter is set, when entering a multi-volume data set on the TC screen (EXTERNAL VOLUME CHECK-IN SCREEN), this message requests that the user confirm each additional volume name as the volume is added.

Corrective Action: Press Enter to confirm each additional volume name.

CTT919E CONTROL-M/TAPE IS NOT ACTIVE. RETENTION BY RULES CANNOT BE REQUESTED.

Explanation: RETENTION BY RULES was specified when checking-in an external volume in screen TC while Control-M/Tape was inactive.

The retention for the checked-in volume cannot be determined. Therefore, the check-in is rejected. Control-M/Tape rules can only be applied when Control-M/Tape is active. Only manually specified retention types can be used in the TC screen when Control-M/Tape is inactive.

The online screen waits for a retention type to be manually specified for the volume.

Corrective Action: Do one of the following:

Start Control-M/Tape using the CTTINIT procedure, and then check-in the volume.
Manually specify a retention type for the volume in screen TC.

CTT920E INVALID UNIT NAME `unitname`

Explanation: The unitname unit name is not defined in the system.

The requested action fails. If issued by the CTTUGNM utility, the utility continues to process the next volume record.

Corrective Action: Perform one of the following actions:

If issued when trying to add a tape in a TC screen, correct the unit name specified in the ON UNIT field to the correct unit name for the volume being added.
If issued in the output of the CTTUGNM utility, the message is followed by message CTT202I, which contains the details of the failing volume. Use CTTMUP to change the unit name for this volume to be a valid unit name that is defined in the system, and rerun the CTTUGNM utility.

CTT921E UNIT NAME IS REQUIRED WHEN CATALOG=Y IS SPECIFIED

Explanation: A unit name should be specified when datasets are cataloged.

Corrective Action: Specify a valid unit name in the ON UNIT field.

CTT922E `service req` FAILED. UNIT=`unitName` RC=`rc` REASON=`rsn`

Explanation: The specified service and request for the unitname unit failed with the specified return and reason codes.

This message is followed by message CTT202I, which contains the details of the failing volume.

The CTTUGNM utility continues to process the next volume record.

Corrective Action: For the EDTINFO service, a request of RTNDEVN, a return code of 8, and a reason code of 00000001, change the unit name for this volume to be a valid unit name that is defined in the system using CTTMUP, and rerun the CTTUGNM utility.

For any other information, verify that the unit name is defined in the system and that there are devices attached to it. If not, change the unit name of the volume record to be a valid unit name and rerun the CTTUGNM utility.

CTT930I `opc` (`type`) RBA=x'`rba'` DT=`date /time` V=`vol /dsn`

Explanation: This information message indicates the physical recovery of a Media Database (MDB) record from the Trace file. The message is issued for every physically recovered MDB record.

The variables in this message are:

opc - Operation code for the operation performed on the MDB.

Valid values are:

opc	Explanation
DEL	The record is deleted from the MDB.
ADD	The record is added to the MDB.
UPD	The record is updated in the MDB.

type - Record type in the MDB.

Valid values are:

type	Explanation
DS	Data set record
VL	Volume record
CT	Vault control
CA	Vault capacity
CN	Vault continuation

rba - RBA of the record being updated, added, or deleted.
date - Date portion of the record timestamp.
time - Time portion of the record timestamp.
vol - For DSN record, the first volume of the data set. For other record types, this field is blank.
dsn - For DSN record, data set name. For other record types, this field is blank.

Corrective Action: No action is required.

CTT931I `opc (type)` U=`userId /jobId` DT=`date /time` V=`vol /lbl /dsName`

Explanation: This information message indicates the logical recovery of a Media Database (MDB) record from the Trace file. The message is issued for every logically recovered MDB record.

The variables in this message are:

opc - Operation code for the operation performed on the MDB.

Valid values are:

opc	Explanation
DEL	The record is deleted from the MDB.
ADD	The record is added to the MDB.
UPD	The record is updated in the MDB.
CAT	The data set is cataloged.
MAT	The MDB record does not match its data in the Trace file.

type - Record type in the MDB.

Valid values are:

type	Explanation
DS	Data set record
VL	Volume record
CT	Control record
CA	Vault capacity
CN	Vault continuation

userId - Job name or user ID of the job that caused the record to be written.
jobId - Jobid of the above job name or user ID.
date - Date portion of the record timestamp.
time - Time portion of the record timestamp.
vol - For a data set name or cat record, the first volume of the data set. For other record types, this field is blank.
lbl - For a data set name or cat record, label number of the data set on the volume. For other record types, this field is blank.
dsn - For a data set name or cat record, data set name. For other record types, this field is blank.

Processing continues unless an error occurs. A later message indicates if the process is prematurely terminated. If terminated, recovery is complete up to the point of termination. All MDB records created prior to that point reflect the unrecovered situation.

Corrective Action: No action is required.

CTT932E `opcode` REQUIRED FOR THE FOLLOWING RECORD BUT IT WAS [NOT] FOUND IN MDB:

Explanation: The opcode action requested for the record cannot proceed. Possible causes are:

If opcode is ADD and the record already exists in the Media Database.
If opcode is DEL or UPD and the record does not exist in the Media Database.
In simulation mode, this message may be issued if previous records were not added to the Media Database.

In normal mode, recovery can be successful without issuing the message.

This message precedes message CTT931I.

Processing of records continues.

Corrective Action: No action is required.

CTT934I `num` RECORDS WERE {DELETED | UPDATED | ADDED}

Explanation: This information message is issued at the end of a logical or physical recovery.

Corrective Action: No action is required.

CTT935E CATALOG FAILED. RC: `rc` DSN: `dsn`

Explanation: The catalog operation for the specified data set failed with the specified rc. Whenever the CTTRTM utility expires a data set, it uncatalogs the data set. When the actions of the CTTRTM run are reversed using Logical Recovery, the CTTRCV utility tries to recatalog the data set.

Corrective Action: Determine why the catalog operation failed and proceed accordingly. If the return code is 8, probably the data set is already cataloged. The meaning of other return codes is in IBM documentation for LOCATE return codes. The CTTRCV utility must run in the same catalog environment in which the CTTRTM utility ran.

CTT936E THE FOLLOWING RECORD WAS FOUND WITH DIFFERENT FIELDS IN THE TRACE FILE AND THE MDB

Explanation: A trace record to be recovered has incompatible data in the Media Database (MDB). The record was updated at least one time after its current appearance in the Trace file. The record cannot be recovered because its trace file afterimage does not match its current data in the MDB. Recovering the data will cause loss of integrity.

This message precedes message CTT931.

Recovery is not performed for all records. However, the recovery job continues running until all records to be recovered are found, and appropriate messages issued.

Corrective Action: To omit processing of the record, use INCLUDE and/or EXCLUDE statements. If you set the FORCE parameter to YES, this message is issued but recovery is performed anyway. Setting FORCE to YES may cause loss of integrity in the MDB. For more information, refer to documentation for the CTTRCV utility in the INCONTROL for z/OS Utilities Guide.

CTT937I `num` RECORDS ARE NOT MATCHED WITH DATA IN THE MDB

Explanation: This statistical information message issued at the end of a logical or physical recovery of the Media Database (MDB) indicates the number of records (num) that were found with different fields in the Trace file and the MDB.

Corrective Action: No action is required.

CTT950E COULD NOT ACCESS `lib (mem)`

Explanation: Dynamic allocation of the mem member in the specified library failed. The indicated library member should contain the rule list. It is usually found in the Control-M/Tape parameter library.

Corrective Action: Check that the DARLLIB DD statement points to a library containing the RULLIST member. If it does, check for possible I/O errors on that library.

CTT951E FILE DARSR COULD NOT BE BROWSED

Explanation: Dynamic allocation of the output file created by simulation the CTTCRSS utility failed. The probable cause of failure is that the output file could not be created by the CTTCRSS utility due to an SPF problem in the profile.

Corrective Action: Reactivate the CTTCRSS utility using CLIST CTTCRSS, and using the DEBUG parameter to get detailed information. If the failure is due to an SPF problem, correct accordingly. Otherwise, notify BMC Customer Support.

CTT952I NO RULE WAS ACTIVATED BY THESE CONDITIONS

Explanation: This information message indicates that the specified combination of conditions caused no rule to be activated.

Since no rules were activated, the simulation showed no results. However, in an identical situation, the Control-M/Tape Real Time environment would use either the JCL EXPIRATION DATE, if supplied, or the retention defaults defined in the installation parameters.

Corrective Action: No action is required.

CTT953S ONE OF THE RULES SPECIFIED BY THE RULE LIST IS INVALID

Explanation: An invalid rule definition was encountered during new RULLIST processing.

Corrective Action: Correct the invalid rule definition and rerun the CTTCRSS simulation utility. To find which rule is invalid, activate CLIST CTTCRSS using the DEBUG parameter. This parameter enables debug listings.

CTT954S INTERNAL ERROR IN "CTTCRSS"

Explanation: An unrecognized return code was issued during the processing of the CTTCRSS simulation utility.

Corrective Action: Reactivate CTTCRSS using CLIST CTTCRSS, and using the DEBUG parameter to get detailed information. Notify BMC Customer Support of the results.

CTT955S UNABLE TO LOAD NEW RULE LIST. CORRECT RULLIST FILE

Explanation: The new rules could not be loaded, probably because invalid data was found in the rule order list file specified in the RULLIST file.

The simulation terminates.

Corrective Action: Correct the RULLIST file and rerun the CTTCRSS simulation utility.

CTT961E {DATA | INDEX} RECORD DOES NOT HAVE MATCHING {INDEX | DATA} RECORD RECTYPE=`type`

Explanation: The CTTIDB utility detected a data or index record in the Media Database (MDB) with no corresponding index or data record. Each data record should have a corresponding index record pointing to it, and each index record should point to a data record.

This message is issued with message CTT724I, which provides additional information about the problem record (volser, rba, and optionally, label, and data set).

The utility continues processing.

Corrective Action: If this problem occurs many times, rebuild the index using the CTTBIX utility.

CTT963E INDEX RECORD DIFFERS FROM DATA

Explanation: The CTTIDB utility detected a data record whose index fields do not match the key of the index record which is pointing to the data record.

This message is issued with messages CTT202I and CTT724I. Message CTT202I indicates the differences between the data record index fields and the key fields of the index record. Message CTT724I provides additional information about the problem record (volser, rba, and optionally, label and data set).

The utility continues processing.

Corrective Action: If this problem occurs many times, rebuild the index using the CTTBIX utility.

CTT964E SPECIFIED VOLUME NUMBER (DDSVOLS#=`num1`) DIFFERS FROM NUMBER OF L INDEX (`num2`)

Explanation: The CTTIDB utility detected that the number of volumes (num1) specified in DDSVOLS# does not equal the L index count (num2). These two values should be equal. DDSVOLS# is the data set data record field that contains the number of volsers on which the data set resides. Each of these volsers should have an L index record in the Index file.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and (optionally) label and data set).

The utility continues processing.

Corrective Action: If this problem occurs many times, rebuild the index using the CTTBIX utility.

CTT967E SPECIFIED LAST DATASET VOLUME RECORD (`num1`) DIFFERS FROM LABEL OF LAST DATASET (`num2`)

Explanation: The CTTIDB utility detected a volume record whose specified number of data sets (num1) is not equal to its highest data set sequence number (num2). These values should be the same.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally, its label).

The utility continues processing.

Corrective Action: Correct the problem manually using the CTTMUP utility. If the problem persists, see the INCONTROL for z/OS Utilities Guide.

CTT968E SPECIFIED NUMBER OF ACTIVE DATSETS (`num1`) IN VOLUME RECORD DIFFERS FROM DATASET COUNT (`num2`)

Explanation: The CTTIDB utility detected a volume record whose specified number of active data sets (num1) is not equal to the actual number of data sets counted (num2). These values should be the same.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally, its label).

The utility continues processing.

Corrective Action: Correct the problem manually using the CTTMUP utility. If the problem persists, see the INCONTROL for z/OS Utilities Guide.

CTT969E RECORD REFERS TO A WRONG VOLUME. TYPE=`type`

Explanation: A Control-M/Tape utility received a record other than the specific volume record that was expected. The record received either belonged to a different volume or was not a volume record.

The utility continues processing.

Corrective Action: Do the following:

Use the CTTIDB utility to list all errors in the Media database.
Use the CTTMUP utility to correct all errors found by the CTTIDB utility.

CTT972E VOLUME `vol` NOT FIRST BUT HAS AN ADDITIONAL VAULT RECORD

Explanation: The CTTIDB utility detected a volume data record that is not the first volume in a multivolume data set, but has an additional vault record associated with it. Only the first volume in a multivolume chain should have an additional vault record associated with it.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally its label).

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT973E SPECIFIED NUMBER OF DATASET VOLUMES (`num1`) DIFFERS FROM VOLUME COUNT (`num2`)

Explanation: The CTTIDB utility detected a data set data record whose specified number of volumes (num1) does not equal its actual number of associated volumes (num2). These values should be the same.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally, its label).

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT975E VOLUME `vol` IS NOT SCRATCHED AND NOT ACTIVE

Explanation: The CTTIDB utility detected a volume data record which is not scratched, deleted, or active. A volume status should be ACTIVE, SCRATCH, or DELETED.

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT976E VOLUME `volser` IS SCRATCH BUT DATASET ON LABEL `num` IS ACTIVE

Explanation: A Control-M/Tape utility detected a SCRATCH volume (volser) that contains an ACTIVE data set. All the data sets on a SCRATCH volume should be SCRATCH. This situation is probably a result of a job abend or a system crash.

The utility continues processing.

Corrective Action: Determine whether the data set and the volume should be SCRATCH or ACTIVE, and change status accordingly using the CTTMUP utility.

CTT977E `status1` VOLUME `volser` IS INCONSISTENT WITH `status2` FIRST VOLUME `first_vol`

Explanation: A Control-M/Tape utility detected a chained volume (volser) with a status different from the status of the first volume for this multivolume chain. This situation is probably a result of a job abend or a system crash. All data sets and volumes of a multivolume chain must have the same status.

The variables in this message are:

status1 -- Status of the detected volume in error.
volser -- Volume serial number of the volume in error.
status2 -- Status of the first volume in the multi volume chain.
first_vol -- Volume serial number of the first volume in the multivolume chain.

The utility continues processing.

Corrective Action: Determine the correct status for the volumes in this multivolume chain, and update the volumes and data sets of the group accordingly, using the CTTMUP utility.

CTT980E RBA `rba`: INVALID RECORD TYPE: `rcrd_type`

Explanation: A Control-M/Tape utility detected a Media Database record with an invalid record type.

The variables in this message are:

rba - the record RBA
rcrd_type - the invalid type

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT982E RBA `rba` : ACTIVEDS(`num`) IS HIGHER THAN LBLNUM (`lbl_num`) OF VOLUME

Explanation: A Control-M/Tape utility detected a logical error in a volume record. The value in the ACTIVEDS field cannot be greater than the value in the LBLNUM field.

The variables in this message are:

rba - Volume record RBA.
num - The number of active data sets on the volume.
lbl_num - The highest label (file sequence number) in use on the volume.

Information message CTT999I, which describes the record in error, is issued with this message.

The utility continues processing.

Corrective Action: Do the following:

Determine the correct values for ACTIVEDS and LBLNUM.
Use the VOLUPD function of the CTTMUP utility to set correct values for ACTIVEDS and/or LBLNUM fields.

The utility continues processing.

See message CTT999I for the volser of the volume in error. If the index record (KEY) is missing, use the VOLBIX function of the CTTMUP utility to build an index for the volume. If the data record is missing, use the VOLADD function of the CTTMUP utility to add the missing volume record.

CTT997E RBA `rba` : I/O ERROR WHILE TRYING TO READ VOLUME: `vol`

Explanation: A Control-M/Tape utility encountered an I/O error while trying to read the volume record of the specified volume. In this message, rba is the RBA of the volume record of the specified volume.

This message is accompanied by message CTT200S, which provides information on the nature of the I/O error.

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT998E RBA `rba` : DSN `num` IS ACTIVE, BUT VOLUME `vol` IS SCRATCH

Explanation: A Control-M/Tape utility detected a SCRATCH volume with an ACTIVE data set. n is the data set label. In this message rba is the RBA of the data set record. A SCRATCH volume cannot contain ACTIVE data sets.

Information message CTT999I, which describes the record in error, accompanies this message.

The utility continues processing.

Corrective Action: Determine if the data set and the volume should be SCRATCH or ACTIVE. Then depending on the results, do one of the following:

Change volume status (VOLSTAT) to ACTIVE using the VOLUPD function of the CTTMUP utility.
Change the data set status (DSSTAT) to SCRATCH using the DSNUPD function of the CTTMUP utility.

CTT999I `rcrd_desc`

Explanation: This information message describes a DATA or INDEX record in error. The nature of the error is described in the previous message.

Possible values for rcrd_desc are set out in the following table:

rcrd_desc value	Explanation
In the case of a data record:
D `dsnvolserlbl`	All fields are taken from the data set record, where: dsn is the data set name volser is the volser on which the data set starts lbl is the data set label
V volser SEQ: num [FIRST: first_vol ] [PREV: prev_vol ] [NEXT: next_vol]	All fields are taken from the volume record, where: volser is the volser of the volume num is the volume sequence number in its multivolume chain first_vol is the volser of the first volume in the multivolume chain prev_vol is the previous volume in the multivolume chain next_vol is the next volume in the multivolume chain Fields (first_vol, prev_vol, and next_vol) that are empty in the volume record do not appear in text of this message.
T volser	A volume continuation record, where `volser` is the volser of this volume continuation record.
B `boxIdmedia num`	A box record, where: `boxId` is the name of the box `media` is the media of the box. `num` is the box record count in the Media Database
In the case of an index record:
K D `dsn`	Index to a data set record, where `dsn` is the data set name.
K V `volser`	Index to a volume record, where `volser` is volser of the volume.
K L `volser lbl`	L-type index, where: `volser` is the volser of the data set `lbl` is the data set label (file sequence number)
K T `volser`	Index to a volume continuation record, where `volser` is the volser of the volume.
K A `vault`	Vault index, where `vault` is the vault name.
K C `hex_contents`	Index to a control record, where `hex_contents` are the contents of the key in hexadecimal format.
K B `boxIdmedia num`	Index to a box record, where: `boxId` is the box name `media` is the media of the box `num` is the box record count in the Media Database

Possible values for DATA rcrd_desc are:

D dsnvolserlbl All fields are taken from the data set record, where:
dsn is the data set name
volser is the volser on which the data set starts
lbl is the data set label
V volser SEQ: num [FIRST: first_vol] [PREV: prev_vol] [NEXT: next_vol]All fields are taken from the volume record, where:
volser is the volser of the volume
num is the volume sequence number in its multivolume chain
first_vol is the volser of the first volume in the multivolume chain
prev_vol is the previous volume in the multivolume chain
next_vol is the next volume in the multivolume chain

Fields (FIRSTVOL, NEXTVOL, and PREVVOL) that are empty in the volume record do not appear in text of this message.

T volser A volume continuation record, where volser is the volser of this volume continuation record.
B boxIdmedia num A box record, where:
boxId is the name of the box.
media is the media of the box.
num is the box record count in the Media Database

Possible values for INDEX rcrd_desc are:

K D dsn Index to a data set record, where dsn is the data set name.
K V volser Index to a volume record, where volser is volser of the volume.
K L volser lbl L-type index, where:
volser is the volser of the data set
lbl is the data set label (file sequence number)
K T volser Index to a volume continuation record, where volser is the volser of the volume.
K A vault Vault index, where vault is the vault name.
K C hex_contents Index to a control record, where hex_contents are the contents of the key in hexadecimal format.
K B boxIdmedia num Index to a box record, where:
boxId is the box name
media is the media of the box
num is the box record count in the Media Database

Corrective Action: No action is required.

Messages CTTA00 through CTTAxx

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

CTTA55E TASK IS NOT APF AUTHORIZED

Explanation: A started task (STC) requiring APF authorization was not APF authorized. Certain STCs (for example, CTMVMON) must be run from APF authorized libraries.

The task stops after issuing the error message.

Corrective Action: Change the JCL or authorize the library so that the STC will be run from an authorized library.

Messages CTTB00 through CTTBxx

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

CTTB00I CTTSBD PROCESSING COMPLETED|STOPPED, MODE=NORMAL|SIMULATION, REASON=`rsn`

Explanation: This information message indicates that the current run of the CTTSBD utility was either completed or stopped. The reason for stopping the current run of the utility is one of the following:

PROCESSED ALL SELECTED VOLUMES - The utility finished processing the selected volumes and ended normally.
OPERATOR REQUEST - The utility was ended in response to an operator command issued by the user.
EXCEEDED ALLOWED NUMBER OF FAILURES (MAXERR=) - More than a specified maximum number of recoverable errors were detected.
FREED REQUESTED NUMBER OF VOLUMES (NUMVOL=) - The utility freed a specified a maximum number of volumes.
REACHED THE ALLOTTED AMOUNT OF TIME - A specified time limit was reached.
INTERNAL ERROR - The utility ended due to an internal error.

The utility stops execution.

Corrective Action: The action depends on the value of rsn, as follows:

If rsn is EXCEEDED ALLOWED NUMBER OF FAILURES (MAXERR), search for other messages that describe the specific errors detected, and make all necessary corrections.
If rsn is INTERNAL ERROR, contact BMC Customer Support.
All other reasons do not require any action.

CTTB02E INPUT VERB INVALID OR OUT OF ORDER

Explanation: The CTTSBD utility encountered an invalid input statement or an input statement that was not in the expected order.

The utility stops execution.

Corrective Action: Check the input to the utility, correct the statement in error, and rerun the utility.

CTTB03E UNRECOGNIZED KEYWORD: `parm`

Explanation: An invalid parameter was specified in the input for the CTTSBD utility.

The utility stops execution.

Corrective Action: Check the input to the utility, correct or replace the invalid parameter, and rerun the utility.

CTTB04E ERROR IN KEYWORD: `parm`

Explanation: An inappropriate value was specified for the parm parameter in the input for the CTTSBD utility.

The utility stops execution.

Corrective Action: Check the input to the utility, correct the parameter in error, and rerun the utility.

CTTB05E OPEN FAILED FOR DDNAME: `ddName`

Explanation: The CTTSBD utility was unable to open the ddName file during this run.

The utility stops execution.

Corrective Action: Check the JCL used to execute the CTTSBD utility and verify that all files used by the CTTSBD utility are allocated properly.

CTTB06E ATTACH/LOAD OF SUBTASK/MODULE: `modName` FAILED

Explanation: The modName module or subtask of the CTTSBD utility could not be activated.

The utility stops execution.

Corrective Action: Verify that the appropriate LINKLIST and STEPLIB libraries are available to the CTTSBD utility, and that a sufficient region size is allocated for the utility.

CTTB07E MISSING CONTINUATION RECORD

Explanation: A syntax error was found in a multiline statement in the input for the CTTSBD utility. A continuation record was not found where expected.

The utility stops execution.

Corrective Action: Check the input to the CTTSBD utility, correct the statement in error, and rerun the utility.

CTTB08E UNABLE TO OBTAIN VIRTUAL STORAGE

Explanation: The CTTSBD utility could not run due to insufficient storage (memory).

The utility stops execution.

Corrective Action: Ensure that sufficient virtual storage is available for CTTSBD execution.

CTTB09E STATEMENT OUT OF ORDER

Explanation: A syntax error was found in the member containing data set group definitions for the CTTSBD utility. This message is issued when a member containing data set group definitions does not start with a GROUP statement.

The utility stops execution.

Corrective Action: Check and correct the data set group definition member referenced by the CTTSBGRP DD statement, and rerun the CTTSBD utility.

CTTB10E CTTSBD INTERNAL ERROR: `mod-func`

Explanation: An internal error was detected in the mod module and func function of the CTTSBD utility.

The utility stops execution.

Corrective Action: Contact BMC Customer Support. Supply the text of this message, and prepare a copy of the JCL used to execute the CTTSBD utility and any output (including the dump) that were produced by this run of the utility.

CTTB11E LOAD OF CONTROL-M/TAPE CONTROL TABLE (TCT) FAILED

Explanation: The CTTSBD utility was unable to locate the Control-M/Tape Control Table. Control-M/Tape is not active. The CTTSBD utility can run only when Control-M/Tape is active.

The utility stops execution.

Corrective Action: Start Control-M/Tape and rerun the utility.

CTTB13I CTTSBD REACHED SPECIFIED TIME LIMIT - PROCEEDING TO COMPLETE CURRENT INPUT VOLUME CHAIN

Explanation: This information message indicates that the CTTSBD utility has been running for the maximum amount of time specified in the TIMELIM parameter.

The utility finishes processing the INPUT volume chain of the current data set and then shuts down.

Corrective Action: No action is required.

CTTB14I CTTSBD SHUTDOWN REQUESTED BY OPERATOR - PROCEEDING TO COMPLETE CURRENT INPUT VOLUME CHAIN

Explanation: This information message indicates that an operator command requested shut down of the CTTSBD utility.

The utility finishes processing the current volume chain and then shuts down.

Corrective Action: No action is required.

CTTB15E CANNOT EXECUTE WITH MODE=NORMAL WHEN CONTROL-M/TAPE IS NOT ACTIVE

Explanation: An attempt to run the CTTSBD utility in NORMAL mode when Control-M/Tape was not active failed. The CTTSBD utility can run in NORMAL mode only when Control-M/Tape is active. If Control-M/Tape is not active, the utility can only be run in SIMULATION mode.

The CTTSBD utility is not run.

Corrective Action: Either run the utility in SIMULATION mode, or activate Control-M/Tape before attempting to rerun the CTTSBD utility.

CTTB16E VOLUME `volser` : MDB VOLUME|DATASET RECORD(S) NOT FOUND. CHAIN PROCESSING STOPPED

Explanation: The CTTSBD utility was unable to locate volume and/or data set records for the specified volser. This volume cannot be processed by the CTTSBD utility.

The CTTSBD utility stops processing the current volume chain and continues with the first data set in the next volume chain.

Corrective Action: No action is required.

CTTB19W CHAIN STOPPED: VOL=`volser` DSN=`dsName` REASON=`rsn`

Explanation: The CTTSBD utility was unable to process the specified input data set. The possible values for rsn and the appropriate action to take for each are listed in the User Response section of this message.

The CTTSBD utility stops processing the current volume chain and continues with the first data set in the next volume chain.

Corrective Action: The action to be taken depends on the reason specified in the message, as follows:

REASON rsn and Explanation	User Response
FAILURE IN DATASET PROCESSING
The utility was unable to copy the specified data set.	Check other messages and events issued by this run of the CTTSBD utility and by the operating system to determine if the problem can be corrected. After the problem is fixed, a subsequent run of the CTTSBD utility can be used to stack the data set.
VOLUME RECORD CHANGED
The Media Database record for the first volume of an input volume chain was modified between the time it was selected and the time the first data set residing on this chain was copied.	To stack the data sets on this input volume chain, rerun the utility. Ensure that the volume or volume record is not accessed by another application during the execution of the CTTSBD utility.
CYCLE RETENTION
The specified data set has a CYCLE retention type. To minimize interference with retention of other data sets, the CTTSBD utility does not process data sets with CYCLE type retention.	The specified data set cannot be processed by the CTTSBD utility. If necessary, copy this data set using other means.
INVALID DATA IN MDB
The CTTSBD utility encountered invalid information in Media Database records for the specified volume and/or data set. (This type of problem is most often a result of conversion from another tape management system.)	Correct the records in error through the Control-M/Tape Inquire/Update screen (TI) or the CTTMUP utility. After the Media Database records have been corrected, rerun the CTTSBD utility on the abandoned volume chain.

CTTB20E UNABLE TO ALLOCATE D=`dsName` V=`volser` U=`unitName` DD=`ddName` RC=`rc` RSN=`rsn`

Explanation: The CTTSBD utility could not dynamically allocate the specified data set. This error may be due to a mismatch between the selected volume and the unit names specified by the INUNIT and OUTUNIT CTTSBD parameters, or to the unavailability of drives of the requested type.

See the appropriate IBM manual containing reason codes for dynamic allocation (SVC 99).

The CTTSBD utility stops processing the current volume chain and continues with the first data set in the next volume chain.

Corrective Action: Either modify the values for the INUNIT and OUTUNIT parameters, or ensure that more drives are available during the subsequent runs of the CTTSBD utility.

CTTB21I UNABLE TO COMPLETE RECOVERY, PROCESSING STOPPED

Explanation: This information message indicates that automatic recovery attempted by the CTTSBD utility abended. During automatic recovery, the CTTSBD utility attempts to recatalog the last data set that was uncataloged. This cataloging operation failed.

This message is preceded by message CTTB29E, which contains the name of the data set that could not be cataloged.

The CTTSBD utility stops execution.

Corrective Action: Recatalog the data set specified in message CTTB29E, and rerun the CTTSBD utility.

CTTB22E UTILITY {IEBGENER | ADRDSSU} ENDED WITH RC=`rsn`

Explanation: The specified IBM utility detected an error.

In this message, rsn is an IBM code that indicates the reason for the error.

The utility terminates.

Corrective Action: Consult IBM documentation for the specified utility to determine the reason for the IBM code rsn and the recommended action, if any.

CTTB23A REQUESTED {INPUT | OUTPUT} VOLUME=`volser` NOT AVAILABLE. PLEASE REPLY C(ANCEL) OR W(AIT)

Explanation: This information message indicates that the CTTSBD utility could not allocate an input or output volume that was already in use or not available. In this message volser is the volume serial number of the unavailable volume

The utility waits for a reply.

Corrective Action: Enter C for Cancel or W for Wait, as follows:

C -- The CTTSBD utility terminates.
W -- The utility waits three minutes and attempts to allocate the requested volume again.

CTTB25E NO INCLUDE STATEMENT FOUND ON SYSIN

Explanation: No INCLUDE statement was specified for the current run of the CTTSBD utility. At least one INCLUDE statement must be specified.

The CTTSBD utility stops execution.

Corrective Action: Specify one or more INCLUDE statements for the CTTSBD utility and rerun the utility.

CTTB26E INVALID INFORMATION RECEIVED FROM CTTX011 = `rc`

Explanation: Control-M/Tape Exit 11 returned an invalid return code to the CTTSBD utility. Exit 11 is expected to return a 1-character code to the utility, which affects the choice of output volume for the current data set. The code returned for the current data set is not recognized by the utility.

The utility stops execution.

Corrective Action: Check and correct the source code in Exit 11 and rerun the CTTSBD utility.

CTTB27E CHAIN PROCESSING STOPPED. OUT DSN EXCEEDS 44 CHARS D=`dsn`

Explanation: The specified output data set has a name that is more than 44 characters in length. A prefix and/or a suffix can be specified for output data set name by means of the OUTPREF and OUTSUFF parameters of the CTTSBD utility. When the prefix and or the suffix was added to the name of the specified data set, the new data set name exceeded the 44-character limit.

In this message, dsn is the output data set name that exceeds the 44-character limit.

The CTTSBD utility stops processing the current volume chain and continues with the first data set in the next selected volume chain.

Corrective Action: Change the settings for the OUTPREF or OUTSUFF parameters and rerun the CTTSBD utility to stack data sets on the volume chain that was abandoned due to this error.

CTTB28E UNABLE TO UNCATALOG DATASET DSNAME=`dsn`

Explanation: The CTTSBD utility was unable to uncatalog the specified input data set. The CTTSBD utility must uncatalog the input data set before cataloging an output data set with the same name.

Common causes of this error include

insufficient authorization for the user who ran the utility
an I/O error

The CTTSBD utility stops processing the current volume chain and continues with the first data set in the next selected volume chain.

Corrective Action: Check the catalog entry for the problem data set, consider any related issues (for example, security), and if necessary correct the problem. It is also recommended that you search the console log for other messages that may be related to this problem.

CTTB29E UNABLE TO CATALOG DATASET DSNAME=`dsn`

Explanation: The CTTSBD utility was unable to catalog the specified output data set.

Common causes of this error include

insufficient authorization for the user who ran the utility
an I/O error

The utility stops execution.

Corrective Action: Check the catalog entry for the problem data set and correct it if necessary. It is also recommended that you search the console log for other messages that may be related to this problem.

CTTB30A DEVICE FOR {INPUT | OUTPUT} VOLUME=`volser` NOT AVAILABLE, PLEASE REPLY C(ANCEL) OR W(AIT)

Explanation: The device required to access volume volser is not available. The CTTSBD utility must access the specified volume for input or output, as specified. However, no device is available on which to mount the specified volume.

The system waits for a response.

Corrective Action: Do one of the following:

Enter C to cancel device allocation and to end the run of the CTTSBD utility.
Enter W to make the utility wait three minutes before trying again to allocate the required device.

Messages CTTC00 through CTTCxx

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

CTTC01E CURRENT TMS IS INVALID

Explanation: An invalid or unsupported tape management system name was specified in the Automated Conversion Step Entry panel, the first screen of the Control-M/Tape automated conversion steps. Automatic conversion is a series of steps, which converts tape management data from another system into Control-M/Tape data format. Valid tape management system names are: CA1, TLMS, RMM, EPIC and CATALOG.

The conversion program waits for a correction to the specified value.

Corrective Action: Specify a valid tape management system name and retry.

CTTC02E INVALID LEVEL. VALID LEVELS FOR CA1 ARE: 4.9, 5.0, 5.1 AND 5.2

Explanation: An invalid or unsupported level was specified for CA-1 in the automatic conversion screen. Valid level values for the CA-1 tape management system: 4.9, 5.0, 5.1, and 5.2.

The conversion program waits for a correction to the specified value.

Corrective Action: Specify a valid level for the CA-1 tape management system and retry.

CTTC03E INVALID LEVEL. VALID LEVELS FOR CA-TLMS ARE: 5.3 AND 5.4

Explanation: An invalid or unsupported level was specified for CA-TLMS in the automatic conversion screen. Valid values for the CA-TLMS tape management system: 5.3 and 5.4

The conversion program waits for a correction to the specified value.

Corrective Action: Specify a valid level for the CA-TLMS tape management system and retry.

CTTC04E INVALID LEVEL. VALID LEVELS FOR EPIC ARE: 3.1, 3.2 AND 3.3

Explanation: An invalid or unsupported level was specified for CA-EPIC/MVS in the automatic conversion screen. Valid values for the CA-EPIC/MVS tape management system: 3.1, 3.2, and 3.3.

The conversion program waits for a correction to the specified value.

Corrective Action: Specify a valid level for the CA-EPIC/MVS tape management system and retry.

CTTC05E LIBRARY/DATASET NOT FOUND

Explanation: A library or data set name that is not found in the MVS CATALOG was specified. The library or the data set name is either misspelled or not cataloged.

The conversion program waits for a correction to the specified data set or library name.

Corrective Action: Specify the cataloged library or data set name correctly and retry.

CTTC06E MEMBER NOT FOUND

Explanation: The member name specified cannot be found in the specified library. The library name or the member name, or both, are incorrect.

The conversion program waits for a correction to the specified library or member name.

Corrective Action: Correct the library name and the member name, and retry.

CTTC07E UNDEFINED OPTION CODE

Explanation: An option that is not supported in the current screen of the Control-M/Tape automatic conversion program was specified. The current screen lists the valid options.

The conversion program waits for specification of a valid option.

Corrective Action: Specify a valid option and retry.

CTTC08E AT LEAST ONE VOLUME RANGE MUST BE DEFINED

Explanation: There was an attempt to delete the last remaining range in the volume range table. The volume range table lists ranges of volumes that should be handled during conversion of tape management data to Control-M/Tape format. At least one volume range must be defined.

The volume range is not deleted.

Corrective Action: Define the correct volume range and then delete the existing volume range.

CTTC09E FROM VOLUME CANNOT BE HIGHER THAN TO VOLUME

Explanation: The current volume range definition contains a FROM value that is higher than its TO value. The TO volser (volume serial number) must not be less than the FROM volser.

The conversion program waits for a correction to the invalid range specification.

Corrective Action: Specify a valid volume range and retry.

CTTC10E REPORT CANNOT BE PROCESSED. MAKE SURE IT WAS SUCCESSFULLY PRODUCED

Explanation: The report that was produced as input to the automated conversion cannot be processed, because it was either empty or in an invalid format. To convert from a different tape management system to Control-M/Tape, a report is produced in the previous tape management environment. After the user confirms that it was successfully produced, the report is used as input to the conversion program.

The conversion program waits for the user to confirm that a report is successfully produced.

Corrective Action: Either produce a new report or wait for the report job to complete and confirm that it was successfully produced.

CTTCBR00 CONTROL-M/TAPE REAL-TIME ENVIRONMENT IS NOT ACTIVE.

Explanation: This message is issued by exit CBRUXVNL when a Control-M/Tape real-time environment is not found.

Waits for one of the replies listed in message CTTCBR12.

Corrective Action: Reply to message CTTCBR12.

CTTCBR01 ACCDB FUNC: `func` FOR VOL: `volser` FAILED. RC= `rc`

Explanation: The high level API of Control-M/Tape (macro CTTACCDB) failed to perform function func for volume volser. The return code is rc.

The specified volume is not processed.

Corrective Action: See the CTTACCDB macro in the Control-M/Tape chapter of the INCONTROL for z/OS Administrator Guide for more information.

CTTCBR02 LAST IOS FUNC: `func`, IOS RC=`rc`, IOS RSN=`rsn`

Explanation: The specified function for the MDB failed. This message follows message CTTCBR01, if the problem is in an operation that modifies the MDB.

The variables in this message are:

func - the function that failed
rc - the return code of the error
rsn - the reason code of the error

Corrective Action: Refer to the CTT200S message for a description of the return code (rc) and reason code (rsn).

CTTCBR03 VOLUME: `volser` NOT FOUND IN MDB. VOL IS MARKED PRIVATE

Explanation: This message is issued by exit CBRUXENT when a volume that is not known to Control-M/Tape enters the automated tape library. The volume serial number of the unknown volume is volser.

Processing continues. The volume is marked PRIVATE in the robotic library database.

Corrective Action: No action is required.

CTTCBR04 VOLUME: `volser` NOT FOUND IN MDB. UPDATE NOT PERFORMED

Explanation: This message is issued by exit CBRUXEJC when a volume that is not known to Control-M/Tape is ejected from the robotic library. The volume serial number of the unknown volume is volser.

Processing continues. The MDB is not updated.

Corrective Action: No action is required.

CTTCBR05 VOLUME: `volser` NOT FOUND IN MDB. CHANGE IS ALLOWED

Explanation: This message is issued by Exit CBRUXCUA when an attempt is made to change the status of a volume that is not known to Control-M/Tape. The volume serial number of the unknown volume is volser.

Processing continues. The status of the volume is changed in the robotic library.

Corrective Action: No action is required.

CTTCBR06 VOLUME: `volser` STATUS CHANGE DENIED BY CONTROL-M/TAPE EXIT

Explanation: This message is issued by Exit CBRUXCUA when an attempt is made to change the status of a volume and the new status contradicts with the status in the Control-M/Tape MDB.

The status of the volume is not changed.

Corrective Action: Check the volume status in the MDB. If appropriate, change the volume status in the MDB using the Control-M/Tape interface. The robotic library will be automatically notified of the change.

CTTCBR07 LINK OF EXIT `exitName` SUCCESSFUL

Explanation: A Control-M/Tape exit successfully linked a similar exit of another tape management system that runs parallel to Control-M/Tape.

Corrective Action: No action is required.

CTTCBR08 LINK OF EXIT `exitName` FAILED

Explanation: A Control-M/Tape exit failed to link a similar exit of another tape management system (TMS) that runs parallel to Control-M/Tape. When Control-M/Tape runs in TEST mode parallel to another TMS, Control-M/Tape interface exits attempt to pass control to similar exits of the other TMS.

Corrective Action: Verify that the STEPLIB or LINKLIST library of the job contains the specified exit. If the exit is in one of these libraries, refer to the messages guide for that exit.

CTTCBR09 VOLUME: `volser` NOT FOUND IN MDB. CANNOT LOCATE IT. PLEASE RESPOND TO CTTCBR12 MESSAGE

Explanation: This message is issued by exit CBRUXVNL when a mount message is issued for a volume that is not in the robotic library and is also unknown to Control-M/Tape.

Waits for one of the replies listed in message CTTCBR12.

Corrective Action: Reply to message CTTCBR12.

CTTCBR10 VOLUME: `volser` NOT IN LIBRARY. LOCATION: `loc` PLEASE RESPOND TO CTTCBR12 MESSAGE

Explanation: This message is issued by exit CBRUXVNL when a mount message is issued for a volume which is not in the robotic library. The message specifies the location of the volume as recorded in the Control-M/Tape database.

Waits for one of the replies listed in message CTTCBR12.

Corrective Action: Reply to message CTTCBR12.

CTTCBR11 VOLUME: `volser` NOT IN LIBRARY ALTHOUGH MARKED AS IN LIBRARY: `lib`. PLEASE RESPOND TO CTTCBR12 MESSAGE

Explanation: This message is issued by exit CBRUXVNL when a mount message is issued for a volume that should be in the robotic library based on data recorded in the Control-M/Tape MDB, but actually is not in the robotic library.

Waits for one of the replies listed in message CTTCBR12.

Corrective Action: Reply to message CTTCBR12.

CTTCBR12 VOLUME: `volser`. REPLY R-RETRY, I-IGNORE, C-CANCEL

Explanation: This message is issued by exit CBRUXVNL when a mount message is issued for a volume that is not in the robotic library. This message follows message CTTCBR09, CTTCBT10, or CTTCBR11.

Waits for user reply.

Corrective Action: Reply with one of the following options:

R -- The volume was manually inserted in the robotic library. The system will again to find the volume in the robotic library.
I -- The system will issue the mount message on a unit other than the robotic library.
C -- The system will cancel the mount volume request and the job will abend.

CTTCBR13 VOLUME: `volser` NOT FOUND IN MDB. VOLUME IS IGNORED

Explanation: This message is issued by exit CBRUXENT when volume volser, which is unknown to Control-M/Tape, is inserted in the robotic library.

The volume status in the robotic library is not initialized by the exit.

Corrective Action: No action is required.

CTTCBR14 VOLUME: `volser` IS CURRENTLY IN EJECT PROCESS. PLEASE RESPOND TO CTTCBR12 MESSAGE

Explanation: This message is issued by exit CBRUXVNL when a mount message is issued for a volume that is currently in eject process from the automated tape library.

Waits for one of the replies listed in message CTTCBR12.

Corrective Action: Reply to message CTTCBR12.

CTTCBR15 VOLUME: `volser` IS MARKED AS DELETED. VOLUME IS EJECTED

Explanation: This message is issued by exit CBRUXENT when volume volser, which is marked for deletion in the Control-M/Tape MDB, is inserted in the robotic library.

The volume is ejected from the robotic library.

Corrective Action: No action is required.

Messages CTTE00 through CTTExx

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

CTTE15S INSUFFICIENT STORAGE. INCREASE SIZE

Explanation: Insufficient memory to perform the task.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter, or exit one of the screens using an END command.

CTTE29S UNABLE TO LOAD MODULE `modName`

Explanation: Loading of the modName module failed. Possible causes are:

The IOA Load library is not in the load modules search list.
There is insufficient storage available to load the module.
The modName module does not exist in the IOA Load library.
The IOA Load library was updated while you were working and the position of the modName module has changed.

The function requested is terminated.

Corrective Action: Look on the system log for additional messages that clarify the problem. Suggested actions:

If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
If the loading failed due to lack of storage then for batch jobs, increase the REGION size, and 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 can release storage that is used by the screens.
Add the modName module to the Load library.
If the IOA Load library was 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. If the IOA Load library is in the Linklist, a refresh to the LLA is needed.

CTTEDM0 `volser` FUNC=`func` RC=`rc` RSN=`rsn` URC=`ursn` FROM CTTAPI

Explanation: The Control-M/Tape interface to the EDM software used CTTAPI to scratch the volser in the Media Database, but CTTAPI ended with an error.

The specified volume is not expired.

Corrective Action: Refer to message CTT203E to understand the explanation for the return codes from CTTAPI.

Check the specified volume status in the Media Database, and if required, expire it online or by means of the CTTMUP utility.

CTTEDM0 {ATTACH | LINK} OF EXIT `exitName` SUCCESSFUL

Explanation: This information message indicates that the exitName exit was successfully activated. The Control-M/Tape interface to EDM software can call another exit after completion of the expiration process, probably an interface to another tape management system or a second Control-M/Tape version.

Corrective Action: No action is required.

CTTEDM0 {ATTACH | LINK} OF EXIT `exitName` FAILED

Explanation: Activation of the exitName exit failed. The Control-M/Tape interface to EDM software can call another exit after completion of the expiration process, probably an interface to another tape management system or a second Control-M/Tape version.

The specified exitName exit is not activated.

Corrective Action: When running two Control-M/Tape versions, verify that the exitName exit exists in the load library that is referenced by the parallel DD as described in Appendix D of the IOA Upgrade Guide. When not running two Control-M/Tape versions, verify that the STEPLIB or LINKLIST libraries contain the specified exitName exit. In addition, look for additional MVS errors messages in the job.

CTTEDM0 OPTION `opt` NOT SUPPORTED

Explanation: CA-Disk exit TMSCTLEX received an unrecognized option.

The Control-M/Tape interface to CA-Disk supports only the Volume Expire option, supplied as option number 1, of this exit. CA-Disk supplies a different option.

No operation is performed. The volume is not expired.

Corrective Action: No action is required.

Messages CTTF00 through CTTFxx

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

CTTF40I UTILITY CTTDBIB STARTED

Explanation: Normal start message of the Index file rebuilding the CTTDBIB utility.

Corrective Action: No action is required.

CTTF41E ERROR `err` AT LINE `line`. CURRENT STATEMENT: `stmt`

Explanation: The CTTDBIB utility failed during reading of the indicated input statement, from the data set pointed to by DD statement SYSIN.

The utility stops executing with a condition code of 08.

Corrective Action: Notify your INCONTROL administrator.

CTTF42I PROGRAM ENDED: `num` KEYS BUILT

Explanation: Normal termination message of the Index file rebuilding the CTTDBIB utility.

Corrective Action: No action is required.

CTTF43S ERROR OPENING SYSPRINT

Explanation: The CTTDBIB utility failed to open the print file pointed to by DD statement SYSPRINT. Possible causes are:

DD statement SYSPRINT is missing.
The data set pointed to by DD statement SYSPRINT cannot be accessed for sequential write.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTTF44E NO INPUT PARAMETERS. PROGRAM STOPPED

Explanation: The input file for the CTTDBIB utility is empty (DD statement SYSIN).

The utility stops executing with a condition code of 04.

Corrective Action: Fill in the input statements and rerun the job.

CTTF45S INTERNAL ERROR WHILE PROCESSING DDNAME `ddName`

Explanation: The CTTDBIB utility failed during processing of the data set pointed to by the specified DD name. This message is followed by message CTTF47S, which contains additional details about the error.

The utility stops executing with a non-zero condition code.

Corrective Action: Contact your INCONTROL administrator with the details displayed in this and the following message.

CTTF46S RETURN CODE `rc` FROM `routineName` ROUTINE, FUNCTION `func`

Explanation: The CTTDBIB utility failed while processing the data set pointed to by the DD name indicated in message CTTF46S, which precedes this message.

The utility stops executing with the indicated return code.

Corrective Action: Notify your INCONTROL administrator.

CTTF47S INSUFFICIENT STORAGE TO RUN UTILITY CTTDBIB

Explanation: The CTTDBIB utility requires more storage to rebuild an Index file.

The utility stops executing with a condition code of 12.

Corrective Action: Increase the REGION size and rerun the job.

CTTF48E INVALID BUILD KEY PARAMETER

Explanation: Invalid build key instructions were specified. Build key instructions are specified by means of the SYSIN DD statement. The key length parameter does not match the total length of the key fields.

The utility stops processing.

Corrective Action: Notify your INCONTROL administrator.

CTTF90S OPEN OF DDCARD `ddName` FAILED

Explanation: Open for the specified DD name pointing to the password member failed.

Possible causes are:

The DD statement is missing.
The file allocated to the DD statement is not a sequential file nor a member in a PDS.

Authorization to access the product is denied.

Corrective Action: Correct the JCL statement for the procedure or the allocations for the CLIST.

CTTF91S PASSWORD MEMBER TOO LARGE (DD `ddName`)

Explanation: The password member (or sequential data set) has too many lines.

The DD statement points to the password member.

Authorization to access the product is denied.

Corrective Action: Remove unnecessary lines from the member.

CTTF92S SYNTAX ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A syntax error was found in the password member. When this message is issued by the monitor, it is generally followed by message CTTF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTTF93S VALUE ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A field in the password member contains invalid data. When this message is issued by the monitor, it is generally followed by message CTTF9DS, which describes the erroneous line in the member.

The ddName DD statement points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

CTTF94S PASSWORD INVALID, PLEASE RECHECK PASSWORD MEMBER (DD `ddName`)

Explanation: Data in the password member was not consistent with the specified password.

The DD statement points to the password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from BMC Customer Support. If it checks, contact the representative.

CTTF95S PASSWORD FOR CONTROL-T IS ABOUT TO EXPIRE IN `num` DAYS

Explanation:Highlighted, unrollable message.

Password expiration period is about to end.

An expiration date is specified in the password member for the product.

Corrective Action: Contact BMC Customer Support for a new password.

CTTF96S PASSWORD FOR CONTROL-T HAS EXPIRED

Explanation:Highlighted, unrollable message.

Password expiration period has ended.

An expiration date is specified in the password member for the product.

Authorization to access the product is denied.

Corrective Action: Contact BMC Customer Support for a new password.

CTTF97S INTERNAL ERROR OCCURRED ON DD `ddName`. PLEASE NOTIFY THE IOA ADMINISTRATOR

Explanation: An internal error has occurred while analyzing the password member pointed to by the DD statement.

Authorization to access the product is denied.

Corrective Action: Notify the IOA administrator.

CTTF98S OBLIGATORY FIELD MISSING FROM PASSWORD MEMBER (DD `ddName`)

Explanation: An obligatory field is missing from a password member.

The DD statement points to the password member. The PROD, START, CPUID, PASS, and TYPE fields should appear at least once in a password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from your INCONTROL administrator.

CTTF9AS PASSWORD FOR CONTROL-T NOT DEFINED IN MEMBER (DD `ddName`)

Explanation: The member pointed to by the DD statement does not contain the password for the appropriate product.

The DD statement should point to the password member.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this product.

CTTF9BS AUTHORIZATION PERIOD HAS NOT STARTED YET (DD `ddName`)

Explanation: The start date of the password has not yet arrived.

The DD statement points to the password member. The START field contains the starting date of the password.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this period.

CTTF9CS CPUID/MODEL NOT FOUND IN AUTHORIZED CPU LIST (DD `ddName`)

Explanation: The current CPU is not defined in the CPU list.

The DD statement points to the password member. Each entry in the CPU list in the password member contains the CPUID of the CPU and its model.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this CPU.

CTTF9DS CARD = `text`

Explanation: This message supplies additional information for a previous error message.

This message may appear after message CTTF92S or CTTF93S which indicates an error has occurred in one of the lines of the password member. Message CTTF9DS displays the erroneous line.

Corrective Action: See messages CTTF92S or CTTF93S.

CTTF9ES PASSWORD DDCARD `ddName` POINTS TO A NON EXISTING MEMBER (ABEND S013-18)

Explanation: The DD statement is allocated to a nonexisting member in a PDS file.

The DD statement should point to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the name of the member in the DD statement or create a member with the specified name.

CTTF9FS PASSWORD FOR CONTROL-`x` EXPIRED, TEMPORARY AUTHORIZATION GRANTED

Explanation: The password for Control- x has expired. Nonetheless, Control-x can be run on the current date.

Despite password expiration, Control- x can be run on the 28th, 29th, 30th, 31st, 1st, 2nd, and 3rd days of each month for special purposes.

Control- x processing continues.

Corrective Action: Contact BMC Customer Support to obtain password renewal.

Messages CTTH00 through CTTHxx

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

CTTHAC01 ACCDB FUNC: `func` FOR VOL: `volser` FAILED. RC= `rc`

Explanation: The high level API of Control-M/Tape (macro CTTACCDB) failed to perform function func for volume volser. The return code is rc.

The specified volume is not processed.

Corrective Action: For more information, see the CTTACCDB macro in the Control-M/Tape chapter of the INCONTROL for z/OS Administrator Guide.

CTTHAC02 LAST IOS FUNC: `func`, IOS RC=`rc`, IOS RSN=`rsn`

Explanation: The specified function for the MDB failed. This message follows message CTTHAC01, if the problem is in an operation that modifies the MDB.

The variables in this message are:

func - the function that failed
rc - the return code of the error
rsn - the reason code of the error

Corrective Action: See the CTT200S message for a description of the return code (rc) and reason code (rsn).

CTTHC001E CONTROL-M/TAPE IS NOT FOUND.

Explanation: Control-M/Tape check running under IBM Health Checker did not find the major Control-M/Tape control block.

Corrective Action: Ensure that Control-M/Tape is active.

CTTHC002E CONTROL-M/TAPE CANNOT LOCATE AN EXIT ROUTINE FOR TLP EXIT `tlp_exit`. RC=`rc` RS=`rs`

Explanation: During initiation, Control-M/Tape installs its exit routines to TLP Exits. However, the Control-M/Tape check running under IBM Health Checker did not find its exit routine for the specified TLP Exit. Return code and reason code are provided for the CSVDYNEX request.

Corrective Action: Ensure that Control-M/Tape is active. In addition, ensure that the Control-M/Tape Exit routine is active for the specified exit. For more information, see Step 7, "MVS Tape Label Processing Exits installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC003E TLP EXIT `tlp_exit` HAS NO CONTROL-M/TAPE EXIT ROUTINE `exit_routine` ATTACHED

Explanation: During initiation, Control-M/Tape installs its exit routines to TLP Exits. However, the Control-M/Tape check running under IBM Health Checker did not find the specified Control-M/Tape exit routine attached to the specified TLP Exit.

Corrective Action: Ensure that Control-M/Tape is active. In addition, ensure that the Control-M/Tape Exit routine is active for the TLP Exit. For more information, see Step 7, "MVS Tape Label Processing Exits installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC004E CONTROL-M/TAPE EXIT ROUTINE `exit_routine` FOR `tlp_exit` TLP EXIT DISABLED

Explanation: During initiation, Control-M/Tape installs its exit routines to TLP Exits. However, the Control-M/Tape check running under IBM Health Checker found that the specified Control-M/Tape exit routine for the specified TLP Exit is disabled.

CTTHC005E CONTROL-M/TAPE DYNAMIC WTO INTERCEPT INACTIVE

Explanation: During initiation, Control-M/Tape installs its own WTO intercept for message modifying. However, the Control-M/Tape check running under IBM Health Checker found no active Control-M/Tape WTO intercept.

Corrective Action: Ensure that Control-M/Tape is active. For more information, see the description of the DYNWTO parameter in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC006E CONTROL-M/TAPE SVC `svc_num` NOT USED

Explanation: During initiation, Control-M/Tape installs its own SVC routine with the SVC number specified by the SVCNUM parameter. However, the Control-M/Tape check running under IBM Health Checker found no active SVC with this number.

Corrective Action: Ensure that Control-M/Tape is active. For more information, see Step 6, "Control-M/Tape SVC installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC007E CONTROL-M/TAPE SVC `svc_num` USED BY ANOTHER PRODUCT

CTTHSC01 ACCDB FUNC: `func` FOR VOL: `volser` FAILED. RC= `rc`

Explanation: The high level API of Control-M/Tape (macro CTTACCDB) failed to perform function func for volume volser. The return code is rc.

The specified volume is not processed.

Corrective Action: For more information, see the CTTACCDB macro in the Control-M/Tape chapter of the INCONTROL for z/OS Administrator Guide.

CTTHSC02 LAST IOS FUNC: `func`, IOS RC=`rc`, IOS RSN=`rsn`

Explanation: The specified function for the MDB failed. This message follows message CTTHSC01, if the problem is in an operation that modifies the MDB.

The variables in this message are:

func - the function that failed
rc - the return code of the error
rsn - the reason code of the error

Corrective Action: See the CTT200S message for a description of the return code (rc) and reason code (rsn).

CTTHSC04 VOLUME: `volser` NOT FOUND IN MDB. UPDATE NOT PERFORMED

Explanation: This message is issued by exit SLSUX06 when the volume ejected from the robotic library is unknown to Control-M/Tape.

Processing continues. The MDB is not updated.

Corrective Action: No action is required.

CTTHSC07 LINK OF EXIT `exitName` SUCCESSFUL

Explanation: A Control-M/Tape exit successfully linked a similar exit of another tape management system that runs parallel to Control-M/Tape.

Corrective Action: No action is required.

CTTHSC08 LINK OF EXIT `exitName` FAILED

Corrective Action: Verify that the STEPLIB or LINKLIST library of the job contains the specified exit exitName. If the exit is in one of these libraries, refer to the messages guide for the exit.

Messages CTTI00 through CTTIxx

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

CTTI00E RBA `rba1,` `rba2:` DUPLICATE {VOLUME | DATASET}

Explanation: The CTTIDB utility detected one of the following:

data records with the same volser in two volumes
data records with the same label number located on the same volume in two data sets
data records with the same label number located on the same multi-volume group in two data sets

In this message, rba1 and rba2 are the RBAs of these two records. This message is followed by two CTT999I information messages, which give the details about these duplicate data records.

Corrective Action: Delete one of the duplicate records by using the RECDEL statement of the CTTMUP utility, and then rebuild the equivalent index entries using the GRPBIX statement of the CTTMUP utility.

CTTI01E RBA `rba`: DUPLICATE {MDB | STK} `x`-INDEX FOUND

Explanation: The CTTIDB utility found a duplicate key in the index component of the Media database (MDB) or the Stacking database (STK). The record type and rba are reported in this message.

Corrective Action: Rebuild the relevant index file using the CTTBIX utility for the Media database or the CTTDBIB utility for Stacking database.

CTTI02E RBA `rba`: CHAIN ERROR: `err_desc`

Explanation: The CTTIDB utility detected an error in a multi-volume group. Information message CTT999I, which describes the record in error, is issued after this message. Many of the errors described by this message refer to the following fields in the volume record that hold information used to link a multi-volume group:

FIRSTVOL - the first volume of the multi-volume group
PREVVOL - the previous volser in the multi-volume group
NEXTVOL - the next volser in the multi-volume group
VOLSEQ - the volume sequence number

The variables in this message are:

rba - the RBA of a record of this multi-volume group
err_desc - text describing the type of group error

Corrective Action: The following table lists and explains the possible texts for the err_desc variable. Perform the corrective action as indicated.

Error Description and Explanation	Corrective Action
FIRST VOL IS NOT THE SAME IN ALL VOLS
The value in the FIRSTVOL field must be the same for each volume record of the multi-volume group. A volume record was detected with a different value in the FIRSTVOL field.	Determine whether the problem is the value of the FIRSTVOL field of this volume, or the NEXTVOL field of the previous volume in the chain. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error. Correct the indexes of the group using the GRPBIX function of the CTTMUP utility.
VOLUME IN BROKEN GROUP
The listed volume belongs to the multi-volume group, which is already recognized as broken.	Determine whether the volume belongs to a broken multi-volume chain. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error. Correct the indexes of the group using the GRPBIX function of the CTTMUP utility.
INVALID PREV/NEXT POINTER
The next or previous volume does not belong to this multi-volume group. The group is probably broken.	Determine whether the problem is the value of the NEXTVOL or PREVVOL fields. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error. Correct the indexes of the group using the GRPBIX function of the CTTMUP utility.
VOLUME OUT OF SEQUENCE
The volume sequence number should be greater by one than the sequence number of previous volume.	Determine whether the problem is the value of the VOLSEQ field. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error.
SCRATCH VOLUME IN THE ACTIVE CHAINACTIVE VOLUME IN THE SCRATCH CHAIN
In compatible MODE, all volumes from the same chain should have the same status (either ACTIVE or SCRATCH).	Determine whether all volumes from the same multi-volume group have the same status. Use the SCRATCH or EXTEND functions of the TI screen to correct this problem or the VOLSCR function of the CTTMUP utility.
INVALID NEXT POINTER IN THE LAST VOLUME
The last volume in the multi-volume chain should not have the NEXTVOL pointer.	Determine whether this volume is really the last volume in the group. Use the VOLUPD function of the CTTMUP utility to reset the VOLNEXT field for the last volume record.
INVALID PREV POINTER IN THE FIRST VOLUME
The first volume in the multi-volume group should not have the PREVVOL pointer.	Determine whether this volume is really the first volume in the group. Use the VOLUPD function of the CTTMUP utility to reset the VOLPREV field for the first volume record.
SINGLE VOLUME WITH WRONG SEQUENCE NUMBER
The sequence number of a single volume (not multi-volume) should be equal to one.	Determine whether this volume is really single volume and does not belong to any multi-volume group. Use the VOLUPD function of the CTTMUP utility to set the VOLSEQ field for this volume to 1.
INVALID VOLFIRST FOR 1ST VOLUME IN GROUP
The first volume field (VOLFIRST) of the volume record that is the first of a multi-volume group (according to the VOLSEQ field) must be equal to the value of the VOLSER field.	Determine whether this volume is the first volume of the multi-volume group, or a single volume. Use the VOLUPD function of the CTTMUP utility to set the VOLFIRST field to the VOLSER value.
DATASET OUT OF SEQUENCE
The label number of a data set is out of sequence with the other labels of its multi-volume group.	Determine whether the problem is that the dataset record is redundant. Use the RECDEL function of the CTTMUP utility to delete the redundant dataset record.

CTTI03E RBA `rba`: UNIDENTIFIED {MDB | STK} {DATA | INDEX} RECORD TYPE=`x`

Explanation: The CTTIDB utility detected a data record or index entry with an invalid type.

Corrective Action: For an invalid type of data record, use the CTTMUP utility to delete the record. For an invalid type of index entry, you need to rebuild the entire index file.

CTTI04E RBA `rba`: VOLUME `volser` OF THIS DATASET RECORD IS NOT FOUND

Explanation: The CTTIDB utility detected a volume specified in a dataset record (the DSVOLSER field) but the corresponding volume data record was not found. In this message, rba is the RBA of the dataset record whose volume was not found. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: See message CTT999I for the volser of the volume in error. Use the VOLADD function of the CTTMUP utility to add the missing volume record, or the RECDEL function to delete the redundant dataset record. The user also may decide to correct the volume name in the dataset record.

CTTI05E RBA `rba`: {VOL-CONT | L-INDEX} [NOT] {EXPECTED | FOUND} BUT [NOT] {FOUND | EXPECTED}

Explanation: The CTTIDB utility either detected an unexpected volume continuation record (T type) or L-index, or did not find one that was expected.

Volume continuation records are expected for single volumes or for the first volume of a multi-volume group that has more than three vaults in its vault pattern. Volume continuation records are not expected for single volumes with up to three vaults in their vault pattern, or for a chained volume that is not the first volume in its multi-volume group.

The L-index is expected for each dataset record and volume combination. For example, if a dataset spans on two volumes, then it will have two L-indexes, one for each volume.

In this message, rba is the RBA of volume record, volume continuation record, or dataset record according to the error detected. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: For an unexpected or expected L-index, use the GRPBIX function of the CTTMUP utility. If the error is not corrected, then rebuild the index file using the CTTBIX utility. For volume continuation record, determine the cause of the problem and correct it by deleting the unexpected volume continuation record, or update the number of vault entries in the VLTENTNM field in the volume record.

CTTI06E VOLUME `volser` IN USE FOR `num` DAYS

Explanation: The CTTIDB utility detected a volume record that is marked as being in use for num days. If a volume record is marked IN-USE for several days, it usually indicates a problem such as a system crash or a job abend.

Corrective Action: Check the USEDAYS parameter of the CTTIDB utility, and adjust it (that is, set it to a higher value) if necessary.

If you are sure that you know the cause of the IN-USE indication, you can reset it. If you are unsure, contact BMC Support before proceeding with the reset. To reset the IN-USE indication, use one of the following methods:

Specify the Z option in the OPT field beside the volume in the TI screen.
Use the VOLUPD function of the CTTMUP utility to reset the IN-USE indicator from the volume record, as follows:

VOLUPD VOLSER=xxxxxx,VOLIND=-INUSE

It is highly recommended that you first run the CTTMUP utility in SIMULATION mode, examine the output, and only then execute it in NORMAL mode.

CTTI07E RBA `rba`: ACTIVE VOLUME WITH NO [ACTIVE] DATASETS

Explanation: The CTTIDB utility detected an active volume with no data set records or with no active data set records. In this message, rba is the RBA of the volume record. Information message CTT999I, which describes the volume record, follows this message.

Corrective Action: Request information on the volume by using the TI screen.

For a single volume: If its status should be SCRATCH, change it using the VOLSCR function of the CTTMUP utility. Otherwise, you can add new active dataset record using the DSNADD function of the CTTMUP utility, or activate one of the existing dataset records using DSNEXT function of CTTMUP utility.
For a volume that is part of a multi-volume group: Use the GRPBIX function of the CTTMUP utility to rebuild the indexes for the multi-volume group. If the error is not fixed, you will probably need to update the VOLSNUM field of a dataset record that is part of the multi-volume group.

CTTI08E RBA `rba`: DSN IS ACTIVE, BUT VOLUME `volser` IS SCRATCH

Explanation: The CTTIDB utility detected a SCRATCH volume with an ACTIVE data set. In this message, rba is the RBA of the data set record. A SCRATCH volume cannot contain ACTIVE data sets. Information message CTT999I, which describes the dataset record in error, accompanies this message.

Corrective Action: Determine if the data set and the volume should be SCRATCH or ACTIVE. Then depending on the results, do one of the following:

Change the volume status (VOLSTAT) to ACTIVE using the VOLUPD function of the CTTMUP utility.
Scratch the volume using the VOLSCR function of the CTTMUP utility.

CTTI09E RBA `rba`: VOLUME IS {NEITHER | BOTH} ACTIVE {NOR | AND} SCRATCH

Explanation: The CTTIDB utility detected a volume record that is either marked as both ACTIVE and SCRATCH, or is marked as neither ACTIVE nor SCRATCH. The volume must be either ACTIVE or SCRATCH, not both. In this message, rba is the record RBA of the volume record. Information message CTT999I, which describes the bad volume record, accompanies this message.

Corrective Action: Determine whether this volume should be ACTIVE or SCRATCH. Then, depending on the results, use the VOLUPD function of the CTTMUP utility to change the status (VOLSTAT) of the volume to either ACTIVE or SCRATCH.

CTTI10E RBA `rba`: LBLNUM `num1` DIFFERS FROM HIGHEST DSN LABEL FOUND `num2`

Explanation: The CTTIDB utility detected a volume record for which the LBLNUM field is not equal to the highest active label number on volume. Information message CTT999I, which describes the volume record in error, accompanies this message.

The variables in this message are:

rba - the RBA of the volume record
num1 - the current value of LBLNUM field from the volume record
num2 - the label number of the highest active data set on the volume

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the LBLNUM field of the volume record to the correct value, which is num2, instead of num1. This error can also be corrected by means of the update function by using the TI screen.

CTTI11E RBA `rba`: ACTIVEDS `num1` DIFFERS FROM # OF DSN RECORDS FOUND `num2`

Explanation: The CTTIDB utility detected a logical error in a volume record. Information message CTT999I, which describes the error volume record, accompanies this message.

The variables in this message are:

rba - the RBA of the volume record for which the error was detected
num1 - the volume record field ACTIVEDS, containing the number of active data sets on the volume
num2 - the number of active data set records that the utility detected on this volume

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the ACTIVEDS field of the volume record to the correct value, which is num2, instead of num1. This error can also be corrected by means of the update function by using the TI screen.

CTTI12E RBA `rba`: VOLSNUM `num1` DIFFERS FROM # OF VOLUME RECORDS FOUND `num2`

Explanation: The CTTIDB utility detected a data set record in which the field value that holds the number of volumes that the data set resides on (VOLSNUM) is not correct. Information message CTT999I, which describes the dataset record in error, accompanies this message.

The variables in this message are:

rba - the RBA of the data set record
num1 - the current value of the VOLSNUM field from the data set record, holding the number of volumes occupied by the data set
num2 - the number of volume records counted by the utility for the data set

Corrective Action: Use the DSNUPD function of the CTTMUP utility to update the VOLSNUM field of the dataset record to the correct value, which is num2, instead of num1. Then use the GRPBIX function of the CTTMUP utility to rebuild the corresponding index entries.

CTTI13E RBA `rba`: MISSING VAULT PATTERN INFORMATION

Explanation: The CTTIDB utility detected a vaulted volume record with missing vaulting information. A vaulted volume means that one of the following flags is set on the volume record: VAULTED, PVLT, PENDVLT. Missing vault information means that the number of vault entries field (VLTENTNM) is zero.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update all vaulting information fields in the volume records (VLTENTNM, VAULT, VLTEXTYP, and VLTEXPDT), or run the CTTVTM utility with RECALC mode and INCLUDE statement on the problematic volume only.

CTTI14E RBA `rba`: SPECIFIED # OF VAULTS `num1` DIFFERS FROM VAULT COUNT `num2`

Explanation: The CTTIDB utility detected a volume record whose specified number of vaults (num1) does not equal its actual vault count (num2). A volume record contains a field that specifies the number of vaults in the vault pattern of the volume (VLTENTNM). Information message CTT999I, which describes the erroneous volume record, accompanies this message.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the VLTENTNM field of the volume record to the correct value, which is num2, instead of num1.

CTTI15E RBA `rba`: VAULT INFO NOT EQUAL TO VAULT INFO OF FIRST VOLUME

Explanation: The CTTIDB utility detected a chained volume record with vaulting information different from vaulting information in the volume record of the first volume of the multi-volume group. Vaulting information in the chained volume record must be identical to the vaulting information for the first volume. The following vaulting information fields of the volume records are compared: VLTENTNM, VAULT, VLTENTDT, VLTEXTYP, and VLTEXPDT. In this message, rba is the RBA of the volume record of the chained volume in error. Information message CTT999I, which describes the erroneous volume record, accompanies this message.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the VLTENTNM, VAULT, VLTENTDT, VLTEXTYP and VLTEXPDT fields of the volume record to have the same value as in the first volume in this multi-volume group. You can also run the CTTVTM utility with RECALC mode and INCLUDE statement on all volumes belonging to that multi-volume group.

CTTI16E VLTVEXP IS INCONSISTENT WITH VAULTING INFORMATION (`vault_seq`)

Explanation: The CTTIDB utility detected a volume data record with incorrect information in the VLTVEXP field. This field identifies the vaulting pattern sequence number that holds the expiration type, which is VOL EXPIRE. In this message, vault_seq is the information that should be in the VLTVEXP field. Information message CTT999I, which describes the erroneous volume record and the current value of the VLTVEXP field, accompanies this message.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the VLTVEXP field of the volume record to the correct value, which is vault_seq.

CTTI17E RBA `rba`: {MDB | STK} KEY NOT FOUND. RECTYPE: `rec_typ`, MISSING KEY: `key_typ`

Explanation: The CTTIDB utility detected a data record for which there is no index record (key). Information message CTT999I, which describes the record in error, accompanies this message.

The variables in this message are:

rba - the RBA of the data record
rec_typ - the data record type
key_typ - the type of the missing index

Corrective Action: If the missing index is a V-type index, use the VOLBIX function of the CTTMUP utility to rebuild this index (key). If the missing index is a L or D-type index, use the GRPBIX function of the CTTMUP utility to rebuild all multi-volume group indexes. For others index types, or if you did not succeed in fixing the error with the CTTMUP utility, rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI18E RBA `rba`: {MDB | STK} KEY BUILT FROM DATA REC IS NOT EQUAL TO REAL INDEX KEY

Explanation: The CTTIDB utility detected a mismatch between a data record and index entry. The index (key) generated from the data record does not match the index pointing to this record. These two indexes should be the same. In this message, rba is the RBA of the data record. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: For V, D, and L index types use the GRPBIX function of the CTTMUP utility to rebuild all multi-volume group indexes. For others index types, or if you did not succeed in fixing the error with the CTTMUP utility, rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI19E RBA `rba`: {MDB | STK} INDEX POINTS TO NOT EXISTING OR FREE DATA RECORD

Explanation: The CTTIDB utility detected an index record that points to a free data record or to one that does not exist. In this message, rba is the RBA of the data record. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: Rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI20E RBA `rba`: WRONG OR REDUNDANT L-INDEX

Explanation: The CTTIDB utility detected an L-type index pointing to an inappropriate data set record. In this message, rba is the RBA of the data record. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: Use the GRPBIX function of the CTTMUP utility to rebuild all indexes of this multi-volume group. If the error is not fixed, rebuild the entire Media database index file using the CTTBIX utility.

CTTI21E RBA `rba1`: INVALID RBA (`rba2`) POINTER IN THE {MDB | STK} HI-LEVEL INDEX

Explanation: The CTTIDB utility detected an invalid pointer from the HI-level index record to an inappropriate LOW-level index record.

The variables in this message are:

rba1 - the RBA of the HI-level index record
rba2 - the invalid RBA pointer found in the HI-level index record

Corrective Action: Rebuild the entire index file using CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI22E RBA `rba1`: HI-LEVEL {MDB | STK} INDEX POINTER `rba2` HAS NO TARGET

Explanation: The CTTIDB utility detected an HI-level index record, which has no target LOW-level index record.

The variables in this message are:

rba1 - the RBA of the problematic HI-level index record
rba2 - the invalid RBA pointer from the HI-level index record

Corrective Action: Rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI23E RBA `rba`: {MDB | STK} LOW LEVEL INDEX IS NOT A TARGET OF ANY HI-LEVEL INDEX

Explanation: The CTTIDB utility detected a LOW-level index record, which is not a target of any HI-level index record. In this message, rba is the RBA of the problematic LOW-level index record.

Corrective Action: Rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI24E RBA `rba`: DIFFERENT SL-NAME `slName` FOUND FOR SCRATCH VOLUME `volser`

Explanation: The CTTIDB utility detected a scratch volume record with different values in the VOLSER and SLNAME fields.

The variables in this message are:

rba - the RBA of the problematic volume record
slName - the value of the SLNAME field
volser - the value of the VOLSER field

Corrective Action: Delete the volume record from the media database using the CTTDLD utility, and then initialize the physical volume with a new unique volser using the CTTTPI utility. Make sure the new volser will be added to the Media database.

CTTI25E RBA `rba`: INVALID DATASET LABEL NUMBER EQUAL TO ZERO

Explanation: The CTTIDB utility detected a dataset record with the label number equal to zero. In this message, rba is the RBA of the problematic dataset record.

Corrective Action: Delete the invalid dataset record by using the RECDEL statement of CTTMUP utility.

CTTI26E RBA `rba`: INVALID {DATA | INDEX} RECORD STATUS `z`(X'xx') in {MDB | STK}

Explanation: The CTTIDB utility detected a record with invalid status. Valid status can be only A (active) or F (free).

The variables in this message are:

z - incorrect status value
rba - the RBA of the problematic record

Corrective Action: Manually update the record by entering either A or F as appropriate.

CTTI27E RBA `rba`: THE {MDB | STK} INDEX FILE IS CORRUPT

Explanation: The internal structure of the index file has been corrupted.

In this message, rba is the RBA of the problematic index record.

Corrective Action: Reformat the INDEX file and rebuild the index using the CTTBIX utility.

CTTI28E RBA `rba1, rba2`: SLOT IS OCCUPIED BY TWO VOLUMES: `volser1, volser2`

Explanation: The CTTIDB utility detected two different volumes, which occupy the same slot in the same vault.

In this message, rba1 and rba2 are RBAs of problematic volume records. This message is followed by message CTT999I, which contains information about the vault and the problematic slot number.

Corrective Action: Manually update one or both volume records by entering a correct slot number. Then run the CTTVTM utility in SLOTBLD mode.

CTTI29E RBA `rba`: VOLUME `volser` ASSIGNED TO NON-EXISTENT VAULT

Explanation: The CTTIDB utility detected the volumes, which are assigned to the vault, but the vault record does not exist.

In this message, rba is the RBA of the problematic volume record. This message is followed by message CTT999I, which contains information about the problematic vault record.

Corrective Action: Create the vault definition, using screen TV. Then run the CTTVTM utility in SLOTBLD mode.

CTTI30E RBA `rba`: VOLUME `volser` IS IN SLOT, BUT SLOT IS MARKED "VACANT"

Explanation: The CTTIDB utility detected the volume that occupied the slot, but the slot is marked as vacant.

In this message, rba is the RBA of the problematic volume record. This message is followed by message CTT999I, which contains information about the vault and the problematic slot number.

Corrective Action: Run the CTTVTM utility in SLOTBLD mode.

CTTI31E RBA `rba`: SLOT IS MARKED "OCCUPIED", BUT NO VOLUME IS ASSIGNED TO IT

Explanation: The CTTIDB utility detected the slot in the vault, which marked as "occupied", but there is no volume, assigned to it.

In this message, rba is the RBA of the problematic vault record. This message is followed by message CTT999I, which contains information about the vault and the problematic slot number.

Corrective Action: Run the CTTVTM utility in SLOTBLD mode.

CTTI32E RBA `rba`: RECVLNUM `num` IS INCONSISTENT WITH VAULTING INFORMATION

Explanation: The CTTIDB utility detected the volume, in which the value of the RECVLNUM field (number of the vaulting pattern "recalled from"), is inconsistent with the value of the VLTENTNM field (total number of vaulting patterns).

This message is followed by message CTT999I, which contains information about the problematic volume.

Corrective Action: Correct the problematic field using the CTTMUP utility.

CTTI33I {TOTAL | NUMBER OF `errmsg}` ERRORS FOUND: `nn`

Explanation: This information message shows statistical information about the number of appropriated errors detected by CTTIDB utility or total number of errors.

In this message, errmsg refers to the corresponding CTTIDB error message, such as CTTI00E or CTTI01E.

Corrective Action: No action is required.

CTTI34W NO VAULT RECORDS FOUND. ALL VAULTING ERROR MESSAGES BLOCKED.

Explanation: When attempting to cross-validate volume records and vault records, the CTTIDB utility found that no vault records exist in the MDB. No further vault-related error or warning messages are displayed.

Corrective Action: Run the CTTVTM utility in SLOTBLD mode to build vault records.

CTTI35E RBA `rba`: VOLUME `volser` CONTAINS INVALID SLOT NUMBER `number`

Explanation: The CTTIDB utility detected an invalid volume record. The slot number in the volume record is not in the range of the slots defined in the vault record.

The variables in this message are:

rba - the RBA of the problematic volume record
volser - the volser of the problematic volume record
number - the problematic slot number in the volume record

Corrective Action: Run the CTTMUP utility to change the problematic slot number to the correct one.

CTTI36E RBA4 `rba`: VOLUME `volser` CONTAINS MUTUALLY EXCLUSIVE STATUS FLAGS `flags`

Explanation: The CTTIDB utility detected status flags with mutually exclusive meanings. For example, the volume record status flags indicate that the volume is a SCRATCH volume and an ACTIVE volume.

The variables in this message are:

rba - the RBA of the problematic volume record
volser - the volser of the problematic volume record
flags - the volume record status flags (in hexadecimal format)

Corrective Action: Run the CTTMUP utility to change the problematic status flag to the correct one.

CTTI37E RBA `rba`: DATASET OUT OF SEQUENCE

Explanation: The CTTIDB utility detected an incorrect data set sequence among the data set records. For example, the utility found the following data set sequence: DS1, DS3, and DS2 (the data sets are not in the proper sequence) or DS1 and DS3 (data set DS2 is missing).

In this message, rba is the RBA of the first data set record out of sequence

Corrective Action: Run the CTTMUP utility to correct the incorrect data set sequence or to add the missing data set record.

CTTI38E RBA `rba`: VOLUME `volser`: INCORRECT DVLUSED VALUE `value`

Explanation: A negative value of DVLUSED was received by Control-M/Tape from the device. (The DVLUSED parameter is required for stacking processing.)

The variables in this message are:

rba - the RBA of the problematic volume record
volser - the volser of the problematic volume record
value - the DVLUSED value

The utility CTTIDB continues to run. The error is automatically fixed when the problematic tape is returned to the scratch pool.

Corrective Action: If stacking is used, you can also resolve the error by running the CTTMUP utility. If stacking is not used, consider this message as an information message.

Messages CTTS00 through CTTSxx

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

CTTS01W THE CTVINTR=NONE SPECIFIED IN THE CTTPARM

Explanation: The CTVINTR parameter is set to NONE in the CTTPARM member. The CTTSYNC utility cannot perform synchronization with Control-V.

The CTTSYNC utility ends.

Corrective Action: Set the CTVINTR parameter to EDM or DSN in the CTTPARM member and rerun the CTTSYNC utility.

CTTS02E THE EDMID OF VOLUME `volser` IS NOT EQUAL `edmid`

Explanation: The volser is controlled by EDM, but the EDMID field in the Media database reflects an incorrect EDM type.

The variables in this message are:

volser - the volser of the problematic volume record
edmid - type of EDM controlled the volume

Normal processing continues.

Corrective Action: Use the CTTMUP utility to update the volume record in the Media database to its correct status.

CTTS03E DATASET `volser/label` STATUS SHOULD BE {ACTIVE | PERM} IN MEDIA DATABASE

Explanation: The dataset is controlled by Control-V, but its status is not active or its retention type is not permanent in the Media database.

Normal processing continues.

Corrective Action: Use the CTTMUP utility to update the dataset record in the Media database to its correct status.

CTTS04E THE CREPGM OF THE DATASET `volser/label` IS NOT "CTVMIG"

Explanation: The dataset is controlled by Control-V, but its create program (CREPGM) field is not equal to CTVMIG in the Media database.

Normal processing continues.

Corrective Action: Use the CTTMUP utility to update the dataset record in the Media database to its correct status.

CTTS05E CONFLICT BETWEEN DSNAMES `volser/label`

Explanation: The dataset is controlled by Control-V, but the dataset name in the Media database is different from dataset name specified in Control-V Migrated User file.

Normal processing continues.

Corrective Action: Decide which is the correct dataset name and make necessary updates in the relevant database.

CTTS06E DATASET `volser/label` IS NOT DEFINED IN MEDIA DATABASE

Explanation: The dataset is controlled by Control-V, but it is not defined in Control-M/Tape Media database.

Normal processing continues.

Corrective Action: Check why the dataset is not defined in the Media database. If the dataset should be defined in Control-M/Tape Media database, then use CTTMUP utility to add the dataset to the Media database.

CTTS07E DATASET `volser/label` IS NOT CONTROLLED BY CONTROL-V

Explanation: The dataset is not controlled by Control-V, but it is marked in the Media database as ACTIVE, its retention type is PERMANENT and its create program (CREPGM) field is CTVMIG.

Normal processing continues.

Corrective Action: Verify that the dataset is really not controlled by Control-V, and scratch the dataset in the Media database using the CTTMUP utility.

CTO–CTT

CTO Messages

Messages CTO0 through CTO0xx

CTO001I {CONTROL-O | CTMCMEM} monitor TIMER SUBTASK STARTED. LEVEL sting

CTO002I {CONTROL-O | CTMCMEM} TIMER SUBTASK ENDED.

CTO004I SVCDUMP WAS CAPTURED SUCCESSFULLY.

CTO005E SVCDUMP WAS FAILED. A PARTIAL DUMP WAS TAKEN BECAUSE THE DUMP DATA SET DID NOT HAVE SUFFICIENT SPACE.

CTO006E SVCDUMP CAPTURED FAILED RC 8 REASON= reason (HEX).

CTO007W RELEASING ORPHAN WSC AT address JOBNAME= jobName ASID= asid

CTO008W RELEASING TIMED-OUT WSC AT address JOBNAME= jobName ASID= asid

CTO009I TIMEOUT WSC AT address JOBNAME= jobName ASID= number

CTO00AE CTOTMO RESUMED AFTER ABENDING WHILE TRYING TO RELEASE A WSC

CTO046S BLDL/LOAD FAILED FOR THE MODULE " modName "

Messages CTO100 through CTO1xx

CTO100I {CONTROL-O | CTMCMEM} RELEASE x.x.xx- MONITOR STARTED

CTO101S MONITOR STARTED WITH INCORRECT STORAGE KEY. CHECK PPT DEFINITION

CTO102I CONTROL-D FUNCTIONS ENABLED

CTO102S {CONTROL-O | CTMCMEM} MONITOR IS NOT APF-AUTHORIZED

CTO103E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

CTO103W CONTROL-D FUNCTIONS DISABLED. "DO CTD REQ." WILL BE REJECTED

CTO104S BLDL/ATTACH FAILED FOR TASK taskName

CTO105S UNRECOVERABLE ERROR ENCOUNTERED

CTO106S SUBTASK taskName ABENDED abCode

CTO107I SHUT DOWN UPON REQUEST FROM OPERATOR

CTO108S UNABLE TO ESTABLISH THE CROSS MEMORY ENVIRONMENT. STEP stepName

CTO109I CONTROL-O MONITOR IS SHUTTING DOWN. A NEW MONITOR WAS STARTED

CTO10AI CONTROL-M FUNCTIONS ENABLED

CTO10BW CONTROL-M FUNCTIONS DISABLED. "DO FORCEJOB / RESOURCE" WILL BE REJECTED

CTO10DW CTOPARM PARAMETER DAYTIMEO ( cto_time) SHOULD BE EQUAL TO DAYTIMEM ( ctm_time) OF CTMPARM.

CTO111E INVALID DATE IN ORDER/FORCE MODIFY COMMAND

CTO112E SMFID smfid IS NOT DEFINED IN IOACPRM INSTALLATION PARAMETERS

CTO115W FORMSUB3 DOES NOT NEED TO BE RUN WHEN SYSTLOGR=Y, NO ACTION TAKEN

CTO120I CONTROL-O MONITOR SHUTTING DOWN

CTO121S CONTROL-O MONITOR ENDED WITH ERROR

CTO122S NOT ENOUGH STORAGE IN EXTENDED CSA FOR blockname. RETURN CODE= rc

CTO123I CONTROL-O INTERVAL IS SET TO nn SECONDS

CTO124E INTERVAL MUST BE A TWO DIGIT NUMBER BETWEEN 01-99 SECONDS

CTO124W CONTROL-O PARAMETER parmName= parmValue{ > | < } parmDefault- USING DEFAULT VALUE

CTO125I parmList

CTO126W LOAD OF IOADEST TABLE FAILED: DO SHOUT WILL NOT BE SUPPORTED

CTO127I NEWDEST COMMAND ACCEPTED

CTO128I RULE TYPE TABLE STATUS LIBRARY PRIORITY

CTO129I ruleName type tableName status lib priority

CTO12BI WISH WO0949 IS {ENABLED | DISABLED} - CICS LONG MESSAGES SUPPORT

CTO12CI WISH WO0975 IS ENABLED - MONITOR WILL WAIT UNTIL MIGRATED LIBRARIES WILL BE RESTORED

CTO12DI WISH WO0975 IS DISABLED - MONITOR WILL IGNORE MIGRATED LIBRARIES

CTO12EI WISH WO0976 IS ENABLED - MESSAGES HANDLED AS IS

CTO12FI WISH WO0976 IS DISABLED - MESSAGES HANDLED IN UPPER CASE

CTO12SI RULE LIST DISPLAY FOR LPAR lpar_name:

CTO130I IN condName date

CTO131I TIME FROM hhmm UNTIL hhmm INTERVAL interval

CTO132I REQUEST TO STOP THE CONTROL-M API ACCEPTED

CTO133I CONTROL-M API STOPPED

CTO134I {CONTROL-O | CTMCMEM} WORKING DATE HAS CHANGED FROM old_dateTO new_date

CTO135I {CONTROL-O | CTMCMEM} DEBUG LEVEL IS SET TO lvl

CTO136E DEBUG LEVEL MUST BE A NUMBER BETWEEN 0-255

CTO136I THE CONTROL-M API WILL BE RESTARTED WITH THE FIRST API REQUEST

CTO137S INVALID PARAMETERS ( parmList) PASSED TO THE {CONTROL-O | CTMCMEM} MONITOR

CTO138I CONTROL-O OPERATING MODE IS opermode

CTO138I CANNOT START THE CONTROL-M API - FIRST REQUEST ALREADY PROCESSED

CTO139I {CONTROL-O | CTMCMEM} SUBSYSTEM subsys IS ALREADY ACTIVE

CTO13AI WISH WO0986 IS NO LONGER SUPPORTED. USE MESSAGE REROUTING FEATURE TO GET THE SAME SERVICE.

CTO13BI CURRENT DATE IS new_date

CTO13JI WISH O10261 IS ENABLED - REGULAR WTO MESSAGES WILL TERMINATE COMMAND-RESPONSE MODE; %%$WAITRC CORRECTIONS

CTO140I CONTROL-O OPERATING MODE IS opermode

CTO141W {CONTROL-O | CTMCMEM} MONITOR WAS CANCELLED BY OPERATOR

CTO142S CONTROL-O MONITOR DETECTED AN INTERNAL abCode ABEND

CTO143I A NEW {CONTROL-O | CTMCMEM} MONITOR IS INITIATED

CTO144E INVALID ORDER/FORCE PARAMETERS

CTO145S AUTOEDIT FAILED, RC= rc, REASON= rsn

CTO146W MISSING GLOBAL AUTOEDIT LIBRARY/MEMBER

CTO147I CONTROL-O INITIALIZATION COMPLETE. TYPE= type SUB= subsys RUN#= nnnn

CTO148W CONTROL-O STATISTICS ALREADY ACTIVE

CTO149W CONTROL-O STATISTICS NOT ACTIVE

CTO14AE INVALID modifyCommand COMMAND KEYWORD = keyword

CTO14BI SVC DUMP keyword NOW ENABLED

CTO14CI SVC DUMP keyword NOW DISABLED

CTO14DE CTOXOH RESUMED AFTER ABENDING WHILE PROCESSING PENDING REQUESTS

CTO14DW SHUTDOWN IS DELAYED DUE TO XES SYSTEM-MANAGED REBUILD PROCESS. TO CANCEL THE DELAY REPLY "FORCE"

CTO14EW monitor INITALIZATION IS CANCELLED. START monitor WHEN XAE STRUCTURES ARE AVAILABLE

CTO001I {CONTROL-O | CTMCMEM} `monitor` TIMER SUBTASK STARTED. LEVEL `sting`

CTO006E SVCDUMP CAPTURED FAILED RC 8 REASON= `reason` (HEX).

CTO007W RELEASING ORPHAN WSC AT `address` JOBNAME= `jobName` ASID= `asid`

CTO008W RELEASING TIMED-OUT WSC AT `address` JOBNAME= `jobName` ASID= `asid`

CTO009I TIMEOUT WSC AT `address` JOBNAME= `jobName` ASID= `number`

CTO046S BLDL/LOAD FAILED FOR THE MODULE " `modName` "

CTO100I {CONTROL-O | CTMCMEM} RELEASE `x.x.xx`- MONITOR STARTED

CTO104S BLDL/ATTACH FAILED FOR TASK `taskName`

CTO106S SUBTASK `taskName` ABENDED `abCode`

CTO108S UNABLE TO ESTABLISH THE CROSS MEMORY ENVIRONMENT. STEP `stepName`

CTO10DW CTOPARM PARAMETER DAYTIMEO ( `cto_time`) SHOULD BE EQUAL TO DAYTIMEM ( `ctm_time`) OF CTMPARM.

CTO112E SMFID `smfid` IS NOT DEFINED IN IOACPRM INSTALLATION PARAMETERS

CTO122S NOT ENOUGH STORAGE IN EXTENDED CSA FOR `blockname`. RETURN CODE= `rc`

CTO123I CONTROL-O INTERVAL IS SET TO `nn` SECONDS

CTO124W CONTROL-O PARAMETER `parmName`= `parmValue`{ > | < } `parmDefault`- USING DEFAULT VALUE

CTO125I `parmList`

CTO129I `ruleName type tableName status lib priority`

CTO12SI RULE LIST DISPLAY FOR LPAR `lpar_name`:

CTO130I IN `condName date`

CTO131I TIME FROM `hhmm` UNTIL `hhmm` INTERVAL `interval`

CTO134I {CONTROL-O | CTMCMEM} WORKING DATE HAS CHANGED FROM `old_dateTO new_date`

CTO137S INVALID PARAMETERS ( `parmList`) PASSED TO THE {CONTROL-O | CTMCMEM} MONITOR

CTO138I CONTROL-O OPERATING MODE IS `opermode`

CTO139I {CONTROL-O | CTMCMEM} SUBSYSTEM `subsys` IS ALREADY ACTIVE

CTO13BI CURRENT DATE IS `new_date`

CTO140I CONTROL-O OPERATING MODE IS `opermode`

CTO142S CONTROL-O MONITOR DETECTED AN INTERNAL `abCode` ABEND

CTO145S AUTOEDIT FAILED, RC= `rc`, REASON= `rsn`

CTO147I CONTROL-O INITIALIZATION COMPLETE. TYPE= `type` SUB= `subsys` RUN#= `nnnn`

CTO14AE INVALID `modifyCommand` COMMAND KEYWORD = `keyword`

CTO14BI SVC DUMP `keyword` NOW ENABLED

CTO14CI SVC DUMP `keyword` NOW DISABLED

CTO14EW `monitor` INITALIZATION IS CANCELLED. START `monitor` WHEN XAE STRUCTURES ARE AVAILABLE

CTO14FS XAE `function` FUNCTION FAILED. RC=`rc` RSN=`rsn`

CTO150I SNAP COMMAND WAS PERFORMED. SNAP ID= `id`

CTO152I STANDALONE FACILITY ENABLED, `rsn`

CTO153I STANDALONE FACILITY DISABLED, `rsn`

CTO155W SWAP OF `addr` CHAIN ERROR, TYPE= `type` RC= `rc`

CTO157I `action` SERVER `serverId` REQUESTED

CTO158W `action` SERVER `serverId` FAILED - `rsn`

CTO159E INVALID SERVER MODIFY COMMAND - `cmd`

CTO15AE INVALID SNAP KEYWORD = `keyName`

CTO15BE INVALID LOG KEYWORD = `keyName`

CTO15CI RULE LOGGING MODE WAS SET TO `modeType`

CTO15DI WATERMARK INFORMATION: FREE= `freeNum`PND= `waitNum` EVC= `execNum` WSC= `wscNum`

CTO15DW LOAD OF EXIT `exitName` FAILED, USER CHECKING IS NOT PERFORMED

CTO15EI `typeUSAGE`: CURRENTLY `currp%,` HIGHEST `highp%`( `curr` AND `high` OUT OF `total`)

CTO15FE INVALID USAGESTATS KEYWORD =`arg`

CTO15LE SERVER `server` IS NOT DEFINED

CTO163I `cmdName` COMMAND COMPLETED

CTO164S INTERNAL ERROR PROCESSING RESOURCE FILE FOR CONDITION `cond`

CTO166W COND `name date`NOT UPDATED BY CONTROL-O - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR

CTO168I COND `name date`ALREADY `action`

CTO177S CONTROL-O STATISTICS SEVERE INTERNAL ERROR, ID= `code`

CTO181S CONTROL-O STATISTICS INTERNAL ERROR. WRITE FAILED FOR SECTION `section`

CTO192E STATISTICS REQUEST FOR MESSAGE ID `msgId`FAILED - MESSAGE ID NOT FOUND

CTO193E STATISTICS REQUEST FOR MESSAGE ID `msgId` FAILED - INVALID REQUEST

CTO195E RESET OF STATISTICS FOR MESSAGE ID `msgId` FAILED

CTO196S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`

CTO198E RESET OF DATE FOR MESSAGE ID `msgId` FAILED

CTO1A6E CONSOLE ERROR. R15 = `rc`, REASON- CODE = `rsn`

CTO1A8E CONSOLE `name` IN USE. TRY AGAIN LATER