|
|
|
|
|
This group includes messages for the Control-O product.
Explanation: This information message is a normal message issued when the Control-O or CMEM monitor is started. The version of the monitor that is starting (x.x.xx) is indicated in the message text.
Corrective Action: No action is required.
Explanation: During initialization self-checks, the Control-O or CMEM monitor discovered that a storage key was specified that was not in the range from 1 through 7. The Control-O or CMEM monitor only works using storage keys 1 through 7.
The monitor terminates.
Corrective Action: Perform the following steps:
Explanation: This information message indicates that during Control-O monitor startup, an installed Control-D was detected. Therefore, Control-D functionality using DO CTD REQ was enabled.
Corrective Action: No action is required.
Explanation: The Control-O or CMEM monitor has lost APF-authorization. Possible causes are:
The Control-O or CMEM monitor shuts down.
Corrective Action: Make sure that the IOA Load library is authorized, and restart Control-O or CMEM.
Explanation: An invalid parameter was passed to the Control-O or CMEM monitor by an operator modify (F) command. This is a header message for message CTO125I. A list of valid modify parameters is displayed on the operator console in message CTO125I.
The modify command is rejected.
Corrective Action: Enter a valid modify parameter.
Explanation: During Control-O monitor startup, no installed Control-D was detected. Therefore, Control-D functionality using DO CTD REQ was disabled.
Monitor startup continues.
Corrective Action: Notify your INCONTROL administrator.
Explanation: Initialization of one of the Control-O or CMEM monitor internal tasks failed.
Possible causes are:
The Control-O or CMEM monitor shuts down.
Corrective Action: Call your systems programmer for assistance. If necessary, increase the Control-O or CMEM REGION size.
Explanation: An unrecoverable error occurred in the operation of the Control-O or CMEM monitor.
The IOA Log usually contains a previous message concerning the error.
The Control-O or CMEM monitor shuts down with user abend 0006.
Corrective Action: Call your systems programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.
Explanation: The Control-O or CMEM monitor internal taskNamehas abended.
The Control-O or CMEM monitor shuts down.
Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support for assistance.
Explanation: This information message indicates that the Control-O or CMEM monitor is shutting down upon operator request.
The Control-O or CMEM monitor is shut down.
Corrective Action: No action is required.
Explanation: Control-O or CMEM monitor could not establish the cross memory environment required for its operation.
Corrective Action: Call your systems programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance and provide the step name indicated in the message.
Explanation: This information message indicates that a new Control-O or CMEM monitor has been started. This message is issued by the previous Control-O or CMEM monitor to indicate that it is shutting down.
The Control-O or CMEM monitor that was operating previously shuts down.
Corrective Action: No action is required.
Explanation: This information message indicates that during Control-O or CMEM monitor startup, Control-M was detected, and therefore, Control-M functions DO FORCEJOB and DO RESOURCE were enabled.
Corrective Action: No action is required.
Explanation: During Control-O or CMEM monitor startup, Control-M functions DO FORCEJOB and DO RESOURCE were disabled because no installed Control-M was detected.
Monitor startup continues.
Corrective Action: Notify the INCONTROL administrator.
Explanation: During the startup of the Control-O monitor, it was found that the value of the DAYTIMEO Control-O parameter was not identical with the value of the DAYTIMEM Control-M parameter.
The DAYTIMEO Control-O parameter sets the start of the work day for Control-O. The DAYTIMEM Control-M parameter sets the start of the work day for Control-M. Any discrepancy between these two parameters may result in the same time being interpreted differently by Control-O and Control-M.
The variables in this message are:
Monitor startup continues.
Corrective Action: Contact your INCONTROL administrator.
Explanation: An invalid date was specified in the ORDER or FORCE modify command. If a date (D) is specified in the ORDER or FORCE modify (F) operator command, it must have a valid site-dependent format.
Valid formats are:
The command is not executed.
Corrective Action: Issue the command with the correct date.
Explanation: The Control-O or CMEM subsystem initialization routine is running under a CPU that was not defined in the IOACPRM member.
Possible causes are:
The Control-O or CMEM monitor shuts down.
Corrective Action: Do the following:
Explanation: This message is received when you attempt to run FORMSUB3 (typically, when adding a new system), and the SYSTEM LOGGER is active (that is, the System Logger manages the communication between Control-M CMEM or Control-O and the subsystems). In such a scenario, there is no need to update the Monitor-to-Subsystem file.
Corrective Action: No action is required.
Explanation: This information message is produced by Control-O or CMEM when shutting down the Control-O or CMEM monitor by a P command, or on certain internal Control-O or CMEM events.
The IOA Log usually contains additional messages concerning the reason for the Control-O or CMEM shutdown.
Control-O or CMEM monitor shuts down.
Corrective Action: No action is required.
Explanation: Highlighted, unrollable message.
A severe error has occurred. Control-O or CMEM monitor is shutting down.
The IOA and systems logs usually contain additional messages concerning the reason for the Control-O or CMEM shutdown.
Control-O or CMEM monitor shuts down. Before shutting down, the Control-O or CMEM monitor attempts to start a new CONTROLO or CMEM monitor to replace itself. If it cannot start after a few attempts, Control-O or CMEM gives up.
Corrective Action: Check the IOA and systems logs for additional messages, and take appropriate corrective action.
Explanation: Control-O or CMEM was unable to acquire enough storage in ECSA for the specified control block ( blockname).
Control-O acquires storage in ECSA for its working areas (WSC), and for wait elements (PND). The number of wait elements is specified by the WAITPR# parameter in the CTOPARM member.
CMEM acquires storage in ECSA for its working areas (WSC).
In this message, rcis the return code issued by the failed GETMAIN call.
Control-O or CMEM terminates.
Corrective Action: Check ECSA utilization of the system. For Control-O, if necessary, reduce the number of wait elements specified by the WAITPR# parameter in the CTOPARM member.
Explanation: This information message is a result of setting a Control-O or CMEM sleeping interval by an operator command.
For more information, see the section on modifying the Control-O or CMEM sleeping interval in the INCONTROL for z/OS Administrator Guide.
Control-O or the CMEM monitor will “wake up” every nnseconds and check on time-related events.
Corrective Action: No action is required.
Explanation: An invalid Control-O or CMEM sleeping interval was specified in an operator modify (F) command. The Control-O or CMEM sleeping interval must be a 2-digit number of seconds, from 01 through 99 seconds. For more information, see the section on modifying the Control-O or CMEM sleeping interval in the INCONTROL for z/OS Administrator Guide.
Corrective Action: No action is required.
Explanation: When the Control-O monitor starts, it checks to ensure that the values of the parameters in CTOPARM are within the valid range. One of the parameters ( parmName) is set to a value ( parmValue) that is either too high (>) or too low (<).
Control-O resets the value of parmNameto the default value for that parameter, and the monitor continues its startup.
Corrective Action: Correct the value of parmNamein CTOPARM. If required, stop and restart the Control-O monitor.
Explanation: This information message provides a list of valid modify parameters that can be passed to the Control-O or CMEM monitor by an operator modify (F) command. This message appears after header message CTO125I.
Corrective Action: No action is required.
Explanation: During the startup of the Control-O monitor or the execution of a NEWDEST command, the Dynamic Destination table was not successfully loaded or renewed.
Monitor startup or operation continues. The Dynamic Destination table is not loaded or renewed. DO SHOUT requests will not be performed.
Corrective Action: Contact your INCONTROL administrator.
Explanation: This information message is a result of the acceptance of an operator NEWDEST command passed to the Control-O or CMEM monitor.
A new dynamic destination table is loaded. The next time that the Control-O or CMEM monitor sends a message using the SHOUT facility, it will use the new destination table.
Corrective Action: No action is required.
Explanation: Normal response of the Control-O or CMEM monitor after the DISPLAY command is issued. This information message is the header of the list of rules being shown in response to the DISPLAY command.
Corrective Action: No action is required.
Explanation: Messages sent by the Control-O or CMEM monitor to the console in response to the DISPLAY command. Each message describes a rule. These information messages are preceded by the MTO128I or CTO128I message, which supplies the header for each field.
Corrective Action: No action is required.
Explanation: This information message is issued by the Control-O monitor when it enables or disables optional wish WO0949.
Corrective Action: No action is required.
Explanation: This information message is issued by the Control-O monitor when it enables optional wish WO0975.
Corrective Action: No action is required.
Explanation: This information message is issued by the Control-O monitor when it disables optional wish WO0975.
Corrective Action: No action is required.
Explanation: This information message is issued by the Control-O monitor when it enables optional wish WO0976.
Corrective Action: No action is required.
Explanation: This information message is issued by the Control-O monitor when it disables optional wish WO0976.
Corrective Action: No action is required.
Explanation: This message is a header for a detailed list of rules generated by the Control-O monitor or CMEM monitor in response to the following commands:
For more information about the generated list of rules, see "Displaying Active Rules" in the Control-O chapter or the Control-M chapter (for CMEM) in the INCONTROL for z/OS Administrator Guide.
Corrective Action: No action is required.
Explanation: Messages sent by the Control-O monitor to the console in response to the DISPLAY command. The message describes the prerequisite conditions necessary for the rule to become eligible.
Corrective Action: No action is required.
Explanation: Messages sent by the Control-O monitor to the console in response to the DISPLAY command. This information message describes the time dependencies required by the specific rule in order to become eligible.
Corrective Action: No action is required.
Explanation: The Control-O monitor accepted an F CONTROLO,CTMAPISTOP command.
The monitor confirms it received the command for execution.
Corrective Action: No action is required.
Explanation: The Control-O monitor successfully processed an F CONTROLO,CTMAPISTOP command.
The monitor confirms it executed the command.
Corrective Action: No action is required.
Explanation: This information message is displayed when Control-O or CMEM changes the working date.
In Control-O, the time is set according to the DAYTIMEO parameter in the CTOPARM member. In CMEM, the time is set according to the DAYTIMEO parameter in the CMMPARM member, which must be the same as the DAYTIMEM parameter in the CTMPARM member.
Control-O or CMEM monitor displays the new date.
Corrective Action: No action is required.
Explanation: This information message indicates that the Control-O or CMEM debug level was set by an operator modify (F) command.
The DEBUG level is set to a new level. Each debug level activates the trace option on different components of Control-O or CMEM.
Corrective Action: No action is required.
Explanation: An invalid DEBUG level has been entered in the modify (F) operator command to activate Control-O or CMEM debugging facilities. Valid DEBUG levels are from 0 through 255. 0 specifies no debugging.
Issue the command with the correct debugging level. The required debugging level should be supplied by BMC Customer Support.
Corrective Action: No action is required.
Explanation: The Control-O monitor successfully processed anF CONTROLO,CTMAPISTART command.
Corrective Action: The monitor confirms that it executed the command, and that the next API request will reallocate the API resources (such the Control-M Active Job File or Control-M Resources file).
Explanation: One or more parameters passed to the Control-O or CMEM monitor in a start command are invalid.
The Control-O or CMEM monitor shuts down.
Corrective Action: For additional information regarding starting a Control-O or CMEM monitor, see the INCONTROL for z/OS Administrator Guide. Check and correct the parameters, and start the Control-O or CMEM monitor again.
Explanation: This is one of two messages with the same ID, but different text.
This information message indicates that the command MODE=RESUME,CANCEL, the command MODE=RESUME,CONTINUE, or a query about Control-O current status was issued.
Control-O resumes automatic processes.
Corrective Action: No action is required.
Explanation: This is one of two messages with the same ID, but different text.
The Control-O monitor successfully processed an F CONTROLO,CTMAPISTART command, but failed. Either the monitor has already processed this command and also processed its first API request, or the monitor processed a CTMAPISTOP command since it was started, and it already has processed API requests.
Corrective Action: No action is required.
Explanation: This information message indicates that the subsystem cannot be activated or initialized because it has already been activated. This is a normal message during subsystem initialization, when Control-O or CMEM determines that a subsystem was already activated by a previous monitor.
A new subsystem is not activated.
Corrective Action: No action is required.
Explanation: Wish WO0986 was used in earlier Control-O releases to suppress message LDT507I from being written to the IOALOG. As of Control-O 6.2.01, the same functionality is obtained using the standard IOA Messages routing function.
The wish is ignored and Control-O or CMEM monitor starts. If you do not perform the following steps, message LDT507I will be written to the IOALOG.
Corrective Action: Perform one of the following options:
Explanation: This information message is displayed at midnight when the date is changed.
Corrective Action: No action is required.
Explanation: This information message is issued by the Control-O monitor when it enables optional wish O10261.
Corrective Action: No action is required.
Explanation: Highlighted, unrollable message
This information message indicates that Control-O issued a MODE=FREEZE, MODE=LOGONLY or MODE=TRIGGERONLY command. The Control-O internal log indicates any rules that failed to run.
Control-O automatic processes act as follows:
Corrective Action: Possible responses are:
Explanation: Highlighted, unrollable message.
This message is issued when the Control-O or CMEM monitor is cancelled by an operator MVS cancel command.
The Control-O or CMEM monitor is shut down.
Corrective Action: No action is required.
Explanation: This message is issued when Control-O or CMEM has detected certain internal system abend codes during operation.
The Control-O or CMEM monitor shuts 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 cannot start after a few attempts, Control-O or CMEM ceases trying.
Corrective Action: Call you systems programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.
Explanation: This information message occurs after Control-O or CMEM detected an internal problem and started a new monitor as a recovery measure.
A new Control-O or CMEM monitor is started, and takes control over the current one.
Corrective Action: Check for additional messages in the IOA and system logs detailing the cause of the abend.
Explanation: An invalid syntax of ORDER or FORCE commands was passed to the Control-O or CMEM monitor by an operator modify (F) command. See the INCONTROL for z/OS Administrator Guide for additional information regarding the parameters of the ORDER or FORCE command.
The command is not executed.
Corrective Action: Correct the syntax of the ORDER or FORCE command.
Explanation: The Control-O or CMEM monitor failed to perform an AutoEdit function.
The problem was probably caused by a failure to read or write the global AutoEdit member, or invalid data in the global AutoEdit member.
The AutoEdit function is not performed.
Corrective Action: Consult the table of return codes and reason codes in the following table to determine the cause of the error, and correct accordingly. If the return code or reason code is not in the table, the cause of failure is an internal error. In this case, contact BMC Customer Support.
Return Code ( rc) |
Reason Code ( rsn) |
Explanation |
|---|---|---|
04 |
GETMAIN or FREEMAIN error |
|
|
1 through 6 |
GETMAIN failure |
|
7 through 10 |
FREEMAIN failure |
08 |
Variable not found |
|
|
13 |
Variable not found and RESOLVE flag is on. |
|
36 |
%%$COMMSYS value length error. |
|
68 |
%%$TIMEINT first argument is not a valid date. |
|
69 |
%%$TIMEINT second argument is not a valid date. |
|
74 |
%%$X2C argument length is greater than 4. |
|
88 |
%%$DOLIMIT first argument is not numeric. |
|
89 |
%%$RULE functions argument is out of rule stack. |
|
90 |
%%$RULE functions argument is not numeric. |
|
98 |
Global variable pool not found. |
|
980 |
Internal error - global pool or database not found |
|
982 |
Internal error - global pool or database not found |
12 |
Syntax error or general error |
|
|
11 |
Empty SET command. |
|
15 |
Empty IF command. |
|
21 |
%% not found in SET command. |
|
22 |
Separator not found after %%. |
|
23 |
‘=’ not found in SET command. |
|
24 |
%%$TIMEOUT value not numeric. |
|
25 |
%%$RESPMSG or %%$TIMEOUT - invalid parentheses. |
|
26 |
%%$RESPMSG or %%$TIMEOUT - too many values. |
|
27 |
%%$WAITKSL or %%$TSO or %%$CMD - invalid value (not YES/NO). |
|
28 |
%%$TIMEOUT - value too large. |
|
29 |
%%$‘STATID value length error. |
|
30 |
%%$AUTOLOG value length error. |
|
37 |
%%$AUTOSYS value length error. |
|
41 |
Function arguments not separated. |
|
42 |
Too few function arguments. |
|
45 |
CTMLINE# PARAMETER NOT NUMERIC when trying to set %%$CTMLINE# to a non-numeric value. |
|
46 |
CTMLINE# > CTMLINES when trying to set %%$CTMLINE# to a value greater than %%$CTMLINES. |
|
47 |
CTMLINE# < 0 when trying to set %%$CTMLINE# to a value less than 0. |
|
52 |
%%$SUBSTR 2nd argument not numeric. |
|
53 |
%%$SUBSTR 3rd argument not numeric. |
|
54 |
%%$SUBSTR 2nd argument out of range. |
|
55 |
%%$SUBSTR 3rd argument out of range. |
|
56 |
%%$RESOLVE argument not recognized. |
|
57 |
%%$RANGE 1st argument not numeric. |
|
58 |
%%$RANGE 2nd argument not numeric. |
|
59 |
%%$RANGE 1st argument out of range. |
|
60 |
%%$RANGE 2nd argument out of range. |
|
61 |
%%$RANGE is too narrow. |
|
62 |
%%$CALCDATE 1st argument not in valid format. |
|
63 |
%%$CALCDATE 2nd argument not in valid format. |
|
64 |
%%$TIMEINT 1st argument is not 11 digits in length. |
|
65 |
%%$TIMEINT 1st argument is not numeric. |
|
66 |
%%$TIMEINT 2nd argument is not 11 digits. |
|
67 |
%%$TIMEINT 2nd argument is not numeric. |
|
71 |
More than one operator in one line. |
|
72 |
Less than two operands for an operator. |
|
73 |
More than two operands for an operator. |
|
75 |
%%$D2X argument length is greater than 10. |
|
76 |
%%$D2X argument is not numeric. |
|
77 |
%%$D2X argument number is greater than 2147483647 (2G). |
|
78 |
%%$X2D argument length is greater than 8. |
|
79 |
%%$X2D argument has an invalid character. |
|
81 |
First operand in arithmetic operation is not numeric. |
|
82 |
Second operand in arithmetic operation is not numeric. |
|
83 |
%%$DIV 2nd operand is 0. |
|
84 |
First operand is greater than 2G. |
|
85 |
Second operand is greater than 2G. |
|
86 |
Result of %%$PLUS case overflow. |
|
87 |
Result of %%$MINUS case overflow. |
|
91 |
Logical operand not numeric. |
|
92 |
Numeric logical operand out of range. |
|
93 |
Invalid logical operator. |
|
94 |
Logical atomic expression expected but not found. |
|
95 |
Unbalanced parentheses in logical expression. |
|
96 |
Too many nested parentheses in logical expression. |
|
97 |
Unbalanced quotes. |
|
99 |
%%$GLOBAL value length error. |
16 |
Errors reading the global member |
|
|
08 |
Insufficient memory. |
|
12 |
Member not found. |
|
16 |
DSN is not a library. |
|
20 |
DSN is not fixed. |
|
24 |
Logical record length is not 80. |
|
28 |
Data set in use. |
|
36 |
Data set not in catalog. |
|
40 |
Dynamic allocation failed. |
|
52 |
Error when opening/processing a directory |
|
56 |
An abend was intercepted. |
20 |
Errors writing the global member |
|
|
08 |
Insufficient memory. |
|
12 |
Member not found. |
|
16 |
DSN is not a library. |
|
20 |
DSN is not fixed. |
|
24 |
Logical record length is not 80. |
|
28 |
Data set in use. |
|
36 |
Data set not in catalog. |
|
40 |
Dynamic allocation failed. |
|
52 |
Error when opening/processing a directory |
|
56 |
An abend was intercepted. |
24 |
Program buffers shortage |
|
|
12 |
Not enough space in RSL buffer. |
|
32 |
Not enough space in VCB for name and value. Variable name and data are too long. |
|
43 |
Arguments too long (ARG buffer overflow). |
32 |
Program errors |
|
|
100 |
No last non-blank for non-blank value in SET command. |
|
101 |
No succeeding RSL for adjoining variables. |
|
102 |
Problems in PUTVAR while initiating. |
|
103 |
Too many arguments requested from PARSARGS. |
|
104 |
Problems calculating weekday. |
|
105 |
Invalid SET system variable. |
|
106 |
No local anchor was passed. |
|
107 |
No global anchor was passed. |
|
109 |
No MCT or SWT present in %%$IPLDATE for date formatting WO0816*. |
36, 40, and 44 |
Global variables errors |
|
|
04 |
Empty chain. |
|
08 |
End of chain. |
|
12 |
PNXH header error. |
|
16 |
PLBH header error. |
|
20 |
CTMMSK mash error, RC from IS is > 4. |
|
24 |
Pool is protected. |
|
32 |
Unable to get XAE information. |
|
33 |
Machine is not participating on XAE. |
|
34 |
Attempt made to set an XAE type 1 database variable in another system image. |
|
98 |
Pool not found. |
|
107 |
No global anchor was passed. Program error. |
|
108 |
Field not defined in database. |
|
109 |
Requested row is out of range. |
48 |
Parse errors |
|
|
08 |
Invalid type. |
|
12 |
Place holder error. |
|
16 |
Position specification too long. |
|
20 |
Non numeric. |
|
24 |
Position null. |
|
28 |
Invalid variable. Specified variable is greater than 256, or the variable name is too long. |
|
32 |
String error. |
|
36 |
Invalid TPE type. |
|
40 |
Section vector overflow. |
|
44 |
Variable buffer overflow. |
|
107 |
No global anchor was passed. |
Explanation: During Control-O initialization, a Global AutoEdit member or its library was not found.
When Control-O is started, it reads the $GLOBAL member. A different Global library (in which a $GLOBAL AutoEdit member resides) is used for each computer (SMFID) on which Control-O operates. Each unique library name is composed of the prefix defined in the GLBPREF parameter of the Control-O installation parameters, and as the last data set name qualifier, the letters CPU followed by the SMFID of the specified computer.
Although Control-O will process Global variables, it will not read or write to this particular Global member/library.
Corrective Action: Check the designation of the GLBPREF parameter in the Control-O installation parameters. You must allocate a Global AutoEdit library for every computer in which Control-O runs. See “Control-O Operational Parameters” in the Control-O chapter of the INCONTROL for z/OS Installation Guide.
Explanation: This information message indicates that Control-O or CMEM initialization has completed successfully and Control-O or CMEM facilities are active.
The variables in this message are:
Control-O or CMEM facilities are now active.
Corrective Action: No action is required.
Explanation: Control-O received the F CONTROLO,STARTSTAT command to start the Message Statistics facility, but the facility was already active.
The STARTSTAT command is ignored.
Corrective Action: No action is required.
Explanation: Control-O received the F CONTROLO,STOPSTAT command to stop the Message Statistics Facility, but the facility was not active.
The STOPSTAT command is ignored.
Corrective Action: No action is required.
Explanation: Control-O or the CMEM monitor received the modifyCommand command with an invalid keyword.
The modifyCommand command is rejected.
Corrective Action: Correct the invalid command and reissue it.
Explanation: This information message is in response to the modify SVCDUMP command, and indicates that a valid keyword has been enabled.
Corrective Action: No action is required.
Explanation: This information message is in response to the modify SVCDUMP command, and indicates that a valid keyword has been disabled.
Corrective Action: No action is required.
Explanation: The Control-O XES subtask CTOXOH has resumed normal execution after abending while trying to purge an XES request that was pending for excessively long time.
An SVCDUMP is generated for the first occurrence of this abend.
Corrective Action: Send the dump to BMC Customer Support for investigation.
Explanation: Control-O or CMEM cannot shut down when an XAE structure is unavailable due to system-managed rebuild. Control-O will resume its termination process when the system-managed process finishes and the structure becomes available again.
When FORCE is replied, Control-O or CMEM will continue termination without waiting for the system-managed process to finish and the XAE structures to become available. Beware that after forcing immediate termination, the following may occur:
Corrective Action: None, unless immediate termination is required. If immediate termination is required, reply FORCE.
See System action for considerations before replying FORCE.
Explanation: The operator replied CANCEL to message IOAFBCW to cancel Control-O or CMEM initialization, after connection to an XAE structure was prevented.
Control-O or CMEM terminates.
Corrective Action: Start Control-O or CMEM after making sure that:
Explanation: A request to the XES AutoEdit facility (XAE) to either put or get a variable from an S1 or S2 database (typically IOAVAR) has failed. The failure might have been caused by either a Coupling Facility-related error or by a Control-O/CMEM internal error.
An SVCDUMP is generated for the first occurrence of this failure.
Corrective Action: Review the SYSLOG, which may contain Coupling Facility-related error messages. If the problem persists, consider starting a new Control-O/CMEM monitor over the old one. Send the dump to BMC Customer Support for investigation.
Explanation: This information message indicates that Control-O or CMEM successfully executed the F CONTROLO,SNAP or F CMEM,SNAP command.
In this message, id is the snap ID as shown in the snap title.
A set of diagnostic snapshots is printed.
Corrective Action: No action is required.
Explanation: Control-O or CMEM was unable to write messages to the IOA Log file. This message follows other messages indicating the cause of the error.
Processing continues. Some messages to the IOA Log file may be lost.
Corrective Action: Check the preceding messages and act accordingly.
Explanation: This information message indicates that Control-O is now entering standalone mode and will now update the IOA Log file.
When Control-M is active, update of the IOA Log file is performed by Control-M. When Control-M is not installed or inactive, update of the IOA Log file is performed by Control-O.
Control-O enters standalone mode and updates the IOA Log file.
Corrective Action: No action is required.
Explanation: This information message indicates that Control-O is exiting standalone mode.
When Control-O is in standalone mode, it updates the IOA Log file. When Control-M becomes active, Control-M takes over the updating of the IOA Log file.
Control-O exits standalone mode and Control-M takes over the updating of the IOA Log file.
Corrective Action: No action is required.
Explanation: Control-O was set to run with SMODE set to N, but Control-M, which must execute some activities on behalf of Control-O, is not installed. If the SMODE (Stand Alone mode) installation parameter is set to N, Control-M must be installed. If Control-M is not installed, SMODE must be set to Y.
Control-O terminates.
Corrective Action: Either install Control-M, or set the SMODE installation parameter to Y.
Explanation: Control-O is unable to pass internal request blocks to the new Control-O monitor.
This message indicates an internal error.
The old Control-O monitor terminates with an error. The new monitor, however, will continue processing. Some requests may be lost.
Corrective Action: Contact BMC Customer Support.
Explanation: This warning message is issued in response to an invalid AUTOLOG MODIFY command. Either the specified parameter is invalid, or the user specified a MODIFY command (F CONTROLO,AUTOLOG=YES/NO) designed to set the Automation Log status to a status that it already had.
The status of writing to the Automation Log is unchanged.
Corrective Action: Verify the command and retry if necessary.
Explanation: This information message indicates that Control-O has begun performing the action requested in a SERVER MODIFY command.
Corrective Action: No action is required.
Explanation: Control-O was unable to execute the requested SERVER MODIFY command (action).
Processing continues. The status of the server remains unchanged.
Corrective Action: Check the reason specified in the message and proceed accordingly.
Explanation: This message is issued in response to a SERVER MODIFY command with invalid parameters.
Processing continues. The command is ignored.
Corrective Action: Specify the MODIFY command with valid parameters.
Explanation: The operator specified an invalid SNAP keyword in an F CONTROLO,SNAP/F CTMCMEM,SNAP command.
The CTOMTO program ignores this keyword. If there was only one keyword, no SNAP request is performed.
Corrective Action: Specify an F CONTROLO,SNAP/F CTMCMEM,SNAP command with valid keywords. For more information, see the SNAP command in the INCONTROL for z/OS Administrator Guide.
Explanation: This information message is an internal message generated by Control-O.
An internal Control-O process is triggered.
Corrective Action: No action is required.
Explanation: The CTOMTO program detected an invalid keyword for the LOG request. Valid keywords are:
The CTOMTO program ignores this LOG command request.
Corrective Action: Resubmit the F CONTROLO,LOG/F CTMCMEM,LOG command with a valid keyword.
Explanation: This information message indicates that Control-O or CMEM have successfully executed the F CONTROLO,LOG command.
Rules will be traced according to the new log mode.
Corrective Action: No action is required.
Explanation: This Control-O or CMEM message displays statistics in response to a WATERMARKS command.
The variables in this message are:
Note:
The WATERMARKS command is currently supported for compatibility reasons only. More detailed statistical information about the usage of internal resources is available by means of the USAGESTATS command. For more information, see the INCONTROL for z/OS Administrator Guide.
Corrective Action: No action is required.
Explanation: Loading of the exitNameControl-O user exit by Control-O failed. Possible causes are:
As a result, no user checking is performed for the rule order.
Corrective Action: Contact your INCONTROL administrator. This is a potential security risk. Someone may be attempting to violate security.
Explanation: This message displays usage statistics relating to internal Control-O or CMEM resources in response to a USAGESTATS command.
The variables in this message are:
Corrective Action: In normal circumstances, highp should remain below 50%. If you notice higher usage percentages, contact your INCONTROL administrator. Possible causes are:
Explanation: A USAGESTATS command was issued, to display usage statistics relating to internal Control-O or CMEM resources. However, the command contained an invalid argument.
In this message, arg is the invalid argument of the USAGESTATS command.
For more information on the USAGESTATS command, see the INCONTROL for z/OS Administrator Guide.
Corrective Action: Reissue the command in a valid format.
Explanation: A modify command F CONTROLO,SERVER= server,command has been issued for a server which has not been defined.
The command is ignored.
Corrective Action: Specify the correct server name.
Explanation: This information message indicates the start of the Control-O Selector task, which controls the runtime selection criteria for rules.
Corrective Action: No action is required.
Explanation: This information message indicates normal termination of the Control-O Selector task that controls the runtime selection criteria for rules.
Corrective Action: No action is required.
Explanation: This internal message triggers an ON EVENT rule after the criteria for triggering the rule have been satisfied. The text may include unprintable characters.
Corrective Action: No action is required.
Explanation: This information message indicates the successful completion of a Control-O ORDER, FORCE, DELETE, READGLOBAL, or WRITEGLOBAL command.
Corrective Action: No action is required.
Explanation: Open of IOA Conditions or Resources file failed (the DARESF or DASINC DD statement).
Possible causes are:
Control-O monitor shuts down with error message.
Corrective Action: Correct the JCL for the Control-O procedure, and restart the monitor.
Explanation: An internal error occurred while the cond condition was being processed.
The Control-O monitor is terminated.
Corrective Action: Contact BMC Customer Support.
Explanation: Highlighted, unrollable message.
There is no more space for adding output conditions to the IOA Conditions file.
The record for the specified day of the month is full. For example, if a condition with date reference of January 3rd cannot be added, an entry in the conditions file which contains conditions for January 3rd, February 3rd, March 3rd, and so on, is full.
The format for the date specified in this message is mmdd.
The condition is not added. A highlighted message is displayed on the operator console. Control-O or CMEM continues to function, but the rules that depend on the condition may not be triggered.
Corrective Action: Perform the following immediate actions and then perform the long term actions described below.
Immediate actions:
Long term actions:
Explanation: This information message indicates that the user requested an action that has already been performed.
The user either tried to add a condition that already exists or tried to delete a condition that had already been deleted.
Corrective Action: No action is required.
Explanation: A DO COND statement in a rule requested the addition of the specified condition with date **** or $$$$. This date specification is valid only when conditions are being deleted.
The DO COND request is not performed.
Corrective Action: Correct the DO COND statement.
Explanation: All Statistics file index entries are in use. No new statistics can be accumulated.
The Statistics Facility could not accumulate statistics because the number of message ID’s exceeds the maximum number of allowable entries in the Statistics file.
Statistics accumulation stops.
Corrective Action: Please review the following recommendations; then format the Statistics file and restart the Statistics Facility:
Explanation: The Statistics file is locked.
Either the Statistics file is in use by another Control-O monitor or utility, or Control-O abended previously while updating the Statistics file.
Statistics accumulation is not performed.
Corrective Action: Check if another Control-O monitor or utility uses this Statistics file. If this is not the case, then reformat the Statistics file and restart the Statistics Facility.
Explanation: The Control-O Statistics facility attempted to open the Statistics file but did not succeed.
Failure to open the Statistics file may be due to the following:
Statistics accumulation is not performed.
Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.
Explanation: The Control-O Statistics Facility attempted to read the file allocated to DD name DASTF, but it is not a formatted Statistics file.
Statistics accumulation is not performed.
Corrective Action: Format the Statistics file and restart the Statistics Facility.
Explanation: The format of the Statistics file is not supported by the current release of Control-O. The Statistics file could not be read by the Control-O Statistics Facility.
The Statistics file was formatted by an earlier release of Control-O.
Statistics accumulation is not performed.
Corrective Action: Format the Statistics file in the currently supported format, and restart the Statistics Facility.
Explanation: The assigned ID of the Statistics file does not match the ID of the Control-O monitor.
When a Statistics file is formatted, it is associated with a particular Control-O monitor. The CTOMFST Statistics Formatting utility takes the ID of the Control-O monitor from the QNAME parameter of CTOPARM, and assigns it to the Statistics file.
The ID of the active Control-O monitor does not match the assigned ID of the Statistics file. The likely cause of the error is that the value of QNAME was changed without reformatting the Statistics file.
Statistics accumulation is not performed.
Corrective Action: Format the Statistics file with the correct Control-O ID and restart the Statistics Facility.
Explanation: The Control-O Statistics Facility encountered an internal error.
In this message, code is the internal error code.
Statistics accumulation stops.
Corrective Action: Look for previous messages to identify the cause of the problem and contact BMC Customer Support.
Explanation: Storage allocation for the Control-O Statistics Facility failed because the Statistics Facility could not obtain enough working storage for processing.
Statistics accumulation is not performed.
Corrective Action: Increase the Control-O region size and restart a new Control-O monitor.
Explanation: A READ/WRITE error occurred when accessing the Statistics file.
Statistics accumulation stops.
Corrective Action: Look for previous MVS error messages regarding Statistics file I/O errors, and correct accordingly. If MVS messages do not clarify the error, please contact BMC Customer Support.
Explanation: The Statistics Facility has encountered a corruption in the Statistics file. The Statistics file cannot be processed.
Statistics accumulation stops.
Corrective Action: Contact BMC Customer Support.
Explanation: Due to an internal error, update of the Statistics file failed while writing a section of the Statistics file.
Statistics accumulation stops.
Corrective Action: Contact BMC Customer Support.
Explanation: During termination, the Control-O Statistics Facility failed to close the Statistics file.
The Statistics Facility continues terminating without closing the Statistics file.
Corrective Action: Check the system log for previous error messages. If none are found, please contact BMC Customer Support.
Explanation: This informative message indicates that the Control-O Statistics Facility initialization completed successfully and that Control-O statistics are being accumulated.
Corrective Action: No action is required.
Explanation: Control-O Statistics Facility did not initialize successfully.
Statistics accumulation is not performed.
Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.
Explanation: The Statistics Facility detected an error while processing requests from the Control-O subsystem.
Statistics accumulation stops.
Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.
Explanation: The Statistics Facility detected an error while updating the Statistics file.
Statistics accumulation stops.
Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.
Explanation: This informative messages is issued after normal termination of the Statistics Facility. Statistics accumulation is discontinued.
Corrective Action: No action is required.
Explanation: Control-O Statistics Facility did not terminate successfully.
The Statistics Facility continues the termination process.
Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.
Explanation: The Statistics Facility detected an error while processing a SHOW, EXCLUDE or RESET online user request.
Statistics accumulation stops.
Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and correct accordingly.
Explanation: A SHOW, EXCLUDE or RESET request for message ID msgId failed.
An online user requested a SHOW/EXCLUDE/RESET for message ID msgId. This message ID was not found in the Statistics file.
The online request is not performed. The Statistics Facility continues processing.
Corrective Action: Notify BMC Customer Support of the problem.
Explanation: Due to an internal error, the user’s online request regarding message ID msgId was not recognized.
The request is not performed. The Statistics Facility continues processing.
Corrective Action: Notify BMC Customer Support.
Explanation: Control-O is attempting to access the Statistics file, but it is in use by another Control-O monitor or Control-O utility.
Control-O waits and attempts to access the Statistics file again.
Corrective Action: This message is not necessarily the result of an error. It may be issued while generating a statistics report or when the Online Facility attempts to access the Statistics file. If the Statistics file is not freed in a reasonable period of time, check what job is using it and free it.
Explanation: An online user requested a RESET of the statistics for message ID msgId, but due to internal error, the request could not be performed by Control-O.
The RESET request is not performed. The Statistics Facility continues processing.
Corrective Action: Notify BMC Customer Support.
Explanation: Dynamic allocation of Statistics file dsn failed with return code rc and reason code rsn.
Statistics accumulation is not performed.
Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide to determine this cause of the error, and correct the error accordingly. If not successful, contact BMC Customer Support.
Explanation: This information message indicates that the global statistics reset command F CONTROLO, RESETSTAT was issued and performed successfully.
Corrective Action: No action is required.
Explanation: Statistics for message ID msgId were reset as requested, but due to an internal error, update of the last reset date was not successful.
Statistics are reset. The Statistics Facility continues processing, but the indicated last reset date is incorrect.
Corrective Action: Notify BMC Customer Support.
Explanation: No command or mask was specified as selection criteria for display in the Option COMMAND window.
The selection window remains displayed.
Corrective Action: Specify a mask or operator command to be displayed.
Explanation: The CTOTMCS Automation Options program was invoked with an invalid action. This message indicates an internal error.
The option is not performed.
Corrective Action: Contact BMC Customer Support.
Explanation: The PARM menu definition statement for this option specifies an invalid time interval. The PARM statement for a menu option can specify the time interval between the issuing of the command and the collection of response messages.
The option is not performed.
Corrective Action: Correct the menu definition, and choose the menu option again.
Explanation: The MVS Extended MCS Console facilities used by Option COMMAND detected an error. The return code rc and reason code rsn are returned by the MCSOPER MVS macro.
The option is not performed.
Corrective Action: For an explanation of rc and rsn, see the appropriate IBM manuals.
Explanation: The MVS Extended MCS Console specified in the message is being used by another user. The console name is the same as the user name used by the IOA Online Facility. Either the same user name is being used by different users, or a previous console session was not closed correctly.
The option is not performed.
Corrective Action: Use operator command DISPLAY CONSOLES to determine who is using the console. If under TSO, log off from TSO and log on again to free any previous session.
Explanation: The user requested an operator command that cannot be issued by the Control-O Automation Options Facility because security exit IOASE07 detected a security violation.
The command is not issued.
Corrective Action: Contact your security administrator.
Explanation: A VM command was requested by means of the Automation Options facility. Such a command can be issued only when MVS runs under VM.
The command is not issued.
Corrective Action: No action is required.
Explanation: The response of the IOA VM command interface exceeded the 4096 bytes that the buffer can hold. The remainder of the response is truncated.
Corrective Action: Change the command so it can be held in the available buffer of 4096 bytes.
Explanation: Option CONSOLE was invoked with an invalid action. This message indicates an internal error.
The option is not performed.
Corrective Action: Contact BMC Customer Support.
Explanation: The console name or console ID specified for option CONSOLE could not be found.
The option is not performed.
Corrective Action: Do the following:
Parent Topic |