|
|
|
|
|
This group includes messages for the Control-O product.
Explanation: This information message is the normal start message of the Control-O or CMEM Executor task that handles tasks that cannot be executed by the Control-O or CMEM subsystem. Certain of these actions require communication with other IOA products.
Corrective Action: No action is required.
Explanation: This information message is the normal termination message of the CONTROLO or CMEM Executor task that handles tasks that cannot be executed by the CONTROLO or CMEM subsystem. Certain of these actions require communication with other IOA products.
Corrective Action: No action is required.
Explanation: The CONTROLO or CMEM monitor failed to allocate the subsystem-to-monitor communication file. The communication file links the CONTROLO or CMEM and Control-M monitors.
Possible causes are:
The Control-O or CMEM monitor shuts down.
Corrective Action: Check the potential reasons for the error listed above. Correct as necessary, and restart the Control-O or CMEM monitor.
Explanation: The Control-O monitor failed to open a subsystem-to-monitor communication file. The communication file links the Control-O or CMEM and Control-M monitors. Possible causes are:
The Control-O or CMEM monitor shuts down.
Corrective Action: Check the communication files that are in use, and make sure that they were properly defined, formatted, and cataloged. In addition, make sure that no restrictions are imposed, for example by MVS or a security package, and the like.
Explanation: The Control-O monitor could not read a monitor-to-subsystem communication file due to an I/O error. The communication file links the Control-O or CMEM and Control-M monitors. The Control-O monitor-to-subsystem communication file may not have been formatted correctly during Control-M Installation Procedure, or may have been incorrectly modified.
The Control-O or CMEM monitor shuts down.
Corrective Action: For formatting information, see the section that describes how to install the Control-M Event Manager Subsystem (CMEM) in the Control-M chapter of the INCONTROL for z/OS Installation Guide. Reformat or restore as necessary, and restart the Control-O or CMEM monitor.
Explanation: The Control-O monitor failed to allocate the monitor-to-system communication file. The communication file links the Control-O or CMEM and Control-M monitors.
Possible causes are:
The Control-O or CMEM monitor shuts down.
Corrective Action: Check the potential reasons for the error listed above. Correct as necessary, and restart the Control-O or CMEM monitor.
Explanation: The Control-O or CMEM monitor failed to open a monitor-to-subsystem communication file. The communication file links the Control-O or CMEM and Control-M monitors. Possible causes are:
The Control-O or CMEM monitor shuts down.
Corrective Action: Check the communication files that are in use, and make sure that they were properly defined, formatted and cataloged. In addition, make sure that no restrictions are imposed by MVS, a security package, and so on.
Explanation: The Control-O or CMEM monitor could not read a subsystem-to-monitor communication file due to an I/O error. The communication file links the Control-O or CMEM and Control-M monitors. The Control-O or CMEM subsystem-to-monitor communication file may not been formatted correctly during Control-M Installation procedure, or may have been incorrectly modified.
The Control-O or CMEM monitor shuts down.
Corrective Action: For formatting information, see the section that describes how to install the Control-M Event Manager Subsystem (CMEM) in the Control-M chapter of the INCONTROL for z/OS Installation Guide. Reformat or restore as necessary, and restart the Control-O or CMEM monitor.
Explanation: The Control-O or CMEM subsystem-to-monitor communication file has not been formatted correctly during the Control-M Installation Procedure or may have been incorrectly modified.
The Control-O or CMEM monitor shuts down.
Corrective Action: For formatting information, see the section that describes how to install the Control-M Event Manager Subsystem (CMEM) in the Control-M chapter of the INCONTROL for z/OS Installation Guide. Reformat or restore as necessary, and restart the Control-O or CMEM monitor.
Explanation: The Control-O monitor failed to open the trace file used when Control-O is operating in LOG and TEST modes.
The Control-O monitor shuts down.
Corrective Action: Make sure that DD name DAACTLOG is allocated to the Control-O monitor, or if no trace is required, to DUMMY.
Explanation: One of the following System Logger requests failed:
CMEM issues r15. Possible values of r15 are:
To determine the system action, check the descriptions of return and reason codes in the IBM manual MVS Programming: Assembler Services Reference, where they are described for each System Logger request separately.
Corrective Action: If you cannot correct the problem, call BMC Customer Support.
Explanation: During Control-O or CMEM start up, the IOACPRM member was not found in the IOA PARM library, and therefore could not be loaded.
Initiation of CMEM fails CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.
Corrective Action: Have the INCONTROL administrator check if the situation is valid. If not, create the IOACPRM member in the IOA PARM library and restart the Control-O or CMEM monitor.
Explanation: During Control-O or CMEM start up, the IOACPRM member in the IOA PARM library does not contain the definition for the system where the Control-O or CMEM monitor is active.
Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.
Corrective Action: Have the INCONTROL administrator check if the situation is valid. If not, add the definitions for the current system to IOACPRM, and restart the Control-O or CMEM monitor.
Explanation: During Control-O or CMEM start up, Control-O or CMEM could not allocate the Subsystem-to-Monitor file S2M, because the name of the file is missing from the definition of the current system in the IOACPRM.
Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.
Corrective Action: Call the INCONTROL administrator to check if the situation is valid. If not, add the name of the Subsystem-to-Monitor file S2M and the definitions for the current system to the IOACPRM in the IOA PARM library, and restart the Control-O or CMEM monitor.
Explanation: During Control-O or CMEM start up, the CMEM Logger facility was required, but the CMMPLEX member that should contain the definition of the logger was not found.
Initiation of CMEM fails. CMEM functions DO FORCEJOB and DO RESOURCE cannot be executed by Control-M.
Corrective Action: No action is required.
Explanation: An invalid date reference format was used in a DO COND statement.
Valid date reference formats are:
Corrective Action: Correct the date format, and reorder the rule table.
Explanation: This information message indicates that a rule remained in Command-Response mode or Wait mode for longer than specified in the TIMEOUT subparameter.
The rule continues executing.
Corrective Action: No action is required.
Explanation: A Command-Response rule could not obtain a subsystem console because all valid subsystem consoles were in use by other Command-Response rules.
Command execution is delayed until the next Control-O interval, when a new attempt to obtain a subsystem console will be made.
Corrective Action: Check the Status screen for Command-Response rules which are executing. Verify that the number of Command-Response rules with a status of EXECUTING matches the number of subsystem consoles.
If this message is issued frequently, there may be an insufficient number of subsystem consoles to handle the Command-Response rules. In this case, increase the number of subsystem consoles in CTOPARM, and define new subsystem consoles to MVS accordingly. For details about subsystem console definition, see the Control-O chapter of the INCONTROL for z/OS Installation Guide.
Explanation: A Command-Response rule could not obtain a subsystem console because no valid subsystem consoles were allocated by Control-O. The cause of the problem is probably in the subsystem console definition.
The command is not executed.
Corrective Action: Make sure that the NUMCONS parameter in CTOPARM is greater than zero, and that the correct number of subsystem consoles is defined in MVS. For details about subsystem console definition, see the Control-O chapter of the INCONTROL for z/OS Installation Guide.
If the console subsystem definition does not seem to be the cause of the problem, check for previous console allocation error messages, and contact BMC Customer Support.
Explanation: In the process of executing DO TSO, DO KSL, or DO SHELL requests, all of the TSP (TSO PARM) blocks in CSA or ECSA were used. Possible causes are:
Further TSO, KSL, or SHELL requests are temporarily suspended until at least one TSP is available.
Corrective Action: If started tasks are not processed due to system corrective measures, wait until they run and their corresponding TSP blocks are freed.
If a started task failed due to a JCL error, perform the following recovery action:
This action frees one TSP, and message CTO215I is issued when the next TSO or KSL request is processed. TSPs also become available when Control-O is brought down after a standard shutdown or an IPL.
Explanation: This information message indicates that normal TSO, KSL, or SHELL processing resumed. TSO, KSL, or SHELL processing was suspended as a result of a shortage of TSP blocks. For more details see message CTO214E.
Corrective Action: No action is required.
Explanation: A DO RESOURCE or DO FORCEJOB request was made when Control-M was not installed. These statements are not supported if Control-M is not installed.
The rule is not ordered.
Corrective Action: Correct the rule or install Control-M.
Explanation: Control-O issued a DO COND request, but the prerequisite condition was not added or deleted. There is no authorization by the security exit to add or delete this condition in the IOA Conditions file.
The DO COND request is ignored and the rule continues execution.
Corrective Action: Contact your INCONTROL administrator.
Explanation: There is no authorization for the requested DO COMMAND statement. Security exit IOASE012 detected a violation. This exit is invoked for each command issued by a rule in which value OWNER or TRIGGER was specified for the RUNTSEC parameter.
The DO COMMAND statement is ignored and the rule continues execution.
Corrective Action: Contact your INCONTROL administrator.
Explanation: This message indicates an internal error.
Control-O or CMEM continues to perform security checks without a security cache.
Corrective Action: Contact BMC Customer Support.
Explanation: The Control-O or the CMEM monitor could not allocate the monitor to the Monitor-to-Subsystem (M2S) file of another IOA environment. During initialization the Control-O or the CMEM monitor compares the QNAME in the IOA environment with the QNAME in the M2S file. They should match.
CMEM stops. Control-O issues the CTO21FS and CTO21SE messages.
Corrective Action: Respond to the CTO21SE message. Then check the CTMPARM member and do one of the following:
Explanation: The Control-O or the CMEM monitor could not allocate the subsystem to the Subsystem-to-Monitor (S2M) file of another IOA environment. During initialization the Control-O or the CMEM monitor compares the qName1 in the IOA environment with the qName2 in the S2M file. They should match.
CMEM stops. Control-O issues the CTO21FS and CTO21SE messages.
Corrective Action: Respond to the CTO21SE message. Then check the IOACPRM member and do one of the following:
Explanation: This information message identifies the Monitor-to-Subsystem (M2S) file that the Control-O or the CMEM monitor allocated for communication with the Control-M monitor.
qName is defined in the M2S file with the DSN dsn.
Corrective Action: No action is required.
Explanation: This information message identifies the Subsystem-to-Monitor (S2M) file that the Control-O or the CMEM monitor allocated for communication with the Control-M monitor. QNAME is defined in the S2M file with the DSN dsn.
Corrective Action: No action is required.
Explanation: The error described in message CTO21ES prevents communication between the Control-O monitor and Control-M. The response to this message determines the next action.
The subtask is suspended until a response to this message is received.
Corrective Action: Select one the following responses:
Explanation: The information message echoes the response to message CTO21EE.
Corrective Action: No action is required.
Explanation: An error occurred during initialization of Subsystem-to-Monitor (S2M) communication for the Control-O monitor. Initialization checks failed for the function that communicates with the Control-M monitor. For details, see previously issued error messages in the JOBLOG or IOA Log file.
Control-O issues the CTO21EE message.
Corrective Action: Respond to the CTO21EE message.
Explanation: Either Control-O disabled communication with Control-M because of a CONTINUE response to message CTO21EE, or a DO FORCEJOB or DO RESOURCE statement was encountered during execution of a Control-O rule with communication disabled.
DO FORCEJOB, DO RESOURCE and NEWCONLIST requests from Control-M are ignored.
Corrective Action: No action is required.
Explanation: When Control-M processes events (received through the Subsystem-to-Monitor communication dataset) slower than CMEM or Control-O adds them, file space shortage may occur, and this could eventually lead to lost events.
The message is issued when the Subsystem-to-Monitor (S2M) communication dataset reaches 80% utilization.
Corrective Action: Perform the following actions:
Explanation: The Subsystem-to-Monitor (S2M) communication dataset space shortage that was reported by message CTO21IE has been relieved.
Dataset utilization returned to a level below 60%.
Corrective Action: No action is required.
Explanation: This information message indicates that during Control-O startup, Control-O allocated num subsystem consoles for use by the DO COMMAND with WAITRESP Y. The number num must be equal to the value of the NUMCONS parameter in the CTOPARM member in the IOA PARM library.
Control-O acquires the allocated subsystem consoles and uses them for the DO COMMAND with RESPMODE set to Y.
Corrective Action: If the value of num is less than the number defined in CTOPARM by the NUMCONS= num statement, define more subsystem consoles in the system. For information on how to do this, see the description of the NUMCONS parameter in CTOPARM and subsystem consoles in the Control-O Installation chapter of the INCONTROL for z/OS Installation Guide.
Explanation: This information message is the normal message issued during Control-O termination if subsystem consoles were allocated.
The subsystem consoles that were allocated to Control-O are freed during termination of the Control-O monitor.
Corrective Action: No action is required.
Explanation: Control-O could not allocate subsystem consoles during initialization, as specified in the NUMCONS parameter in the CTOPARM member.
No subsystem consoles are allocated.
Corrective Action: Define a sufficient number of MVS consoles for Control-O use. If other products use a subsystem console, calculate the number of subsystem consoles required for all products. For more details, see the Control-O installation chapter in the INCONTROL for z/OS Installation Guide, and to the relevant MVS manuals.
Explanation: Control-O attempted to allocate subsystem consoles during initialization but not enough consoles are available.
All the available subsystem consoles are allocated by Control-O. This message is followed by message CON220I which details how many consoles were allocated for Control-O use.
Corrective Action: Decrease the number of consoles required for Control-O (the NUMCONS parameter in CTOPARM), or define a sufficient number of consoles for Control-O use in MVS. If other products use a subsystem console, calculate the number of subsystem consoles required for all products. For more details, see the Control-O installation chapter in the INCONTROL for z/OS Installation Guide, and the relevant MVS manuals.
Explanation: Control-O attempted to perform an OBTAIN or RELEASE function on a subsystem console. The subsystem console service routine failed to perform the requested function.
The system action varies, depending on whether Control-O was initializing or terminating at the time of its issue, as follows:
Snap dumps are produced with the relevant control blocks.
Corrective Action: Save the snap dumps and call your INCONTROL administrator for assistance.
Explanation: There is insufficient storage in the Control-O address space to perform the OBTAIN or RELEASE subsystem console function.
The system action varies, depending on whether Control-O was initializing or terminating at the time of its issue, as follows:
Corrective Action: Increase the region size specified in the Control-O procedure.
Explanation: This message is issued during Control-O initialization when there is insufficient space in CSA or ECSA for Control-O console-related control blocks.
Control-O initialization continues without using subsystem consoles.
Corrective Action: Check if the storage defined for CSA or ECSA is large enough. If not, increase the CSA or ECSA size.
Explanation: The subsystem console service routine abended when attempting to perform the OBTAIN or RELEASE function for a subsystem console, and the function was not performed or was performed partially.
The system action varies, depending on whether Control-O was initializing or terminating at the time of its issue, as follows:
Abend and snap dumps are produced.
Corrective Action: Save the abend and snap dumps and call your INCONTROL administrator for assistance.
Explanation: This information message indicates that Control-O allocated a total of num EMCS CONSOLES according to the definitions in the CTOPARM member.
Corrective Action: No action is required.
Explanation: This information message indicates that Control-O allocated a total of num EMCS CONSOLES with migration IDs according to the definitions in the CTOPARM member.
Corrective Action: No action is required.
Explanation: Control-O failed to allocate an EMCS CONSOLE. The MCSOPER service ended with an error. When this happens, Control-O attempts to allocate an EMCS CONSOLE in order to issue a command or message. However, the attempt failed.
Control-O ignores the console.
Corrective Action: Do the following:
Explanation: Control-O failed to allocate an EMCS CONSOLE. CONVCON service ended with an error. When this happens, Control-O tries to allocate an EMCS CONSOLE in order to issue a command or message. However, the attempt failed.
Control-O ignores the console.
Corrective Action: Do the following:
Explanation: During Control-O initialization, Control-O failed to activate the Control-O subsystem that suppresses JES2 commands. To suppress JES2 commands, Control-O uses the subsystem whose name is specified in the statement JCMDSSN= subsys in the CTOPARM member in the IOA PARM library.
Control-O initialization continues, but the JES2 command suppression function is disabled.
Corrective Action: Notify the INCONTROL administrator.
Explanation: During Control-O initialization, Control-O failed to activate the Control-O subsystem that suppresses JES2 commands, because the subsystem was not properly predefined. To suppress JES2 commands, Control-O uses the subsystem whose name is specified in the statement JCMDSSN= subsys in the CTOPARM member in the IOA PARM library. This subsystem should be, but was not, defined in SYS1.PARMLIB(IEFSSN xx), and activated in the last IPL before Control-O is started.
Control-O initialization continues, but the JES2 command suppression function is disabled.
Corrective Action: Notify the INCONTROL administrator.
Explanation: During Control-O termination, Control-O tried to deactivate the IOA subsystem and the Control-O subsystem currently in use, but the subsystem identified in the message was already inactive.
Control-O termination continues.
Corrective Action: Notify the INCONTROL administrator.
Explanation: During Control-O initialization, Control-O tried to activate the IOA subsystem and the Control-O subsystem, but the subsystem identified in the message was already active.
Control-O initialization continues.
Corrective Action: Notify the INCONTROL administrator.
Explanation: The subsystem initialization routine found a blank subsystem name definition in the IOAPARM member.
Corrective Action: Correct the SSNAME parameter in the IOAPARM member to specify a valid subsystem name, and check that the other subsystem-related parameters were defined correctly.
If Control-D subsystem functions are requested, check the AMNAME parameter in CTDPARM and correct if necessary.
Explanation: Control-O could not find at least one of the alternate subsystem function routines.
While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.
Control-O continues without activating the alternate subsystem.
Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries and reactivate Control-O.
Explanation: Control-O could not load at least one of the alternate subsystem function routines.
While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.
Control-O continues without activating the alternate subsystem.
Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries and reactivate Control-O.
Explanation: Control-O could not acquire enough CSA (Common Service Area) storage to load alternate subsystem function routines or to build the SSVT for the alternate subsystem.
Control-O continues without activating the alternate subsystem.
Corrective Action: If storage defined for CSA is not large enough, increase the CSA size and perform an IPL.
Explanation: This information message indicates that the CTOSSO module successfully activated the alternate subsystem.
Corrective Action: No action is required.
Explanation: This information message indicates that the Control-M or Control-O subsystem functions received the NEWCONLIST request from the Control-M monitor, and accordingly reloaded (refreshed) the CMEM table.
The Control-M or Control-O subsystem functions reloaded the CMEM table.
Corrective Action: No action is required.
Explanation: Highlighted, unrollable message.
The Statistics file is approaching its maximum capacity.
The Statistics file continues accumulating statistics until it becomes full.
Corrective Action: The user can do one of the following:
Explanation: Highlighted, unrollable message.
The Statistics file is full.
All statistics records according to the number (STREC#) set in the CTOPARM parameter file have been utilized.
Control-O continues to collect statistics for existing messages, but the statistics for new message IDs are not saved.
Corrective Action: The user can do one of the following:
Explanation: An error occurred during interface with the locally used security product.
Control-O or CMEM continues working.
Corrective Action: Contact BMC Customer Support.
Explanation: This information message indicates a normal response to operator command F CONTROLO,NEWSECDEF or F CTMCMEM,NEWSECDEF. The runtime security cache containing previously handled security definitions was successfully refreshed.
If security definitions were changed, the new definitions are used.
Corrective Action: No action is required.
Explanation: This information message is an audit message that logs a DO SNMP request executed by Control-O.
Corrective Action: No action is required.
Explanation: Control-O tried to send an SNMP request using a DO SNMP statement, but the request contained an error.
Possible return and associated reason codes are described in the following table:
Return Code ( rc ) |
Reason Code ( rsn ) |
Explanation |
|---|---|---|
04 |
|
|
|
00 |
Successful completion, minor errors discovered. |
|
04 |
SHL value exceeds 70, truncated. |
08 |
|
|
|
04 |
Failed to get local IP address. |
|
08 |
Failure to get storage for an SNMP trap. |
|
12 |
Allocation storage has failed. |
|
16 |
Hostname could not be resolved. |
|
20 |
SNMP trap sending failed. |
|
24 |
Socket call failed. |
|
28 |
Internal error; buildTrapMessage() failed. |
|
32 |
See message SNMT10S for details. |
|
36 |
See message SNMT11S for details. |
|
40 |
See message SNMT12S for details. |
|
44 |
See message SNMT13S for details. |
|
48 |
See message SNMT14S for details. |
|
52 |
See message SNMT15S for details. |
|
56 |
See message SNMT16S for details. |
|
60 |
See message SNMT17S for details. |
|
64 |
See message SNMT18S for details. |
|
68 |
See message SNMT19S for details. |
|
72 |
See message SNMT20S for details. |
|
76 |
See message SNMT21S for details. |
|
80 |
See message SNMT22S for details. |
|
84 |
See message SNMT23S for details. |
|
96 |
ISTACK parameter is specified in the IOAPARM member and the system has TCP/IP dual stack mode, but the specified stack is not running. |
|
100 |
Invalid IPv6 destination. The destination contains the colon (:) character, but the address is not a syntactically valid IPv6 address. |
|
104 |
SNMP destination contains the colon (:) character, but IPv6 is not enabled in the z/OS system. |
12 |
|
|
|
04 |
Missing SNMP message address. |
|
08 |
Invalid or missing SNMP message length. |
|
12 |
Neither Destination Table nor HOST and PORT provided. |
|
20 |
Bad or missing HOST parameter when no Destination Table. |
|
24 |
Bad or missing PORT parameter when no Destination Table. |
|
28 |
Invalid Destination Table. |
|
32 |
Specified Destination Table unavailable. |
|
36 |
Specified Translation Table unavailable. |
|
40 |
An invalid IP address was provided in HOST. |
20 |
|
Internal error. |
24 |
|
|
|
04 |
Invalid or missing MCT address. |
|
08 |
Invalid or missing SNMV vector. |
|
12 |
Failure to load IOAMEM. |
|
24 |
Insufficient storage to read Destination Table. |
|
28 |
Destination Table is empty. |
|
32 |
Destination Table unavailable. |
|
36 |
Insufficient storage to build Destination Table. |
|
40 |
IOASNMC failed SNMV not initialized. |
|
44 |
Call can be issued after MODE=INIT only. |
|
48 |
Failure to refresh Destination Table. |
The DO SNMP request is not sent, and fails.
Corrective Action: Notify the INCONTROL administrator.
Explanation: The IOASECUR security module was unable to delete the security environment. This message indicates an internal error.
Corrective Action: Contact BMC Customer Support.
Explanation: A server action cannot be performed because the server is not in the expected status. An action was attempted on a server that is either stuck or has disappeared.
Server status is set to IN ERROR.
Corrective Action: Do the following:
Explanation: Control-O monitor or CMEM monitor tries to write a message to ACTLOG sysout. The DD card ACTLOG is missing from the Control-O or CMEM procedure.
The monitor writes the message to the SYSPRINT sysout. In the monitor address space this may cause ABEND S02A with a return code of 0C in some cases. Since the Monitor can recover itself from the abend, the monitor is not immediately terminated.
Corrective Action: Add the following DD statement to the Control-O procedure (CTOTROLO) and the CMEM procedure (CTMCMEM):
//ACTLOG DD &OUTLIST,SYSOUT=&OUT
Explanation: Control-O or CMEM issued a CTMAPI request for a list of MVA-type Load-Indexes, but the request failed. The message provides the return code and reason code from CTMAPI. The message is always followed by message CTO25JS.
As a result of the failed request, setting of levels for MVA-type Load-Indexes was disabled.
Corrective Action: Check the reasons for the error. Correct as necessary, and restart the Control-O or CMEM monitor.
Explanation: Control-O or CMEM faced a private memory shortage when attempting to obtain buffers for a CTMAPI request for a list of MVA-type Load-Indexes. The message is always followed by message CTO25JS.
As a result of this issue, setting of levels for MVA-type Load-Indexes was disabled.
Corrective Action: Contact BMC Customer Support.
Explanation: Control-O or CMEM failed to build a list of MVA-type Load-Indexes, due to the reason described in message CTO25HE or message CTO25IE. This message always follows one of those messages.
Corrective Action: See message CTO25HE or message CTO25IE.
Explanation: Control-O or CMEM successfully built a list of MVA-type Load-Indexes, and is ready to set Load-Index levels based on MainView Alarms.
Corrective Action: No action is required.
Explanation: Control-O or CMEM issued a CTMAPI request for a list of MVA-type Load-Indexes, but no defined MVA-type Load-Indexes were found.
As a result of this issue, setting of levels for MVA-type Load-Indexes was disabled.
Corrective Action: If no MVA-type Load-Indexes exist, consider setting OPTMVLID=N in CTMPARM, to disable setting levels for MVA-type Load-Indexes based on MainView Alarms.
Explanation: A DO COMMAND statement specifying a VM CP command failed. The return code indicates the cause of the error, as follows:
Return Code |
Explanation |
|---|---|
4 |
MVS not running under VM. |
8 |
Insufficient space (GETMAIN failed). |
12 |
IOAVMC not APF authorized. |
16 |
FREEMAIN error. |
The specified command is ignored.
Corrective Action: The recommended action depends on the return code, as follows:
Explanation: Control-O or CMEM has detected an MVS System Logger error, and is attempting to reconnect to the MVS System Logger.
In this message, rsn is a reason code that is documented in the IBM manual MVS Programming: Assembler Services Reference. Check that publication for the system action relevant to the reason code in the message. Each System Logger request is in a separate section of the guide. The reason codes are described in the topic “Return and Reason Codes” for the IXGWRITE System Logger request.
Control-O or CMEM tries several times to reconnect to the MVS System Logger.
Corrective Action: No action is required.
Explanation: Control-O or CMEM detected an MVS System Logger error, and attempted several times to reconnect to the MVS System Logger, without success.
Corrective Action: No action is required.
Explanation: Control-O or CMEM detected an MVS System Logger error. Either this error was so severe as not to be recoverable, or Control-O or CMEM attempted several times to reconnect to the MVS System Logger, without success.
Control-O or CMEM has stopped attempting to reconnect to the MVS System Logger. The CMEM facility is deactivated.
Corrective Action: If and when the MVS System Logger becomes operational, stop and restart the Control-O or CMEM monitor.
Explanation: Ignore this message. It is an internal message used by Control-O to pass information to Control-M/Links for Distributed Systems executing in a WINDOWS NT machine using MVS console emulation, when Control-O processes a DO CTOPCMSG statement. The message text contains the event that should trigger the rule on Control-M/Links for Distributed Systems.
Corrective Action: No action is required.
Explanation: Ignore this message. It is an internal message used by Control-M/Links for Distributed Systems in a WINDOWS NT machine to satisfy the ON CTOPCMSG event that triggers the rule. Control-M/Links for Distributed Systems passes the information in this message to Control-O using its MVS console emulation.
Corrective Action: No action is required.
Explanation: Ignore this message. It is an internal message used by the CTOJFRQ Control-O IEFJFRQ exit module to trigger a SYSOUT event. The text may include unprintable characters.
Corrective Action: No action is required.
Explanation: This information message indicates that as part of its termination process, the Control-O monitor successfully disabled and removed dynamic exit IEFJFRQ, which uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.
Corrective Action: No action is required.
Explanation: Upon termination, the Control-O monitor failed to disable and remove dynamic the exit IEFJFRQ that uses the CTOJFRQ module. This exit should have been disabled and removed upon monitor termination. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.
Control-O terminates without removing the dynamic exit IEFJFRQ that uses the CTOJFRQ module. This may cause an S0C4 code in various jobs under the subsystem interface. In this case, MVS automatically disables the dynamic exit IEFJFRQ that uses the CTOJFRQ module.
Corrective Action: Inform the system programmer, and check the return code and reason code of macro CSVDYNEX in the IBM manual MVS Programming: Authorized Assembler Services Reference.
Explanation: When Control-O monitor started, it failed to load and enable the IEFJFRQ dynamic exit, which uses the CTOJFRQ module. This exit should have been loaded at monitor startup. Control-O uses the CTOJFRQ module for ON SYSOUT and JES2 command suppression function.
Control-O starts without enabling the IEFJFRQ dynamic exit that uses the CTOJFRQ module. As a result, ON SYSOUT and JES2 command suppression functions will not be active.
Corrective Action: Inform your system programmer.
Explanation: When the Control-O monitor started, it failed to load and activate the dynamic exit IEFJFRQ that uses the CTOJFRQ module. This exit should have been loaded and activated at monitor startup. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.
Control-O starts without enabling the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Therefore, ON SYSOUT and/or JES2 command suppression functions will not be active.
Corrective Action: Inform your system programmer and check the RC and REASON CODE of the CSVDYNEX macro in the IBM OS/390 Authorized Macros and Services Guide.
Explanation: This information message indicates that when the Control-O monitor started, it successfully enabled the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and/or JES2 command suppression function.
Corrective Action: No action is required.
Explanation: This information message displays the message issued from a Control-O rule.
(Note: CTO281I cannot be trapped with an ON MESSAGE rule and therefore it cannot trigger any rule.)
Corrective Action: No action is required.
Explanation: Highlighted, unrollable message.
This information message is activated by the SHOUT facility.
In this message, userId is the user ID of the job order requesting the SHOUT.
Corrective Action: No action is required.
Explanation: Ignore this message. It is an internal message used by the CMEM executor module to trigger a CMEM event using ON DSNEVENT and ON STEP. The text may include unprintable characters.
Corrective Action: No action is required.
Explanation: Control-O stopped job execution due to a DO STOPJOB statement. This message is issued for all DO STOPJOB statements for events, except data set events for an NCT2 disposition.
The steps following the current step are not executed.
Corrective Action: No action is required.
Explanation: The rule identified in the message was suspended because it reached the rule threshold limit, which determines the maximum number of times a rule may be triggered. The rule threshold limit is defined in the THRSHOLD parameter in the CONTROL section of the CTOPARM member in the IOA PARM library.
The rule is suspended.
Corrective Action: Check why the rule reached the limit, and if there is a problem correct it. Adjust the threshold value, if needed, or use the Rule Status screen to release the rule from its SUSPEND state.
Explanation: Control-O could not obtain a free element. Control-O has an internal queuing request mechanism that obtains a request from a free chain, and puts it on one of various work chains. Once processing is complete, the request is returned to the free chain. This message is issued when trying to obtain a free request element, and there are none available.
The request is aborted.
Corrective Action: Inform BMC Customer Support.
Explanation: A rule executed more than 10,000 DO statements. This message is followed by another message containing the name of the problematic rule.
In order to avoid an infinite loop, only a limited number of DO statements can be executed. The default setting is 10,000. You can override this default by setting %%DOLIMIT to a higher value.
The rule is aborted.
Corrective Action: Either correct the rule to perform less than 10,000 DO statements, or set %%DOLIMIT to a higher value.
Explanation: The dateref field in the DO COND statement contains wildcard symbols ($$$$ or ****).
The rule is aborted or ignored.
Corrective Action: Specify a distinct date in the dateref field.
Explanation: The maximum number of nested rules executed in response to a DO RULE statement has been exceeded. Rules can be nested up to 20 deep.
The rule at the twenty first level is aborted or ignored
Corrective Action: Correct the logic so that there are no more than 20 nesting levels for rules.
Explanation: The rule invoked by means of a DO RULE statement was not found in the specified, or default, table.
The rule is aborted or ignored
Corrective Action: Correct the DO RULE statement to contain a rule defined in the specified or default table, or define the rule in the specified table.
Explanation: A rule invoked another rule by using the DO RULE statement did not satisfy the Runtime Scheduling criteria.
Processing continues. The invoked rule is ignored.
Corrective Action: If this is not intentional, correct the invoked rule definition so that it satisfies the Runtime Scheduling criteria.
Explanation: A rule aborted because of an error. This message is preceded by another message that describes the cause of the error.
The rule is aborted at the point of error.
Corrective Action: Correct the error according to the preceding message.
Explanation: This warning message indicates that a problem occurred when processing a rule. This message is preceded by another message that describes the problem.
The rule is ignored. Processing continues.
Corrective Action: Correct the problem according to the preceding message.
Explanation: This information message indicates that the Automation Log subtask began.
Corrective Action: No action is required.
Explanation: The Automation Log subtask detected an error while processing requests.
The subtask and the Control-O or CMEM monitor shut down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.
Corrective Action: Contact your INCONTROL administrator.
Explanation: The Automation Log subtask terminated after an error was detected.
The subtask and the Control-O or CMEM monitor shut down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.
Corrective Action: Contact your INCONTROL administrator.
Explanation: This information message indicates that the Automation Log subtask terminated successfully.
The subtask and the monitor shut down.
Corrective Action: No action is required.
Explanation: The Automation Log subtask attempted to open the Automation Log file but failed.
Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.
Corrective Action: Do the following:
Explanation: The Automation Log subtask failed to open the file referenced by the DAACTLOG DD statement.
The subtask and the Control-O or CMEM monitor shut down. Before shutting down, the Control-O or CMEM monitor attempts to start a new Control-O or CMEM monitor to replace itself. If it does not succeed after a few attempts, Control-O or CMEM ceases trying.
Corrective Action: Check the JCL of your Control-O or CMEM starting procedure to verify that the DAACTLOG DD statement exists. If the problem is not resolved, contact your INCONTROL administrator.
Explanation: The Automation Log subtask was unable to write to the Automation Log file.
Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.
Corrective Action: Contact your INCONTROL administrator.
Explanation: This information message indicates that the Automation Log subtask completed the change of Automation Log status.
This message is displayed in response to the operator command F CONTROLO,AUTOLOG=YES/NO.
The Automation Log subtask writes to the new destination.
Corrective Action: No action is required.
Explanation: The Automation Log subtask detected an error while trying to ENQUEUE the Automation Log file.
Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules are written to the DAACTLOG sysout of the Control-O monitor.
Corrective Action: Contact your INCONTROL administrator.
Explanation: The Automation Log subtask detected an error while trying to dequeue the Automation Log file.
Control-O continues working but now works as if AUTOMLOG was set to N in the CTOPARM member. Subsequent traces of rules will be written to the DAACTLOG sysout of the Control-O monitor.
Corrective Action: Contact your INCONTROL administrator.
Explanation: Highlighted, unrollable message.
The Control-O or CMEM monitor detected a severe shortage of WSC blocks. All WSC blocks were in use simultaneously. This is a severe condition, and must be avoided, because the operation of Control-O may be affected in unexpected ways.
Possible causes are:
The availability of WSC blocks is essential for the monitor to be able to process system events.
This message is issued only the first time there is no free WSC. After the CTO2A7I message indicates that the shortage has been relieved, the CTO2A6S message is deleted and can be issued again.
This message is highlighted, and will be deleted when message CTO2A7I is issued.
The variables in this message are:
For more information, see the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.
As long as all WSC blocks remain in use, the Control-O or CMEM monitor cannot react to events. However, the Control-O or CMEM monitor continues to function and is not terminated.
Corrective Action: Contact your INCONTROL administrator.
Explanation: Highlighted, unrollable message.
A severe shortage of WSC blocks was previously detected by the Control-O or CMEM monitor, and the CTO2A6S message was displayed. As of the last check, at least 25% of the WSC blocks are free. The check is performed every minute, or longer if the Control-O/CMEM INTERVAL parameter is greater than 1 minute.
This message is highlighted, but if another WSC shortage occurs and is then relieved, the message relating to the preceding shortage is deleted.
The variables in this message are:
For more information, see the description of the preceding CTO2A6S message and the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.
Control-O or CMEM resumes normal operation. However, it is possible that information was lost during the period of the shortage, and the shortage may have unexpected effects.
Corrective Action: Contact your INCONTROL administrator.
Explanation:One or more system events occurred of a type which is usually tracked by the Control-O or CMEM monitor. However, because a severe shortage of WSC blocks existed at the time of the events (as indicated by the display of the CTOA6S message), the events are ignored by the Control-O or CMEM monitor.
The variables in this message are:
For more information, see the description of the preceding CTO2A6S and CTO2A7I messages and the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.
The events are ignored, and future events might also be ignored until the shortage of WSC blocks is relieved.
Corrective Action: Contact your INCONTROL administrator.
Explanation: Highlighted, unrollable message.
WSC, RQC, or PND might be soon exhausted, causing serious Control-O/CMEM functional impairment, as follows:
The variables in this message are:
Corrective Action: Contact your INCONTROL administrator.
A Control-O rule may be written so that WSC allocation is increased automatically using the MODIFY SETPARM,WSC#= command. See the INCONTROL for z/OS Administrator Guide.
Also, the WSC#,RQC# and WAITPR# parameters can be increased in CTOPARM, and Control-O/CMEM recycled. See the INCONTROL for z/OS Installation Guide: Installing.
This message is not re-issued until a corresponding relief message (CTO2ABI) for the resource type (WSC/RQC/PND) is issued.
Explanation: 85% utilization of WSC/RQC/PND blocks was previously detected by the Control-O or CMEM monitor, and the CTO2AAW message was displayed. As of the last check, at least 25% of the WSC/RQC/PND blocks are free. The check is performed every minute, or longer if the Control-O/CMEM INTERVAL parameter is greater than 1 minute.
This message is highlighted, but if another WSC/RQC/PND 85% utilization condition occurs and is then relieved, the message relating to the preceding shortage is deleted.
The variables in this message are:
For more information, see the description of the preceding CTO2AAW message and the description of the USAGESTATS command in the INCONTROL for z/OS Administrator Guide.
Corrective Action: Contact your INCONTROL administrator.
Explanation: Control-O failed to activate XCF support. Control-O detected this error while allocating internal storage by means of a STORAGE OBTAIN operation.
In this message, rc is the contents of register R15 from macro STORAGE OBTAIN.
The CTOXCF Control-O program ends with an error.
Corrective Action: Based on the return code, determine the cause of the error, and fix the problem. Restart Control-O to activate XCF support.
Explanation: Control-O detected an error during a STORAGE RELEASE operation. STORAGE RELEASE operations are used to free internal storage.
In this message, rc is the contents of register R15 from the STORAGE RELEASE macro.
The CTOXCF program ends with an error. Control-O fails to start or terminate XCF support.
Corrective Action: Based on the return code, determine the cause of the error, and fix the problem. Restart Control-O.
Explanation: Control-O attempted to initialize an XCF session. The attempt failed. When Control-O begins initializing an XCF session, it observes the session start. If the session starts with status XCF-LOCAL, this message is issued and Control-O does not connect to XCF.
Corrective Action: None, if Sysplex configuration is not needed. However, if Sysplex configuration is needed, configure the session as MONOPLEX or SYSPLEX. For more information, see MVS documentation on initialization and tuning.
Parent Topic |