Messages EXO200 through EXO2xx

This group includes messages for the Control-O CMEM product.

EXO200I {CONTROL-O | CTMCMEM} EXECUTOR STARTED

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

Corrective Action: No action is required.

EXO201I {CONTROL-O | CTMCMEM} EXECUTOR ENDED

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

Corrective Action: No action is required.

EXO202S ERROR ALLOCATING THE SUBSYSTEM-TO- MONITOR COMMUNICATION DATASET

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

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

The Control-O or CMEM monitor shuts down.

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

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

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

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

The Control-O or CMEM monitor shuts down.

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

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

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

The Control-O or CMEM monitor shuts down.

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

EXO205S ERROR ALLOCATING THE MONITOR-TO-SUBSYSTEM COMMUNICATION DATASET

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

Possible causes are:

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

The Control-O or CMEM monitor shuts down.

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

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

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

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

The Control-O or CMEM monitor shuts down.

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

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

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

The Control-O or CMEM monitor shuts down.

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.

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

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

The Control-O or CMEM monitor shuts down.

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.

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

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

The Control-O monitor shuts down.

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

EXO20AS SYSPLEX TABLE MISSING - SYSTEM LOGGER INTERFACE DISABLED

Explanation: CMEM attempted to read the Sysplex Table and could not find the table or encountered errors while reading the Sysplex Table. Possible causes are:

• Sysplex Table is not in the STEPLIB concatenation of load libraries.
• The Sysplex Table has an invalid internal format.
• The Sysplex Table has no valid, active table entries.

CMEM attempts to allocate, open, and use the subsystem-to-monitor (S2M) communication files to implement CMEM-Control-M communication.

Corrective Action: Determine if the Sysplex Table is not in the load library or has an invalid format. Correct the problem and recycle CMEM.

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

Explanation: One of the following System Logger requests failed:

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

CMEM issues r15. Possible values of r15 are:

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

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

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

EXO20CI SYSTEM LOGGER INTERFACE ACTIVATED

Explanation: This information message indicates that CMEM has successfully initialized the System Logger interface. CMEM can now begin communicating with Control-M.

Corrective Action: No action is required.

EXO20CW IOACPRM NOT DEFINED. CMEM FUNCTION IS NOT SUPPORTED

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

Initiation of CMEM fails. The 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.

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

Explanation: During the start up of Control-O or CMEM, 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 the IOACPRM member in the IOA PARM library, and restart the Control-O or CMEM monitor.

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

Explanation: During Control-O or CMEM start up, Control-O or CMEM could not allocate the Subsystem-to-Monitor file, 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 and the definitions for the current system to the IOACPRM in the IOA PARM library, and restart the Control-O or CMEM monitor.

EXO20FE NO CMMPLEX MEMBER. CMEM FUNCTION NOT SUPPORTED

Explanation: During Control-O or CMEM start up, the CMEM Logger facility was required, but the CMMPLEX member containing 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: If the Logger should be used, create the CMMPLX member in the IOA PARM library. If the Logger facility is not required, set the SYSLOGR parameter in the CMEMCOMM section of the IOACPRM member in the IOA PARM library to N. Once the member definitions are correct, restart the Control-O or CMEM monitor.

EXO210E INVALID DATE date IN A DO COND STATEMENT

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

Valid date reference formats are:

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

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

EXO212W CONTROL-O WAITING FOR SUBSYSTEM CONSOLE

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

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

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

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

EXO213E NO VALID SUBSYSTEM CONSOLE EXISTS

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

The command is not executed.

Corrective Action: Make sure that the NUMCONS parameter in CTOPARM is greater than zero, and that the correct number of subsystem consoles is defined in MVS. For information about defining subsystem consoles, 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.

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

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

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

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

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

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

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

This action frees one TSP, and message EXO215I 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.

EXO215I TSO/KSL/SHELL PROCESSING IS RESUMED

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

Corrective Action: No action is required.

EXO216W REQUEST PROCESSING BYPASSED DUE TO CONTROL-O STANDALONE MODE

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

The rule is not ordered.

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

EXO217E COND name date NOT action BY CONTROL-O - SECURITY VIOLATION

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

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

Corrective Action: Contact your INCONTROL administrator.

EXO218E COMMAND cmdName NOT ISSUED BY CONTROL-O - SECURITY VIOLATION

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

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

Corrective Action: Contact your INCONTROL administrator.

EXO219E RUNTIME SECURITY CACHE INITIALIZATION ERROR - rsn

