Messages MTO100 through MTO1xx

This group includes messages for the Control-O product.

MTO100I {CONTROL-O | CTMCMEM} RELEASE x.x.xx - MONITOR STARTED

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.

MTO101S MONITOR STARTED WITH INCORRECT STORAGE KEY. CHECK PPT DEFINITION

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:

Define the CTOMTO7 in SYS1.PARMLIB(SCHED xx) with a key in the range from 1 through 7.
Refresh the SCHED xx using the MVS SET command.
Stop the Control-D subsystem by means of the command S IOASTERM,TYPE=D
Disconnect the IOA subsystem by means of the command S IOASDISC,SSNAME=ioa_subsystem
Start the Control-O or CMEM monitor.
Start the Control-D monitor and subsystem.

MTO102I CONTROL-D FUNCTIONS ENABLED

Explanation: This information message indicates that during Control-O monitor startup, an installed Control-D was detected. Therefore, the Control-M function DO CTD REQ was enabled.

Corrective Action: No action is required.

MTO103W CONTROL-D FUNCTIONS DISABLED. "DO CTD REQ." WILL BE REJECTED

Explanation: During Control-O monitor startup, no installed Control-D was detected. Therefore, the Control-M function DO CTD REQ was disabled.

Monitor startup continues.

Corrective Action: Notify your INCONTROL administrator.

MTO104S BLDL / ATTACH FAILED FOR TASK taskName

Explanation: Initialization of one of the Control-O or CMEM monitor internal tasks failed.

Possible causes are:

The task is not found in the IOA Load library.
There is insufficient storage for the Control-O or CMEM monitor.

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.

MTO105S UNRECOVERABLE ERROR ENCOUNTERED

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.

MTO106S SUBTASK subtask ABENDED abCode

Explanation: The identified Control-O or CMEM monitor internal subtask has 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.

MTO107I SHUT DOWN UPON REQUEST FROM OPERATOR

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.

MTO108S UNABLE TO ESTABLISH THE CROSS MEMORY ENVIRONMENT. STEP stepName

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.

MTO109I {CONTROL-O | CTMCMEM} MONITOR IS SHUTTING DOWN. A NEW MONITOR WAS STARTED

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.

MTO10AI CONTROL-M FUNCTIONS ENABLED

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.

MTO10BW CONTROL-M FUNCTIONS DISABLED. "DO FORCEJOB / RESOURCE" WILL BE REJECTED

Explanation: During Control-O or CMEM monitor startup, because no installed Control-M was detected, the Control-M functions DO FORCEJOB and DO RESOURCE were disabled.

Monitor startup continues.

Corrective Action: Notify the INCONTROL administrator.

MTO10DW CTOPARM PARAMETER DAYTIMEO (cto_time) SHOULD BE EQUAL TO DAYTIMEM (ctm_time) OF CTMPARM.

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:

cto_time - the value of the DAYTIMEO Control-O parameter
ctm_time - the value of the DAYTIMEM Control-M parameter

Monitor startup continues.

Corrective Action: Contact your INCONTROL administrator.

MTO120I {CONTROL-O | CTMCMEM} MONITOR SHUTTING DOWN

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.

MTO121S {CONTROL-O | CTMCMEM} MONITOR ENDED WITH ERROR

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.

MTO122S NOT ENOUGH STORAGE IN EXTENDED CSA FOR blockname. RETURN CODE= rc

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, rc is 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.

MTO123I {CONTROL-O | CTMCMEM} INTERVAL IS SET TO nn SECONDS

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 CMEM monitor will “wake up” every nn seconds and check on time-related events.

Corrective Action: No action is required.

MTO124W CONTROL-O PARAMETER parmName = parmValue { > | < } parmDefault - USING DEFAULT VALUE

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 parmName to the default value for that parameter, and the monitor continues its startup.

Correct the value of parmName in CTOPARM. If required, stop and restart the Control-O monitor.

Corrective Action: No action is required.

MTO126W LOAD OF IOADEST TABLE FAILED: DO SHOUT WILL NOT BE SUPPORTED

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.

MTO127I NEWDEST COMMAND ACCEPTED

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.

MTO128I RULE TYPE TABLE STATUS LIBRARY PRIORITY

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 shown in response to the DISPLAY command.

Corrective Action: No action is required.

MTO129I ruleName type tableName status lib priority

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.

MTO12BI WISH WO0949 IS {ENABLED | DISABLED} - CICS LONG MESSAGES SUPPORT

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.

MTO12CI WISH WO0975 IS ENABLED - MONITOR WILL WAIT UNTIL MIGRATED LIBRARIES WILL BE RESTORED

Explanation: This information message is issued by the Control-O monitor when it enables optional wish WO0975.

Corrective Action: No action is required.

MTO12DI WISH WO0975 IS DISABLED - MONITOR WILL IGNORE MIGRATED LIBRARIES

