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

Parent Topic

CTO messages