Explanation: This message indicates an internal error.

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

Corrective Action: Contact BMC Customer Support.

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

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

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

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

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

EXO21BE S2M FILE FOR SMFID smfid IS OF ANOTHER INSTALLTION QNAME qName1. IOA QNAME qName2 DSN dsn

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

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

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

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

EXO21CI M2S FILE FOR IOA QNAME qName. DSN=dsn

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

QNAME is defined in the M2S file whose DSN is dsn.

Corrective Action: No action is required.

EXO21DI S2M FILE FOR SMFID smfid QNAME qName DSN=dsn

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

Corrective Action: No action is required.

EXO21EE REPLY ABORT, CONTINUE OR TERMINATE

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

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

Corrective Action: Select one the following responses:

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

EXO21EI THE REPLY TO MESSAGE EX021EE WAS: reply

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

Corrective Action: No action is required.

EXO21ES SUBSYSTEM TO CONTROL-M MONITOR FUNCTION DISABLED

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

CMEM stops with a return code of 8. Control-O issues the message EXO21EE.

Corrective Action: Correct the problem and restart the CMEM monitor, or respond to the EXO21EE message.

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

Explanation: Either Control-O disabled communication with Control-M because of a CONTINUE response to the message EXO21EE, 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.

EXO21GE JOB jobname JOBID jobid DID NOT PERFORM 'DO FORCEJOB' jobname table library

Explanation: The specified Control-O rule failed to perform the specified DO FORCEJOB statement. Details are provided for the Control-O rule and for the job that contains the DO FORCEJOB statement.

This message appears after message EXO21FE. Additional previous messages explain the nature of the failure.

Corrective Action: Use the provided details to correct each occurrence of this failure.

EXO21HE JOB jobname JOBID jobid DID NOT PERFORM 'DO RESOURCE' resource name and size

Explanation: The specified Control-O rule failed to perform the specified DO RESOURCE statement. Details are provided for the Control-O rule and for the resource.

This message appears after message EXO21FE. Additional previous messages explain the nature of the failure.

Corrective Action: Use the provided details to correct each occurrence of this failure.

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

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

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

Corrective Action: Perform the following actions:

1. Eliminate the cause of the delay in event processing by Control-M.
2. Consider increasing the size of the Subsystem-to-Monitor communication dataset.

EXO21JI S2M FILE RECORDS SHORTAGE HAS BEEN RELIEVED

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

Dataset utilization returned to a level below 60%.

Corrective Action: No action is required.

EXO250E RUNTIME SECURITY CLEANUP FAILED, RC=rc

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

Control-O or CMEM continues working.

Corrective Action: Contact BMC Customer Support.

EXO251I RUNTIME SECURITY REFRESH ENDED OK

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

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

Corrective Action: No action is required.

EXO252I SNMP REQUEST HOST=hostname PORT=portNumber SEVERITY=s TEXT=msgText

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

Corrective Action: No action is required.

EXO253E SNMP REQUEST ERROR, RETURN CODE=rc, REASON CODE=rsn

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

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

The DO SNMP request is not sent, and fails.

Corrective Action: Notify the INCONTROL administrator.

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

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

Corrective Action: Contact BMC Customer Support.

EXO255W CONTROL-O SERVER ERROR. SERVER id-rsn

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:

1. Check the sysout of the server in error for the cause of the error.
2. Correct the detected errors, such as errors in the JCL.
3. Restart the server.

EXO256W DO request WAITING FOR id SERVER WAS REROUTED TO IMMEDIATE SERVER

Explanation: A DO KSL, DO TSO, or DO SHELL request waited for a server longer than the QWAIT time specified in the server definition in the CTOPARM member.

The request is routed for execution in an Immediate server.

Corrective Action: To prevent this problem in the future, do one of the following:

• Define more servers.
• Increase the QWAIT time specification.

EXO257E DO request BY USER user WAS CANCELED - SECURITY VIOLATION

Explanation: A DO KSL, DO TSO, or DO SHELL request is not executed, because security exit CTOSE03 detected a security violation. Exit CTOSE03 is invoked for every DO KSL, DO TSO, or DO SHELL request issued by a rule in which value OWNER or TRIGGER is specified for the RUNTSEC parameter.

The DO KSL, DO TSO, or DO SHELL request is not performed.

Corrective Action: Contact your IOA security administrator.

EXO258W DO request WAS DELAYED. NO IMMEDIATE SERVER AVAILABLE