Explanation: This information message is issued by the Control-O monitor when it disables optional wish WO0975.

Corrective Action: No action is required.

MTO12EI WISH WO0976 IS ENABLED - MESSAGES HANDLED AS IS

Explanation: This information message is issued by the Control-O monitor when it enables optional wish WO0976.

Corrective Action: No action is required.

MTO12FI WISH WO0976 IS DISABLED - MESSAGES HANDLED IN UPPER CASE

Explanation: This information message is issued by the Control-O monitor when it disables optional wish WO0976.

Corrective Action: No action is required.

MTO130I IN condName date

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.

MTO131I TIME FROM hhmm UNTIL hhmm INTERVAL interval

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.

MTO132I REQUEST TO STOP THE CONTROL-M API ACCEPTED

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.

MTO133I CONTROL-M API STOPPED

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.

MTO134I {CONTROL-O | CTMCMEM} WORKING DATE HAS CHANGED FROM old_date TO new_date

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.

MTO135I REQUEST TO STOP THE CONTROL-M API NOT ACCEPTED. API NOT ACTIVE

Explanation: The Control-O monitor attempted to process an F CONTROLO,CTMAPISTOP command, but the API could not be stopped because it is not active.

The monitor indicates that it cannot execute the requested command, because the API is not active. Note that the API is started with the first API request, such as a DO FORCEJOB statement with ODAT set to ?.

Corrective Action: No action is required.

MTO136I THE CONTROL-M API WILL BE RESTARTED WITH THE FIRST API REQUEST

Explanation: The Control-O monitor successfully processed anF CONTROLO,CTMAPISTART command.

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

Corrective Action: No action is required.

MTO137I CANNOT START THE CONTROL-M API - ALREADY WAITING FOR FIRST REQUEST

Explanation: The Control-O monitor attempted to process anF CONTROLO,CTMAPISTART command, but failed. Either the monitor has already processed this command and is therefore waiting for the first API request to allocate the files, or the monitor has not processed an API request since it was started.

Corrective Action: No action is required.

MTO138I CANNOT START THE CONTROL-M API - FIRST REQUEST ALREADY PROCESSED

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

MTO142S {CONTROL-O | CTMCMEM} MONITOR DETECTED AN INTERNAL abCode ABEND

Explanation: This message is issued when Control-O or CMEM detects 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.

MTO145S AUTOEDIT FAILED, RC= rc, REASON= rsn

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

MTO146W MISSING GLOBAL AUTOEDIT LIBRARY/MEMBER

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

MTO147I CONTROL-O INITIALIZATION COMPLETE. TYPE= type SUB= subsys RUN#= nnnn

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:

type - the type of the startup which was passed to Control-O or CMEM as a parameter in the START commandIf no TYPE value was passed to Control-O or CMEM, the default is TYPE=REGULAR.
subsys - the name of the subsystem that started Control-O or CMEM (JES2, JES3, MSTR, and so on)
nnnn - the number of times Control-O was replaced by a new Control-O or CMEM

Control-O or CMEM facilities are now active.

Corrective Action: No action is required.

MTO148W CONTROL-O STATISTICS ALREADY ACTIVE

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.

MTO149W CONTROL-O STATISTICS NOT ACTIVE

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.

MTO14AE INVALID modifyCommand COMMAND KEYWORD = keyword

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.

MTO14BI SVC DUMP keyword NOW ENABLED

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.

MTO14CI SVC DUMP keyword NOW DISABLED

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.

MTO14DW SHUTDOWN IS DELAYED DUE TO XES SYSTEM-MANAGED REBUILD PROCESS. TO CANCEL THE DELAY REPLY "FORCE"

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:

Abends in processes accessing the IOA Global variables (subsystem environment, online, and so on.).
Further delays in Control-O termination due to requests issued to the XAE structures when writing the IOA Global pools to the databases as part of the termination process may be deferred by the system-managed process in progress.

Corrective Action: None, unless immediate termination is required. If immediate termination is required, reply FORCE.

See System action for considerations before replying FORCE.

MTO14EW monitor INITALIZATION IS CANCELLED. START monitor WHEN XAE STRUCTURES ARE AVAILABLE

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:

The coupling facility required for XAE structures is available.
XAE structures, if already allocated, are available.

MTO150I SNAP COMMAND WAS PERFORMED. SNAP ID= id

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.

MTO151W IOA LOG UPDATE FAILED. SOME MESSAGES MAY BE LOST

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.

MTO152I STANDALONE FACILITY ENABLED. rsn

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.

MTO153I STANDALONE FACILITY DISABLED. rsn

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.

MTO154E CONTROL-O CANNOT START. CONTROL-M IS NOT INSTALLED

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.

MTO155W SWAP OF add CHAIN ERROR. TYPE= type RC= rc

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.

