Messages MTO800 through MTO8xx

This group includes messages for the Control-O product.

MTO820I INITIALIZATION OF SMS SUPPORT STARTED

Explanation: This information message indicates that Control-O started initializing SMS support.

Corrective Action: No action is required.

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

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

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

MTO824W 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 occur:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Check the IOA load library.

MTO825W UNABLE TO REGISTER WITH SMS INTERFACE rsn

Explanation: Control-O could not register with the SMS interface during initialization.

Valid values for rsn are:

rsn	Explanation
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.

The following system actions occur:

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.

MTO826W 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 occur:

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.

MTO827E INITIALIZATION OF SMS SUPPORT FAILED

Explanation: An initialization error occurred when Control-O tried to install the SMS interface.

The following system actions occur:

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.

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

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

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

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

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

MTO830I DEACTIVATION OF SMS SUPPORT STARTED

Explanation: This information message indicates that Control-O started deactivating an SMS interface.

Corrective Action: No action is required.

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

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

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

MTO834W DEACTIVATION OF SMS SUPPORT FAILED

Explanation: An error occurred when Control-O tried to remove the SMS interface module.

The following system actions occur:

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.

MTO835W 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 occur:

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.

MTO836W SUBSYSTEM NOT REMOVED FROM SMS INTERFACE: rsn

Explanation: Control-O could not remove its subsystem name from the SMS interface.

The value of rsn may be one of the following:

SUBSYSTEM NOT FOUND - The name of the current Control-O subsystem is not registered in the SMS interface.
LOCK CANNOT BE OBTAINED - 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 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.

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

MTO83AI INITIALIZATION OF AUTOOPERATOR SUPPORT STARTED

Explanation: This information message indicates that Control-O started initializing AutoOPERATOR support.

Corrective Action: No action is required.

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

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

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

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

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

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

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

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

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

MTO83KI DEACTIVATION OF AUTOOPERATOR SUPPORT STARTED

Explanation: This information message indicates that Control-O started deactivating the AutoOPERATOR interface.

Corrective Action: No action is required.

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

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

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

MTO83OI SUBSYSTEM REGISTRATION REMOVED FROM AUTOOPERATOR INTERFACE

Explanation: This information message indicates that Control-O unregistered the AutoOPERATOR interface.

Corrective Action: No action is required.

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

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

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

MTO840E INITIALIZATION OF SUBSYSTEM TABLE FAILED: text

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems if they were not already defined. During the definition process, an error occurred.

In this message, text identifies the nature of the error. Valid values for text are:

text	Explanation
LOAD OF CTOSSI FAILED	The Control-O interface was not successfully loaded.
CSA GETMAIN FAILED	Control-O failed to GETMAIN in CSA.
LOCK CANNOT BE OBTAINED	Control-O failed to obtain LOCK.
TOO MANY SUBSYSTEMS	Control-O failed to define the subsystem, because the SSVT subsystem table already contained the maximum permitted number of subsystems.

Control-O terminates with a return code of 8.

Corrective Action: The necessary action depends on the value of text.

If the value of text is LOAD OF CTOSSI FAILED, ensure that the Control-O STC is using the correct STEPLIB library, then restart Control-O.
If the value of text is CSA GETMAIN FAILED, ensure that Control-O has sufficient storage. Control-O requires about 50K in CSA. It may be necessary to restart the system.
If the value of text is LOCK CANNOT BE OBTAINED, the error may be a Control-O internal error. Try again to start Control-O. If the same error occurs, contact BMC Customer Support.
If the value of text is TOO MANY SUBSYSTEMS, reduce the number of subsystems that are active, and try again to start Control-O. It may be necessary to deactivate one or more active subsystems, or to restart the system, before trying to restart Control-O.

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

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

MTO843I 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 ACS exit routines to trigger rules based on MAINVIEW events.

Corrective Action: No action is required.

MTO844W 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 occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check the IOA load library.

MTO845W UNABLE TO REGISTER WITH MAINVIEW INTERFACE rsn

Explanation: Control-O could not register with the MAINVIEW interface during initialization.

Valid values for rsn are:

rsn	Explanation
TOO MANY SUBSYSTEMS	The MAINVIEW interface had already registered the maximum number of subsystems.
LOCK CANNOT BE OBTAINED	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: 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.

MTO846W LOAD OF MAINVIEW INTERFACE FAILED: rsn

Explanation: Control-O could not load the MAINVIEW interface module.

Valid values for rsn are:

rsn	Explanation
LOAD TO PRIVATE REGION FAILED	Control-O could not load the MAINVIEW 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 MAINVIEW interface module.
LOAD TO CSA FAILED	Control-O could not load the MAINVIEW interface module into the CSA.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW 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.

MTO847E INITIALIZATION OF MAINVIEW SUPPORT FAILED

Explanation: An initialization error occurred when Control-O tried to install the MAINVIEW interface.

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.

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

MTO84AI INITIALIZATION OF MAINVIEW SUPPORT STARTED

Explanation: This information message indicates that Control-O started initializing MAINVIEW support.

Corrective Action: No action is required.

MTO84BI DEACTIVATION OF MAINVIEW SUPPORT STARTED

Explanation: This information message indicates that Control-O started deactivating an MAINVIEW interface.

Corrective Action: No action is required.

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

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

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

MTO84FW DEACTIVATION OF MAINVIEW SUPPORT FAILED

Explanation: An error occurred when Control-O tried to remove the MAINVIEW interface module.

The following system actions occur:

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.

MTO84GW 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 occur:

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.

MTO84HW SUBSYSTEM NOT REMOVED FROM MAINVIEW INTERFACE: rsn

Explanation: Control-O could not remove its subsystem name from the MAINVIEW interface.

Valid values of rsn are:

rsn	Explanation
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 occur:

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.

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

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

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

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

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

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

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

Parent Topic

MTO messages