|
|
|
|
|
This group includes messages for the Control-O product.
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.
Explanation: The CTOVPL program received an incorrect parameter list while executing a LOADGLOBAL/ WRITEGLOBAL command.
This message indicates an internal error.
Corrective Action: Contact BMC Customer Support.
Explanation: The CTOVPL program was unable to open the Global Pool List during execution of a LOADGLOBAL/ WRITEGLOBAL command.
The Global Pool List is defined by the DAGLBLST DD statement in the procedure of the Control-O monitor.
The LOADGLOBAL/WRITEGLOBAL command is ignored.
Corrective Action: Check and correct the DD statement and related data set specifications in the Control-O monitor procedure.
Explanation: The user issued a LOADGLOBAL command with the poolid 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.
Explanation: Control-O could not load variables from the poolid 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.
Explanation: Control-O could not write variables to the poolid 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.
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: Do the following:
Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL/ WRITEGLOBAL command.
This message indicates an internal error.
Corrective Action: Contact BMC Customer Support.
Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL/WRITEGLOBAL command.
This message indicates an internal error.
Corrective Action: Contact BMC Customer Support.
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.
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.
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.
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.
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:
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.
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.
Explanation: This message indicates an internal error.
Corrective Action: Contact BMC Customer Support.
Explanation: Control-O detected an invalid AutoEdit expression in the poolid Global Variable pool at startup or while executing command LOADGLOBAL.
The poolid Global variable specified in the AutoEdit expression was not loaded. The error was caused for one of the following reasons:
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. Command LOADGLOBAL continues with the next line in the DAGLBLST member.
Corrective Action: Do the following:
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.
Explanation: This information message indicates that the Global Variable pool poolid was successfully written.
Corrective Action: No action is required.
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 DD name DAGLBLST contains, among other things, a list that specifies the Control-O Global AutoEdit Variable database and the IOA 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
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.
Explanation: This information message indicates that the CTOVPL program successfully completed execution of command LOADGLOBAL/WRITEGLOBAL.
Corrective Action: No action is required.
Explanation: There is a conflict between inconsistent IOAPLEX and DAGLBLST settings, as follows:
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.
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.
Explanation: Control-O or CMEM monitor encounter an invalid keyword in a record in the DAGLOBAL list file.
Corrective Action: No action is required.
Explanation: Control-O or CMEM monitor the control record in the DAGLOBAL list file is all blank.
Corrective Action: No action is required.
Explanation: Control-O or CMEM monitor encounter an empty control record format in the DAGLOBAL list file.
Corrective Action: No action is required.
Explanation: Control-O or CMEM monitor encounter an invalid control record value in the DAGLOBAL list file.
Corrective Action: No action is required.
Explanation: Control-O or CMEM monitor encounter an invalid control record format in the DAGLOBAL list file.
Corrective Action: No action is required.
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.
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.
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.
Parent Topic |