Explanation: A DO KSL, DO TSO, or DO SHELL request designed for an Immediate server cannot be performed because all defined Immediate servers are busy.

The request is executed in the next available Immediate server.

Corrective Action: Consider increasing the number of Immediate servers to be defined. The number of Immediate servers is specified in the SRVIMD# parameter in the CTOPARM member.

EXO259I VM/CP COMMAND EXECUTED, VMRC=rc, COMMAND=vm_cmnd

Explanation: This information message indicates that a DO COMMAND statement specifying the VM CP command vm_cmnd was successfully executed. This message also supplies the return code rc returned by the VM execution.

Corrective Action: No action is required.

EXO25AI TRAN transaction_id action_typ jobnam (jobId) STATUS=stat

Explanation: This information message provides information about a job request that either the Control-O or the CMEM monitor sent to Control-M in the communication file. It is output to the SYSPRINT SYSOUT file of the Control-O or the CMEM monitor. The next message provides more details about the request.

The variables in this message are:

• action_typ - Possible values are: FORCEJOB, RESOURCE, or COND (CMEM) monitor only
• jobnam(jobId) - The kind of job and the specific JES job ID that created the request.
• stat - Possible values are: S (Started), E (Ended), or O (Control-O event, On Spool job)

Corrective Action: Check the message that follows for more information about the job request.

EXO25BI TRAN transaction_id transaction_info

Explanation: This information message provides detailed information about a job request that either the Control-O or the CMEM monitor executed and sent to Control-M in the communication file (S2M). It is output to the SYSPRINT SYSOUT file of the Control-O or the CMEM monitor, and it always follows EXO25AI.

Corrective Action: No action is required.

EXO25CI CTD REQUEST MISSION date FORCE MISSION=missn CATEGORY=catgry

Explanation: This information message is an audit message that logs a DO CTD REQ executed by Control-O. It is always followed by EXO25GI.

Corrective Action: No action is required.

EXO25EE CTDCMI ERROR RETURN CODE=rc, CHECK CONTROL-O MONITOR SYSPRINT OR IOALOG FOR MORE INFORMATION

Explanation: Control-O tried to have Control-D force a mission using a DO CTD REQUEST statement, but the mission was not forced. The Control-D error message should appear on the SYSPRINT monitor or in the IOA log.

The DO CTD REQUEST fails. The mission is not forced.

Corrective Action: Notify the INCONTROL administrator.

EXO25FW MONITOR USE SYSPRINT SYSOUT INSTEAD OF ACTLOG SYSOUT

Explanation: Control-O monitor or CMEM monitor tries to write a message to ACTLOG sysout. The ACTLOG DD statement 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

EXO25GI CTD REQUEST MISSION date FORCE LIBRARY=library

Explanation: This information message is a continuation of message EXO25CI, and includes the library name.

Corrective Action: No action is required.

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

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

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.

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

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

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

Corrective Action: Contact BMC Customer Support.

EXO25JS UPDATING LOAD-INDEXES BASED ON MAINVIEW ALARMS STOPPED

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

Corrective Action: See message EXO25HE or message EXO25IE.

EXO25KI UPDATING OF LOAD-INDEXES BASED ON MAINVIEW ALARMS STARTED

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

Corrective Action: No action is required.

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

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

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

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

EXO260E EXECUTION OF VM/CP COMMAND ABORTED. RC=rc

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

The specified command is ignored.

Corrective Action:The user response depends on the value of the return code (rc). The following table displays possible values for rc, together with their explanations and the appropriate user action.

EXO261I ATTEMPTING TO RECONNECT TO MVS SYSTEM LOGGER DUE TO ERROR rsn

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

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

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

Corrective Action: No action is required.

EXO262E ATTEMPT TO RECONNECT TO MVS SYSTEM LOGGER FAILED

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

Corrective Action: No action is required.

EXO263E MVS SYSTEM LOGGER ERROR - CMEM FEATURE DISABLED

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

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

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

EXO264E INCORRECT PORT PARAMETER portNumber WAS SPECIFIED. ONLY NUMERIC VALUE IS ALLOWED

Explanation: Control-O tried to send an SNMP request using a port number parameter (portNumber) that was incorrect.

The DO SNMP request is not sent, and fails.

Corrective Action: Ensure that a correct port number is specified. Only numeric characters (from 0 through 9) are allowed.

EXO281I user_message

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

Corrective Action: No action is required.