MTO156W AUTOMATION LOG STATUS UNCHANGED

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.

MTO157I action SERVER serverId REQUESTED

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.

MTO158W action SERVER serverId FAILED - rsn

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.

MTO159E INVALID SERVER MODIFY COMMAND - cmd

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.

MTO15AE INVALID SNAP KEYWORD = keyName

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.

MTO15BE INVALID LOG KEYWORD = keyName

Explanation: The CTOMTO program detected an invalid keyword for the LOG request. Valid keywords are:

ALL
DEFAULT
TRIGGER

The CTOMTO program ignores this LOG command request.

Corrective Action: Resubmit the F CONTROLO,LOG/F CTMCMEM,LOG command with a valid keyword.

MTO15CI RULE LOGGING MODE WAS SET TO modeType

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.

MTO15DI WATERMARK INFORMATION: FREE= freeNum PND= waitNum EVC= execNum WSC= wscNum

Explanation: This Control-O or CMEM message displays statistics in response to a WATERMARKS command.

The variables in this message are:

freeNum - the lowest number of RQC blocks that have been free simultaneously since the monitor was startedRQC blocks are used when information is being transferred from various address spaces to the address space of the monitor. A total of 20,000 RQC blocks are available.
waitNum - the highest number of PND blocks that have been in use simultaneously since the monitor was startedPND blocks store information about rules that are in Wait mode, meaning rules that are in execution and waiting to be redispatched. The allocation of PND blocks is controlled by the WAITPR# parameter.
execNum - the number of events (meaning messages, commands, and so on) that have been handled by the monitor since it was startedThis number is reset to zero each time it reaches 1,000,000.
wscNum - the number of WSC blocks that are allocated for use by the monitor WSC blocks store temporary information while handling events. The allocation of WSC blocks is controlled by the WSC# parameter.

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.

MTO15EI type USAGE: CURRENTLY curr%, HIGHEST high% (curr AND high OUT OF total)

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:

type - the type of resource to which the usage statistics displayed relate. Valid values for type are:

type	Explanation
PND	PND blocks, also known as "wait elements" PND blocks store information about rules that are in Wait mode, meaning rules that are in execution and waiting to be redispatched. The allocation of PND blocks is controlled by the WAITPR# parameter.
RQC	RQC blocks, also known as "request elements"RQC blocks are used when information is being transferred from various address spaces to the address space of the monitor. A total of 20,000 RQC blocks are available.
WSC	WSC blocks, also known as "work buffers" WSC blocks store temporary information while handling events. The allocation of WSC blocks is controlled by the WSC# parameter.

curr% - the percentage of the allocated type resources that are currently in use
high% - the highest percentage of type resources that have been in use at one time since the monitor was started
curr - the amount of type resources currently in use
high - the highest amount of type resources that have been in use at one time since the monitor was started
total - the total amount of type resources currently allocated

Corrective Action: In normal circumstances, the highp percentage figure should remain below 50%. If you notice high usage percentages, contact your INCONTROL administrator. Possible causes are:

There are rules in the system that consume excessive amounts of internal resources.
Some parameters require adjustment to accommodate the workload of the system.

MTO15FE INVALID USAGESTATS KEYWORD = type

Explanation: A request was made for usage statistics relating to internal Control-O or CMEM resources, by means of a USAGESTATS command.

However, the request referred to an invalid type of resources.

In this message, type is the invalid resource type. Valid values for the resource type keyword are:

Valid values for type are:

Resource Type Keyword	Explanation
ALL	All resource types supported by the USAGESTAT commandDefault.
PND	PND blocks, also known as "wait elements" The allocation of PND blocks is controlled by the WAITPR# parameter.
RQC	RQC blocks, also known as "request elements"A total of 20,000 RQC blocks are available.
WSC	WSC blocks, also known as "work buffers" The allocation of WSC blocks is controlled by the WSC# parameter.

For more information on the USAGESTATS command, see the INCONTROL for z/OS Administrator Guide.

Corrective Action: Reissue the command with a valid type value, or with no value for type (which defaults to ALL).

MTO160I MSGMON IS SET TO {YES | NO}

Explanation: This information message displays the current MSGMON status.

Corrective Action: No action is required.

MTO161I MSGMON HAS BEEN SET TO {YES | NO}

Explanation: The MSGMON status was changed through a user command.

Corrective Action: No action is required.

MTO162W MSGMON IS ALREADY SET TO {YES | NO}

Explanation: The user issued a command to modify the MSGMON status, however the intended status is the same as the current status. The command was ignored.

Corrective Action: No action is required.

MTO169E INVALID MSGMON VALUE SPECIFIED (USE YES/NO)

Explanation: The user entered an invalid value to modify the MSGMON status. The command was ignored.

Corrective Action: Enter either YES or NO for the MSGMON value and try again.

Parent Topic

MTO messages