K–M

This group includes messages for the Control-D (including Control-D/Image and Control-D/Page on Demand), Control-M for z/OS (including Control-M/Assist, Control-M/Links for z/OS Control-M/Restart), Control-M/Tape, Control-O, and IOA products.

KOA MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages KOA0 through KOA0xxLink copied to clipboard

This group includes messages for the Control-O product.

KOA003E VTAM APPLICATION IS NOT RESPONDINGLink copied to clipboard

Explanation: The VTAM application did not respond within the time limit. The VTAM application is probably not active.

The response time limit is specified in two places:

the KOATIME parameter in the CTOPARM member
the TIMEOUT parameter in the IOAYCNST member

The KOA session terminates.

Corrective Action: Ensure that the required VTAM application is active. If the application is active but does not respond, contact your system administrator. Consider increasing the value set for the KOATIME parameter.

KOA004E A LOGICAL OR PHYSICAL ERROR OCCURRED. SENSE= `rc. fdb2.fdbk2`Link copied to clipboard

Explanation: An error occurred while exit routine LERAD/SYNAD was activated for this session.

The variables in this message are:

rc - MVS return code
fdb2 - MVS FDB2 function
fdbk2 - MVS FDBK2 function

For more information, see the description of RPL-based macroinstruction errors and special conditions in the IBM manual VTAM Programming.

Session terminates.

Corrective Action: Contact your system administrator.

KOA005E VTAM CANNOT ESTABLISH THE REQUESTED SESSIONLink copied to clipboard

Explanation: The application received a network service request unit.

The network service request unit was one of these:

Cleanup session request unit
Notify request unit
Network services procedure error request unit

For more information, see the description of the NSEXIT Exit Routine in the IBM manual VTAM Programming.

Session terminates.

Corrective Action: Contact your system administrator.

KOA008E INSUFFICIENT STORAGE. INCREASE THE REGION SIZELink copied to clipboard

Explanation: Insufficient memory to perform the task.

Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.

KOA009E THE SPECIFIED LU IS ALREADY BEING USEDLink copied to clipboard

Explanation: The Logical Unit is active in another session.

The session terminates.

Corrective Action: Change the Logical Unit name or contact your system administrator.

KOA00AE THE SPECIFIED LU IS NOT DEFINEDLink copied to clipboard

Explanation: The requested Logical Unit name was not defined in VTAM or was not activated.

The session terminates.

Corrective Action: Contact your system administrator.

KOA00BE ALL THE DEFINED APPLICATIONS ARE BEING USEDLink copied to clipboard

Explanation: No Logical Units are available.

The session terminates.

Corrective Action: Change the Logical Unit name or contact your system administrator. Consider increasing the number of Logical Terminals specified in the KOATERM parameter in the CTOPARM member.

KOA00CE THE SPECIFIED APPLICATION IS NOT AVAILABLELink copied to clipboard

Explanation: The requested application was not defined in VTAM.

The session terminates.

Corrective Action: Contact your system administrator.

KOA00EE FUNCTION `func` FAILED. SENSE= `rc. fdb2. fdbk2`Link copied to clipboard

Explanation: The user requested function func. However, func cannot be executed.

The variables in this message are:

rc - MVS return code
fdb2 - MVS FDB2 function
fdbk2 - MVS FDBK2 function

For more information, see Return Codes and Sense Fields for RPL-based Macro instructions in the IBM manual VTAM Programming.

The session terminates.

Corrective Action: Contact your system administrator.

KOA00FE NON-LU2 TYPE HAS BEEN DEFINEDLink copied to clipboard

Explanation: The user specified a Logical Unit name with a non-LU2 type.

The session terminates.

Corrective Action: Contact your system administrator.

KSL MessagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages KSL300 through KSL3xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

KSL320E MAXIMUM NUMBER OF ARGUMENTS IN A CALL COMMAND IS 9Link copied to clipboard

Explanation: A CALLMEM command was followed by more than nine (9) arguments.

The maximum number of arguments in a CALLMEM command is 9. The arguments must be separated with blanks. An argument specified between quotes and containing blanks is interpreted as a few arguments.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.Link copied to clipboard

Corrective Action: Correct the syntax of the CALLMEM command.

KSL321E CALLMEM MEMBER IS EMPTYLink copied to clipboard

Explanation: The member that has been invoked by the CALLMEM command was empty.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the CALLMEM command or put a valid command in the called member.

KSL322E ARGUMENT REPLACEMENT WILL EXPAND THE CARD OVER ITS MAXIMUM LENGTHLink copied to clipboard

Explanation: The result of argument replacement in a line of the member invoked by a CALLMEM command caused the line to be expanded over column 72. The problem line is printed before this message.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the CALLMEM command or of the erroneous line.

KSL337I `text`Link copied to clipboard

Explanation: This information message indicates that at KeyStroke Language Report termination, the variable %MSG contained the text.

It is usually a message which is intentionally issued as part of the report definition.

Corrective Action: No action is required.

KSL338E INVALID VALUE OF %RC - `val`Link copied to clipboard

Explanation: At KeyStroke Language Report termination, the variable %RC contained an invalid value.

A valid %RC value must be a numeric string of no more than 4 characters and not higher than 4095.

The KeyStroke Language Report will terminate with a condition code of 4095.

Corrective Action: Correct the syntax of the report.

KSL339E LINE IDENTIFIER `id` IS NOT DEFINEDLink copied to clipboard

Explanation: A line identifier specified in a PRINTLINE command has not been previously defined by a SETLINE command.

In this message, id is the undefined line identifier.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the PRINTLINE command.

KSL340E SCREEN SIZE ALREADY SET, OR SCREEN COMMANDS ALREADY ACTIVATEDLink copied to clipboard

Explanation: A SCREENSIZE command has already been issued, or a screen related command has already been activated (for example, TYPE, ENTER, and so on).

Screen size cannot be defined twice in the same report. Upon execution of a screen related command, if the screen size has not been set, a default of 24 lines and 80 columns is assumed.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the report.

KSL341E PAGE SIZE ALREADY SET, OR PRINT/HEADER/BOTTOM COMMANDS ALREADY ACTIVATEDLink copied to clipboard

Explanation: A PAGESIZE command has already been issued, or a print related command has already been activated (for example, HEADERLINE, PRINT SCREEN).

Page size cannot be defined twice in the same report. Upon execution of a print related command, if the page size has not been set, a default of 60 lines, 132 columns is assumed.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the report.

KSL342E INTERNAL PRINTING ERROR. RC= `rc`Link copied to clipboard

Explanation: Internal error in the Control- x KeyStroke Language printing routines.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Contact BMC Customer Support. A printed sample of the erroneous report and the report definition will be required, preferably with the TRACE ON option.

KSL343E LABEL ALREADY DEFINEDLink copied to clipboard

Explanation: The label specified in the previous line has already been defined in the same report member.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Correct the syntax of the report.

KSL344E GOTO TO AN UNDEFINED LABEL `label`Link copied to clipboard

Explanation: A label specified in a GOTO command is not defined in the report member.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Correct the syntax of the report.

KSL345E IFSCREEN COMMAND NOT IN SCREEN RANGELink copied to clipboard

Explanation: The string to compare with the contents of the screen in the current cursor position exceeds the width of the screen line. Therefore it cannot be compared.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the IFSCREEN command.

KSL346E MAXCOMMAND ALREADY SETLink copied to clipboard

Explanation: The MAXCOMMAND has already been activated.

The MAXCOMMAND command cannot be activated twice in the same report (this may result in an endless loop).

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the report.

KSL347E HEADERSIZE/BOTTOMSIZE MUST BE ACTIVATED BEFORE A HEADERLINE/BOTTOMLINE COMMANDLink copied to clipboard

Explanation: A HEADERLINE command or a BOTTOMLINE command has been activated before both the header and bottom size have been defined by a HEADERSIZE and BOTTOMSIZE command.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Correct the syntax of the report.

KSL348E UNDEFINED VARIABLE - `varName`Link copied to clipboard

Explanation: A reference to a user variable which has not yet been defined by a SETVAR command.

A user variable is valid only inside the same report member. A user variable defined in another report member is not accessible from other report members (including the calling member).

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the report.

KSL349E ERROR WHILE EXECUTING COMMAND - `cmdText`Link copied to clipboard

Explanation: A severe error occurred during the processing of a command. Previous messages should describe the error.

In this message, cmdText is the text of the command that was being executed when the error occurred.

The KeyStroke Language Report will terminate with a condition code of 12.

Corrective Action: Correct the syntax of the report.

Messages KSL400 through KSL4xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

KSL401I A KEYSTROKE REPORT STARTEDLink copied to clipboard

Explanation: This information message is a normal start message of a KeyStroke Language Report.

Corrective Action: No action is required.

KSL402I A KEYSTROKE REPORT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that a KeyStroke Language Report ended successfully.

The report ended successfully from the point of view of report syntax and execution. A user may set the condition code to any condition code and send a message indicating otherwise. It is recommended to check the condition code as well (using the Control-M/D facilities).

Corrective Action: No action is required.

KSL403E TEXT EXPECTED BETWEEN QUOTES IN THE COMMANDLink copied to clipboard

Explanation: A text between quotes is expected as one of the command parameters. The command line is printed in the previous line.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Refer to the Control-M for z/OS User Guide or the Control-D and Control-V User Guide for the valid command syntax.

KSL404E REDUNDANT PARAMETERS IN THE REPORT COMMANDLink copied to clipboard

Explanation: Redundant text in the report line (columns 1-80). The command line is printed in the previous line.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Correct the syntax of the report.

KSL405E MISSING/INVALID PARAMETERS IN THE REPORT COMMANDLink copied to clipboard

Explanation: A parameter of a command has an invalid value, or an obligatory command parameter is missing. The command line is printed in the previous line.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Refer to the Control-M for z/OS User Guide or the Control-D and Control-V User Guide for valid command syntax.

KSL406E INVALID LINE/COL NUMBER - `num` (OR OUT OF RANGE)Link copied to clipboard

Explanation: A line number or a column number used in a KeyStroke Language Report command is not within the limits of the screen size or the limits of the print page size (or the header/bottom size), or cannot be referred to in the erroneous command.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Refer to the KSL section of your CONTROL product user guide for valid command syntax.

KSL407E INTERNAL COMMAND HANDLER ERROR RC `rc`Link copied to clipboard

Explanation: An internal error occurred in the KeyStroke Language (KSL) command handler.

The return code (rc) is for internal use only.

The KSL report terminates with a condition code of 12.

Corrective Action:

Verify that all the sysouts produced by the KSL procedure point to a printable class.
Add TRACE ON and DBGLEVEL 255 statements to the KSL or KOA script to produce trace information:.
Submit the job.
Report the problem with all the sysouts of the job and the return code (rc) to BMC Customer Support.

KSL408E MAXIMUM NUMBER OF COMMANDS EXCEEDED. REPORT IS TERMINATEDLink copied to clipboard

Explanation: The maximum number of report commands as defined in MAXCOMMAND, has been exceeded.

The default MAXCOMMAND value is 400. It can be set to any number up to the seven digit value 9999999.

The KeyStroke Language Report terminates with a condition code of 12.

Corrective Action: Check for a possible loop. Correct the syntax of the report, and set a larger value for MAXCOMMAND.

KSL409E A KEYSTROKE REPORT ENDED WITH ERROR(S)Link copied to clipboard

Explanation: Syntax/execution error during processing of a report.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Look for the error in the report listing (the DAKSLOUT DD statement).

KSL410E TYPING IN A "SCREEN" PROTECTED AREA IS NOT PERMITTED - THE REPORT IS TERMINATEDLink copied to clipboard

Explanation: A text (string) used in a TYPE command does not fall within the limits of one unprotected data field on the screen.

As in normal screen processing, it is impossible to type over protected screen areas.

The KeyStroke Language Report will terminate with a condition code of 12.

The current screen and the current cursor position are printed to help resolve the problem.

Corrective Action: Correct the syntax of the report.

Messages KSLA00 through KSLAxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

KSLA60I EXCEPTIONAL CONDITION RC=`rc`, ERROR=`err`, FEEDBACK=`feedback`, APPLID= `applId`Link copied to clipboard

Explanation: This information message indicates that an exceptional VTAM condition was encountered during the execution of a KOA communication command.

This informational message is issued by the KOA Facility. Return code, error and feedback information are detailed in the KeyStroke Language (KSL) User Guide.

The KOA script continues processing. If an ON SCREENERROR statement was specified, the processing resumes at the label specified in the ON statement.

Corrective Action: Analyze the specific VTAM error, and take the corresponding corrective actions. Make sure that the error is handled correctly by the KOA script.

KSLA61E SCREEN COMMAND EXECUTED WITH NO SCREEN AVAILABLELink copied to clipboard

Explanation: A screen command was executed; however, no screen was available to the KOA script.

Either a screen command was executed before a KOA session was established by means of a LOGON command, or the KOA session was lost due to communication errors.

The KOA script is terminated.

Corrective Action: Check previous error messages. If necessary, correct the error handling inside the KOA script.

KSLA62E CONTROL-O IS NOT ACTIVE. GLOBAL VARIABLES CANNOT BE USEDLink copied to clipboard

Explanation: A SETOGLB KOA statement was executed while the Control-O monitor was not active.

Control-O Global variables may be set by a KOA script only while Control-O is active.

The KOA script is terminated.

Corrective Action: Correct the KOA script, or start the Control-O monitor.

KSLA63E SPECIFIED SESSION ID IS NOT ACTIVELink copied to clipboard

Explanation: A SETSESS KOA statement specified the ID of a session which is not active.

Either the session was not established through a LOGON command, or the session was lost due to communication errors.

The KOA script is terminated.

Corrective Action: Check for previous error messages. Correct the KOA script accordingly, and resubmit.

KSLA64E KEYSTROKE UTILITY DETECTED INTERNAL ABEND `abCode`Link copied to clipboard

Explanation: An internal abend was intercepted by the KeyStroke utility.

The KSL/KOA script is terminated.

Corrective Action: Check the associated error messages. Correct the KOA script accordingly, and resubmit.

KSLA65E ALLOC OF DDNAME `ddName` FAILED, RC = `rc`, ERROR= `err`, DSN= `dsn`Link copied to clipboard

Explanation: An ALLOC statement failed due to a dynamic allocation error.

The KSL/KOA script is terminated.

Corrective Action: Check the return code and error information. Correct the KSL/KOA script accordingly, and resubmit.

KSLA66E FREE OF DDNAME `ddName` FAILEDLink copied to clipboard

Explanation: A FREE statement failed due to a dynamic deallocation error.

The KSL/KOA script is terminated.

Corrective Action: Correct the KSL/KOA script accordingly, and resubmit.

KSLA67E OPEN OF DDNAME `ddName` FAILEDLink copied to clipboard

Explanation: An OPENFILE statement failed.

The KSL/KOA script is terminated.

Corrective Action: Check the preceding KSL or MVS error messages. Correct the KSL/KOA script accordingly, and resubmit.

KSLA68E CLOSE OF DDNAME `ddName` FAILEDLink copied to clipboard

Explanation: A CLOSEFILE statement failed.

The KSL/KOA script is terminated.

Corrective Action: Check the preceding KSL or MVS error messages. Correct the KSL/KOA script accordingly, and resubmit.

KSLA69E I/O ERROR WHEN READING FROM DDNAME `ddName`Link copied to clipboard

Explanation: A GETFILE statement failed due to an I/O error.

The KSL/KOA script is terminated.

Corrective Action: Check the preceding KSL or MVS error messages. If necessary, check that the DCB characteristics of the file are correct. Correct the KSL/KOA script accordingly, and resubmit.

KSLA6AE I/O ERROR WHEN WRITING TO DDNAME `ddName`Link copied to clipboard

Explanation: A PUTFILE statement failed due to an I/O error.

The KSL/KOA script is terminated.

Corrective Action: Check the DCB characteristics of the file. Make sure it is a fixed length record data set. Correct the KSL/KOA script accordingly, and resubmit.

KSLA6BE UNSUPPORTED DCB CHARACTERISTICS FOR DDNAME `ddName`Link copied to clipboard

Explanation: The KeyStroke utility handles only fixed length record data sets. An OPENFILE statement failed because the record format of the specified data set is not fixed or the record length exceeds 150 characters.

The KSL/KOA script is terminated.

Corrective Action: Check the DCB characteristics of the file. Make sure the file is a fixed length record data set with a record length that does not exceed 150 characters. Correct the KSL/KOA script accordingly and resubmit.

KSLA6CE ENQ ERR RC= `rc`, Q= `queueName`, R= `resourceName`Link copied to clipboard

Explanation: The execution of the KSL OPEN statement issued an Enqueue request which failed.

The request is terminated.

Corrective Action: Check the return code of the Enqueue failure and proceed accordingly.

KSLA6DE RSV ERR RC= `rc`, Q= `queueName`, R= `resourceName`Link copied to clipboard

Explanation: The execution of the KSL OPEN statement issued a Reserve request which failed.

The request is terminated.

Corrective Action: Check the return code of the Reserve failure and proceed accordingly.

KSLA6EE DDNAME `ddName` NOT FOUNDLink copied to clipboard

Explanation: Control-O was unable to locate the specified data set while executing an OPENFILE request.

The OPENFILE request fails.

Corrective Action: Check why ddName is not allocated. Correct the KOA/KSL script or the JCL, and rerun.

KSLA6FE SETOLOC/SETOGLB ERROR CODE = `rc` REASON = `rsn`, TEXT=`AutoEdit_expression`Link copied to clipboard

Explanation: An error was detected while trying to resolve a SETOGLB or SETOLOC KSL/KOA statement.

The KSL/KOA program is terminated.

Corrective Action:

Ensure that the AutoEdit expression in the SETOLOC or SETOGLB statement is correctly written.
For an explanation of the return code and reason code included in this message, see the table in the explanation of message WTO283E.

KSLA70E THERE IS AN ERROR IN IOAKPRM MEMBER. PLEASE CHECK THE SMFID FIELD.Link copied to clipboard

Explanation: The SMFID of the CPU to which the KSL job was submitted does not appear in the IOAKPRM member in the IOA PARM library.

The KSL stops running.

Corrective Action: Add the SMFID by making the appropriate entry in the IOAKPRM member. The best way of doing this is by means of the INCONTROL Installation and Customization Engine (ICE). For more information on ICE, see the ICE chapter in the INCONTROL for z/OS Installation Guide.

LDT MessagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages LDT500 through LDT5xxLink copied to clipboard

This group includes messages for the Control-O product.

LDT500I RULE= `rule` TYPE= `rule_typ` TABLE= `tableName` LIB= `lib`Link copied to clipboard

Explanation: This information message provides information about each rule in the table that was not loaded by ORDER or FORCE requests.

The variables in this message are:

rule - the name of the rule
rule_typ - the type of rule
tableName - the name of the table containing the rule
lib - the name of the library containing the table

Corrective Action: Examine previously issued messages to ascertain the reason why the rule identified in this message was not loaded, and take appropriate corrective action.

LDT501I `func` OF RULE TABLE(S) STARTEDLink copied to clipboard

Explanation: This information message indicates that the function func started on the rule tables.

Corrective Action: No action is required.

LDT502E MEMBER IN USE= `memb` DSN= `dsn`Link copied to clipboard

Explanation: The user attempted to load a rule table but the table was currently being used.

This message is issued immediately after message CTM684E to give the name of the member and data set that are in use.

The table is not loaded.

Corrective Action: Try to load the required table manually or by an automated operations product when the table is not in use.

LDT503S RULE ORDER LIST IS EMPTY. DDNAME= {DARULLST | DACTMLST}Link copied to clipboard

Explanation: Open of rule list data set failed (the DARULLST or DACTMLST DD statement).

Possible causes are:

The DARULLST or DACTMLST DD statement is missing.
The data set described by the DARULLST or DACTMLST DD statement cannot be opened for sequential read, or the record length is not 80.

The Control-O or CMEM monitor shuts down or continues processing according to the status of the monitor.

Corrective Action: Correct the JCL and restart the Control-O or CMEM monitor.

LDT504S INVALID DATA IN RULE ORDER LIST CARDSLink copied to clipboard

Explanation: Invalid data has been found in the rule order list.

For valid format information, see the INCONTROL for z/OS Administrator Guide.

Corrective Action: Check the format of the rule list in the PARM library; correct and restart the Control-O or CMEM monitor.

LDT505S MEMBER `memName` NOT FOUND IN LIBRARY `lib`Link copied to clipboard

Explanation: The memName member that was specified in the rule order was not found in the lib library.

The member (rule table) may be specified incorrectly or may be missing from the library.

The rule table is not ordered.

Corrective Action: Check and correct the member specification; reorder the rule table.

LDT506S ORDER OF TABLE `tableName` RULE `ruleName` FAILEDLink copied to clipboard

Explanation: The order of rule ruleName from table tableName failed. Prior messages usually explain why the rule table could not be ordered.

The rule is not be ordered.

Corrective Action: Check earlier messages for reasons the rule order failed. Correct as necessary, and reorder the rule table.

LDT507I LOAD ENDED FOR TABLE `table` LIBRARY `lib`Link copied to clipboard

Explanation: This information message indicates that after ordering or forcing a Control-O rule table, loading of rules from the table ended.

Corrective Action: No action is required.

LDT508I {ORDER | FORCE} OF RULES’ TABLE(S) ENDEDLink copied to clipboard

Explanation: This information message indicates that ordering or forcing of the Control-O rule table ended.

Corrective Action: No action is required.

LDT509I NUMBER OF TABLES `numtbl` PROCESSED. `numrul1` RULES LOADED AND `numrul2` RULES REJECTEDLink copied to clipboard

Explanation: This information message indicates the number of tables processed, and the number of rules that were loaded or deleted (not loaded) as a result of an ORDER or FORCE request. This information can be used for manual verification purposes.

Corrective Action: Check the results to ensure that the rule loading was performed correctly.

LDT50AI NUMBER OF TABLES `numtbl` RULES `numrul` DELETEDLink copied to clipboard

Explanation: This information message indicates the number of tables (numtbl) and the number of rules (numrul) deleted as a result of a MODIFY command to the Control-O or CMEM monitor.

Corrective Action: No action is required.

LDT50BE HOLD BY `jobId` ASID `asid` ON SYSTEM `systemId`Link copied to clipboard

Explanation: An ORDER or FORCE command to the Control-O or CMEM monitor to load a table or tables of rules failed, because the library is held by the jobId job with the asid ASID on the systemId system.

The command fails.

Corrective Action: Try to determine why the library is held. If possible, release it, and try again to ORDER or FORCE the table or tables.

LDT50CE LIBRARY WAS MIGRATED BY HSM DSNAME=Link copied to clipboard

Explanation: An ORDER or FORCE command to the Control-O or CMEM monitor to load a table or tables of rules failed, because the library had been migrated by HSM.

The command fails.

Corrective Action: If possible, restore or recall the library, then try again to ORDER or FORCE the table or tables.

LDT50FI `text`Link copied to clipboard

Explanation: This information message displays the control record from the DARULLST or DACTMLST DD statement.

Corrective Action: No action is required.

LDT516S ERROR IN RULE DATA - MANDATORY `stmt_type` CARD IS EITHER MISSING OR IN AN INCORRECT ORDERLink copied to clipboard

Explanation: A stmt_type statement is either missing or in the wrong order in a rule definition member.

Someone may have tampered with the rule definition data; the data do not conform to a valid Control-O or CMEM format.

The rule is not ordered.

Corrective Action: Restore the table to its original state from a backup copy, and reorder the rule table.

LDT517S RULE DATA NOT AVAILABLE: MEMBER `memName` IS EMPTYLink copied to clipboard

Explanation: The memName member that was designated in the rule list is empty. This error message is issued by the CTOLDT program, which loads tables when a new Control-O or CMEM monitor is activated.

The table is not ordered.

Corrective Action: Check that the specification of the member in the rule list is correct. If so, check why the member is empty. Correct, and reorder the rule table.

LDT518S INVALID SCHEDULING DATE - `date`Link copied to clipboard

Explanation: An invalid scheduling date format was used in the rule list or in a order/force request.

Valid date formats are:

ddmmyy - Day, month, and year.
mmddyy - Month, day, and year.
* (Asterisk) - Current Control-O or CMEM working date.

The requested table order fails.

Corrective Action: Correct the date, then reorder the rule table.

LDT521S ERROR IN RULE DATA: INVALID 'EXIT' TYPE. VALUES ALLOWED MESSAGE OR WHILELink copied to clipboard

Explanation: A logical check performed during rule loading detected an invalid DO EXIT statement.

The rule is not loaded.

Corrective Action: Correct the rule definition and reload the table.

LDT522S ERROR IN RULE DATA: EXIT WHILE NOT IN WHILE BLOCKLink copied to clipboard

Explanation: A logical check performed during rule loading detected a DO EXIT WHILE statement that was not in a DO WHILE block. A DO EXIT WHILE statement is only valid if it is located within a DO WHILE block.

The rule is not loaded.

Corrective Action: Correct the rule definition and reload the table.

LDT523S ERROR IN RULE DATA: INVALID IF-THEN-ELSE NESTINGLink copied to clipboard

Explanation: This message is issued during the ordering of the rule. The rule definition contains an invalid IF-ELSE-ENDIF nesting.

The rule is not ordered.

Corrective Action: Correct the rule definition and order it again.

LDT524S func RULE TABLE(S) ENDED WITH ERRORSLink copied to clipboard

Explanation: The indicated function of the CTOLDT program ended with errors. This program loads rule tables when a new Control-O or CMEM monitor is activated, and performs order/force of rule tables.

The IOA Log should contain prior messages concerning the errors.

Depending on when it fails, either the Control-O or CMEM monitor shuts down, or the table is not ordered.

Corrective Action: No action is required.

LDT525I func RULE TABLE(S) ENDEDLink copied to clipboard

Explanation: This information message is a normal message issued when the indicated function of the CTOLDT program has terminated successfully. This program loads rule tables when a new Control-O or CMEM monitor is activated, or performs order/force of rule tables.

Corrective Action: No action is required.

LDT526S ** ERROR IN RULE CARDS. CHECK THE FOLLOWING CARDS *Link copied to clipboard

Explanation: The rule definition has been corrupted and the data do not conform to a valid Control-O or CMEM format.

This message is followed by one or more LDT527S messages describing all statements belonging to the damaged rule order. An asterisk (*) appears in the line under the erroneous data.

The rule is not ordered.

Corrective Action: Using the Online Viewing Facility, or by editing the member, restore the table to its original state, and reorder the rule table.

LDT527S CARD = `stmt`Link copied to clipboard

Explanation: The rule definition has been corrupted.

This message follows message LDT526, and displays each statement in the damaged rule in the scheduling table. An asterisk * appears in the line under a damaged statement.

Corrective Action: Restore the table to its original state.

LDT528I RULE `ruleName rule_type` TABLE `tableName` LIBRARY `lib` ODATE `odate` LOADEDLink copied to clipboard

Explanation: This information message is a normal message when a rule order is successfully loaded by the Control-O or CMEM monitor.

The rule is now in Control-O or CMEM memory.

Corrective Action: No action is required.

LDT529I TABLE `tableName` LIBRARY `lib` DELETEDLink copied to clipboard

Explanation: This information message indicates that rule table tableName has been deleted from the Control-O or CMEM monitor as a result of an F CONTROLO,D=... operator command.

Corrective Action: No action is required.

LDT530E DELETE OF TABLE `tableName` LIBRARY `lib` FAILED, TABLE NOT FOUNDLink copied to clipboard

Explanation: A request to delete a rule table from the Control-O or CMEM monitor has failed. Table tableName has not been found under Control-O or CMEM.

The table may be specified incorrectly or it may never have been ordered.

The table is not deleted.

Corrective Action: If the table specification incorrect, check and correct the table specification and issue the delete request again. If the table was never ordered, there is no reason to attempt to delete it.

LDT531I NO RULE WAS LOADED - TABLE `tableName` LIBRARY `lib`Link copied to clipboard

Explanation: This information message indicates that the Control-O monitor did not load new rules from table tableName in library lib.

While ordering or forcing a rule library, Control-O found no rules that matched the Basic Scheduling parameters.

No rule is loaded.

Corrective Action: No action is required.

LDT532E MASK `mask` DOES NOT MATCH IN DSN= `dsn`Link copied to clipboard

Explanation: The specified mask does not match any members in the rule library.

During rule ordering, the Control-O monitor found no members matching the specified mask.

No rule is loaded.

Corrective Action: Check and correct the parameters specified in the ORDER/FORCE command or in the rule list.

LDT536S SEVERE ERROR IN RULE DATA CARDSLink copied to clipboard

Explanation: Severe error was found in the rule definition data statements. It is followed with additional messages regarding the error.

The rule table is not ordered.

Corrective Action: Check for additional messages concerning the errors in the systems and IOA Log and Control-O or CTMCMEM sysprint; correct the error and reorder the table.

LDT537S INSUFFICIENT STORAGE IN (EXTENDED) CSA. CANNOT LOAD TABLELink copied to clipboard

Explanation: Insufficient storage in the Extended Common Service Area (CSA) to load the rule table.

If any rules have been previously loaded, the Control-O or CMEM monitor proceeds without loading the table. If no rules were previously loaded, the Control-O or CMEM monitor shuts down.

Corrective Action: Check why there is insufficient CSA. You may need to contact your systems programmer. After correcting the problem, reload the table, or restart Control-O or CMEM, as necessary.

LDT539W ORDER CANCELLED BY USER EXIT: RULE `ruleName` TABLE `tableName` LIBRARY `lib`Link copied to clipboard

Explanation: The specified rule order failed as a result of a user exit check.

The IOA Log should contain prior messages concerning the reason for failure.

The rule order is not ordered/loaded by the Control-O or CMEM monitor.

Corrective Action: Check the IOA Log for further information.

LDT545E DO-MISSION NOT SUPPORTED WITHOUT CONTROL-D INSTALLEDLink copied to clipboard

Explanation: An attempt was made to order a rule specifying DO MISSION, but Control-D is not installed. DO MISSION is supported only if Control-D is installed.

The rule is not ordered.

Corrective Action: Either remove this statement from the rule or install Control-D.

LDT548E SEVERE ERROR IN CALENDAR `calName` OR YEAR NOT FOUND IN CALENDARLink copied to clipboard

Explanation: Severe error in the IOA calendar calName, or the year was not found in the calendar.

Either the year is not defined in the calendar or the calendar has been incorrectly modified.

The rule is not ordered.

Corrective Action: Check the contents of the rule order and the calendar. Correct and reorder the rule.

LDT549E DO FORCEJOB/RESOURCE NOT SUPPORTED WITHOUT CONTROL-M INSTALLEDLink copied to clipboard

Explanation: An attempt was made to order a rule specifying DO FORCEJOB or DO RESOURCE, but Control-M is not installed.

These statements are not supported if Control-M is not installed.

The rule is not ordered.

Corrective Action: Remove these statements from the rule or install Control-M.

LDT54AE INVALID "ON" STATEMENT FOR CMEM RULELink copied to clipboard

Explanation: An attempt was made to load a CMEM table containing a rule with an invalid “ON” statement.

The table is loaded without the erroneous rule.

Corrective Action: Delete the rule from the table, or load the table as a Control-O table (if Control-O is installed).

LDT54BE INVALID "DO" STATEMENT FOR CMEM RULELink copied to clipboard

Explanation: An attempt was made to load a CMEM table containing a rule with an invalid “DO” statement.

The table is loaded without the erroneous rule.

Corrective Action: If the rule is required, load the table as a Control-O table. If the rule is not required, delete it from the table.

LDT54CW LOAD REQUEST IGNORED. TABLE `tableName` LIBRARY `lib` ALREADY LOADEDLink copied to clipboard

Explanation: During monitor startup or REBUILD/NEWCONLIST command, Control-O tried to load a certain table more than once.

This problem can be caused by one of the following:

Duplicate statements appear in the same list, for example, DACTMLST, DARULLST.
The same statement appears in different lists, for example, DACTMLST, DARULLST.
Different generic statements appear in the same or different lists, producing one or more duplicate statements, for example, CTO* and C*.

Only the first appearance of the table is loaded.

Corrective Action: Check the lists for duplicate statements and correct if necessary.

LDT54DE RULE TYPE IS INCORRECT. TABLE `tableName` LIBRARY `lib`Link copied to clipboard

Explanation: The user attempted to order or force a CMEM rule table from Control-O screen OR, or a Control-O rule table from CMEM screen C.

Control-O rules can only be ordered or forced from Control-O screen OR. CMEM rules can only be ordered or forced from CMEM screen C.

The table specified in the message is not loaded.

Corrective Action: If you issued the command from screen OR, issue it from screen C, or vice versa.

LDT54EW RULE WAS NOT LOADED: SCHEDULING DATE WAS NOT SATISFIEDLink copied to clipboard

Explanation: Control-O did not load a rule because the scheduling date for that rule does not match the current date.

When Control-O loads a rule during startup or as a result of an order, it does not load rules whose scheduling date does not match the current one.

The Control-O monitor sends this message to SYSPRINT and to the IOALOG, and does not load the rule.

Corrective Action: To load the rule, make the scheduling date match the current date and reload the table containing the rule.

LDT54FW RULE WAS NOT LOADED: {SYSTEM | SMF ID} { `rul_sysname`|`rul_smfid`} DOES NOT MATCH { `cur_sysname`|`cur_smfid`}Link copied to clipboard

Explanation: Control-O did not load a rule because the environment specified for that rule does not match the current environment.

When Control-O loads a table of rules during startup or as a result of an order, it does not load rules whose specified environment does not match the current one.

The Control-O monitor sends this message to SYSPRINT and to the IOALOG, and does not load the rule.

Corrective Action: To load a rule, make the environment specified for it match the current one and reload the table containing the rule.

LGC messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages LGC900 through LGC9xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

LGC988S DATE SHOULD NOT BE GREATER THAN YESTERDAYLink copied to clipboard

Explanation: Invalid date specified for archival or backup (the CTMLGC utility).

The archive date should not be greater than yesterday’s date.

The utility stops execution with a condition code of 08.

Corrective Action: Correct the date field.

LGC989S OPEN OF DDNAME "DALOGHIS" FAILED. LOG ARCHIVAL NOT PERFORMEDLink copied to clipboard

Explanation: Open of log archival data set failed (the CTMLGC utility).

Possible causes are:

the DALOGHIS DD statement missing.
The DALOGHIS DD statement describes a file which is not in the format of the IOA Log.

The utility stops execution with a condition code of 08.

Corrective Action: Correct JCL for the job. You should run the CTMFRLOG utility to allocate and format an archival file in exactly the same format as the IOA Log.

LGC990I action OF IOA LOG STARTEDLink copied to clipboard

Explanation: This information message is a normal message which is issued when starting to backup the IOA Log (the CTMLGC utility).

Corrective Action: No action is required.

LGC991I action OF IOA LOG ENDEDLink copied to clipboard

Explanation: This information message is a normal message which is issued when the backup of the IOA Log ends (the CTMLGC utility).

Corrective Action: No action is required.

LGC992W OPEN OF DDNAME "DALOGBKP" FAILED, BACKUP OF IOA LOG NOT TAKENLink copied to clipboard

Explanation: Open of data set described by the DALOGBKP DD statement failed.

Possible causes are:

The DALOGBKP DD statement missing.
The data set described by the DALOGBKP DD statement cannot be opened for sequential write.

Backup of IOA Log not taken. Processing continues.

Corrective Action: If you want to backup the entire Log file, correct the JCL for the job.

LGC993S OPEN OF DDNAME "DALGCIN" FAILED. LOG ARCHIVAL NOT PERFORMEDLink copied to clipboard

Explanation: Open of the data set described by the DALGCIN DD statement.

Possible causes are:

The DALGCIN DD statement is missing.
Data set described by the DALGCIN DD statement cannot be opened for sequential read.

Log archival is not performed.

Corrective Action: Correct the JCL for the job.

LGC994S FILE CONNECTED TO DDNAME "DALGCIN" IS EMPTYLink copied to clipboard

Explanation: The data set described by the DALGCIN DD statement is empty.

Log archival is not performed.

Corrective Action: Correct the JCL for the job.

LGC995S RECORD LENGTH OF DDNAME "DALGCIN" IS NOT 80Link copied to clipboard

Explanation: Record length of the data set described by the DALGCIN DD statement must be 80 bytes.

Log archival is not performed.

Corrective Action: Check the contents of the data set described by the DALGCIN DD statement.

LGC996S "UNTIL DATE" OF LOG ARCHIVAL IS NOT A VALID DATELink copied to clipboard

Explanation: A parameter for the UNTIL date is invalid.

Corrective Action: Correct the UNTIL date parameter of the Log archival utility.

LGC997S NUMBER OF DAYS TO KEEP IN LOG FILE IS NOT NUMERICLink copied to clipboard

Explanation: Invalid number of days to keep in the Log file.

The number of days to keep in the Log file must be numeric.

Corrective Action: Correct the number of days.

LGC998S ARCHIVAL FILE ALLOCATED TO "DALOGHIS" IS FULLLink copied to clipboard

Explanation: The archival file allocated to the DALOGHIS DD statement is full.

Archival will not be executed.

Corrective Action: No action is required.

LGC999S NOTHING TO DO. NEITHER BACKUP NOR ARCHIVAL IS NEEDEDLink copied to clipboard

Explanation: Neither file DALOGHIS nor file DALOGBKP has been opened by the CTMLGC utility.

The utility terminates with a return code of 12.

Corrective Action: No action is necessary.

LGP messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages LGP900 through LGP9xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

LGP9A0I action OF IOA LOG STARTEDLink copied to clipboard

Explanation: This information message is a normal start message of the IOACPLOG utility. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

Corrective Action: No action is required.

LGP9A1I action OF IOA LOG ENDEDLink copied to clipboard

Explanation: This information message is a normal termination message of the IOACPLOG utility. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

Corrective Action: No action is required.

LGP9A2S action OF IOA LOG ENDED WITH ERRORS.Link copied to clipboard

Explanation: The IOACPLOG utility failed to copy the IOA Log file. IOACPLOG is used to copy the contents of the IOA Log to another IOA Log file or to a sequential file. The actions COPYTOSEQ and COPYTOLOG are currently supported.

The IOACPLOG utility ended with a condition code of 08 or 12.

Corrective Action: Check the preceding error messages in the job log or in the SYSPRINT sysout, correct the problem, and rerun the job.

LNR messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages LNR0 through LNR0xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

LNR051S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed. This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions list. Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version of IOA or of a different IOA monitor.

The IOALDNRS utility is not performed. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR052S OPEN OF IOA MANUAL SYNC FILE FAILEDLink copied to clipboard

Explanation: Open of the IOA Manual Conditions Synchronization file failed. This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions list. Possible causes are:

The DANSINC DD statement is missing.
The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR054I LOADING OF IOA MANUAL CONDITIONS FILE STARTEDLink copied to clipboard

Explanation: This information message indicates that loading of the IOA Manual Conditions file has started. The IOALDNRS utility will start collecting the Manual Conditions from the job orders on the Active Jobs file. These are all the prerequisite conditions which are suspected of requiring manual confirmation.

Corrective Action: No action is required.

LNR055I LOADING OF IOA MANUAL CONDITIONS FILE ENDEDLink copied to clipboard

Explanation: This information message indicates that the IOA Manual Conditions file has finished loading. The Manual Conditions file currently contains all the missing conditions for the job orders on the Active Jobs file.

Corrective Action: No action is required.

LNR056S IOA MANUAL CONDITIONS FILE WAS NOT LOADEDLink copied to clipboard

Explanation: The IOA Manual Conditions file was not loaded (the IOALDNRS utility). The utility output should contain a prior message which describes the cause of the problem.

Corrective Action: Correct the problem and rerun the utility.

LNR057S OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED - DDNAME "DACKPT"Link copied to clipboard

Explanation: Open of Control-M Active Jobs file failed (the DACKPT DD statement). The error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List, and is due to one of the following:

The DACKPT DD statement is missing.
The data set described by the DACKPT DD statement is not the Control-M Active Jobs file. The data set described by the DACKPT DD statement is the Control-M Active Jobs file, but of another Control-M monitor, or of a different version of Control-M.

The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR058E FILE ALLOCATED TO DDNAME "DACKPT" IS NOT CONTROL-M ACTIVE JOBS FILELink copied to clipboard

Explanation: The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file. This error message is issued by the IOALDNRS utility which is used to load/create the Manual Conditions List and may be due to one of the following:

The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.
The file allocated to the DACKPT DD statement is the Control-M Active Jobs file, but it is of a different version or of a different Control-M monitor.

The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file will not be loaded.

Corrective Action: Correct the JCL for the job.

LNR059E ACTIVE JOBS FILE IS BEING FORMATTED. PLEASE TRY AGAIN LATERLink copied to clipboard

Explanation: The Active Jobs file is currently being formatted, which indicates that the New Day procedure is running. This error message is issued by the IOALDNRS utility (used to load or create the Manual Conditions List), which terminates with a condition code of 08. The IOA Manual Conditions file is not be loaded.

Corrective Action: Try again later. If the Control-D and Control-M New Day procedures start at the same time, you need to ensure that both procedures finish before running the IOALDNRS utility or the CTDLDNRS step. Use one of the following options:

Set Control-D New Day time (DAYTIMED) long enough after Control-M New Day time (DAYTIME) to ensure that Control-M New Day is ended.
Remove the CTDLDNRS step from the CTDNDAY procedure. Run the IOALDNRS utility after both Control-M and Control-D New Day procedures have finished.

LNR060W ACTIVE JOBS FILE IS EMPTYLink copied to clipboard

Explanation: The IOA Manual Conditions file is not built. The Active Jobs file is empty. This error message is issued by the IOALDNRS utility which loads or creates the Manual Conditions List. No manual conditions are found because there are no job orders. The IOA Manual Conditions file will not be loaded.

Corrective Action: No action is required.

LNR061E FILE ALLOCATED TO DDNAME "DASINC" IS NOT THE IOA SYNCHRONIZATION FILELink copied to clipboard

Explanation: The data set described by the DASINC DD statement is not the IOA Conditions Synchronization file. This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. Possible causes are:

The file allocated to the DASINC DD statement is not the IOA Conditions Synchronization file.
The file allocated to the DASINC DD statement is the IOA Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR062E FILE ALLOCATED TO DDNAME "DANSINC" IS NOT THE IOA MANUAL CONDS SYNC FILELink copied to clipboard

Explanation: The data set described by the DANSINC DD statement is not the IOA Manual Conditions Synchronization file. This error message is issued by the IOALDNRS utility, which loads or creates the Manual Conditions List. Possible causes are:

The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is of a different version or of a different IOA monitor.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR063E NO MORE PLACE IN MANUAL CONDS FILE FOR COND `cond` ODATE `odate`Link copied to clipboard

Explanation: The Manual Conditions file is full. This error message is issued by the IOALDNRS utility which loads or creates the Manual Conditions List. No more conditions are added to the Manual Conditions List.

Corrective Action: The IOALDNRS utility reads the complete NRS file and processes it in memory. When processing completes successfully, the records are written to the file itself. Thus, message LNR063E indicates that no more space was available in the record in memory. Even though the IOAVERFY utility may show that there is still sufficient room in the file, this is because IOAVERFY only displays the initial status of the file. Increasing the size of the NRS file resolves the problem. See the NRSREC# parameter in the IOAPARM member of the IOA PARM library for details.

LNR064E INVALID PARAMETER:- `parm`Link copied to clipboard

Explanation: Invalid parameter for the IOALDNRS utility. This error message is issued by the IOALDNRS utility, which is used to load or create the Manual Conditions List. For more details, please refer to the IOALNDRS utility in the INCONTROL for z/OS Utilities Guide. The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

LNR065E MISSING PARAMETER AFTER:- `parm`Link copied to clipboard

Explanation: Missing subparameter after parm. This error message is issued by the IOALDNRS utility which is used to load or create the Manual Conditions List. For more details, please refer to the IOALDNRS utility in the INCONTROL for z/OS Utilities Guide. The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

LNR066E REDUNDANT PARAMETER: - `parm`Link copied to clipboard

Explanation: Redundant parameter for the IOALDNRS utility. This error message is issued by the IOALDNRS utility which loads or creates the Manual Conditions List. For more details, please refer to the IOALDNRS utility in the INCONTROL for z/OS Utilities Guide. The IOALDNRS utility will terminate with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the parameter syntax (the IOALDNRS utility).

LNR067W CONTROLM YES PARAMETER WILL BE IGNORED.Link copied to clipboard

Explanation: The CONTROLM YES parameter has been specified, but the indication in the IOAPARM Installation Parameters is that Control-M is not installed.

Corrective Action: No action is required.

LNR069E OPEN OF ACTIVE MISSIONS FILE FAILED - DDNAME "DAAMF"Link copied to clipboard

Explanation: Open of Control-D Active Missions file failed (the DAAMF DD statement). This error message is issued by the IOALDNRS utility which is used to load/create the Manual Conditions List and is due to one of the following:

The DAAMF DD statement is missing.
Data set described by the DAAMF DD statement is not the Control-D Active Missions file.
Data set described by the DAAMF DD statement is the Control-D Active Missions file, but of another Control-D monitor, or of a different version of Control-D.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR070E FILE ALLOCATED TO DDNAME "DAAMF" IS NOT THE EXPECTED ACTIVE MISSIONS FILELink copied to clipboard

Explanation: The file allocated to the DAAMF DD statement is not the Control-D Active Missions file. This error message is issued by the IOALDNRS utility which is used to load or create the Manual Conditions List and may be due to one of the following:

The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.
The file allocated to the DAAMF DD statement is the Control-D Active Missions file, but of another Control-D monitor, or of a different version of Control-D.

The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file is not loaded.

Corrective Action: Correct the JCL for the job.

LNR071E ACTIVE MISSIONS FILE IS FORMATTING NOWLink copied to clipboard

Explanation: The Control-M Active Missions file is currently formatting, meaning that the Control-D New Day procedure is running. This error message is issued by the IOALDNRS utility which is used to load or create the Manual Conditions List. The IOALDNRS utility terminates with a condition code of 08. The IOA Manual Conditions file will not be loaded.

Corrective Action: Try again later.

LNR072E ACTIVE MISSIONS FILE IS DAMAGED - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: The Active Missions file is probably damaged. The program stops executing with a condition code of 08.

Corrective Action: Check whether the file allocated to the DAAMF DD statement is the Control-D Active Missions file. If it is, it has been damaged - consult your IOA administrator or BMC Customer Support.

LNR073S OPEN DDNAME "SORTIN" FAILEDLink copied to clipboard

Explanation: Open of work file failed (the SORTIN DD statement) -- the IOALDNRS utility. This is due to one of the following:

The SORTIN DD statement is missing.
Data set described by the SORTIN DD statement cannot be opened for sequential read.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

LNR074S OPEN OF DDNAME "SORTOUT" FAILEDLink copied to clipboard

Explanation: Open of work file failed (the SORTOUT DD statement) - the IOALDNRS utility. This is due to one of the following:

The SORTOUT DD statement is missing.
The data set described by the SORTOUT DD statement cannot be opened for sequential read.

The program stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

LOG messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages LOG0 through LOG0xxLink copied to clipboard

This group includes messages for the Control-O product.

LOG001I UTILITY IOALOGI STARTEDLink copied to clipboard

Explanation: This information message indicates that the IOALOGI utility has started creating an IOA Log Index file based on an existing IOA Log file.

Corrective Action: No action is required.

LOG002I UTILITY ENDED: `num` KEYS { BUILT | DELETED }Link copied to clipboard

Explanation: This information message indicates the normal termination of the IOALOGI utility.

In this message, num is the count of built or deleted keys.

Corrective Action: No action is required.

LOG003I INDEX FILE IS VALIDLink copied to clipboard

Explanation: This information message indicates that the current IOA Log Index file corresponds to information contained in the IOA Log file.

Corrective Action: No action is required.

LOG004E ERROR `errorNumber` AT LINE `lineNumber`. CURRENT STATEMENT: `stmt`Link copied to clipboard

Explanation: The IOALOGI utility failed while reading the indicated input statement from the data set referenced by the SYSIN DD statement.

The variables in this message are:

errorNumber - the error number
lineNumber - the line number in the data set referenced by the SYSIN statement
stmt - the statement of the incorrect line

The utility stops executing.

Corrective Action: Notify your INCONTROL administrator.

LOG005S INTERNAL ERROR WHILE PROCESSING DDNAME `ddName`Link copied to clipboard

Explanation: The IOALOGI utility failed while processing of the data set referenced by the ddName DD statement.

The utility stops executing.

Corrective Action: Notify your INCONTROL administrator.

LOG007S INSUFFICIENT STORAGE TO RUN UTILITYLink copied to clipboard

Explanation: The IOALOGI utility requires more storage to rebuild an Index file.

The utility stops executing.

Corrective Action: Increase the REGION size, and rerun the job.

LOG008E NO INPUT PARAMETERS. PROGRAM STOPPEDLink copied to clipboard

Explanation: The input file for the IOALOGI utility is empty.

The utility stops executing.

Corrective Action: Fill in the input statements, and rerun the job.

LOG009S ERROR OPENING SYSPRINTLink copied to clipboard

Explanation: An error was detected during an attempt to open the file referenced by the SYSPRINT DD statement.

The file referenced by the SYSPRINT DD statement is not opened.

Corrective Action: Check the system job log, and correct the problem accordingly. Rerun the job.

LOG00AS INDEX FILE IS FULL. UNABLE TO ADD A KEY.Link copied to clipboard

Explanation: The IOALOGI utility was not able to add an index element to the IOA Log Index file because it was full.

The utility stops executing.

Corrective Action: Allocate a new index file with more space than the original, and rerun the IOALOGI utility.

LOG00BI DELETE ENDED: `num` KEYS DELETEDLink copied to clipboard

Explanation: This information message indicates that during rebuilding, the IOA Log Index file deleted num index elements.

Corrective Action: No action is required.

Messages LOG900 through LOG9xxLink copied to clipboard

This group includes messages for the Control-O product.

LOG951S RELEASE OF LOG FILE NOT SUPPORTED BY THIS RELEASE OF IOA.Link copied to clipboard

Explanation: Release of Log file is not supported by this release of IOA. This could be due to one of the following reasons:

The release of IOA has been changed, and you are working on a file of a different release.
Your Log file has been corrupted.

Access to the IOA Log is prevented. An “OPEN OF LOG FILE FAILED” message will appear.

Corrective Action: Correct the allocation of your Log file (the DALOG DD statement).

LOG952S OPEN OF IOA LOG FILE FAILEDLink copied to clipboard

Explanation: Open of IOA Log file failed (the DALOG DD statement). Possible causes are:

The DALOG DD statement is missing.
The file allocated to the DALOG DD statement is not the IOA Log file.
The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA installation.

Termination of the requested function.

Corrective Action: Look on the computer log or job log SYSOUT for additional messages that clarify the reason for the failure. Then, correct the JCL for the job, or the allocations of the CLIST.

LOG954S IOA LOG FILE - WRITE ERRORLink copied to clipboard

Explanation: I/O error while writing to an IOA Log file. Possible causes are:

The file allocated to the DALOG DD statement is not the IOA Log file.
Real I/O error on the Log file.

Corrective Action: Check the contents of the computer log for additional messages which may clarify the situation, or logon again.

LOG957S FILE ALLOCATED TO DDNAME " `ddName`" IS NOT YOUR IOA LOGLink copied to clipboard

Explanation: The data set described by the specified DD statement is not the IOA Log file of this IOA installation. It is an IOA Log file, but it is of a different QNAME. It belongs to another IOA installation.

Corrective Action: Correct the JCL for the job or CLIST.

LOG958S FILE ALLOCATED TO DDNAME " `ddName`" IS NOT AN IOA LOGLink copied to clipboard

Explanation: The data set described by the specified DD statement is not an IOA Log file.

Corrective Action: Correct the JCL for the job or CLIST.

LOG959S IOA LOG FILE IS FORMATTED. IOABLG PROBABLY ABENDEDLink copied to clipboard

Explanation: The IOABLG program, which formats the IOA Log file, probably abended.

Corrective Action: Check the IOA Log format job output to see why the IOABLG program abended. Delete the file and recreate it using the INCONTROL Installation and Customization Engine (ICE).

LOG95AE UNABLE TO SYNCRONIZE THE LOG FILELink copied to clipboard

Explanation: Internal synchronization of the Log file failed, probably because another process in the same address space has been holding the Log file for a long time. A record might be missing in the IOA Log file.

The Log operation fails.

Corrective Action: Take a dump of the failing address space. When the dump completes, stop and restart it to release the internal lock. Have your system programmer call your IOA representative for assistance.

LOG95BS INVALID FUNCTIONLink copied to clipboard

Explanation: An invalid function was passed to the IOALOGXC utility.

Valid functions are:

ACT
DACT

The utility stops executing with a return code of 16.

Corrective Action: Correct the parameter syntax and reactivate.

LOG9A1E AT LEAST ONE TYPE MUST BE "Y"Link copied to clipboard

Explanation: At least one type of record must be included in the Automation Log display, but show criteria have been used to eliminate all records from the display.

Y (Yes) must be specified for at least one record type (MSG or CMD). The user specified N (No) for both of these fields in the Show Option Window.

The Show Option Window remains displayed.

Corrective Action: Specify Y for MSG or CMD or both.

LOG9A2E AT LEAST ONE WORK TYPE MUST BE "Y"Link copied to clipboard

Explanation: At least one JTYPE value must be included in the Automation Log display, but show criteria have been used to eliminate all records from the display.

Y (Yes) must be specified for at least one JTYPE (JOB, STC, or TSO). The user specified N (No) for all of these fields in the Show Option Window.

The Show Option Window remains displayed.

Corrective Action: Specify Y for at least one option (JOB, STC, or TSO).

LOG9A3E AT LEAST ONE SUPPRESS FLAG MUST BE "Y"Link copied to clipboard

Explanation: At least one type of record must be included in the Automation Log display, but show criteria have been used to eliminate all records from the display.

Y (Yes) must be specified for at least one record type (SUPPRESSED or NOT SUPPRESSED). The user specified N (No) for both of these fields in the Show Option Window.

The Show Option Window remains displayed.

Corrective Action: Specify Y for SUPPRESSED and/or NOT SUPPRESSED.

LOG9A4E AT LEAST ONE HANDLE FLAG MUST BE "Y"Link copied to clipboard

Explanation: At least one type of record must be included in the Automation Log display, but show criteria have been used to eliminate all records from the display.

Y (Yes) must be specified for at least one record type (HANDLED or NOT HANDLED). The user specified N (No) for both of these fields in the Show Option Window.

The Show Option Window remains displayed.

Corrective Action: Specify Y for HANDLED and/or NOT HANDLED.

LOG9A5E AT LEAST ONE ENVIRONMENT MUST BE "Y"Link copied to clipboard

Explanation: Records for at least one environment must be included in the Automation Log display, but show criteria have been used to eliminate all records from the display.

Y (Yes) must be specified for at least one environment field (MVS, CICS, or IMS). The user specified N (No) for all of these fields in the Show Option Window.

The Show Option Window remains displayed.

Corrective Action: Specify Y for at least one of the environment fields (MVS, CICS, or IMS).

LOG9A6E AT LEAST ONE JES3 FLAG MUST BE "Y"Link copied to clipboard

Explanation: At least one type of record must be included in the Automation Log display, but show criteria have been used to eliminate all records from the display.

If N (No) is specified for both these fields and N is specified for the CMD field, all records are eliminated from the Automation Log display. To avoid this problem the user must specify Y (Yes) for at least one field (REISSUED or NOT REISSUED). The above message is issued when the user specifies N for both fields.

The Show Option Window remains displayed.

Corrective Action: Specify Y for REISSUED and/or NOT REISSUED.

LOG9A7E AT LEAST ONE RECORD TYPE MUST BE "Y"Link copied to clipboard

Explanation: At least one type of record must be included in the Automation Log display, but show criteria have been used to eliminate all records from the display.

Y (Yes) must be specified for at least one record type (LOG, SHOUT, or TRACE). The user specified N (No) for all of these fields in the Show Option Window.

The Show Option Window remains displayed.

Corrective Action: Specify Y in at least one field (LOG, SHOUT, or TRACE).

LOG9A8E LEFT/RIGHT IS NOT ALLOWED WHEN IN WRAP MODELink copied to clipboard

Explanation: The user attempted to use command LEFT or command RIGHT while in wrap mode.

In wrap mode, information that normally continues beyond the screen display appears within the screen display. The LEFT and RIGHT commands are unnecessary and are therefore disabled until return to default mode.

The LEFT/RIGHT command is ignored.

Corrective Action: If you wish to return to default mode and enable the LEFT/RIGHT commands, reenter command WRAP.

LOG9A9E INVALID LOCATE ARGUMENTLink copied to clipboard

Explanation: An invalid time or an invalid time prefix was specified for command LOCATE.

The format for the time specified for command LOCATE is hhmmss. When a time value (a time prefix) is specified for command LOCATE, it is interpreted in the following manner:

If there is an even number of digits in the specified value, the first two digits are interpreted as the hour, the second two (if they exist) are interpreted as the minutes, and the last two (if they exist) are interpreted as the seconds.
If there is an odd number of digits in the specified value, the first digit only is interpreted as the hour, the next two digits (if they exist) as the minutes, and the last two (if they exist) are interpreted as the seconds.

Command LOCATE is ignored.

Corrective Action: Specify a valid time or time prefix for command LOCATE.

LOG9B0E INVALID LIMIT ARGUMENTLink copied to clipboard

Explanation: An invalid parameter was specified for command LIMIT.

Command LIMIT is ignored.

Corrective Action: Specify valid parameters for command LIMIT.

LOG9B1W DRIVER RETURNED RC=8 - NO DATA TO DISPLAYLink copied to clipboard

Explanation: The IOATLOG program received an unexpected return code.

This message indicates the presence of an internal error.

The Automation Log display is terminated.

Corrective Action: Contact BMC Customer Support.

LOG9B3E UNABLE TO OPEN THIS DATASETLink copied to clipboard

Explanation: The IOATLOG program is unable to open the Automation Log file.

The IOATLOG program detected an error while executing a SWAP command.

The SWAP window remains displayed.

Corrective Action: Check and correct the name of the Automation Log file specified in the SWAP window.

LOG9B4E INVALID TRACE ARGUMENTLink copied to clipboard

Explanation: An invalid parameter was specified for command TRACE.

Command TRACE is ignored.

Corrective Action: Specify valid parameters for command TRACE.

LOG9WRI LOG WRAP AROUND `number` HAS BEEN DETECTED J= `jobName` (`jobID`)Link copied to clipboard

Explanation: This information message indicates that the IOA Log file is full, a wraparound has been performed, and new records are being written starting at the top line of the Log.

The variables of this message are:

number - number of wraparounds.
jobName - name of the job or user ID that issues a message the moment the Log file is full.
jobID - ID of the job that issues a message the moment the LOG file is full.

Corrective Action: No action is required.

MAN messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages MAN800 through MAN8xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

MAN850S `modName` BLDL FAILED FOR MODULELink copied to clipboard

Explanation: BLDL for the modName module failed.

This is due to one of the following:

The module is not in one of the load module libraries used by the IOA Online Facility (Linklist, STEPLIB or invoked CALL library).
There is insufficient memory to load the program.

The requested module is not activated. Control is returned to the calling program. The IOA Online Facilities may abend on initialization.

Corrective Action: Verify whether the module appears in IOA Load library or any other concatenated load module library.

MAN851S ONLY ONE PROGRAM CAN BE SELECTEDLink copied to clipboard

Explanation: More than one program has been marked for selection.

Only one program may be selected at a time.

Corrective Action: Select one program only.

MAN852S NO PROGRAM SELECTIONLink copied to clipboard

Explanation: No program selection specified.

Corrective Action: Mark S near the program name for selection of program.

MAN853S `pgm` PROGRAM ACTIVE, CANNOT BE CANCELLEDLink copied to clipboard

Explanation: This entry is in use by a program which is currently active.

Enter the active program, and terminate its execution normally, so that the entry can be used for another program.

Corrective Action: Exit the program using the END command or use a new entry.

MAN855S INVALID PARAMETER SUPPLIED TO MODULE `modName` - `parm`Link copied to clipboard

Explanation: An invalid input parameter (parm), was supplied to the main IOA online module (modName).

The modName module expects a series of parameters to be input, which describe the environment in which it is to be activated.

The expected parameters are:

APPLTYPE=type,APPLID=id,

where

type is S (for TSO), R (for KSL), I (for ISPF) or X (for OMEGAMON)
id is the user application ID

However, these parameters were missing or invalid.

The IOA online environment is not built.

Corrective Action: Check for errors in the CLIST which activates the IOA online interface.

MAN856S DDNAME `ddName` NOT ALLOCATEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

The DD name specified in the error message was not allocated before the user entered IOA.

The IOA Online facility terminates.

Corrective Action: Allocate the specified DD name and reenter IOA.

MAN857S PRODUCT `productName` NOT RECOGNIZEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

A user tried to enter IOA using a user-defined transaction member which contained a definition of a product not recognized by IOA.

The IOA Online facility stops.

Corrective Action: Correct the product definition in the transaction member and reenter IOA.

MAN858S MEMBER NAME - `memName` IN TRANID `transMem` NOT FOUND IN PARM LIBRARYLink copied to clipboard

Explanation:Highlighted, unrollable message.

A user tried to enter IOA using a user-defined transaction.

In this message, transMem is a member that pointed to a PGM member name that did not exist in the parameter library referenced by the DD name DAONLPRM.

The Online facility terminates.

Corrective Action: Check that the PGM member is correctly specified in the transaction member. If it is correctly specified in this member, add it to the parameter library. Reenter IOA.

MAN859S TRANID MEMBER NOT FOUND - `transMem`Link copied to clipboard

Explanation: The user tried to enter IOA using a user-defined transaction.

In this message, transMem is a member that does not exist in the parameter library referenced by the DAONLPRM DD name.

The IOA Online facility stops.

Corrective Action: Add the transaction member identified in the message to the parameter library and reenter IOA.

MAN85AS INVALID KEYWORD FOUND IN - `transMem`Link copied to clipboard

Explanation: The user tried to enter IOA using a user-defined transaction.

In this message, transMem is the member that contained an invalid keyword.

The Online facility stops.

Corrective Action: Check the keywords in the transaction member and correct them accordingly. See the section on Transaction Members in the INCONTROL for z/OS Administrator Guide. Reenter the IOA Online facility.

MAN85BS PLEASE CHECK THE TRANID MEMBER - `transMem`Link copied to clipboard

Explanation: An internal error occurred when a user tried to enter IOA using a user-defined transaction.

The internal error occurred when the IOA Online facility tried to initiate the IOA session using the transMem transaction member.

The IOA Online facility stops.

Corrective Action: Supply BMC Customer Support with a printout of the transMem member.

MAN85CS ERROR OCCURRED DURING ALLOCATION PROCESS. PLEASE CHECK THE ALC MEMBERSLink copied to clipboard

Explanation: IOA online system failed to allocate a file.

When the IOA Online facility starts up, it allocates all the files needed for the current session. At least one of these files could not be allocated.

Preceding messages detail the files that could not be allocated.

The IOA Online system stops.

Corrective Action: Correct the ALCxxx members according to information from the preceding messages and reenter IOA.

MAN85DS `ddName` DDNAME IS ALLOCATED. PLEASE FREE IT AND TRY AGAINLink copied to clipboard

Explanation: The file whose DD name is specified in the error message was already allocated to the IOA Online environment when the IOA Online facility started up.

When the IOA Online facility starts up, certain files are dynamically allocated by it to the IOA environment. In this case, the file identified in the message was already allocated to the IOA environment when IOA started up.

The Online facility terminates.

Corrective Action: Deallocate this DD name from the IOA environment.

MAN85ES MODULE `modName` RETURNED WITH RC= `rc`Link copied to clipboard

Explanation:This is one of two messages with the same ID, but different text.:

A severe error occurred in the modName module when the user tried to enter an IOA option. In most cases, the called program could not issue an error message.

Valid values for rc are:

rc	Explanation
8	There is no region below the line for the application
12	There is no region above the line for the application
16	A severe error occurred. The called program issued an error message
20	A severe error occurred. An error message could not be issued

The called program abends.

Corrective Action: If modName is CTDTOBJ and RC=12, check the IOA LOG for message CTDE12E. If CTDE12E was issued, see “CTDE12E RESOURCE LIBRARY HAS AN INCORRECT FORMAT” in the INCONTROL for z/OS Messages Manual.

Otherwise, consider the following actions, according to the return code:

08, 12--In case of TSO, log off and log on again. In case of IOAOMON, stop and restart IOAOMON. If this doesn’t help, reduce the number of IOAOMON users by modifying the MAXSESS parameter in the IOAXPRM member.
16--Follow the instructions in the error message issued by the called program.
20--Contact BMC Customer Support.

MAN85ES MESSAGE `msgId` WAS NOT FOUND OR MEMBER `memName` DOES NOT EXIST IN THE MESSAGE LIBRARY.Link copied to clipboard

Explanation:This is one of two messages with the same ID, but different text.:

Either the msgId message is missing from the memName member, or the msgId message member is missing from the IOA MSG library.

Corrective Action: No action is required.

MAN85FS MAXIMUM NUMBER OF IOA SESSIONS REACHEDLink copied to clipboard

Explanation: TSO user tried to activate a fifth IOA session in his TSO address space.

In the TSO environment, the user can activate IOA sessions by executing the IOATSO or IOAISPF CLISTs. IOA allows a maximum of 4 sessions to be activated. If the user tries to activate a fifth session, this error message is generated.

The fifth session is not established.

Corrective Action: Terminate one of the previous sessions in order to initiate a new session.

MAN85GS USER PROFILE MEMBER CANNOT BE ACCESSEDLink copied to clipboard

Explanation: IOA could not access the user profile member during IOA online initialization.

The IOA online session terminates.

Corrective Action: Call your INCONTROL administrator.

MAN85HS UNABLE TO LOCATE MESSAGE `msgId`, CALL TECHNICAL SUPPORT FOR HELPLink copied to clipboard

Explanation: The msgId message is missing from the IOA MSG library.

Corrective Action: No action is required.

MAN85HS THE MESSAGE PROCESSING FACILITY WAS NOT INITIALIZED PROPERLYLink copied to clipboard

Explanation: The message processing facility was not initialized properly. It is therefore impossible to issue any messages.

The IOA session is ended.

Corrective Action: No action is required.

MAN85HS UNABLE TO OBTAIN ENQ FOR THE MESSAGES or UNABLE TO OBTAIN LOCK FOR THE MESSAGESLink copied to clipboard

Explanation: The message processing facility encountered a problem while trying to obtain an exclusive lock in order to issue a message.

The IOA session is ended.

Corrective Action: No action is required.

MAN85HS OPEN FAILED FOR MESSAGE LIBRARYLink copied to clipboard

Explanation: The message processing facility is unable to open the IOA MSG library.

The IOA session is ended.

Corrective Action: No action is required.

MAN85HS TOO MANY MESSAGE MEMBERS WERE LOADEDLink copied to clipboard

Explanation: The message processing facility is unable to process any more messages because of a storage shortage.

The IOA session is ended.

Corrective Action: No action is required.

MAN85HS UNABLE TO OBTAIN STORAGE FOR MESSAGELink copied to clipboard

Explanation: The message processing facility is unable to process any more messages because of a storage shortage.

The IOA session is ended.

Corrective Action: No action is required.

MAN85IS GLOBAL PROFILE VARIABLES ($PROFILE) COULD NOT BE ACCESSEDLink copied to clipboard

Explanation: An attempt to access the $PROFILE member in the IOAENV library failed.

The most common cause is that the member is held by another user or program.

The IOA Online facility is not entered.

Corrective Action: Determine which user or program is holding the member, and try to obtain its release.

MAN85JS TRANID MEMBER `memName` CONTAINS IRRELEVANT OPTIONSLink copied to clipboard

Explanation: An irrelevant option was specified in the memName transaction member.

The IOA online session terminates.

Corrective Action: Change the memName transaction member and log on again to the IOA online session.

MAN85KE AN ERROR OCCURRED WHILE THE PROFILE MEMBER WAS BEING UPDATEDLink copied to clipboard

Explanation: IOA was unable to write the user profile member.

The write process is ignored.

Corrective Action: Check whether or not there is enough space in the profile library.

MCI messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages MCIA00 through MCIAxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

MCIA20E PROGRAM CTMCIOC DISABLED OR NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIUS program failed to link to the CTMCIOC program because the program was disabled or was not defined in the CICS tables.

The CTMCIUS program scans the open/close status of CICS files defined for Control-M, and updates any changed status in the IOA Conditions file. Updating is accomplished by means of a link to the CTMCIOC program.

The CTMCIUS program stops executing.

Corrective Action: Check that the CTMCIOC program is enabled, and that it is correctly defined in the CICS PPT. For more information, please refer to the installation instructions in the IOA CICSSAMP library.

MCIA21E CTMCIUS PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCIUS program failed due to an internal error.

The CTMCIUS program scans the open/close status of CICS files defined for Control-M, and updates any changed status in the IOA Conditions file.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and err indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

The CTMCIUS program stops executing and a CICS transaction dump is produced.

Corrective Action: Check the dump and any relevant messages in the system log. If the problem is related to CICS customization, or to storage violations as a result of user transactions, correct the problem. Otherwise, contact BMC Customer Support.

MCIA22E I/O ERROR ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: An I/O error occurred while attempting to read the CICS Temporary Storage file.

This error message is issued by the CTMCIUS program, which scans the open/close status of CICS files defined for Control-M, and updates any changed status in the IOA Conditions file. Possible causes are:

Invalid record size.
CICS customization error.
File corruption.

The CTMCIUS program stops executing.

Corrective Action: Check the status of the Temporary Storage file and if possible, correct the problem. If the error persists, contact BMC Customer Support.

MCIA23E TRANSACTION `transid` NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIUS program failed to start the transid transaction because the transaction was disabled or was not defined in the CICS tables.

The transid transaction invokes the CTMCIUS program, which scans the open/close status of CICS files defined for Control-M, and updates any changed status in the IOA Conditions file. If the program ends due to an error, it issues a start command to restart itself after a given time interval. This error message is issued if the start is unsuccessful.

The CTMCIUS program stops executing.

Corrective Action: Check that transaction transid is enabled, and that it is correctly defined in the CICS PPT. For more information, please refer to the installation instructions in the IOA CICSSAMP library.

MCIA24I CONTROL-M FILE STATUS SCANNING STARTEDLink copied to clipboard

Explanation: This information message is a normal start message of the CTMCIUS program. CTMCIUS scans the status of CICS files defined for Control-M, and updates any changed status in the IOA Conditions file.

The CTMCIUS program scans the open/close status of CICS files for which conditions have been defined in the Control-M file table CTMCITB. The program updates the open/close status for files whose status was changed outside the IOA/CICS Interface.

Corrective Action: No action is required.

MCIA25I CONTROL-M FILE STATUS SCANNING ENDEDLink copied to clipboard

Explanation: This information message is a normal end message of the CTMCIUS program. CTMCIUS scans the status of CICS files defined for Control-M, and updates any changed status in the IOA Conditions file.

The CTMCIUS program usually stops executing as a result of transaction CTMP issuing a shut request. However, this message is also issued when the program stops executing as a result of an error.

If the program stopped executing due to an error, an attempt will be made to restart it automatically after a set time interval.

Corrective Action: No action is required.

MCIA27E CTMCISP PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCISP program failed due to an internal error.

The CTMCISP program is invoked by transaction CTMP to terminate the file status scanning the CTMCIUS program.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and err indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

A CICS transaction dump is produced.

MCIA28E I/O ERROR ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: An I/O error occurred while attempting to write to the CICS Temporary Storage file.

This error message is issued by the CTMCISP program, which is invoked by the CTMP transaction to terminate the CTMCIUS file status scanning program.

The error may be due to one of the following:

Invalid record size.
CICS customization error.
File corruption.

The CTMCISP program stops executing.

Corrective Action: Check the status of the Temporary Storage file and if possible, correct the problem. If the error persists, contact BMC Customer Support.

MCIA29E NO SPACE ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: A NOSPACE condition was detected while attempting to write to the CICS Temporary Storage file.

This error message is issued by the CTMCISP program, which is invoked by CTMP transaction to terminate the CTMCIUS file status scanning program.

The CTMCISP program stops executing.

Corrective Action: Delete unnecessary records from the Temporary Storage file or increase the file size.

MCIA30I FILE SCANNING SHUT REQUEST HAS BEEN ISSUEDLink copied to clipboard

Explanation: This information message indicates that transaction CTMP, which requests termination of file scanning the CTMCIUS program, has been entered.

The CTMCIUS program will detect the shut request and will stop executing.

Corrective Action: No action is required.

MCIA31E TRANSACTION `transid` NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIUP program could not start the transid transaction because the transaction is not defined in the CICS tables.

The CTMCIUP program starts the transid transaction (the CTMCIST program) in order to add a CICS-UP condition to the IOA Conditions file.

The CTMCIUP program stops executing, and the CICS-UP condition is not added.

Corrective Action: Check that the transid transaction is enabled, and that it is correctly defined in the CICS PPT. For more information, please refer to the installation instructions in the IOA CICSSAMP library.

MCIA32E SECURITY CHECK FAILED FOR TRANSACTION START `transid`Link copied to clipboard

Explanation: The CTMCIUP program could not start the transid transaction because the necessary security authorization was not available.

The CTMCIUP program starts the transid transaction (the CTMCIST program) in order to add a CICS-UP condition to the IOA Conditions file.

The CTMCIUP program stops executing and the CICS-UP condition is not added.

Corrective Action: Contact your CICS system programmer to define the correct security level in the CICS PCT entry of the started transaction, using the RSL parameter.

MCIA33E CTMCIUP PROCESSING ERROR: EIBFN= `func` EIBRCODE= `rc` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCIUP program failed due to an internal error.

The CTMCIUP program starts the transid transaction (the CTMCIST program) in order to add a CICS-UP condition to the IOA Conditions file.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and rc indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

A CICS transaction dump is produced.

MCIA34E PROGRAM CTMCIOC DISABLED OR NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCISS program, which is invoked at CICS startup, failed to link to the CTMCIOC program because the program was disabled or was not defined in the CICS tables.

The CTMCISS program builds the Temporary Storage Queue, which consists of Control-M files defined in the CTMCITB module. It does so by linking to the CTMCIOC program with an initialization request.

The CTMCISS program stops executing and the Temporary Storage Queue is not built.

MCIA35E CTMCISS PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCISS program, which is invoked at CICS startup, failed due to an internal error.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and err indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

The CTMCISS program stops executing.

Corrective Action: Check the system log for any relevant messages. If the problem is related to CICS customization, or to storage violations as a result of user transactions, correct the problem. Otherwise, contact BMC Customer Support.

MCIA36E I/O ERROR ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: An I/O error occurred while attempting to read the CICS Temporary Storage file.

This error message is issued by the CTMCISS program, which reads the Temporary Storage file in order to obtain the list of CICS files defined for Control-M in the CTMCITB table. The error may be due to one of the following:

invalid record size.
CICS customization error.
file corruption.

The CTMCISS program stops executing.

Corrective Action: Check the status of the Temporary Storage file and if possible, correct the problem. If the error persists, contact BMC Customer Support.

MCIA37E TRANSACTION `transid` NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCISS program failed to start transaction transid because the transaction was not defined in the CICS tables.

Transaction transid invokes CICS file scanning the CTMCIUS program.

The CTMCISS program stops executing.

MCIA38I CONTROL-M PLT FILE STATUS SCANNING STARTEDLink copied to clipboard

Explanation: This information message is a normal start message of the CTMCISS program. CTMCISS scans files defined in table CTMCITB to determine if the open/close status of the files has been altered.

Corrective Action: No action is required.

MCIA39I CONTROL-M PLT FILE STATUS SCANNING ENDEDLink copied to clipboard

Explanation: This information message is a normal end message of the CTMCISS program.

The CTMCISS program initialized the Temporary Storage Queue and issued a start command to transaction CTM2, which will invoke the CTMCIUS program after termination of the scanning interval.

Corrective Action: No action is required.

Messages MCID00 through MCIDxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

MCID01I CTMAJO SUCCESSFUL COMPLETIONLink copied to clipboard

Explanation: This information message notifies that the CTMAJO program, which is invoked by the CTMCIJO program, successfully placed a job order in the Active Jobs file.

Corrective Action: No action is required.

MCID02E INVALID OR NO COMMAREA SUPPLIED TO CTMCIJO ROUTINELink copied to clipboard

Explanation: Either no COMMAREA was supplied to job order submission the CTMCIJO program, or the length of the COMMAREA supplied was less than that expected by the program.

The COMMAREA must be defined according to DSECT CTMCIAJO, or COPY the CTMCICJO member.

The CTMCIJO program stops executing with a condition code of 04.

Corrective Action: Check that the length of the COMMAREA is not less than the length of DSECT CTMCIAJO or COPY the CTMCICJO member. Contact your CICS system programmer for assistance if necessary.

MCID03E CTMCIJO PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCIJO job order submission program, failed due to an internal error.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and err indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

A CICS transaction dump is produced and the program stops executing with a condition code of 52.

MCID04E STORAGE NOT AVAILABLE TO PROCESS REQUESTLink copied to clipboard

Explanation: Insufficient storage was available in CICS to process the user request.

This error message is issued by the CTMCIJO job order submission program, which requires CICS storage to build parameters for the CTMAJO program, which places the job on the Active Jobs file.

The CTMCIJO program stops executing with a condition code of 08.

Corrective Action: Retry the transaction, and if the error persists, contact your CICS system programmer.

MCID05E KEYWORD PARAMETER MISSING: `keyName`Link copied to clipboard

Explanation: Missing //*CONTROLM JCL statement with keyword keyName in the input parameter list passed to the CTMCIJO job order submission program.

The input parameter list must contain two //*CONTROLM statements, with keywords TABLE and JCL respectively. For details, refer to the section on the Control-M Quick Submit Command in the Control-M for z/OS User Guide.

The CTMCIJO program stops executing with a condition code of 12.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID06E INVALID KEYWORD FOUND: `keyName`Link copied to clipboard

Explanation: Invalid keyword keyName, found in a //*CONTROLM JCL statement in the input parameter list passed to the CTMCIJO job order submission program.

The only valid keywords for //*CONTROLM statements are TABLE and JCL, and a statement with each must be included in the input parameter list. For more details see the Control-M Quick Submit Command in the Control-M for z/OS User Guide.

The CTMCIJO program stops executing with a condition code of 16.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID07E KEYWORD TABLE ERROR FOUNDLink copied to clipboard

Explanation: The CTMCIJO job order submission program failed due to an internal error while scanning the JCL statements specified in the input parameter list.

The CTMCIJO program stops executing with a condition code of 60.

Corrective Action: Save the CICS job log and have your INCONTROL administrator contact BMC Customer Support.

MCID08E VALUE MISSING FOR `parm`Link copied to clipboard

Explanation: No value was specified for the parm parameter in a //*CONTROLM JCL statement in the input parameter list that was passed to the CTMCIJO job order submission program.

The //*CONTROLM statement contained a valid keyword (TABLE or JCL), but it was not followed by the expected data. For details, refer to the Control-M Quick Submit Command in the Control-M for z/OS User Guide.

The CTMCIJO program stops executing with a condition code of 20.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID09E INVALID VALUE FOUND: `val`Link copied to clipboard

Explanation: An invalid value val was specified for a parameter in a //*CONTROLM JCL statement in the input parameter list passed to the CTIMCIJO job order submission program.

The //*CONTROLM statement contains a valid keyword (TABLE or JCL), but the data following it is invalid for that keyword. For more information, see the Control-M for z/OS User Guide.

The CTMCIJO program stops executing with a condition code of 24.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID10E NUMBER OF JCL STATEMENTS NOT SPECIFIEDLink copied to clipboard

Explanation: The COMMAREA passed to the CTMCIJO job order submission program did not indicate the number of JCL statements included in the input parameter list.

The number of JCL statements must be indicated in the fixed part of the COMMAREA passed to the CTMCIJO program.

The CTMCIJO program stops executing with a condition code of 28.

Corrective Action: Contact your CICS system programmer for assistance.

MCID11E TABLE LIBRARY NOT SPECIFIEDLink copied to clipboard

Explanation: No scheduling table library was specified in a //*CONTROLM JCL statement in the input parameter list passed to the CTMCIJO job order submission program.

The job order request cannot be processed unless keyword TABLE is followed by a valid scheduling library name. For more details please refer to the Control-M for z/OS User Guide.

The CTMCIJO program stops executing with a condition code of 32.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID12E JCL LIBRARY NOT SPECIFIEDLink copied to clipboard

Explanation: No JCL library was specified in the //*CONTROLM JCL statement in the input parameter list passed to the CTMCIJO job order submission program.

Keyword JCL must be followed by a valid JCL library name in order for the JCL defined in the COMMAREA to be saved for subsequent processing by Control-M.

The CTMCIJO program stops executing with a condition code of 36.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID13E TABLE LIBRARY MEMBER NOT SPECIFIEDLink copied to clipboard

Explanation: No scheduling table library member was specified in a //*CONTROLM JCL statement in the input parameter list passed to the CTMCIJO job order submission program.

The job order request cannot be processed unless the MEMBER keyword is followed by a valid scheduling library member name. For more details please refer to the Control-M for z/OS User Guide.

The CTMCIJO program stops executing with a condition code of 40.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID14E INVALID DATA FOUND IN AUTOEDIT PARAMETERSLink copied to clipboard

Explanation: Invalid data was found in the AutoEdit parameter string passed to the CTMCIJO job order submission program.

The error may be due to one of the following:

An AutoEdit variable is not preceded by %%.
The statements are not separated by commas.
The number of AutoEdit parameters specified in the COMMAREA header does not match the number of AutoEdit statements in the parameter string.

The CTMCIJO program stops executing with a condition code of 44.

Corrective Action: Correct the input and re-invoke the CTMCIJO program. Contact your CICS system programmer for assistance if necessary.

MCID15E ERROR IN CTMAJO ATTACH. RC= `rc`Link copied to clipboard

Explanation: Execution of a MVS ATTACH macro ended with return code rc.

This error message is issued by the CTMCIJO job order submission program, which processes job order requests by passing parameters to the CTMAJO program by means of an MVS ATTACH macro.

The subtask for executing CTMAJO is not created and the CTMCIJO program stops executing with a condition code of 48.

Corrective Action: Refer to the relevant IBM manual for an explanation of the return code. If the problem cannot be resolved, contact BMC Customer Support.

MCID16E ERROR IN CTMAJO PROCESSING. RC= `rc`Link copied to clipboard

Explanation: The CTMCIJO job order submission program invoked the CTMAJO program to process the job order specified by the input parameter list. Processing of the request ended with return code rc.

The CTMCIJO program stops executing with a condition code of 52.

Corrective Action: For an explanation of the return code returned by the CTMAJO program, refer to the ROSORDER sample program in the IOA SAMPLE library. If the problem cannot be resolved, contact BMC Customer Support.

MCID17E ROUTINE CTMAJO ABENDED `abCode`Link copied to clipboard

Explanation: The CTMCIJO job order submission program invoked the CTMAJO program to process the job order specified by the input parameter list. The CTMAJO program abended with code abCode.

The CTMCIJO program stops executing with a condition code of 56.

Corrective Action: For an explanation of the abend code, refer to the relevant IBM manual. If the problem cannot be resolved, contact BMC Customer Support.

Messages MCIF00 through MCIFxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

MCIF01E COMMAREA LENGTH INVALIDLink copied to clipboard

Explanation: The length of the CICS COMMAREA supplied to the CTMCICN prerequisite condition processing program was less than that expected by the program.

The parameter list is passed to the program by means of a CICS COMMAREA which must be defined according to DSECT CTMCIACN or COPY the CTMCICCN member.

The CTMCICN program stops executing.

Corrective Action: If the program which links to CTMCICN is user-written, check that the length of the COMMAREA specified in the LINKD statement is not less than the length of DSECT CTMCIACN or COPY the CTMCICCN member. Contact your CICS system programmer for assistance if necessary.

If the program linking to CTMCICN is part of the IOA/CICS Interface and has not been altered, have your INCONTROL administrator contact BMC Customer Support.

MCIF02E CONDITION ALREADY FOUND OR MISSINGLink copied to clipboard

Explanation: The condition specified in an ADD request already exists in the IOA Conditions file, or the condition specified in a DELETE or CHECK request could not be found.

This message is issued by prerequisite processing the CTMCICN program.

The CTMCICN program stops executing.

Corrective Action: No action is required.

MCIF03E ONE OR MORE PARAMETERS PASSED TO PROGRAM "CTMCICN" ARE INVALIDLink copied to clipboard

Explanation: An invalid parameter was passed to the CTMCICN prerequisite condition processing program.

The CTMCICN program stops executing.

Corrective Action: If the program which links to CTMCICN is user-written, check that the parameters passed to the program conform to DSECT CTMCIACN or COPY the CTMCICCN member. If the program linking to CTMCICN is part of the IOA/CICS Interface and has not been altered, have your INCONTROL administrator contact BMC Customer Support.

MCIF04E ROUTINE `routineName` ABENDED `abCode`Link copied to clipboard

Explanation: An internal error occurred in routine routineName, and processing abends with code abCode.

This error message is issued by prerequisite condition processing the CTMCICN program, which accesses the IOA Conditions files by means of subtask IOACND.

The CTMCICN program stops executing.

Corrective Action: Have your INCONTROL administrator inform BMC Customer Support of the abend code.

MCIF05E ERROR IN IOACND ATTACH. RC= `rc`Link copied to clipboard

Explanation: Execution of an MVS ATTACH macro ended with return code rc.

This error message is issued by prerequisite condition processing the CTMCICN program, which accesses the IOA Conditions files by means of an ATTACH to subtask IOACND.

The CTMCICN program stops executing.

Corrective Action: Refer to the relevant IBM manual for an explanation of the return code. If the problem cannot be resolved, contact BMC Customer Support.

MCIF06I "`func`" SUCCESSFUL. CONDITION: `cond`Link copied to clipboard

Explanation: This information message is issued by prerequisite condition processing the CTMCICN program, and indicates that function func was successfully executed for prerequisite condition cond.

Corrective Action: No action is required.

MCIF11E PROGRAM CTMCICN NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIST program failed to link to the CTMCICN program because the program was disabled, or was not defined in the CICS tables.

The CTMCIST program attempted to link to the CTMCICN program in order to set a CICS-UP or CICS-DOWN condition in the IOA Conditions file.

The CICS-UP or CIS-DOWN condition is not added to the IOA Conditions file.

Corrective Action: Check that the CTMCICN program is enabled, and that it is correctly defined in the CICS tables. For more information, please refer to the installation instructions in the IOA CICSSAMP library.

MCIF12E NO INPUT PARAMETER RECEIVEDLink copied to clipboard

Explanation: The CTMCIST program did not receive an UP or DOWN input parameter.

The CTMCIST program is invoked by means of a START command from CTMCIUP or CTMCIDN during CICS startup and shutdown respectively. Include the UP or DOWN parameter with the START command, to indicate whether to add CICS-UP or a CICS-DOWN condition to the IOA Conditions file.

The CTMCIST program stops executing.

Corrective Action: Supply the correct parameter with the START command. Contact your CICS system programmer for assistance if necessary.

MCIF13I CICS STATUS SET SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that a CICS-UP or CICS-DOWN condition was successfully added to the IOA Conditions file.

This message is issued when the CTMCIST program is invoked by means of a START command from CTMCIUP or CTMCIDN.

Corrective Action: No action is required.

MCIF14E CTMCIST PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCIST program, which sets CICS-UP and CICS-DOWN conditions in the IOA Conditions file, failed due to an internal error.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and err indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

The program stops executing, and a CICS transaction dump is produced.

MCIF21E INVALID OR NO COMMAREA SUPPLIED TO CTMCIOC ROUTINELink copied to clipboard

Explanation: The length of the CICS COMMAREA supplied to the CTMCIOC program was less than that expected by the program.

The CTMCIOC program is called to open or close Control-M files defined in table CTMCITB. Parameters are passed to the program by means of a CICS COMMAREA which must be defined according to DSECT CTMCIAOC, or COPY the CTMCICOC member.

The CTMCIOC program stops executing with a condition code of 04.

Corrective Action: If the program which links to CTMCIOC is user-written, check that the length of the COMMAREA specified in the LINK statement is not less than the length of DSECT CTMCIAOC or COPY the CTMCICOC member. Contact your CICS system programmer for assistance if necessary.

If the program linking to CTMCIOC is part of the IOA/CICS Interface and has not been altered, have your INCONTROL administrator contact BMC Customer Support.

MCIF22E FUNCTION NOT SPECIFIED OR INVALIDLink copied to clipboard

Explanation: The parameter list passed to the CTMCIOC program contained either no function or an invalid function.

The CTMCIOC program is called to open or close Control-M files defined in table CTMCITB. Valid functions are O (open) and C (close).

The CTMCIOC program stops executing with a condition code of 08.

Corrective Action: Supply a valid function.

MCIF23E GROUP NOT SPECIFIED OR NOT FOUND ON FILELink copied to clipboard

Explanation: The parameter list passed to the CTMCIOC program contained either no group, or a group which could not be found on the Temporary Storage Queue of Control-M files.

This error message is issued by the CTMCIOC program, which is called to open or close Control-M files defined in table CTMCITB.

The CTMCIOC program stops executing with a condition code of 12.

Corrective Action: Supply a valid value for the GROUP parameter.

MCIF24E DATASET NOT SPECIFIED OR NOT FOUND ON FILELink copied to clipboard

Explanation: The parameter list passed to the CTMCIOC program contained either no data set name, or a data set name which could not be found on the Temporary Storage Queue of Control-M files.

This error message is issued by the CTMCIOC program, which is called to open or close Control-M files defined in table CTMCITB.

The CTMCIOC program stops executing with a condition code of 16.

Corrective Action: Supply a valid value for the DSN parameter.

MCIF25E DDNAME NOT SPECIFIED OR NOT FOUND ON FILELink copied to clipboard

Explanation: The parameter list passed to the CTMCIOC program contained either no DD name, or a DD name which could not be found on the Temporary Storage Queue of Control-M files.

This error message is issued by the CTMCIOC program, which is called to open or close Control-M files defined in table CTMCITB.

The CTMCIOC program stops executing with a condition code of 20.

Corrective Action: Supply a valid value for the DD parameter.

MCIF26E STORAGE NOT AVAILABLE TO PROCESS REQUESTLink copied to clipboard

Explanation: Insufficient CICS DSA storage was available to process the user request.

This message is issued by the CTMCIOC program, which is called to open or close Control-M files defined in table CTMCITB. The program failed during a CICS GETMAIN command.

The CTMCIOC program stops executing with a condition code of 08.

Corrective Action: Retry the transaction, and if the error persists, contact your CICS system programmer.

MCIF27I DDNAME= `ddName` ALLOCATED TO CICS `cics_version` DSNAME= `dsn`Link copied to clipboard

Explanation: This information message is issued by the CTMCIOC program, and indicates that a Control-M file defined in table CTMCITB was successfully allocated to CICS as a result of a request to open it.

Corrective Action: No action is required.

MCIF28I DDNAME= `ddName` DEALLOCATED FROM CICS `cics` DSNAME= `dsn`Link copied to clipboard

Explanation: This information message is issued by the CTMCIOC program, and indicates that a Control-M file defined in table CTMCITB was successfully deallocated from CICS as a result of a request to close it.

Corrective Action: No action is required.

MCIF29I DDNAME= `ddName` OPEN SUCCESSFULLink copied to clipboard

Explanation: This information message is issued by the CTMCIOC program, and indicates that a request to open a Control-M file defined in table CTMCITB was successfully performed.

Corrective Action: No action is required.

MCIF30I DDNAME= `ddName` CLOSE SUCCESSFULLink copied to clipboard

Explanation: This information message is issued by the CTMCIOC program, and indicates that a request to close a Control-M file defined in table CTMCITB was successfully performed.

Corrective Action: No action is required.

MCIF31E DDNAME= `ddName` ERROR= `rc rsn info_code msg`Link copied to clipboard

Explanation: The CTMCIOC program was called to open or close Control-M files defined in the CTMCITB table. However, an error occurred during file allocation or deallocation processing.

The variables in this message are:

rc - the return code produced by the dynamic allocation routine
rsn - the reason code produced by the dynamic allocation routine
info_code - the information code produced by the dynamic allocation routine
msg - the meaning of the return codes

For further explanation of the return codes, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The CTMCIOC program stops executing with a condition code of 28.

Corrective Action: Contact your CICS system programmer for assistance if necessary.

MCIF32E DDNAME= `ddName` NOT DEFINED IN FCTLink copied to clipboard

Explanation: The CTMCIOC program was called to open or close Control-M files defined in the CTMCITB table, but the DD name specified in the Control-M files table is not defined in the FCT of the specific CICS.

The DD name is ignored and processing either continues with the next member of the group (if group processing was specified), or the program stops executing.

Corrective Action: No action is required.

MCIF33E DDNAME= `ddName` AUTHORIZATION REQUIRED TO PROCESS REQUESTLink copied to clipboard

Explanation: The CTMCIOC program was called to open or close Control-M files defined in table CTMCITB. However, the file referenced by the ddName DD statement could not be opened because the necessary security authorization was not available.

The CTMCIOC program stops executing with a condition code of 40.

Corrective Action: Contact your CICS system programmer to define the correct security level for the transaction, both for the SET command to perform file open/close, and for access to the specific data set.

MCIF34E DDNAME= `ddName` I/O ERROR IN ACCESSING DATASETLink copied to clipboard

Explanation: The CTMCIOC program was called to open or close Control-M files defined in table CTMCITB, but the open/close failed for a VSAM file.

The CTMCIOC program stops executing with a condition code of 44.

Corrective Action: Check that the data set is properly defined and that the definition conforms to the FCT definition for the data set.

MCIF35E PROGRAM "`pgm`" DISABLED OR NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIOC program was called to open or close Control-M files defined in table CTMCITB. However, its attempt to link or load program pgm failed.

The CTMCIOC program stops executing with a condition code of 52.

Corrective Action: Check that all programs for the IOA/CICS Interface are enabled and correctly defined in the CICS PPT/PCT. For more information, please refer to the installation instructions in the IOA CICSSAMP library.

MCIF36E DDNAME= `ddName` UNABLE TO CLOSE DATASETLink copied to clipboard

Explanation: The file referenced by the DD name identified in the message could not be closed.

The CTMCIOC program was called to close Control-M files defined in table CTMCITB. The program made the maximum number of attempts permissible to close the data set, but was unsuccessful. The maximum number of close attempts is set in installation modifiable variable &TRYLIM, in the CTMCIGLC member, and has a default value of three.

The CTMCIOC program stops executing with a condition code of 48.

Corrective Action: Check that all transactions holding the file have terminated and then re-enter the CLOSE request. If necessary, have your CICS system programmer increase the value of variable &RTRYLIM.

MCIF37E CTMCIOC PROCESSING ERROR: EIBFN= `func` EIBRCODE= `error` ABEND= `abend` Link copied to clipboard

Explanation: The CTMCIOC program failed due to an internal error.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and error indicates the error code.

In the case of a program check, abend indicates the CICS abend code.

The program stops executing with a condition code of 64 and a CICS transaction dump is produced.

MCIF38E I/O ERROR ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: An I/O error occurred while attempting to access records in the CICS Temporary Storage file.

This error message is issued by the CTMCIOC program, which was called to open or close Control-M files defined in table CTMCITB.

The error may be due to one of the following:

invalid record size
CICS customization error
file corruption

The CTMCIOC program stops executing with a condition code of 60.

Corrective Action: Check the status of the Temporary Storage file and if possible correct the problem. If the error persists, contact BMC Customer Support.

MCIF39E NO SPACE ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: A NOSPACE condition was detected while attempting to write or update records on the Temporary Storage file.

This error message is issued by the CTMCIOC program, which was called to open or close Control-M files defined in table CTMCITB.

The CTMCIOC program stops executing with a condition code of 56.

Corrective Action: Delete unnecessary records from the Temporary Storage file or increase the file size.

MCIF40I `num1` OF `num2` FILES PROCESSED SUCCESSFULLYLink copied to clipboard

Explanation: This information message is issued by the CTMCIOC program, which is invoked to open or close Control-M files defined in table CTMCITB, and indicates that number1 files were processed successfully from a group containing number2 files.

This summary message is issued following processing of a file group, and follows messages MCIF29I or MCIF30I which are issued to indicate the successful processing of the individual files.

Corrective Action: No action is required.

MCIF41I TEMPORARY STORAGE FILE SUCCESSFULLY INITIALIZEDLink copied to clipboard

Explanation: This information message indicates that the CTMCIOC program has successfully built the Temporary Storage Queue containing the Control-M files defined in table CTMCITB.

Corrective Action: No action is required.

MCIF42E ERROR INVOKING DYNAMIC ALLOCATION SUBTASK. INLINE SVC WILL BE USEDLink copied to clipboard

Explanation: An error occurred during an ATTACH of a dynamic allocation subtask.

This error message is issued by the CTMCIOC program, which is called to open or close Control-M files defined in table CTMCITB.

The dynamic allocation SVC will be invoked from the CTMCIOC mainline program.

Corrective Action: Check the CICS job log for any additional messages. Verify that OSCORE is sufficiently large for the IOACND program. For details of the CICS OSCORE requirements for the product, please refer to the installation instructions in the IOA CICSSAMP library. Contact your CICS system programmer for assistance if necessary.

MCIF43E DDNAME= `ddName` ALLOCATED DSNAME DOES NOT MATCH TABLE SPECIFICATIONLink copied to clipboard

Explanation: The CTMCIOC program was called to open a Control-M file defined in table CTMCITB. However, the data set name specified in table CTMCITB for the identified DD name did not match the data set name currently allocated in CICS for this DD name.

The CTMCIOC program stops executing with a condition code of 68.

Corrective Action: Correct the data set name in table CTMCITB so that it matches the data set name currently allocated to the DD name in CICS.

MCIF44E DDNAME= `ddName` DISPOSITION CANNOT BE ALTERED FOR AN OPEN FILELink copied to clipboard

Explanation: An attempt was made to change the disposition of an open file.

This message is issued by the CTMCIOC program, which was invoked in order to process a Control-M file defined in table CTMCITB.

The CTMCIOC program stops executing with a condition code of 72.

Corrective Action: Close the file before specifying a different disposition.

MCIF45E INVALID CONTROL-M FILE TABLE LENGTHLink copied to clipboard

Explanation: The total length of the Control-M file table CTMCITB is not a multiple of the length of a file entry.

This message is issued by the CTMCIOC program, which is invoked to build the Temporary Storage Queue containing a list of Control-M files as defined in table CTMCITB. The program performs a validity check on file table CTMCITB in order to calculate the number of entries in the table. The problem may have been caused by assembly of the table using the CICS command level assembly procedure, instead of a standard assembly procedure, as is required.

The CTMCIOC program stops executing with a condition code of 76.

Corrective Action: Ensure that the length of the CTMCITB module is correct. Reassemble the table using a standard assembly procedure if it was incorrectly assembled originally. Contact your CICS system programmer for assistance if necessary.

MCIF46I ALL CONTROL-M FILES ALREADY CLOSEDLink copied to clipboard

Explanation: This information message is issued by the CTMCIOC program during CICS shutdown processing.

The CTMCIDN program invoked the CTMCIOC program with a request to close all Control-M files defined in table CTMCITB. However, all Control-M files were already closed.

Corrective Action: No action is required.

MCIF50E PROGRAM CTMCIOC DISABLED OR NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCICT program failed to link to the CTMCIOC program because the program was disabled or was not defined in the CICS tables.

The CTMCICT program is invoked by transactions CTMO/CTMC in order to process open/close requests for files defined in the Control-M file table CTMCITB. The program attempted to link to the CTMCIOC program to process the requests.

The CTMCICT program stops executing.

MCIF51E INVALID DATA RETURNED IN COMMAREA OF LINK TO ROUTINE CTMCIOCLink copied to clipboard

Explanation: An invalid table address was returned to the CTMCICT program.

The CTMCICT program, which processes open/close requests for files defined in the Control-M file table CTMCITB, links to the CTMCIOC program in order to process the request. When processing is requested for more than one file, diagnostic messages for each file are returned to the CTMCICT program in a table pointed to by an address in the COMMAREA.

The CTMCICT program stops executing.

Corrective Action: Check the CICS job log for additional messages which may indicate the cause of the problem. If necessary, contact BMC Customer Support.

MCIF52E INVALID INPUT DATA LENGTH FOUNDLink copied to clipboard

Explanation: The CTMCICT program failed due to an internal error.

The error occurred while processing input data for transaction CTMO/CTMC, following a CICS RECEIVE command.

The CTMCICT program stops executing.

Corrective Action: Check the CICS job log for any relevant CICS error messages, and contact BMC Customer Support with the information.

MCIF53E INVALID INPUT DATA ADDRESS FOUNDLink copied to clipboard

Explanation: The CTMCICT program failed due to an internal error.

The error occurred while processing input data for transaction CTMO/CTMC, following a CICS RECEIVE command.

The CTMCICT program stops executing.

Corrective Action: Check the CICS job log for any relevant CICS error messages, and contact BMC Customer Support with the information.

MCIF54E KEYWORD PARAMETER MISSING: `keyName`Link copied to clipboard

Explanation: The data entered with transaction CTMO/CTMC do not contain any of the following keywords: DD, DSN, GROUP, DISP, or COND.

At least one of the keywords must be entered following the transaction name.

The CTMCICT program, which is invoked by transaction CTMO/CTMC, stops executing.

Corrective Action: Correct the input data and re-enter the transaction.

MCIF55E INVALID KEYWORD FOUND: `keyName`Link copied to clipboard

Explanation: The data entered with transaction CTMO/CTMC contain the invalid keyword keyName.

Valid keywords are:

DD
DSN
GROUP
DISP
COND

The CTMCICT program, which is invoked by transaction CTMO/CTMC, stops executing.

Corrective Action: Correct the input data and reenter the transaction.

MCIF56E VALUE MISSING FOR KEYWORD `keyName`Link copied to clipboard

Explanation: The data entered with transaction CTMO/CTMC contain keyword keyName with no following value.

The CTMCICT program, which is invoked by transaction CTMO/CTMC, stops executing.

Corrective Action: Correct the input data and re-enter the transaction.

MCIF57E INVALID VALUE FOUND: `keyName=val`Link copied to clipboard

Explanation: The data entered with transaction CTMO/CTMC contain an invalid value, following keyword keyName.

The value found was invalid for the keyword for which it was specified.

The CTMCICT program, which is invoked by transaction CTMO/CTMC, stops executing.

Corrective Action: Correct the input data and re-enter the transaction.

MCIF59E CTMCICT PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCICT program failed due to an internal error.

The CTMCICT program is invoked by transactions CTMO/CTMC to perform open/close functions.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and err indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

A CICS transaction dump is produced.

MCIF60I FILE PROCESSING COMPLETELink copied to clipboard

Explanation: This information message indicates that the CTMCICT program, which is invoked by transactions CTMO/CTMC to perform open/close functions, completed processing successfully.

Corrective Action: No action is required.

MCIF66E COMMAND INVALIDLink copied to clipboard

Explanation: The command specified was not recognized by the CTMCIDS program, which is invoked by transaction CTM3.

Valid commands are:

M (List Commands)
K (Keys)
U (Up)
D (Down)
P (Process)
R (Reset)

Corrective Action: Enter a valid command.

MCIF67E DISP "SHR" OR "OLD" MAY BE SPECIFIEDLink copied to clipboard

Explanation: An invalid value was entered in the disposition field of the file menu displayed by transaction CTM3.

Valid values are:

Corrective Action: Enter a valid value.

MCIF68I PROCESSING REQUEST CANCELLEDLink copied to clipboard

Explanation: This information message indicates that a processing request was cancelled as a result of a user entering the R (Reset) command or pressing PF06.

A request was entered in the file menu displayed by transaction CTM3, to open or close a Control-M file. However, the request was subsequently cancelled by the user.

All processing requests are cancelled, and the display is cleared of any outstanding file commands.

Corrective Action: No action is required.

MCIF69I COMMANDS: U UP, D DOWN, P PROCESS, R RESETLink copied to clipboard

Explanation: This information message is displayed in the Control-M CICS file Management Facility Menu, as the result of the M (List Commands) command being entered by the user to request a list of valid commands.

Corrective Action: No action is required.

MCIF70E PROGRAM CTMCIOC DISABLED OR NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIDS program failed to link to the CTMCIOC program because the program was disabled or was not defined in the CICS tables.

The CTMCIDS program processes open/close requests for Control-M files defined in table CTMCITB by means of a link to the CTMCIOC program.

The CTMCIDS program stops executing.

MCIF71E CTMCIDS PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCIUS program failed due to an internal error.

The CTMCIUS program scans the open or close status of CICS files defined for Control-M, and updates any changed status in the IOA Conditions file.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and err indicates the error code.

In the case of a program check, abCode indicates the CICS abend code.

The CTMCIUS program stops executing and a CICS transaction dump is produced.

MCIF72E PROGRAM CTMCIDS INITIALIZATION ERRORLink copied to clipboard

Explanation: The CTMCIDS program failed due to an internal error.

The CTMCIDS program failed to calculate the number of entries per display due to invalid data in the Temporary Storage Queue containing the Control-M file information.

The CTMCIDS program stops executing.

Corrective Action: Delete the Control-M files Temporary Storage Queue and re-enter the transaction. If the problem persists, contact BMC Customer Support.

MCIF73I ENTRIES TO BE PROCESSED: `num.` PRESS PF5 TO PROCESS ENTRIESLink copied to clipboard

Explanation: This information message indicates that as a result of one or more requests to open/close Control-M files being entered in the file menu displayed by transaction CTM3, the num entries indicated in the message are to be processed.

The message indicates the total number of files to be processed, which may be greater than the number of individual entries selected as a result of groups being specified for processing.

Corrective Action: Press PF05 to continue processing or PF06 to cancel the request.

MCIF74E INVALID OPTION SPECIFIEDLink copied to clipboard

Explanation: An invalid line command was entered in the Control-M CICS file Management Facility Menu.

Valid line commands consist of two characters as follows:

First character O (open) or C (close).
Second character D (DD name), S (data set name), or G (group).

Corrective Action: Enter a valid line command.

MCIF76E CONFLICTING OPTIONS SPECIFIEDLink copied to clipboard

Explanation: The CTMCIDS program, which is invoked by transaction CTM3, detected that conflicting line commands were entered in the Control-M CICS file Management Facility Menu.

Both C (close) and O (open) commands were specified for a number of entries using the group option. Two or more files were found to have conflicting processing requests.

Corrective Action: Remove the conflicting commands and re-enter the request.

MCIF77E FILE LIST HAS BEEN ALTERED - RE-ENTER TRANSACTIONLink copied to clipboard

Explanation: The Temporary Storage Queue containing the Control-M file list has been updated since the last time ENTER was pressed in the Control-M CICS file Management Facility Menu.

The menu displayed is no longer up-to-date and therefore user requests cannot be processed.

The current user requests will not be processed.

Corrective Action: End the current transaction and re-enter the transaction in order to display the updated file status.

MCIF78I TOP OF DATALink copied to clipboard

Explanation: This information message appears in the Control-M CICS file Management Facility Menu to indicate that the beginning of the file list has been reached as a result of scrolling up using PF7.

Corrective Action: No action is required.

MCIF79I BOTTOM OF DATALink copied to clipboard

Explanation: This information message appears in the Control-M CICS file Management Facility Menu to indicate that the end of the file list has been reached as a result of scrolling down using PF8.

Corrective Action: No action is required.

MCIF80I CONTROL-M FILE DISPLAY PROCESSING ENDEDLink copied to clipboard

Explanation: This information message indicates that PF03 has been pressed in the Control-M CICS file Management Facility Menu, in order to end the CTM3 transaction.

Corrective Action: No action is required.

MCIF81E I/O ERROR ON TEMPORARY STORAGE FILELink copied to clipboard

Explanation: An I/O error occurred while attempting to read the CICS Temporary Storage file.

This error message is issued by the CTMCIDS program, which is invoked by transaction CTM3, and which reads the Temporary Storage file in order to obtain the list of CICS files defined for Control-M in table CTMCITB.

The error may be due to one of the following:

invalid record size
CICS customization error
file corruption

The CTMCIDS program stops executing.

Corrective Action: Check the status of the Temporary Storage file and, if possible, correct the problem. If the error persists, contact BMC Customer Support.

MCIF82E STORAGE NOT AVAILABLE TO PROCESS REQUESTLink copied to clipboard

Explanation: Insufficient DSA storage was available for the CTMCIDS program to process the user request.

This error message is issued by the CTMCIDS program, which is invoked by transaction CTM3.

The CTMCIDS program stops executing.

Corrective Action: Retry the transaction, and if the error persists, contact your CICS system programmer.

MCIF83I NO ENTRIES FOUND TO PROCESSLink copied to clipboard

Explanation: This information message indicates that PF05 was pressed in the Control-M CICS file Management Facility Menu, in order to request processing of files, but no O (open) or C (close) line commands were found.

Corrective Action: No action is required.

MCIF84I FILE PROCESSING COMPLETELink copied to clipboard

Explanation: This information message indicates that all requests for open or close of files, as specified in the Control-M CICS file Management Facility Menu, have been processed. Each file entry contains a message indicating whether or not processing was successful.

Corrective Action: No action is required.

MCIF85I ENTRY SELECTED FOR PROCESSINGLink copied to clipboard

Explanation: This information message appears in the Control-M CICS file Management Facility to indicate entries which were selected for processing.

The entries may have been selected either by specification of O (Open) or C (Close) next to the entry, or as a result of a specification being made for the file group to which the entry belongs.

Corrective Action: No action is required.

MCIF86I PFKEYS: PF03 END, PF05 PROCESS, PF06 CANCEL, PF07 UP, PF08 DOWNLink copied to clipboard

Explanation: This information message is displayed in the Control-M CICS file Management Facility Menu, as a result of the K (Keys) command being entered by the user to request a list of PF key functions.

Corrective Action: No action is required.

Messages MCIJ00 through MCIJxxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

MCIJ61E TRANSACTION `transid` NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIDN program failed to start transaction transid because the transaction was disabled or was not defined in the CICS tables.

The CTMCIDN program starts transaction transid (the CTMCIST program) in order to add a CICS-DOWN condition to the IOA Conditions file.

The CTMCIDN program stops executing.

Corrective Action: Check that transaction transid is enabled, and that it is correctly defined in the CICS PPT. For more information, refer to the installation instructions in the IOA CICSSAMP library.

MCIJ62E SECURITY CHECK FAILED FOR TRANSACTION START `transid`Link copied to clipboard

Explanation: The CTMCIDN program could not start transaction transid because the necessary security authorization was not available.

The CTMCIDN program starts transaction transid (the CTMCIST program) to write a CICS-DOWN condition in the IOA Conditions file.

The CTMCIDN program stops executing, and the CICS-DOWN condition is not added.

Corrective Action: Contact your CICS system programmer to define the correct security level in the CICS PCT entry of the started transaction using the RSL parameter.

MCIJ63E CTMCIDN PROCESSING ERROR: EIBFN= `func` EIBRCODE= `err` ABEND= `abCode`Link copied to clipboard

Explanation: The CTMCIDN program failed due to an internal error.

The CTMCIDN program is invoked in order to add a CICS-DOWN condition to the IOA Conditions file.

Where the error occurred as a result of an EXEC CICS command, func indicates the function code, and error indicates the error code.

In the case of a program check, abend indicates the CICS abend code.

The CTMCIDN program stops executing.

Corrective Action: Check the abend code specified in the message and any relevant messages in the system log. If the problem is related to CICS customization, or to storage violations as a result of user transactions, correct the problem. Otherwise, contact BMC Customer Support.

MCIJ64E PROGRAM CTMCIOC DISABLED OR NOT DEFINED IN CICSLink copied to clipboard

Explanation: The CTMCIDN program failed to link to the CTMCIOC program because the program was disabled or was not defined in the CICS tables.

The CTMCIDN program is optionally invoked during CICS shutdown processing in order to close all Control-M files defined in table CTMCITB. The program attempted to link to the CTMCIOC program in order to process the requests.

The CTMCIDN program stops executing.

MCIJ65E INVALID DATA RETURNED IN COMMAREA OF LINK TO ROUTINE CTMCIOCLink copied to clipboard

Explanation: An invalid table address was returned to the CTMCIDN program.

The CTMCIDN program, which is optionally invoked during CICS shutdown processing to close all Control-M files defined in table CTMCITB, links to the CTMCIOC program to process the request. When processing is requested for more than one file, diagnostic messages for each file are returned to the CTMCICT program in a table pointed to by an address in COMMAREA.

The CTMCIDN program stops.

Corrective Action: Check the CICS job log for additional messages which may indicate the cause of the problem. If necessary, contact BMC Customer Support for assistance.

MDT messagesLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

Messages MDT100 through MDT1xxLink copied to clipboard

This group includes messages for the IOA (infrastructure) product.

MDT130E `modName` - REASON: DEVICE `deviceId` IS NOT ASSIGNED TO THIS MEDIALink copied to clipboard

Explanation: An attempt was made to reference device deviceId, which currently is not assigned to media mediaName. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more details, refer to the section that describes the IOA Archive Server in the Control-D and Control-V User Guide. Issue a DISPLAY command to obtain information about each media and its resources that are known to the IOA Archive Server. Reissue the MODIFY operator command with the correct deviceId number.

MDT131E `mediaName` - REASON: DEVICE `deviceId` ALREADY INACTIVELink copied to clipboard

Explanation: An attempt was made to stop device deviceId, which is currently inactive. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: No action is required.

MDT132E `mediaName` - REASON: DEVICE `deviceId` ALREADY ACTIVELink copied to clipboard

Explanation: An attempt was made to start device deviceId, which is currently active.

This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: No action is required.

MDT133W `mediaName` - `nn` CYCLES PERFORMED WHILE WAITING FOR DEVICE INITIALIZATION TO BE COMPLETEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName cannot complete the initialization phase.

During initialization, the media waits for devices which have been started to complete their initialization process. No responses were received from these devices. Each “cycle” is one IOA Archive Server sleeping interval whose value (in hundredths of a second) is defined in the INTERVAL parameter in the IOASPRM member in the IOA Archive Server Installation Parameters.

The initialization of media mediaName is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If media mediaName waits a long time for devices to complete initialization and the reason for the delay cannot be determined, issue a CANCEL operator command to stop the IOA Archive Server. Start the IOA Archive Server again. If the problem is not resolved, contact BMC Customer Support.

MDT134E `mediaName` - MEDIA SHUT DOWN - INITIALIZATION OF ALL DEVICES FAILEDLink copied to clipboard

Explanation: The initialization process for all devices assigned to media mediaName failed.

Media mediaName is terminated and becomes unavailable for use by the IOA Archive Server.

Corrective Action: Check the IOA Log file and system log for messages about the initialization failure. Issue an operator command to restart media mediaName. If the problem is not resolved, contact BMC Customer Support.

MDT135W `mediaName` - `nn` CYCLES PERFORMED WHILE WAITING FOR DEVICE TO TERMINATELink copied to clipboard

Explanation: Highlighted, unrollable message.

Media mediaName cannot complete the termination phase.

During termination, media mediaName waits for devices to terminate. Each “cycle” is one IOA Archive Server sleeping interval whose value (in hundredths of a second) is defined in the INTERVAL parameter in the IOASPRM member in the IOA Archive Server Installation Parameters.

The termination of media mediaName is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If media mediaName waits a long time for devices to complete termination and the reason for the delay cannot be determined, issue a CANCEL operator command stop the IOA Archive Server. If the problem is not resolved, contact BMC Customer Support.

MDT136E `mediaName` - REASON: LENGTH OF DEVICE NUMBER IN DEVICE= `deviceId` IS INCORRECTLink copied to clipboard

Explanation: The DEVICE parameter was specified with an invalid length. The length of the DEVICE parameter in the MODIFY operator command should be:

Three digits for MVS/SP4 and below
Four digits for MVS/SP5 and above

This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: Reissue the MODIFY command with a correct DEVICE parameter.

MDT137E `mediaName` - COMMAND FAILED `cmdText`Link copied to clipboard

Explanation: An invalid command or parameter was passed to media mediaName by a MODIFY operator command. This message is followed by other messages that clarify why the operator command failed.

The MODIFY command is not executed.

Corrective Action: Check the system log for a message that indicates why the command failed. Correct the problem, and reissue the MODIFY operator command.

MDT138E `mediaName` - REASON: PARAMETER IS INVALIDLink copied to clipboard

Explanation: An invalid parameter was passed to media mediaName by the MODIFY operator command. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Enter a MODIFY command with valid parameters.

MDT139I `mediaName` - MEDIA SHUT DOWN UPON REQUEST FROM OPERATORLink copied to clipboard

Explanation: This information message indicates that media mediaName is shutting down upon the operator’s request.

Corrective Action: No action is required.

MDT13AI mediaName - MEDIA SHUT DOWN UPON REQUEST OF MAIN TASKLink copied to clipboard

Explanation: This information message indicates that media mediaName is shutting down upon the IOA Archive Server’s request.

Possible causes are:

The IOA Archive Server is shutting down due to operator request.
The IOA Archive Server encountered an unrecoverable error.

The IOA Archive Server shuts down the media before it shuts down. The IOA Log file and system log should contain additional messages concerning the situation.

Media mediaName shuts down.

Corrective Action: Check the IOA Log file and system log for messages explaining the situation. Contact the system programmer for assistance, if needed.

MDT13BE `mediaName` - REASON: VALUE SPECIFIED IN DEVICE= PARAMETER IS INVALIDLink copied to clipboard

Explanation: The DEVICE parameter was specified in a MODIFY operator command without specifying its value. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

MODIFY is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Reissue the MODIFY command with a valid DEVICE parameter.

MDT13DE `mediaName` - REASON: DEVICE= PARAMETER IS INVALID FOR DYNAMIC DEVICESLink copied to clipboard

Explanation: An attempt to start a specific device by operator command failed because the devices used by the IOA Archive Server are allocated dynamically. This message follows message IOA137E/MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

MODIFY is not executed.

Corrective Action: For more information about how to control the device, refer to the section on media and resource management in the Control-D and Control-V User Guide. Reissue the MODIFY command with appropriate parameters.

MDT13FW `mediaName` - REASON: ALL DEVICES ARE ALREADY ACTIVELink copied to clipboard

Explanation: An attempt to start one or more devices by issuing a MODIFY operator command failed, because all devices were already active.

This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command. The operator cannot increase the number of devices the IOA Archive Server can use to more than the maximum quantity defined in the IOASPRM member in the IOA Archive Server Installation Parameters.

The MODIFY command is not executed.

Corrective Action: Issue a DISPLAY command to get information about each media and its resources that are allocated to the IOA Archive Server. For more information about how to control devices, refer to the section on media and resource management in the Control-D and Control-V User Guide.

MDT140S `mediaName` - BLDL/ATTACH/LOAD FAILED FOR THE MODULE `modName`Link copied to clipboard

Explanation: Initialization of the mediaName media failed.

Possible causes are:

The Control-V LOAD library is not in the load modules search list (STEPLIB + LinkList).
Insufficient memory is available to attach the task.
The modName module is not in the LOAD library.

The IOA Archive Server shuts down.

Corrective Action: Check the system log for additional messages which clarify the situation. Try one of the following:

If the attach failed because of lack of memory, increase the REGION size in the IOA Archive Server procedure.
If the modName module does not exist in the IOA LOAD library, contact BMC Customer Support.

MDT141I `mediaName` - INITIALIZATION STARTEDLink copied to clipboard

Explanation: This information message indicates that media mediaName has started and is building the required internal environment.

Corrective Action: No action is required.

MDT142I `mediaName` - INITIALIZATION SUCCESSFULLY COMPLETEDLink copied to clipboard

Explanation: This information message indicates that media mediaName was successfully initialized.

Corrective Action: No action is required.

MDT143W `mediaName` - REASON: ALL DEVICES ARE ALREADY INACTIVELink copied to clipboard

Explanation: An attempt to stop one or more devices by issuing a MODIFY operator command failed, because all the devices were already inactive. This message follows message IOA137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Issue a DISPLAY command to get information about each media and its resources that are allocated to the IOA Archive Server.

MDT144S `mediaName` - INSUFFICIENT STORAGE FOR INITIALIZATIONLink copied to clipboard

Explanation:Highlighted, unrollable message.

Insufficient memory is available to initiate media mediaName.

Media mediaName shuts down. The IOA Archive Server shuts down.

Corrective Action: Increase the IOA Archive Server REGION size.

MDT145E `mediaName` - FREEMAIN ERROR ENCOUNTEREDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName encountered an internal error.

The media mediaName task terminates with user abend 0007. The IOA Archive Server terminates with user abend code 0006. The output includes a dump of the abend.

Corrective Action: Contact your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

MDT146E `mediaName` - MEDIA INITIALIZATION FAILEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName encountered an internal error.

This message is preceded by other messages which clarify the situation.

Media mediaName shuts down.

Corrective Action: Check the IOA Log file and the system log for messages describing the error. Contact your system programmer for assistance, if needed. If the problem is not resolved, contact BMC Customer Support.

MDT147S `mediaName` - INTERNAL ERROR DURING INITIALIZATION - MEDIA INITIALIZATION FAILEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Media mediaName encountered an internal error.

Media mediaName abends with user abend 0007. The IOA Archive Server shuts down with User Abend 0006. The output includes a dump of the abend.

Corrective Action: Contact your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

MDT148S `mediaName` - INTERNAL ERROR RC=`rc`Link copied to clipboard

Explanation: Media mediaName encountered an internal error.

One of the following actions occurs, depending on severity of the internal error:

Media mediaName terminates and IOA Archive Server continues processing.
Media mediaName abends with user abend 0007. The IOA Archive Server terminates with User Abend 0006. The output includes a dump of the abend.

Corrective Action: Check the IOA Log file and system log for messages describing the error. Contact your system programmer for assistance. If the problem is not resolved, report the value of rc to BMC Customer Support.

MDT149E `mediaName` - REASON: COMMAND IS INVALIDLink copied to clipboard

Explanation: An invalid command was passed to media mediaName by the MODIFY operator command. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section on the IOA Archive Server in the Control-D and Control-V User Guide. Enter a valid MODIFY command.

MDT14AE `mediaName` - REASON: VALUE SPECIFIED IN DEVQTY= PARAMETER IS INVALIDLink copied to clipboard

Explanation: An invalid value was specified for the DEVQTY parameter. This message follows message IOA137E or MDT137E, which indicates that operator command MODIFY failed and contains the text of the failed command. Possible causes are:

The value for the DEVQTY parameter is missing in the MODIFY operator command.
The length of the DEVQTY parameter exceeds the maximum allowable length.
The value of the DEVQTY parameter is invalid. Valid values are numeric or the character string ALL.
The value of the DEVQTY parameter is greater than the maximum quantity defined in the IOASPRM member in the IOA Archive Server Installation Parameters.
The value of the DEVQTY parameter is greater than the number of active devices allocated to the IOA Archive Server.

The MODIFY command is not executed.

MDT14BE `mediaName` - LOCATE ERROR FOR `dsn` RC= `rc`Link copied to clipboard

Explanation: A CDAM data set cannot be found in the catalog.

The user requested a report which resides on a CDAM file which is uncataloged or does not exist.

The request is ignored.

Corrective Action: Catalog the file or take other corrective action and try again.

MDT14CI `mediaName` - MEDIA SHUTTING DOWNLink copied to clipboard

Explanation: This information message indicates that media mediaName is shutting down.

Corrective Action: No action is required.

MDT14DS `mediaName` - DEVICE `deviceId` ABENDEDLink copied to clipboard

Explanation: A media internal subtask abended.

Media mediaName issues an implicit start command for device deviceId. Attempts are made to initialize this device and continue normal processing. If these attempts fail, media mediaName sets the status of the designated device to never active and this device becomes unavailable for use by the IOA Archive Server.

Corrective Action: Check the IOA Log file and system log for additional messages which indicate why device deviceId abended.

MDT14ES `mediaName` - PARAMETER DEVADDR NUMBER `num` DEFINED IN IOASPRM INSTALLATION PARAMETERS IS INVALIDLink copied to clipboard

Explanation: The DEVADDR parameter contains an invalid value.

The format of the device number specified in the DEVADDR parameter in the IOASPRM member (IOA Archive Server Installation Parameters) must be:

three digits for MVS/SP4 and below
four digits for MVS/SP5 and above

Initialization of media mediaName fails. The IOA Archive Server shuts down with a return code of 08.

Corrective Action: Set the DEVADDR parameter to a valid numeric value and restart the IOA Archive Server.

MDT14FI `mediaName` - ALL DEVICES WERE DEFINED AS INACTIVE IN IOASPRM INSTALLATION PARAMETERSLink copied to clipboard

Explanation: This information message indicates that mediaName is inactive because all devices which belong to it are defined as inactive in the IOASPRM member (IOA Archive Server Installation Parameters).

Corrective Action: If necessary, issue operator MODIFY commands to start the media and the devices.

MIG messagesLink copied to clipboard

This group includes messages for the Control-M/Tape product.

Messages MIG500 through MIG5xxLink copied to clipboard

This group includes messages for the Control-M/Tape product.

MIG5ABW DSNLENF= `dsnLength` TAPELENF= `tapeLength` TAPELEFT= `unusedLength`Link copied to clipboard

Explanation: This message is generated in the event of an unexpected tape switch or a short cartridge.

This message follows message MIG5B7W and provides the information listed below:

Variable	Explanation
`dsnLength`	Length in feet of the data set being written when the unexpected tape switch occurred.
`tapeLength`	Length of the tape in feet (taken from IOASPRM).
`unusedLength`	Estimated free space on the tape in feet when the unexpected tape switch occurred.

The file is continued on the next tape and becomes a multivolume file. Subsequent files of this migration job will be written to a new scratch volume.

Corrective Action: Check the values provided in this message and determine a new value for tape length in the IOASPRM member.

MIG5ACE ERROR INITIALIZING INPUT MEDIA `mediaName`Link copied to clipboard

Explanation: Initializing an input media for multistage migration failed.

The attempt to initialize media mediaName, in order to copy files from it to the target media, failed.

Files that should have been copied from this input media to the target media are skipped. Subsequent files are processed.

Corrective Action: Check other messages received in the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

MIG5ADE ERROR TERMINATING INPUT MEDIA `mediaName`Link copied to clipboard

Explanation: The process of terminating media mediaName for multistage migration failed.

This media is the input media for the migration job.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages received in the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

MIG5AEE ERROR ALLOCATING MIGRATED FILE `fileName`Link copied to clipboard

Explanation: A file that should be moved to another media could not be allocated.

A failure occurred while attempting to allocate an input media file.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

MIG5AFE ERROR OPENING MIGRATED FILE `fileName`Link copied to clipboard

Explanation: A file that should be moved to another media could not be opened.

A failure occurred while attempting to open an input media file.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

MIG5AGE ERROR CLOSING MIGRATED FILE `fileName`Link copied to clipboard

Explanation: A file that should be moved to another media could not be closed.

A failure occurred while attempting to close an input media file.

Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

MIG5AHE ERROR READING MIGRATED FILE `fileName`Link copied to clipboard

Explanation: A file that should be moved to another media could not be read.

A failure occurred while reading an input media file.

The migration of file filename is stopped. Subsequent files in the migration job are processed.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.

MIG5AJE ERROR CALLING CTVFNM - MIGDSNAME `dsn`, RC: `rc`Link copied to clipboard

Explanation: A failure occurred in a routine used for scanning migrated file names.

This message indicates that an internal error has occurred.

The file to be migrated, dsn, is skipped and subsequent files are processed.

Corrective Action: Record the return code and notify BMC Customer Support.

MIG5ALE INVALID FUNCTION CODE SPECIFIED FOR CTVAMIGLink copied to clipboard

Explanation: Routine CTVAMIG received an invalid function code.

This message indicates that an internal error has occurred.

The migration job continues processing but does not use “continuous migration”. A scratch volume is used for files migrated in this migration job.

Corrective Action: Notify BMC Customer Support. Reorder or rerun the migration mission.

MIG5AME CTVAMIG TERMINATED WITH ERROR. RC: `rc`Link copied to clipboard

Explanation: A failure occurred in routine CTVAMIG.

Routine CTVAMIG reads and updates migration stages in sequence without skipping a stage.

The migration job continues processing but does not use “continuous migration”. A scratch volume is used for files migrated in this migration job.

Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and rerun or reorder the migration mission.

MIG5ANI UNABLE TO ALLOCATE TAPE VOLUME `volser`, SCRATCH TAPE WILL BE USED INSTEADLink copied to clipboard

Explanation: This information message indicates that an attempt to allocate a tape volume in order to perform continuous migration failed.

The migration job attempted to allocate a specific volume that was used in a previous migration job in order to add files migrated by the current migration job after the last file on the volume.

A scratch volume is allocated for the files migrated by current migration job.

Corrective Action: Check other messages to determine the cause for the failure.

MIG5API DAMIG DD STATEMENT MISSING - FOR OLD MIG SKELETONS - A NEW VOLUME WILL BE USED FOR EACH MIG RUNLink copied to clipboard

Explanation: This information message indicates that a DD statement for the migrated user file is missing.

For each migration mission, a record that specifies information about continuous migration is saved in the migrated user file. This information enables files migrated by the current migration job to be written in the same volume used by a previous migration job for the same migration mission.

Continuous migration is not performed. Files migrated by the current migration job are written to a new scratch volume.

Corrective Action: Add DAMIG and DAMIGI DD statements for the migrated user file in migration job step MIGRAT.

MIG5B0E OPTFILE= `dsn` -FDB REWRITE FAILEDLink copied to clipboard

Explanation: The migration process failed while rewriting the File Description Block (FDB).

During the migrate-to-disk process, several extents may be written. After writing the last extent, the FDB is rewritten to the first extent.

All migrated file extents are deleted. The migration for this CDAM terminates with an error.

Corrective Action: Determine the cause of the rewrite failure and rerun the migration job.

MIG5B1I INDEX= `dsn` - MIGRATION ENDED OK VOL= `vol` PLTID= `platterId`Link copied to clipboard

Explanation: This information message indicates that the dsn index migrated successfully.

The message identifies the volume serial number and, for OSS migration, the platter ID to which the index migrated. This message is issued for each index file.

Corrective Action: No action is required.

MIG5B2I INDEX= `dsn` - HAS ALREADY BEEN MIGRATED VOL= `volser` PLTID= `platterId`Link copied to clipboard

Explanation: This information message indicates that the dsn index has previously migrated to the same target media.

This message identifies the volume serial number and, for OSS migration, the platter ID to which the index migrated.

Any previously unfinished action relating to this index migration is performed now.

Corrective Action: No action is required.

MIG5B3S DEVTYPE FAILED FOR DDNAME `ddName`, RC = `rc`Link copied to clipboard

Explanation: A tape migration job failed to obtain the device type of the file.

The macro DEVTYPE for the DDOPT DD statement failed. This macro is used after a file is written to tape so that the device type can be used for cataloging the file. The return code is the hexadecimal return code in register 15 from the DEVTYPE macro.

The migration process is terminated.

Corrective Action: Record the return code. Consult your system programmer. If necessary, contact BMC Customer Support.

MIG5B4E CATALOGING `dsn` FAILED, RC: `rc`Link copied to clipboard

Explanation: Tape migration failed to catalog the migrated file. The return code is the hexadecimal return code in register 15 from the CATALOG macro.

This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.

Corrective Action: Record the values of dsn and rc. Contact BMC Customer Support.

MIG5B5S IOAT2A FAILED IN JFCBEXAD TRANSLATION - RC: `rc`Link copied to clipboard

Explanation: Tape migration failed to get the JFCB extension.

Routine IOAT2A, which translates JBCBEXAD from token to address, received return code rc.

This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.

Corrective Action: Record the return code. Contact BMC Customer Support.

MIG5B6S IOASLOS - SORT ENDED WITH RC OTHER THAN 0Link copied to clipboard

Explanation: OSS migration failed to build platter and volume tables using routine IOASLOS.

Routine IOASLOS failed to sort platter and volume tables.

The migration process is terminated.

Corrective Action: Check the migration skeleton job. If you cannot resolve the problem, contact BMC Customer Support.

MIG5B7W AN UNEXPECTED TAPE SWITCH HAS OCCURRED - CHECK LENGTH OF TAPE DEFINITION IN IOASPRMLink copied to clipboard

Explanation: The migrated file expanded to another tape volume.

A file that was expected to fit on one volume, or in the space available on the current volume, has expanded to another volume.

Corrective Action: Check the tape length definition in the IOASPRM member. If it is too short, specify the correct length. If hardware compression is utilized, the actual compression factor may be lower than the estimated compression factor.

MIG5B8S INVALID RC FROM CTVTPCP - UNABLE TO CALCULATE DATASET LENGTH IN FEETLink copied to clipboard

Explanation: Routine CTVTPCP, which calculates tape lengths, returned a non-zero return code.

Tape migration failed to calculate the data set’s length on tape.

The migration process is terminated.

Corrective Action: Record the return code. Contact BMC Customer Support.

MIG5B9E UNABLE TO MIGRATE `dsn` - HAS MORE THAN 32767 BLOCKSLink copied to clipboard

Explanation: The number of CDAM blocks exceeds 32767.

The OSS migration process cannot migrate files which contain more than 32767 blocks.

This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.

Corrective Action: Reduce the report size or divide the report so that the number of CDAM blocks required does not exceed 32767.

MIG5BAS PARM IS OMITTED - PLEASE SPECIFY REQUIRED PARAMETERSLink copied to clipboard

Explanation: The PARM parameter is not specified in the migration job.

The user must specify a media name and prefix or the keyword “NOCHECK”.

The migration process is terminated.

Corrective Action: Add the PARM parameter and specify a media name and prefix or the keyword NOCHECK.

MIG5BBS INVALID MEDIA = `mediaName` WAS SPECIFIED IN PARM - CALL ADMINISTRATORLink copied to clipboard

Explanation: The migration process received an invalid media name in the PARM field.

The media name should be specified in the NAME parameter of the IOASPRM member in the IOA PARM library.

The migration process is terminated.

Corrective Action: Change the IOASPRM member or the migration skeleton job so a valid media name is specified in the migration job.

MIG5BCI MIGRATION STARTED FOR MEDIA = `mediaName`Link copied to clipboard

Explanation: This information message indicates that the migration process has started.

Corrective Action: No action is required.

MIG5BDE AN INVALID TAPE WAS ALLOCATED FOR MIGRATIONLink copied to clipboard

Explanation: The OPT file was successfully allocated and opened, but RDJFCB for a migrated file failed or no volumes were found in the JFCB.

This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.

Corrective Action: Ask your system programmer to contact BMC Customer Support.

MIG5BEE AN ERROR OCCURRED FOR ONE OR MORE OF THE CDAM EXTENTS OR AN INDEX FILELink copied to clipboard

Explanation: An error occurred while writing a CDAM extent or an index file.

Possible causes include:

A failure to dynamically allocate the CDAM extent or index file for a read.
A failure to write an optical file.

This CDAM data set or index is not migrated. The migration process continues to migrate other CDAM files and indexes.

Corrective Action: Check the job’s system log and SYSPRINT for error messages. Correct the problem and resubmit the migration job.

MIG5BFI PLATTER `platterId` SIDE `x` HAS AVAILABLE SPACE, BUT NO VOLUME IS AVAILABLE - PLEASE DEFINE MORE VOLSLink copied to clipboard

Explanation: This information message indicates that OSS migration found a platter side with enough space for the CDAM file but no volume was available.

The migration process could not allocate the file on platter platterId because no empty volume was available.

Another platter or side is used.

Corrective Action: Define more volumes for platter platterId side x so that it can be used for migration.

MIG5C0S CANNOT ALLOCATE DEVICE: `deviceId`Link copied to clipboard

Explanation: The OSS device could not be obtained for OSS migration, or the tape drive could not be allocated for tape migration.

The CTVSRVD program must execute before OSS migration to ensure that the IOA Archive Server releases the first device defined for OSS. A tape drive must be allocated for tape migration.

The migration process is terminated.

Corrective Action: For OSS migration, ensure the CTVSRVD program executes before the migration step. For tape migration, check if the device is available for allocation. If no error is discovered, contact BMC Customer Support.

MIG5C1E INVALID INPUT - FILE NAME MUST BE FOLLOWED BY BLANKLink copied to clipboard

Explanation: The migration process did not identify the file name.

A blank is expected at the end of the file name on the SYSIN DD statement.

The migration process is terminated.

Corrective Action: Check the migration skeleton job for an error in the SYSIN data set definition. If no error is found, contact BMC Customer Support.

MIG5C2E LOCATE ERROR FOR FILE `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The migration process encountered a data set that could not be located.

A CDAM extent or index file was not cataloged.

The entire CDAM data set or index file is not migrated. Other data sets continue to migrate.

Corrective Action: Correct the problem and rerun the Migration Mission.

MIG5C3E OBTAIN FAILED FOR FILE `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: A file could not be obtained on the device to which it was cataloged.

The migration process uses LOCATE and OBTAIN macros to get file attributes. The OBTAIN macro failed.

The entire CDAM data set or index file is not migrated. Other data sets continue to migrate.

Corrective Action: Correct the problem and rerun the Migration Mission.

MIG5C4E MIGRATION IS NOT ALLOWED FOR MORE THAN 5 TAPES - CDAM=`dsn`Link copied to clipboard

Explanation: The CDAM file for the dsn data set spans more than five tape volumes.

Before writing each file, the migration process determines if the file will fit on a volume, based on the media capacity specified in the IOASPRM member. If the file is larger than the specified volume capacity, the migration process uses as many volumes as needed (up to a maximum of five).

The CDAM file is not migrated.

Corrective Action: Modify the report (for example, by subdividing it into two or more reports) or the decollating mission (for example, by specifying migration to a different media) so that the migrated file will not require more than five tape volumes.

MIG5C5E INVALID BLKSIZE OF FILE=`dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The file block size is larger than 100K bytes.

BLKSIZE must not exceed 100K bytes.

This data set is not migrated.

Corrective Action: Redefine the block size and rerun the Migration Mission.

MIG5C6E TTR TO BBB CONVERSION FAILEDLink copied to clipboard

Explanation: A CDAM TTR could not be converted to BBB.

IOASTBT calculates the BBB of the CDAM. The conversion failed for this CDAM file.

This CDAM file is not migrated. Other CDAM files continue to migrate.

Corrective Action: Correct the problem and rerun the Migration Mission. If the problem cannot be resolved, contact BMC Customer Support.

MIG5C7S INVALID UNIT NAME DEFINED IN IOASPRM: `unitName`Link copied to clipboard

Explanation: The unit name of the target media is unknown to the migration process. The TYPE parameter in the IOASPRM member contains an invalid value.

The migration process is terminated.

Corrective Action: Correct the TYPE parameter. Rerun the Migration Mission.

MIG5C8S DEVICE `deviceId` IS OUT OF SPACELink copied to clipboard

Explanation: No more space is available on the deviceId device.

There is no volume with enough space for this migration.

The migration process is terminated.

Corrective Action: Free space on the volumes available to the migrated files allocation. Rerun the migration mission.

MIG5C9S IOASLOS RETURNED NON-ZERO RC: `rc`Link copied to clipboard

Explanation: The IOASLOS module failed.

OSS migration uses the IOASLOS module to load OSS platter and volume tables to memory.

The migration process is terminated.

Corrective Action: Check the OSS migration skeleton for errors and rerun the Migration Mission. If the problem persists, contact BMC Customer Support.

MIG5CAI CDAM= `dsn` - MIGRATION ENDED OK VOL= `volser` PLTID= `platterId`Link copied to clipboard

Explanation: This information message indicates that a Migration Mission completed successfully.

The message identifies the volume serial number and, for OSS migration, the platter ID to which the CDAM data set migrated. This message is issued once for each CDAM extent.

Corrective Action: No action is required.

MIG5CBS OPEN OF DDNAME `ddName` FAILEDLink copied to clipboard

Explanation: The data set referenced by the ddName DD statement could not be opened.

Possible causes are:

The ddName DD statement is missing.
The data set referenced by the ddName DD statement does not exist.

The migration process is terminated.

Corrective Action: Check the migration skeleton job for errors and rerun the Migration Mission.

MIG5CCI MIGRATION OF `dsn` HAS STARTEDLink copied to clipboard

Explanation: This information message indicates that a Migration Mission started processing the CDAM data set whose name is dsn.

Corrective Action: No action is required.

MIG5CDI MIGRATION OF `dsn` HAS ENDEDLink copied to clipboard

Explanation: This information message indicates that a Migration Mission finished processing the CDAM data set whose name is dsn.

The CDAM data set migrated successfully. This message is issued once after all extents of the CDAM file have migrated.

Corrective Action: No action is required.

MIG5CEI CDAM `dsn` HAS ALREADY BEEN MIGRATED VOL= `volser` PLTID= `platterId`Link copied to clipboard

Explanation: This information message indicates that CDAM data set dsn has already migrated to the same target media.

The message identifies the volume serial number and, for OSS migration, the platter ID to which the CDAM data set migrated. This message is issued once for each CDAM extent.

Any previously unfinished action relating to this CDAM migration is performed now.

Corrective Action: No action is required.

MIG5CFI STOP TIME FOR MIGRATION PROCESS WAS REACHED - EXITINGLink copied to clipboard

Explanation: This information message indicates that the time for ending the migration process has passed. The stop time defined in the MIGENDTM parameter in the IOASPRM member in the IOA PARM library prevents the migration process from interfering with online work during the day.

The migration process is terminated when the currently migrating CDAM data set finishes migrating.

Corrective Action: In the future, start the migration process earlier, or change the MIGENDTM parameter to a later time. Order the migration mission again the next night to complete the migration.

MIG5CGS ERROR IN `routineName`. RC IN R15: `rc`Link copied to clipboard

Explanation: Internal routine routineName failed.

The migration process terminates with a return code of 16 in register 15.

Corrective Action: Contact BMC Customer Support.

MIG5CHS NO MORE ROOM ON DISKS WITH PREFIX: `prefix`Link copied to clipboard

Explanation: An attempt to write a data set on disk failed because the data set requires more space than is available on any disk with the specified prefix.

The data set is not written or cataloged.

Corrective Action: Do one or more of the following:

Assign the specified prefix to one or more additional disks.
Delete unneeded data sets from disks with the specified prefix.
Specify a different disk prefix for the data set that was not written.

MIG5CIE ERROR DELETING FILE `dsn` - FILE SKIPPEDLink copied to clipboard

Explanation: The migration job has encountered a file which could not be deleted.

The migration job could not delete a file during cleanup after an error occurred while writing a migrated file to DASD.

The file is not deleted.

Corrective Action: Determine why the delete failed. Delete the file before rerunning the migration process.

MIG5CKW MIGRATION TO ANOTHER DISK TYPE CAUSES A WASTE OF X‘ `nnnnn`’ BYTES IN EACH TRACKLink copied to clipboard

Explanation: This warning message is issued when a BLKSIZE definition causes disk space to be wasted.

The CDAM file’s BLKSIZE becomes the BLKSIZE of the migrated file. The disk migration process discovered that the migrated file BLKSIZE wastes a large number of bytes on each track.

The file is migrated.

Corrective Action: Consider redefining the CDAM file’s BLKSIZE to minimize wasted disk space after migration.

MIG5CNE ERROR WRITING FDB, RC: `rc`Link copied to clipboard

Explanation: The Filetek storage machine WRITE function that is activated by a migration job failed.

In this message, rc is the return code from the WRITE function.

The migration job skips the problematic file and continues with the next file.

Corrective Action: Check the return code of the WRITE function against the Filetek documentation, and correct the problem accordingly.

MIG5CPE ERROR WRITING BLOCK, RC: `rc`Link copied to clipboard

Explanation: The Filetek storage machine WRITE function that is activated by a migration job failed.

In this message, rc is the return code from the WRITE function.

The migration job skips the problematic file and continues with the next file.

Corrective Action: Check the return code of the WRITE function against the Filetek documentation, and correct the problem accordingly.

MIG5CUE ERROR IN LOCATE PROCESSING IN FTK OPT = `fileName`. RC: `rc`Link copied to clipboard

Explanation: The migration job failed to locate a file in the Filetek storage machine.

The variables in this message are:

fileName - the name of the file that the migration job is unable to locate
rc - the return code from the migration job LOCATE function

The migration job skips the problematic file and continues with the next file.

Corrective Action: Check the messages the migration job issues for the locate failure, and correct accordingly.

MIG5CVE START-SEARCH PROCESSING FAILED. OPT = `fileName`, RC: `rc`Link copied to clipboard

Explanation: The Filetek storage machine START_SEARCH function that was activated by a migration job failed.

The variables in this message are:

fileName - the name of the file searched for by the migration job
rc - the return code from the START_SEARCH function

The migration job skips the problematic file and continues with the next file.

Corrective Action: Check the return code of the START_SEARCH function against the Filetek documentation, and correct the problem accordingly.

MIG5CWE END-SEARCH PROCESSING FAILED, OPT = `fileName`, RC: `rc`Link copied to clipboard

Explanation: The Filetek storage machine END_SEARCH function that was activated by a migration job failed.

The variables in this message are:

fileName - the name of the file searched for by the migration job
rc - the return code from the END_SEARCH function

The migration job skips the problematic file and continues with the next file.

Corrective Action: Check the return code of the END_SEARCH function against the Filetek documentation, and correct the problem accordingly.

MIG5DAW NO. OF BLOCKS IN OBJECT = `obj_num` IS TOO LARGE FOR BLOCKSIZE = `blksize`. USE MAXIMUM OBJECT SIZELink copied to clipboard

Explanation: OAM MEDIA issued a warning that the total size of the object exceeds the maximum.

The user-defined number of blocks in an object was multiplied by the block size. The result exceeded the maximum allowed size. The maximum size allowed by Control-D is 3,000,000 bytes.

obj_num - the number of blocks (specified by the user) for the object
blksize - the size of each block

The object size is automatically set to be the maximum possible size. This value is both a multiple of blocksize and a number less than 3,000,000.

Corrective Action: Consider reducing the value of the OBJSIZ parameter in IOASPRM.

MIG5DHW IN LOCATE PROCESSING, OBJECT 0 -NOT FOUND `collName`Link copied to clipboard

Explanation: During LOCATE processing in OAM, Control-D found a collection without a first object.

IBM macro OSREQ was issued with a QUERY request to OAM on the first object in the collection. This object was not found. However, the reason code returned was other than x2C01 (“DIRECTORY ENTRY NOT FOUND”).

In this message, collName is the name of the collection with the missing first object.

The system treats the file as an empty file. The migration attempts to re-migrate file collName to OAM.

Corrective Action: See the OAM Programmer’s Reference or the DFSMSdfp Diagnosis Reference for an explanation of this warning.

MIG5DIS FAILED TO LOAD DSNALI MODULE OF DB2Link copied to clipboard

Explanation: Control-V was unable to load the DSNALI module.

The DSNALI module verifies updates to OAM files. There are two responses to an attempt to update an OAM file:

If an OAM file is successfully updated, the migration program performs a DB2 COMMIT action.
If an OAM file fails to update, the migration program performs an ABORT (terminates) and does not load the DSNALI module.

The migration program terminates.

Corrective Action: Make the DSNALI module available to Control-V. Note the error message and consult your DB2 administrator.

MIG5E0I `text`Link copied to clipboard

Explanation: This information message is an internal message that Control-V uses to transfer information from one program to another.

Corrective Action: No action is required.

MIG5E3I CLIP_ID= `clipId`Link copied to clipboard

Explanation: This information message is issued for each Centera clip created during Control-V migration to the EMC Centera storage system.

In this message, clipId is the name of the clip.

Corrective Action: No action is required.

MIG5E4E CENTERA INIT ERROR: RC= `rc`, REASON CODE= `rsn`Link copied to clipboard

Explanation: Connection to EMC Centera cannot be established. This message is followed by message MIG5E9I, which issues the Centera pool value used for connection.

The variables in this message are:

rc - return code from the EMC Centera API.
rsn - reason code from the EMC Centera API.

The job terminates with a nonzero return code.

Corrective Action: Refer to EMC Centera documentation for a description of the received reason code.

Check the pool value printed in the accompanying MIG5E9I message. If the IP addresses are not correct, update them in parameters POOL1-POOL4 in the IOASPRM member. Then rerun the migration mission or the utility that issued this message.

MIG5E5E CENTERA CLIP CREATE ERROR: RC= `rc`, REASON CODE= `rsn`, DSN= `dsn`Link copied to clipboard

Explanation: An error was detected during creation of a new EMC Centera clip for a migrated CDAM or index file.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API
dsn - the name of the migrated dataset

The dsn dataset is not migrated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

MIG5E6E CENTERA BLOCK WRITE ERROR: RC= `rc`, REASON CODE= `rsn`, DSN= `dsn`Link copied to clipboard

Explanation: An error was detected while writing a block of the migrated dataset to the EMC Centera clip.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API
dsn - the name of the migrated dataset

The dsn dataset is not migrated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

MIG5E7E CENTERA CLIP CLOSE ERROR: RC= `rc`, REASON CODE= `rsn`, DSN= `dsn`Link copied to clipboard

Explanation: An error was detected while closing an EMC Centera clip.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API
dsn - the name of the migrated dataset

The dsn dataset is not migrated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

MIG5E8E CENTERA TERMINATE ERROR- RC= `rc`, REASON CODE= `rsn`Link copied to clipboard

Explanation: An error was detected during termination of the EMC Centera device.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API

The EMC Centera connection is not terminated.

Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.

MIG5E9I POOL= `pool`Link copied to clipboard

Explanation: This information message follows message MIG5E4E.

In this message, pool is the pool value specified in parameters POOL1-POOL4 in the IOASPRM member.

Corrective Action: No action is required.

MIG5EAI DELETE CENTERA CLIP: RC= `rc`, REASON CODE= `rsn`Link copied to clipboard

Explanation: This information message is issued for each Centera clip deleted by the CTVCLMIG utility. This message is followed by message MIG5E3I, which contains the deleted clip name.

The variables in this message are:

rc - return code from the EMC Centera API
rsn - reason code from the EMC Centera API

Corrective Action: No action is required.

MIG5EBE CENTERA RETENTION CLASS `className` READ ERROR, RC= `rc`, REASON CODE= `rsn`Link copied to clipboard

Explanation: A className error was detected while retrieving the retention period for the specified retention class. Usually this message is issued when the specified retention class does not exist in the EMC Centera definitions.

className - Class name.
rc - Return code from the EMC Centera API.
rsn - Reason code from the EMC Centera API.

The migration job stops with a return code of 12. Files are not migrated.

Corrective Action: Check the specified className in the migration mission definition CENTERA RETENTION CLASS field. If the specified className is incorrect, correct it and reorder the migration mission. Otherwise contact EMC Centera technical support.

MIG5ECE MEDIA NAME `mediaName` NOT FOUND IN IOASPRMLink copied to clipboard

Explanation: This message is issued by the CTVCLMIG utility if the media name kept in the $SYSDATA record is not found in the IOASPRM member.

mediaName - media name of the migrated report

The CTVCLMIG utility stops with a return code of 8.

Corrective Action: Add the specified mediaName in the message media to the IOASPRM member and rerun the CTVCLMIG utility.

MIG5EEI DELETE UFS FILE: RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: This information message is issued for each deleted file migrated to UFS. This message is followed by message MIG5EFI, which contains the name of the deleted file. The message includes the return code (rc) and reason code (rsn).

Corrective Action: No action is required.

MIG5EFI UFSFILE=`fileName`Link copied to clipboard

Explanation: This is an informative message that follows several UFS-related messages. The message specifies the name of the migrated file.

Corrective Action: No action is required.

MIG5F0E UFS FILE CREATE ERROR: RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: An error was detected while attempting to create a file migrated to UFS. The file is not created. The message includes the return code (rc) and reason code (rsn) for the error.

This message is followed by message MIG5EFI.

Corrective Action: Ensure that the address space that is trying to create the file has sufficient permissions to create the file.

MIG5F1E UFS FILE DELETE ERROR: RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: An error was detected while attempting to delete a file migrated to UFS. The file is not deleted. The message includes the return code (rc) and reason code (rsn) for the error.

This message is followed by message MIG5EFI.

Corrective Action: Ensure that the file exists and that the deleting address space has sufficient permissions to delete the file.

MIG5F2E UFS POOL FILE NOT FOUND POOLNAME=`pool`Link copied to clipboard

Explanation: No pool file with the name specified by the POOL parameter was found in the primary and secondary migration target folders pointed to by the PATHPRI and PATHSEC parameters.

Corrective Action: Ensure that the file exists and that the remote NFS is mounted.

MIG5F3E UFS INIT ERROR: RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: UFS media initialization has failed. The message includes the return code (rc) and reason code (rsn) for the error.

Corrective Action: Check the UFS media configuration in the IOASPRM parameter member and re-check the UFS media setup steps described in the INCONTROL for z/OS Administrator Guide.

MIG5F4E UFS PERMISSION DENIEDLink copied to clipboard

Explanation: Control-V has failed to perform an action in the PATHPRI or PATHSEC folder.

This message is followed by message MIG5EFI.

Corrective Action: Ensure that the address space has sufficient permissions to perform the action.

MIG5F5E UFS BLOCK WRITE ERROR: RC=`rc`, REASON CODE=`rsn`, DSN=`dsname`Link copied to clipboard

Explanation: An error was detected while writing a file to UFS. The message specifies the name of the original data set and also includes the return code (rc) and reason code (rsn) for the error.

This message is followed by message MIG5EFI.

Corrective Action: Ensure that the address space has sufficient permissions to perform the action.

MIG5F6E UFS READ ERROR: RC=`rc`,REASON CODE=`rsn`,DSN=`dsname`,BLN=`blk`,L=`len`Link copied to clipboard

Explanation: An error was detected while reading a file migrated to UFS. This message contains the following variables:

rc – return code
rsn – reason code
dsname – original data set name
blk – error block number
len – error block length

This message is followed by message MIG5EFI.

Corrective Action: Ensure that the address space has sufficient permissions to perform the action.

MIG5F7E UFS FILE CLOSE ERROR: RC=`rc`, REASON CODE=`rsn`, DSN=`dsname`Link copied to clipboard

Explanation: An error was detected while closing a file migrated to UFS. The message specifies the name of the original data set and also includes the return code (rc) and reason code (rsn) for the error.

This message is followed by message MIG5EFI.

Corrective Action: Ensure that the address space has sufficient permissions to perform the action.

MIG5F8E UFS TERMINATE ERROR: RC=`rc`, REASON CODE=`rsn`Link copied to clipboard

Explanation: UFS media termination has failed. The message includes the return code (rc) and reason code (rsn) for the error.

Corrective Action: Check the UFS media configuration in the IOASPRM parameter member and re-check the UFS media setup steps described in the INCONTROL for z/OS Administrator Guide.

MIG5F9E UFS READ ERROR: RC=`rc`,REASON CODE=`rsn`,BLN=`blk`,L=`len`Link copied to clipboard

Explanation: An error was detected while reading a file migrated to UFS. This message contains the following variables:

rc – return code
rsn – reason code
blk – error block number
len – error block length

This message is followed by message MIG5EFI.

Corrective Action: Ensure that the address space has sufficient permissions to perform the action.

MOF messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages MOF100 through MOF1xxLink copied to clipboard

This group includes messages for the Control-O product.

MOF15BE ORDER/FORCE FAILED. CONTROL-O MONITOR IS INACTIVELink copied to clipboard

Explanation: An O/F (Order/Force) command was specified, but cannot be executed because the Control-O monitor is not active.

The Order/Force command is not executed.

Corrective Action: Start the Control-O monitor before ordering rules.

MOF15CI TABLE `tableName` ODATE `date` WILL BE ORDERED BY CONTROL-OLink copied to clipboard

Explanation: This information message indicates that an ORDER or FORCE request was made for rule table tableName odate date. Control-O will order or force the table.

Corrective Action: No action is required.

MOF15EE FORCE ORDER REJECTED BY USER EXITLink copied to clipboard

Explanation: An ORDER or FORCE command was specified but was rejected by security exit CTOSE01.

Security exit CTOSE01 has determined that you are not authorized to perform ORDER or FORCE commands.

The ORDER or FORCE command is not executed.

Corrective Action: If you think you should be authorized to perform these commands, please contact your INCONTROL administrator.

MON messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages MON100 through MON1xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

MON100I CONTROL-D MONITOR STARTED IN mode MODELink copied to clipboard

Explanation: This general information message is issued when the Control-D monitor is started in one of the following modes:

INT - internal mode
EXT - external mode

Corrective Action: No action is required.

MON102E INVALID PARM GIVEN TO MONITOR. PARM CAN BE " " OR "1" FOR PRIMARY MONITOR AND "2-9" FOR SECONDARY MONITORSLink copied to clipboard

Explanation:Highlighted, unrollable message.

The value of the PARM field in the Control-D monitor procedure or the secondary monitor procedure is invalid.

The Control-D monitor or the secondary monitor shuts down.

Corrective Action: Check the value defined in the CTDMON# field in CTDPARM. Change the PARM field in the appropriate procedure to correspond to this value and start Control-D.

For example, for the CONTROL2 procedure: //CONTROLD EXEC PGM=CTMMON,PARM=‘2’

MON103E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:Link copied to clipboard

Explanation: An invalid parameter was passed to the File Transfer monitor by an operator modify command. A list of valid modify parameters is displayed on the operator console following this message.

The operator modify command is rejected.

Corrective Action: Enter an operator modify command with valid parameters.

MON104S BLDL/ATTACH FAILED FOR TASK `taskName`Link copied to clipboard

Explanation: Initialization of one of the Control-D monitor internal tasks failed.

Possible causes are:

The task is not found in the IOA Load library.
Insufficient memory for Control-D monitor.

The exact reason (system code) can be found on the computer log.

Control-D monitor shuts down.

Corrective Action: Call your system programmer for assistance. If necessary, increase the Control-D monitor REGION size.

MON105S UNRECOVERABLE ERROR ENCOUNTEREDLink copied to clipboard

Explanation: Unrecoverable error in the operation of the Control-D monitor.

The IOA Log should contain a previous message concerning the error.

The Control-D monitor will shut down with user abend 0006.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.

MON106S ONE OF THE SUBTASKS HAS ABENDEDLink copied to clipboard

Explanation: One of the Control-D monitor internal subtasks has abended.

The Control-D monitor will shut down with user abend 0006. A dump of the abending task which is needed for problem resolution will also be included in the output.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.

MON107I SHUT DOWN UPON REQUEST FROM OPERATORLink copied to clipboard

Explanation: This information message is a Control-D monitor shut down message when the shut down was requested by the operator.

Control-D monitor shuts down.

Corrective Action: No action is required.

MON109W CONTROL-D PASSWORD WILL EXPIRE IN `n` DAYS. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: The password for testing Control-D will expire in n days.

In n days, the Control-D monitor will stop operating.

Corrective Action: Please contact your IOA administrator.

MON110S PASSWORD HAS EXPIRED. NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation: The password for testing Control-D has expired.

The Control-D monitor no longer operates.

Corrective Action: Please contact your IOA administrator.

MON111W NO MORE WORK LEFTLink copied to clipboard

Explanation: Internal Control-D error.

Corrective Action: Have your system programmer call BMC Customer Support immediately.

MON112W MISSIONS LEFT IN ACTIVE MISSIONS FILE CANNOT BE DONELink copied to clipboard

Explanation: Internal Control-D error.

Corrective Action: Have your system programmer call BMC Customer Support immediately.

MON113W CONTROL-D MONITOR SHUTTING DOWN FOR A NEW DAYLink copied to clipboard

Explanation:Highlighted, unrollable message.

Normal message of Control-D monitor shutting down for the New Day procedure.

The Control-D monitor shuts down once a day at a specific time for the New Day procedure. For more information on the New Day procedure, see the Control-D and Control-V User Guide.

Control-D monitor will shut down and start the New Day procedure (CTDNDAY). When it finishes executing, it will start the Control-D monitor again.

Corrective Action: No action is required.

MON116S OPEN OF ACTIVE MISSIONS FILE FAILED - DDNAME "DAAMF"Link copied to clipboard

Explanation:Highlighted, unrollable message.

Open of Control-D Active Missions file failed (the DAAMF DD statement). Possible causes are:

The DAAMF DD statement is missing.
The data set described by the DAAMF DD statement is not the Control-D Active Missions file.
The data set described by the DAAMF DD statement is the Control-D Active Missions file, but it is of another Control-D monitor, or of a different Control-D version.

The Control-D monitor will shut down.

Corrective Action: Correct the JCL for the Control-D monitor.

MON117S ACTIVE MISSIONS FILE IS BEING FORMATTED NOWLink copied to clipboard

Explanation:Highlighted, unrollable message.

Control-D monitor has been brought up while the Active Missions file is under formatting.

The New Day procedure did not finish formatting the file, either because it was still working, or because it abended. It is impossible to start the Control-D monitor until the New Day procedure finishes executing successfully.

The Control-D monitor shuts down.

Corrective Action: Check how the New Day procedure finished executing. All the problems of the New Day procedure must be corrected before restarting the Control-D monitor. Note, however, that if an IPL occurred during the previous run of the New Day procedure, it will correct itself when restarted. Therefore, it can be restarted without correction.

MON118S FILE ALLOCATED TO DDNAME "DAAMF" IS NOT THE EXPECTED ACTIVE MISSIONS FILELink copied to clipboard

Explanation:Highlighted, unrollable message.

The data set described by the DAAMF DD statement is not the expected Control-D Active Missions file.

This could be due to one of the following:

The file allocated to the DAAMF DD statement is not the Control-D Active Missions file.
The file allocated to the DAAMF DD statement is the Control-D Active Missions file, but it is of a different version or of a different Control-D monitor.

Control-D monitor will shut down.

Corrective Action: Correct JCL for the Control-D monitor.

MON119S ACTIVE MISSIONS FILE IS DAMAGED - NOTIFY THE IOA ADMINISTRATORLink copied to clipboard

Explanation:Highlighted, unrollable message.

The contents of the Active Missions file have been corrupted.

The Active Missions file is marked as FORMAT during New Day procedure processing, and marked as FREE at successful completion. Currently, the file is not marked as FORMAT, nor as FREE.

Control-D monitor will shut down.

Corrective Action: Call your system programmer for assistance. Examine messages issued during the NEWDAY procedure, take appropriate corrective action, and then rerun the NEWDAY procedure. If the problem recurs, take appropriate action on the Active Mission file: To compress or copy the Active Mission file, use the CTDCAMF utility. To reformat the Active Mission file use the CTDFRAMF utility.

MON120I CONTROL-D MONITOR SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message is a general Control-D message issued when shutting down the Control-D monitor by a P command, or on certain internal Control-D events.

The IOA Log should contain additional messages concerning the reason for shutting down.

Control-D monitor shuts down.

Corrective Action: No action is required.

MON121S CONTROL-D MONITOR ENDED WITH ERRORLink copied to clipboard

Explanation:Highlighted, unrollable message.

Control-D monitor ended with an error. The IOA Log should contain additional messages concerning the specific error.

Control-D monitor shuts down.

Corrective Action: Check the IOA Log or the computer log for the reason. Call the system programmer for assistance if needed. Try to start the Control-D monitor again as soon as possible.

MON122W YOUR CONTROL-D IS ALREADY ACTIVE. QNAME `qName`Link copied to clipboard

Explanation:Highlighted, unrollable message.

Corrective Action: No action is required.

MON123I CONTROL-D INTERVAL IS SET TO `nn` SECONDSLink copied to clipboard

Explanation: This information message is produced as a result of setting a Control-D sleeping interval by an operator command.

For more details refer to the INCONTROL for z/OS Administrator Guide.

Control-D monitor will “wake up” every nn seconds and check what it has to do.

Corrective Action: No action is required.

MON124E INTERVAL MUST BE A TWO DIGIT NUMBER BETWEEN 03-99 SECONDSLink copied to clipboard

Explanation: An invalid Control-D sleeping interval was specified in an operator modify command. The Control-D sleeping interval must be a 2-digit number from 03 through 99 seconds. For more details, see the INCONTROL for z/OS Administrator Guide.

Corrective Action: Enter a valid interval.

MON125I `validModifyParm`Link copied to clipboard

Explanation: This message displays a valid parameter that can be used in MODIFY.

Corrective Action: No action is required.

MON126I NEW EXIT `exitName` LOADEDLink copied to clipboard

Explanation: This information message indicates a successful execution of the “exit refresh” operator modify command.

A new copy of a Control-D user exit was loaded successfully.

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

Corrective Action: No action is required.

MON127I NEWDEST COMMAND ACCEPTEDLink copied to clipboard

Explanation: This information message is the result of acceptance of an operator NEWDEST command passed to the Control-D monitor.

The next time that the Control-D monitor tries to SHOUT a message, it will load a new dynamic destination table.

Corrective Action: No action is required.

MON128S RECIPIENT TREE WAS NOT LOADED BECAUSE OF ERROR - CONTROL-D IS TERMINATINGLink copied to clipboard

Explanation: The loading of the Control-D Recipient Tree was unsuccessful.

As part of its initialization processing, the Control-D monitor attempts to load the Recipient Tree. However, the loading of the Recipient Tree was not successful.

The Control-D monitor will shut down.

Corrective Action: There are additional messages describing the problem on the IOA Log and the system log.

MON129I ERROR WHILE LOADING EXIT `exitName`. EXIT NOT LOADEDLink copied to clipboard

Explanation: This information message indicates that the Control-D monitor failed to load the exitName user exit.

Common reasons for failure include:

The IOA Load library is in the Linklist, and someone has updated the library without performing a refresh for the LLA.
The last assembly or linkage of exitName failed.
There is insufficient memory to load this exit.

The Control-D monitor will continue to run. However, the exitName user exit will not be activated.

Corrective Action: Check the system log for the reason for the failure.

MON12AI CONTROL-D MONITOR IS SUSPENDING FOR A NEW DAYLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor is being suspending while the New Day procedure is running in internal mode.

The Control-D monitor is suspended once a day at a specific time for the New Day procedure when it runs in internal mode. For more information on the New Day procedure, see the INCONTROL for z/OS Administrator Guide.

The Control-D monitor suspends all mission processes. When it finishes, message MON12CI is issued.

Corrective Action: No action is required.

MON12BI CONTROL-D MONITOR IS SUSPENDING BY OPERATOR REQUESTLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor is being suspending due to an operator request.

The Control-D monitor suspends all mission processes. When it finishes, message MON12CI is issued.

Corrective Action: No action is required.

MON12CI CONTROL-D MONITOR SUSPENDEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor is being suspended while the New Day procedure is running in internal mode.

The Control-D monitor has started the New Day subtask. When it finishes executing, the monitor will resume and start the New Day procedure (CTDNDAY).

Corrective Action: No action is required.

MON12DI CONTROL-D MONITOR RESUMEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor has resumed after being suspended for the New Day procedure or by operator request.

The Control-D monitor resumes all mission processes.

Corrective Action: No action is required.

MON12EI CONTROL-D NEW DAY TIME STAMP IS `timeStamp`Link copied to clipboard

Explanation: This information message indicates that the New Day process has set the timeStamp time stamp as the time of a new day.

The timeStamp timestamp is a hexadecimal representation of the time-of-day clock value used for synchronization for the CTDDELRP utility and for backup missions. It is displayed for tracking and debugging purposes.

For an explanation of the synchronization process, see message MONA59I.

Corrective Action: No action is required.

MON12FE UNABLE TO UPDATE THE MISSION STATUSLink copied to clipboard

Explanation: The Control-D monitor is unable to update the status of a decollation mission, which was suspended during a New Day procedure that was executing in internal mode. The monitor begins to process such a mission before the New Day procedure begins, but only finishes after the procedure ends. The reason is that the mission was updated outside of the Control-D monitor.

The Control-D monitor continues to run. However, the mission status is not updated.

Corrective Action: Restart the Control-D monitor.

MON12GS NEWDAY SUBTASK ENDED WITH ERRORLink copied to clipboard

Explanation: A New Day subtask ended with an error or abended.

The Control-D monitor shuts down with user abend 0006.

A dump of the abending task which is needed for problem resolution is also included in the output.

Corrective Action: No action is required.

MON12HS INVALID NEWDAY MODELink copied to clipboard

Explanation: The incorrect NDAYMODE parameter was specified in the start command for the Control-D monitor or the CTDNDAY procedure.

Valid values are:

INT - internal mode. The Control-D or Control-V monitors execute simultaneously with the New Day procedure.
EXT - external mode. The Control-D monitor starts the New Day procedure, and then shuts down the Control-D monitor or the CTDNDAY procedure.

The Control-D monitor or the CTDNDAY procedure shuts down.

Corrective Action: Restart the Control-D monitor or the CTDNDAY procedure with the correct parameter.

MON12LI SECONDARY MONITOR CAN'T START DURING NEWDAYLink copied to clipboard

Explanation: The secondary monitor could not start due to a synchronization issue during the NEWDAY process.

Corrective Action: Try to start the monitor again after the NEWDAY process has completed. If the problem persists, contact BMC Customer Support.

MON130I COMMAND " `cmd`" ACCEPTED FOR PRINTER `prtr`Link copied to clipboard

Explanation: This information message indicates acceptance of an operator STARTPRT or STOPPRT command passed to the Control-D monitor.

The requested printer is opened (started) or closed (stopped).

Corrective Action: No action is required.

MON131I TREE WAS NOT LOADED BECAUSE IT IS IN USE BY ONE OF THE SUBTASKS - TRY AGAIN LATERLink copied to clipboard

Explanation: This information message is a result of an operator LOADTREE command passed to the Control-D monitor.

The Recipient Tree is used by several subtasks of the Control-D monitor. One of the subtasks had exclusive control of the Recipient Tree for a short period of time.

The new Recipient Tree is not loaded. Control-D continues using the old Recipient Tree.

Corrective Action: Try to load a new Recipient Tree later.

MON132E PRINTER `prtr` IS NOT DEFINED TO CONTROL-DLink copied to clipboard

Explanation: Result of an operator STARTPRT or STOPPRT command passed to the Control-D monitor.

The PRINTER Control-D Installation Parameter defines the logical printers on which Control-D can print. However, the printer name prtr is not defined in the PRINTER Installation Parameter.

The requested STARTPRT or STOPPRT function is not performed.

Corrective Action: Enter the correct printer name in the STARTPRT or STOPPRT command.

MON133I STARTING THE CONTROL-D PRINTERS CONTROL MONITOR - `prtr`Link copied to clipboard

Explanation: This information message is issued during normal initialization processing in the Control-D monitor.

The Control-D monitor activates the Printers Control monitor prtr as an independent started task.

The Control-D monitor invokes the started task prtr. This name is taken from the PRTSTC Control-D Installation Parameter.

Corrective Action: No action is required.

MON134I WAITING FOR THE CONTROL-D PRINTERS CONTROL STC (`name`) TO STARTLink copied to clipboard

Explanation: This information message indicates that the Printers Control monitor has been activated by the Control-D monitor.

The Control-D monitor waits for the Printers Control started task to start executing. This message can appear more than once. If, after a number of times, the Control-D monitor cannot find the Printers Control monitor, it assumes that it has failed and the Control-D monitor shuts down.

Corrective Action: No action is required.

MON135E CONTROL-D PRINTERS CONTROL MONITOR `monName` ENDED ABNORMALLY. CONTROL-D SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

The Printers Control monitor monName was shut down due to errors.

The Control-D monitor will shut down.

Corrective Action: Check the IOA Log for additional clarification messages on the reason for the shutdown.

MON136I STOPPING THE PRINTERS CONTROL MONITORLink copied to clipboard

Explanation: This information message indicates that a shutdown process has been issued from the Control-D monitor.

Before the Control-D monitor shuts itself down, it will shut down the Printers Control monitor first.

Control-D will shut down.

Corrective Action: No action is required.

MON137I WAITING FOR THE PRINTERS CONTROL STC (`name`) TO TERMINATELink copied to clipboard

Explanation: This information message indicates that a shutdown process has been issued from the Control-D monitor.

The Control-D monitor has issued the command to shut down the Printers Control monitor, and is now waiting for a response. This message can appear more than once, but not more than 10 times.

Corrective Action: No action is required.

MON138E WAITING TOO LONG FOR THE PRINTERS CONTROL STC (`name`). STC BEING CANCELLEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

A shutdown process issued from the Control-D monitor.

The Control-D monitor has issued the command to the Printers Control monitor to shut itself down, but there was no response from the Printers Control monitor.

The Printers Control monitor is cancelled (operator command C name).

Corrective Action: Check the system log, the IOA Log, and the JCL of the Control-D monitor and the Printers Control monitor.

MON139I GENERIC JOB DECOLLATION IS ACTIVE ON CLASSES (`classList`)Link copied to clipboard

Explanation: This information message indicates that the Generic decollation from the classList Generic classes is now active. The Control-D monitor issues this message when starting, after new day processing and after successfully executing the STARTGEN command.

Control-D will start decollating sysouts from the classList Generic classes. For more information, see the description of generic processing in the INCONTROL for z/OS Administrator Guide.

Corrective Action: No action is required.

MON13AE GENERIC DECOLLATION CANNOT BE ACTIVATED. GENCLAS IS NOT DEFINED IN CTDPARMLink copied to clipboard

Explanation: The operator issued the command ‘F CONTROLD,STARTGEN’ but no generic classes were defined in CTDPARM.

The command is ignored.

Corrective Action: For information on specifying generic classes in CTDPARM, see the Control-D chapter of the INCONTROL for z/OS Installation Guide, and proceed accordingly.

MON13BI PRINTER `prtrId` DEST `dest` TYPE `type` IS OPENLink copied to clipboard

Explanation: This information message indicates that the prtr_id logical printer has opened following a STARTPRT command issued by the operator.

The variables in this message are:

prtrId - the identity of the logical printer that has opened
dest - the value of the Dest Printer Definition parameter
type - the value of the Type Printer Definition parameter

For more information on these Printer Definition parameters, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

MON13CI STOPPING THE MONITOR `monName`Link copied to clipboard

Explanation: This information message is issued when the monitor stops as a result of receiving the modify command /F CONTROLD,STOP=monName.

Corrective Action: No action is required.

MON13DE THE MONITOR `monName` WAS NOT ORIGINALLY ACTIVE.Link copied to clipboard

Explanation: The modify command /F CONTROLD,STOP=monName was issued, but the monName monitor was not activated when Control-D started.

Control-D cannot start a new monitor that was not activated when Control-D started.

The new monitor is not started.

Corrective Action: Correct the value of monName in the modify command.

MON13EI MQ DECOLLATION IS ACTIVELink copied to clipboard

Explanation: This information message indicates a successful execution of the STARTMQ operator modify command.

MQ decollation for MQ Queues is now active.

Control-D will start decollating messages from MQ Queues.

Corrective Action: No action is required.

MON140I GENERIC JOB DECOLLATION IS BEING DEACTIVATEDLink copied to clipboard

Explanation: This information message indicates a successful execution of the STOPGEN operator modify command.

Deactivation of Generic decollation from all Generic classes is in process.

Control-D will not start new decollations from Generic classes. Currently executing (decollating) missions will finish the processing of jobs whose output processing has already started.

Corrective Action: No action is required.

MON141I STARTING THE SECONDARY CONTROL-D MONITOR `monName`Link copied to clipboard

Explanation: This information message is a normal start message for initialization processing of the Control-D monitor monName.

The Control-D monitor activates the secondary monitor as an independent started task.

The Control-D monitor invokes the started task name, CONTROL ?, where ? indicates the number of the monitor.

Corrective Action: No action is required.

MON142I WAITING FOR THE SECONDARY CONTROL-D MONITOR `monName` TO STARTLink copied to clipboard

Explanation: This information message indicates that although a start command has been issued by the Control-D monitor, the Control-D secondary monitor monName has not yet started.

This is due to one of the following:

JES queues are busy.
The secondary monitor procedure does not exist in the procedure library (PROCLIB).
There is a JCL error in the secondary monitor procedure.

If this situation is not corrected, the Control-D monitor makes up to eight (8) attempts to initialize. After eight (8) unsuccessful attempts, the Control-D monitor shuts down.

Corrective Action:

If JES queues are busy, no action is required.
If there is a problem with the secondary monitor procedure, correct it, and start Control-D.

MON143E SECONDARY CONTROL-D MONITOR `monName` ENDED ABNORMALLY. CONTROL-D SHUTTING DOWNLink copied to clipboard

Explanation:Highlighted, unrollable message.

Secondary Control-D monitor monName ended with errors. The IOA Log should contain additional messages concerning specific errors.

The Control-D monitor and the secondary monitor monName shut down.

Corrective Action: Check the IOA Log and the system log for the cause of the problem. If necessary, call the system programmer for assistance. Try to start the Control-D monitor again as soon as possible.

MON144I WAITING FOR CONTROL-D SECONDARY MONITOR `monName` TO TERMINATELink copied to clipboard

Explanation: This information message indicates that a shutdown process command was issued from the Control-D monitor.

The Control-D monitor has issued a shutdown command to the secondary monitor monName, and is now waiting for the secondary monitor to shut down. This message may appear more than once. The secondary monitor will shut down at the end of the currently executing decollation.

Corrective Action: No action is required.

MON145I UNABLE TO READ THE MEMBER CTDPLEX FROM THE CTD PARM LIBRARY. RC=`rc`. THE SYSPLEX OPTION IS NOT ACTIVE.Link copied to clipboard

Explanation: The CTDPLEX member was not found in the Control-D PARM library.

In this message, rc is the error return code. For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

The use of multiple monitors using SYSPLEX support is not activated.

Corrective Action: Ensure that the CTDPLEX member is present in the Control-D PARM library.

MON146I MQ DECOLLATION IS BEING DEACTIVATEDLink copied to clipboard

Explanation: This information message indicates a successful execution of the STOPMQ operator modify command.

Deactivation of MQ decollation from all MQ QUEUES is in process.

Control-D will not start new decollations from MQ QUEUES, although currently existing decollating missions will finish the processing of messages whose output processing has already begun.

Corrective Action: No action is required.

MON147I CONTROL-D MONITOR RESTARTED IN `nday_mode` MODELink copied to clipboard

Explanation: This is a general information message that is issued when the Control-D monitor is restarted on a new LPAR in the specified NEWDAY procedure mode nday_mode.

The valid values are:

INT - internal mode
EXT - external mode.

Corrective Action: No action is required.

MON148I CONTROL-D MONITOR SHUTTING DOWN FOR RESTARTLink copied to clipboard

Explanation: Highlighted, unrollable message. This information message is a general Control-D message issued when shutting down the Control-D monitor by a RESTART command.

Control-D monitor shuts down, then restarts on a new LPAR.

Corrective Action: No action is required.

MON14BI NUMBER OF DECOLLATION MONITORS FOR GENERIC PROCESS WILL BE CHANGED AUTOMATICALLYLink copied to clipboard

Explanation: Control-D will automatically change the number of active Control-D decollation monitors based on the number of JOBs in the JES spool that are waiting for decollation in the generic class.

Corrective Action: No action is required.

MON14CW GENJOBM >= GENJOBX. QUEUE IN JES SPOOL WILL NOT BE CHECKED FOR CHANGING NUMBER OF DECOLLATION MONITORS FOR GENERIC PROCESSLink copied to clipboard

Explanation: Parameter GENJOBM (Threshold of QUEUE size to stop a secondary Control-D monitor) is bigger than GENJOBX (Threshold of QUEUE size to start a secondary Control-D monitor). Control-D will not automatically change the number of active Control-D decollation monitors.

Corrective Action: Correct GENJOBM and/or GENJOBX and restart the Control-D monitor.

MON14DW QUEUE IN JES SPOOL IS TOO LONG. INCREASE NUMBER OF DECOLLATION MONITORS FOR GENERIC PROCESS IN PARAMETER CTDMON#Link copied to clipboard

Explanation: Based on queue size, Control-D tries to start a secondary Control-D monitor for generic process. However, the maximum number of secondary monitors was reached.

Corrective Action: Increase the number of Control-D monitors in parameter CTDMON# in CTDPARM.

MON14EE THE NUMBER OF MONITORS IS CHANGED AUTOMATICALY. RESTART COMMAND IS REJECTEDLink copied to clipboard

Explanation: Control-D monitor rejected the RESTART command to restart itself because the number of active Control-D decollation monitors was automatically changed.

Corrective Action: No action is required.

MON14FE MONITOR IS NOT STARTED ON LPAR `lpar_name`. RESTART COMMAND IS REJECTEDLink copied to clipboard

Explanation: The Main Control-D monitor has not started successfully on the new LPAR after the RESTART command. The monitor continues to work on the current LPAR.

Corrective Action: Check error messages on the new LPAR, fix the problem, and repeat the RESTART command.

MON14GI WAITING FOR THE CONTROL-D MONITOR TO RESTART ON LPAR `lpar_name`Link copied to clipboard

Explanation: The old Main Control-D monitor is waiting for the new one to start successfully on the new LPAR after the RESTART command. If it started, the old monitor shuts down. If it does not start, the old monitor continues to work on the current LPAR.

Corrective Action: No action is required.

MON14HI RESTART IS WAITING FOR SYNCHRONIZATION FOR BACKUP/CTDDELRP/NEWDAYLink copied to clipboard

Explanation: The Main Control-D monitor has received a RESTART command, but one of the BACKUP/CTDDELRP/NEWDAY processes are executing. The RESTART command will be processed after the other process has finished.

Corrective Action: No action is required.

MON14IE RESTART OF MONITOR FAILED ON NEW LPAR BECAUSE `parmname` IS CHANGEDLink copied to clipboard

Explanation: The Main Control-D monitor is not started successfully on the new LPAR after the RESTART command because the parmname parameter of the CTDPARM member was changed. The monitor continues to work on the current LPAR.

Corrective Action: Restore the CTDPARM member to the status of the starting of the Control-D monitor and repeat the RESTART command.

MON14JE RESTART OF MONITOR FAILED ON NEW LPAR BECAUSE I/O AUF ERRORLink copied to clipboard

Explanation: The Main Control-D monitor is not started successfully on the new LPAR after the RESTART command because of an I/O error for the Active User File. The monitor continues to work on the current LPAR.

Corrective Action: See the preceding CTDU99E message.

MON14KE THE SYSPLEX OPTION IS NOT ACTIVE. RESTART COMMAND IS REJECTED.Link copied to clipboard

Explanation: Control-D monitor rejected the RESTART command to restart a monitor on another LPAR because the z/OS SYSPLEX option is not active.

Possible reasons are:

CTDPLEX member is missing in the CTD PARM library.
ENABLE=NO is defined in the CTDPLEX member.
LPAR name specified for the secondary decollation monitor or Print monitor is not specified in the CTDPLEX member for this monitor.
SYSPLEX is really inactive.

Corrective Action: No action is required.

MON14LE MONITOR `monName` IS NOT ACTIVE. RESTART COMMAND IS REJECTED.Link copied to clipboard

Explanation: The Restart command failed because the Control-D monitor is currently not active.

Corrective Action: Activate the Control-D monitor and then try again.

MON14ME LPAR `lpar_name` IS NOT DEFINED IN CTDPLEX FOR THIS MONITORLink copied to clipboard

Explanation: Control-D monitor rejected the RESTART command to restart the monitor on another LPAR, because LPAR lpar_name is not specified for this monitor.

Corrective Action: Use only those LPARs that are defined for this monitor in CTDPLEX.

Messages MON700 through MON7xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

MON778I CONTROL-D MAIN MONITOR ONLYLink copied to clipboard

Explanation:

This information message indicates that the user tried to issue a MODIFY or STOP command to either the Control-D Printers Control monitor or to a Control-D secondary monitor. A MODIFY or STOP command to the Control-D Printers Control monitor or a Control-D secondary monitor can only be issued by the Control-D primary monitor.

The MODIFY or STOP command is ignored.

Corrective Action: No action is required.

Messages MONA00 through MONAxxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

MONA59I SYNCHRONIZATION WITH BACKUP/CTDDELRP STARTEDLink copied to clipboard

Explanation: This information message is the normal message which is issued when the Control-D monitor receives a synchronization request from a Backup Mission or from the CTDDELRP utility.

Before starting synchronization, the CTDDELRP utility or a Backup Mission issues a synchronization request to the decollation task on each Control-D monitor (if more than one is active) to ensure that the report deletion/backup process is coordinated with each decollation task.

Upon receiving a request, each decollation task finishes its current decollation and closes all multijob CDAM data sets. It then issues a timestamp to the requesting utility or mission and waits for a response from that utility or mission.

The utility or mission waits until all monitors have responded. It selects a timestamp returned by the monitors and notifies Control-D decollation tasks of the timestamp selected. Synchronization is then complete and processing continues.

Coordination of the processes is achieved using an algorithm based on the timestamp.

Corrective Action: No action is required.

MPR messagesLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages MPR700 through MPR7xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

MPR775I `monName` CONTROL-D PRINTERS CONTROL MONITOR STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-D Printers Control monitor monName started.

Corrective Action: No action is required.

MPR776E `monName` CONTROL-D PRINTERS CONTROL MONITOR ALREADY ACTIVELink copied to clipboard

Explanation:Highlighted, unrollable message.

Someone tried to start Control-D Printers Control monitor monName, which is already active. The Control-D Printers Control monitor is automatically activated from the Control-D monitor. It should not be activated manually.

The newly-started Control-D Printers Control monitor will shut down.

Corrective Action: No action is required.

MPR777S `monName` CONTROL-D PRINTERS CONTROL MONITOR ENDED WITH ERRORSLink copied to clipboard

Explanation:Highlighted, unrollable message.

Control-D Printers Control monitor monName ended with errors. The IOA Log should contain additional messages concerning each specific error.

The Control-D Printers Control monitor and the Control-D monitor will shut down.

Corrective Action: Check the IOA Log and the system log for the reason. Call the system programmer for assistance if needed. Try to start the Control-D monitor again as soon as possible.

MPR778I `monName` ALL MODIFY/STOP COMMANDS MUST BE ISSUED BY CONTROL-D MAIN MONITOR ONLYLink copied to clipboard

Explanation: This information message indicates that the user tried to issue a MODIFY or STOP command to either the Control-D Printers Control monitor or to a Control-D secondary monitor. A MODIFY or STOP command to the Control-D Printers Control monitor or a Control-D secondary monitor can only be issued by the Control-D primary monitor.

The MODIFY or STOP command is ignored.

Corrective Action: No action is required.

MPR779I `monName` CONTROL-D PRINTERS CONTROL MONITOR ENDEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

This information message is the general message which is issued when the Control-D Printers Control monitor monName ends.

Corrective Action: No action is required.

MPR77AE INCORRECT PARM FIELD IN PRINT JOB `jobName`Link copied to clipboard

Explanation: The print mission running as a batch job received an invalid PARM field value from the EXEC statement, or the PARM field is missing from the EXEC statement.

The value PARM is the COM record number. This value must be 4 digits long. If it is not, or if the PARM field is not in the EXEC statement, this message is issued.

The job ends abnormally with a return code of 116, and the print mission ends NOT OK.

Corrective Action: Correct the EXEC statement in the print skeleton, and rerun the print mission.

Messages MPR900 through MPR9xxLink copied to clipboard

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

MPR980S `monName` LOAD OF CONTROL-D SPECIAL ROUTINES FAILEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

Initialization of the monName Printers Control monitor failed because of missing modules.

The Control-D Printers Control monitor and the Control-D monitor will shut down.

Corrective Action: Determine who deleted the missing load modules and why. Restore these modules from a backup tape of the IOA Load library, and bring up the Control-D monitor.

MPR981S `proc` RECIPIENT TREE WAS NOT LOADED BECAUSE OF ERROR – CONTROL-D PRINTERS CONTROL MONITOR IS TERMINATINGLink copied to clipboard

Explanation:Highlighted, unrollable message.

The Recipient Tree was not loaded because of an error.

The Control-D Printers Control monitor and the Control-D monitor will shut down.

Corrective Action: Look at the IOA Log and the computer log for additional error messages. These additional messages pinpoint the specific problem encountered while loading the Recipient Tree.

MPR982I `monName` CONTROL-D PRINTER MONITOR IS WAITING FOR ONE OR MORE PRINT SUBTASKS TO TERMINATELink copied to clipboard

Explanation: This information message indicates that a shutdown process command was issued from the Control-D monitor, but the Control-D Printers Control monitor is still printing.

The Printing Mission that is still printing can be found in the Active Missions Status screen.

If the Printers Control monitor is still printing when a shutdown request is issued, it continues to print. The Control-D monitor does not shut down until printing is finished.

Corrective Action: If you allow the Printing Mission to finish printing, no action is required.

To shut down the Control-D monitor immediately, change the status of the active Printing Mission in the Active Missions Status screen (AMS) to HOLD. Free it after the Control-D monitor has restarted.

MPR983E `monName` CONTROL-D PRINTER MONITOR IS TERMINATING EVEN THOUGH ONE OR MORE PRINT SUBTASKS HAS NOT TERMINATEDLink copied to clipboard

Explanation:Highlighted, unrollable message.

The Control-D monitor is shutting down the Control-D Printers Control monitor monName.

The Control-D monitor issued a command to shut down the Printers Control monitor monName. The Printers Control monitor was not shut down because one or more print subtasks were awaiting completion. Under certain circumstances, the Control-D monitor forces shutdown of the Printers Control monitor after a default site-specific length of time.

The Control-D Printers Control monitor monName shuts down.

Corrective Action: No action is required.

MPR98AI PRINT MISSION POSTPONED. MAX NUMBER OF SUBTASKS IS REACHED IN THE CURRENT MONITORLink copied to clipboard

Explanation: This information message indicates that the current print mission cannot be processed because the print monitor is already processing the maximum number of missions as defined in optional wish WD2618.

The print mission is delayed until one of the missions being processed terminates.

Corrective Action: If this message appears frequently, it is recommended to increase the maximum number of print missions the print monitor can process concurrently.

MPR98BI PRINT MISSION CONTINUES PROCESSINGLink copied to clipboard

Explanation: This information message indicates that the print monitor resumed processing a mission that was postponed (see message MPR98AI)

Corrective Action: No action is required.

MRG messagesLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

Messages MRG100 through MRG1xxLink copied to clipboard

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

MRG100I MERGE PROCESSING STARTEDLink copied to clipboard

Explanation: This information message indicates that the Merge utility began executing a MERGE command, requesting that either two Active Job files or two History files be merged.

Corrective Action: No action is required.

MRG101I MERGE PROCESSING ENDEDLink copied to clipboard

Explanation: This information message indicates that the Merge utility has completed execution.

Corrective Action: No action is required.

MRG102I {JOB | GROUP} `name` ODATE `odate` ORDERID `oldOrderId` MERGED - NEW ORDERID `newOrderId`Link copied to clipboard

Explanation: This information message indicates that the name job or group, with order date odate and order ID oldOrderId, was successfully copied into the target (merged) Active Jobs file.

If the parameter UPDORDID was specified, the job will have a new orderid (newOrderId) in the merged file. If the parameter UPDORDID was not specified, the original order ID is not changed. In this case, the values of oldOrderId and newOrderId in the message will be identical.

Corrective Action: No action is required.

MRG103S OPEN OF SOURCE/TARGET FILE FAILEDLink copied to clipboard

Explanation: An attempt to open a Control-M Active Jobs file or History file failed. This may be due to a missing DD statement referencing the file.

The program terminates with a non-zero return code.

Corrective Action: Correct the JCL and submit the job again.

MRG104S SOURCE/TARGET FILE IS NOT 'AJF' OR 'HST'Link copied to clipboard

Explanation: One of the files used as input or output to the Merge utility is not recognized as an Active Jobs file or History file.

The program terminates with a non-zero return code.

Corrective Action: Correct the JCL and submit the job again.

MRG105S OPEN OF PARAMATER FILE FAILEDLink copied to clipboard

Explanation: The file containing the command input to the Merge utility, referenced by the DAMRGIN DD name, could not be opened.

The program terminates with a non-zero return code.

Corrective Action: Correct the JCL and submit the job again.

MRG106E COPY TO MERGED FILE FAILED: `cause` REASON CODE: `rsn`Link copied to clipboard

Explanation: An error occurred while copying records from the source Active Jobs file or History file to the target Active Jobs file or History file.

The variables in this message are:

cause - the cause of the error
rsn - the reason code, which may contain additional information

The program terminates with a non-zero return code.

Corrective Action: No action is required.

MRG107E MERGE PROCESSING MODULE NOT FOUNDLink copied to clipboard

Explanation: An attempt to load the CTMHCP module failed. The load may have failed because the module does not exist in the IOA Load library.

The program terminates with a non-zero return code.

Corrective Action: Verify that the IOA Load library contains the required module.

MRG108S SOURCE/TARGET FILE RELEASE LEVEL NOT SUPPORTEDLink copied to clipboard

Explanation: The source or target file specified for the Merge utility was created under an unsupported version. The Merge utility cannot process such a file, and terminates with a non-zero return code.

Corrective Action: Verify that both the source and target files are of supported versions. (The version can be found in record 0 of each file.)

MRG109S SOURCE AND TARGET FILE TYPE MISMATCHLink copied to clipboard

Explanation: The source and target file types are not identical. They must both be either Active Job files or History files.

The program terminates with a non-zero return code.

Corrective Action: Verify that the file types are identical. The file type can be found in record 0 of each file.

MRG110I MERGE PROCESSING FOR FILE TYPE: AJF/HSTLink copied to clipboard

Explanation: This information message indicates the type of merge being processed by the Merge utility. Merging of either two Active Job files or two History files is supported.

Corrective Action: No action is required.

MRG111I SOURCE FILE CONTAINS NO JOBSLink copied to clipboard

Explanation: This information message indicates that no jobs were found in the file used as input to the Merge utility.

The program terminates with a non-zero return code.

Corrective Action: No action is required.

MSG messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages MSGI00 through MSGIxxLink copied to clipboard

This group includes messages for the Control-O product.

MSGI18I `text`Link copied to clipboard

Explanation: This information message is an echo message showing the /CTO command as received by the DFSAOE00 interface module from IMS.

Corrective Action: No action is required.

MTO messagesLink copied to clipboard

This group includes messages for the Control-O product.

Messages MTO100 through MTO1xxLink copied to clipboard

This group includes messages for the Control-O product.

MTO100I {CONTROL-O | CTMCMEM} RELEASE `x.x.xx` - MONITOR STARTEDLink copied to clipboard

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 DEFINITIONLink copied to clipboard

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 ENABLEDLink copied to clipboard

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 REJECTEDLink copied to clipboard

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`Link copied to clipboard

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 ENCOUNTEREDLink copied to clipboard

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`Link copied to clipboard

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 OPERATORLink copied to clipboard

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`Link copied to clipboard

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 STARTEDLink copied to clipboard

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 ENABLEDLink copied to clipboard

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 REJECTEDLink copied to clipboard

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.Link copied to clipboard

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 DOWNLink copied to clipboard

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 ERRORLink copied to clipboard

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`Link copied to clipboard

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` SECONDSLink copied to clipboard

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 VALUELink copied to clipboard

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 SUPPORTEDLink copied to clipboard

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 ACCEPTEDLink copied to clipboard

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 PRIORITYLink copied to clipboard

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`Link copied to clipboard

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 SUPPORTLink copied to clipboard

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 RESTOREDLink copied to clipboard

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 LIBRARIESLink copied to clipboard

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 ISLink copied to clipboard

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 CASELink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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 ACCEPTEDLink copied to clipboard

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 STOPPEDLink copied to clipboard

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`Link copied to clipboard

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 ACTIVELink copied to clipboard

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 REQUESTLink copied to clipboard

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 REQUESTLink copied to clipboard

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 PROCESSEDLink copied to clipboard

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` ABENDLink copied to clipboard

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`Link copied to clipboard

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/MEMBERLink copied to clipboard

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`Link copied to clipboard

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 ACTIVELink copied to clipboard

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 ACTIVELink copied to clipboard

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`Link copied to clipboard

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 ENABLEDLink copied to clipboard

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 DISABLEDLink copied to clipboard

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"Link copied to clipboard

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 AVAILABLELink copied to clipboard

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`Link copied to clipboard

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 LOSTLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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 INSTALLEDLink copied to clipboard

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`Link copied to clipboard

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 UNCHANGEDLink copied to clipboard

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`REQUESTEDLink copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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`Link copied to clipboard

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.

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`)Link copied to clipboard

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`Link copied to clipboard

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}Link copied to clipboard

Explanation: This information message displays the current MSGMON status.

Corrective Action: No action is required.

MTO161I MSGMON HAS BEEN SET TO {YES | NO}Link copied to clipboard

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

Corrective Action: No action is required.

MTO162W MSGMON IS ALREADY SET TO {YES | NO}Link copied to clipboard

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)Link copied to clipboard

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.

Messages MTO200 through MTO2xxLink copied to clipboard

This group includes messages for the Control-O product.

MTO272I CTOJFRQ EXIT POINT SUCCESSFULLY REMOVEDLink copied to clipboard

Explanation: This information message indicates that as part of its termination process, the Control-O monitor successfully disabled and removed the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and JES2 command suppression functions.

Corrective Action: No action is required.

MTO273W CTOJFRQ EXIT POINT NOT REMOVED RC = `rc` REASON CODE = `rsn`Link copied to clipboard

Explanation: Upon termination, the Control-O monitor has failed to disable and remove the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and JES2 command suppression function.

Control-O terminates without removing the dynamic exit IEFJFRQ that uses the CTOJFRQ module. This may cause an S0C4 code in various jobs under the subsystem interface. In this case, MVS automatically disables the dynamic exit IEFJFRQ that uses the CTOJFRQ module.

Corrective Action: Inform the system programmer, and check the return code and reason code of the CSVDYNEX macro in the IBM manual MVS Programming: Authorized Assembler Services Reference.

MTO274E ERROR WHILE LOADING CTOJFRQ EXIT POINTLink copied to clipboard

Explanation: When Control-O monitor started, it failed to load and enable the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and JES2 command suppression function.

Control-O starts without enabling the dynamic exit IEFJFRQ that uses the CTOJFRQ module. As a result, ON SYSOUT and JES2 command suppression functions will not be active.

Corrective Action: Inform your system programmer.

MTO275E CTOJFRQ EXIT POINT NOT INSTALLED RC = `rc` REASON CODE= `rsn`Link copied to clipboard

Explanation: When the Control-O monitor started, it failed to load and activate the IEFJFRQ dynamic exit, which uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and JES2 command suppression function.

Control-O starts without enabling the IEFJFRQ dynamic exit that uses the CTOJFRQ module. As a result, ON SYSOUT and JES2 command suppression functions will not be active.

Corrective Action: Inform your system programmer and check the RC and REASON CODE of the CSVDYNEX macro in the IBM OS/390 Authorized Macros and Services Guide.

MTO276I CTOJFRQ EXIT POINT SUCCESSFULLY INSTALLEDLink copied to clipboard

Explanation: This information message indicates that when the Control-O monitor started, it successfully enabled the dynamic exit IEFJFRQ that uses the CTOJFRQ module. Control-O uses the CTOJFRQ module for ON SYSOUT and JES2 command suppression function.

Corrective Action: No action is required.

Messages MTO300 through MTO3xxLink copied to clipboard

This group includes messages for the Control-O product.

MTO350E ERROR FREEING STORAGE. ADDR= `addr` LEN= `length` SP= `subpool` RELATED = `rel`Link copied to clipboard

Explanation: An internal error was detected.

During termination, Control-O or CMEM frees internal control blocks and work areas. An error occurred while this was being done.

Control-O or CMEM continues termination.

Corrective Action: Contact BMC Customer Support.

MTO351I SERVER `serverId`WAS actionLink copied to clipboard

Explanation: This information message indicates that a requested SERVER MODIFY command was performed successfully.

Corrective Action: No action is required.

MTO352W SERVER `serverId`DID NOT RESPOND TO STOP REQUESTS. SERVER STATUS OVERRIDDENLink copied to clipboard

Explanation: Server serverId did not respond to a STOP request.

When Control-O executes a server STOP request, it waits for acknowledgment from the server. If the server does not respond within thirty seconds, this message is displayed.

The specified server is given the status ENDED WITH AN ERROR.

Corrective Action: Check output and messages issued by the problem server. If necessary, bring down the server and start a new one.

MTO353I `mod` RELOADED. OLD: `datetime1` NEW: `datetime2`Link copied to clipboard

Explanation: This information message indicates that the RELOAD command completed execution successfully.

This message provides the installation date and time of the old and newly-replaced modules in mm/dd/yy hh.mm format.

The variables in this message are:

mod - the name of the module that was successfully reloaded
datetime1 - the assembly date of the old module
datetime2 - the assembly date of the newly installed module

Corrective Action: No action is required.

MTO354I SERVER STCID TYP QLN STIME STATUSLink copied to clipboard

Explanation: This information message is the normal response of the Control-O monitor to the F CONTROLO,SERVER=serverid,DISPLAY operator command.

This message is the header for information in messages CTO355I and MTO355I.

Corrective Action: No action is required.

MTO355I `serverId jobId type queueLength statusTime status`Link copied to clipboard

Explanation: The Control-O monitor sends this information message to the console in response to the command F CONTROLO,SERVER=serverId,DISPLAY.

Each occurrence of this message describes a server defined to Control-O. These messages are preceded by message CTO354I or MTO354I that provides the header. The information in this message is in the same format as the Option SERVERS screen of the Automation Options facility.

For more information, see the online facilities chapter of the Control-O User Guide.

Corrective Action: No action is required.

MTO356I `modifyCmdText`Link copied to clipboard

Explanation: This information message displays the text of the submitted modify command.

Corrective Action: No action is required.

MTO357I COMMAND ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the last modify command ended successfully.

Corrective Action: No action is required.

MTO358W LIMIT OF LINES REACHED. FURTHER LINES NOT DISPLAYEDLink copied to clipboard

Explanation: More than 1,000 lines were issued in response to a modify command specified with the DISPLAY parameter.

When more than 1,000 lines are issued to the operator’s console, Control-O terminates the command which is creating the lines, to avoid a shortage of space in the console’s buffer.

Only the first 1,000 lines are displayed.

Corrective Action: No action is required.

MTO359W CONTROL-O COSMOS IS NOT ACTIVELink copied to clipboard

Explanation: The user attempted to stop COSMOS while it was not active.

The COSMOSSTOP command is ignored.

Corrective Action: No action is required.

MTO35AW CONTROL-O COSMOS IS ALREADY ACTIVELink copied to clipboard

Explanation: The user attempted to start COSMOS while it was active.

The COSMOSSTART command is ignored.

Corrective Action: No action is required.

MTO35BI OBJECTDB METHODDB MODELink copied to clipboard

Explanation: This information message is the header for data provided in message CTO35CI.

This message is the normal response of Control-O to the F CONTROLO,COSMOS=cosmosdb,DISPLAY operator command.

This command displays general information about COSMOS Object databases.

Corrective Action: No action is required.

MTO35CI `objectDb methodDb mode`Link copied to clipboard

Explanation: This information message is the normal response of Control-O to the F CONTROLO,COSMOS= cosmosdb,DISPLAY operator command.

Each occurrence of this message describes an Object database under COSMOS control. Message CTO35BI generates the message header.

The variables in this message are:

objectDb - Working COSMOS object database.
methodDb - COSMOS Method databases.
mode - Current COSMOS database mode.

Corrective Action: The COSMOS commands are explained in the Control-O/COSMOS User Guide.

MTO35DW INVALID COSMOS MODIFY COMMAND - `errorText`Link copied to clipboard

Explanation: The user issued a COSMOS command with invalid parameters.

In this message, errorText describes the error.

The command is ignored. Processing continues.

Corrective Action: Specify the COSMOS command with valid parameters. For more information on COSMOS commands, see the Control-O/COSMOS User Guide.

MTO35EW `action` COSMOS `id` FAILED - `text`Link copied to clipboard

Explanation: The specified action (action) on the id COSMOS ID failed.

An invalid syntax, action or ID was specified.

The system ignores the command.

Corrective Action: Correct the syntax, action, or ID and reissue the command.

MTO35FW MODIFY COMMAND REJECTEDLink copied to clipboard

Explanation: The user attempted to issue an invalid modify command to the Control-O monitor.

The system rejects the command.

Corrective Action: Correct the command syntax and reenter the command

MTO360E ERROR IN RELOAD INITIALIZATIONLink copied to clipboard

Explanation: The RELOAD modify command encountered a problem with the Control-O SSVT or one of its function routines.

The internal control block structure has been corrupted.

The RELOAD modify command is terminated.

Corrective Action: Bring down and restart Control-O. RELOAD is not necessary.

MTO361E ERROR IN RELOAD PRELIMINARY PHASELink copied to clipboard

Explanation: The RELOAD modify command encountered a problem with an MVS macro instruction.

The user tried to reload the CTOWTO Control-O module in storage but this module was not found in the Control-O STEPLIB libraries.

The RELOAD modify command is terminated.

Corrective Action: Bring down and restart Control-O. RELOAD is not necessary.

MTO362E ERROR IN RELOAD PROCESSINGLink copied to clipboard

Explanation: The RELOAD modify command encountered a problem with an MVS macro instruction.

There may not be enough CSA (Common Service Area) storage available to load the new CTOWTO module.

The RELOAD modify command is terminated.

Corrective Action: Bring down and restart Control-O. RELOAD is not necessary.

MTO363E ERROR IN RELOAD BACK-END PROCESSINGLink copied to clipboard

Explanation: In response to the RELOAD modify command, Control-O encountered a problem when attempting to deallocate a routine.

The internal control block structure has been corrupted.

The RELOAD modify command is completed, but cleanup processing is aborted.

Corrective Action: No action is required.

MTO364E ALTERNATE SUBSYSTEM SSCT ENTRY NOT FOUNDLink copied to clipboard

Explanation: The alternate subsystem SSCT entry specified in ALTSSN CTOPARM parameter is not in the system.

Control-O monitor failed to find the SSCT prior to activating the alternate subsystem.

Control-O monitor routine continues without activating the alternate subsystem.

Corrective Action: Add the alternate subsystem name to the IEFSSNxx member in the SYS1.PARMLIB library and then IPL the system. The alternate subsystem cannot be activated until after the IPL.

MTO366E CONTROL-O COSMOS IS NOT INSTALLEDLink copied to clipboard

Explanation: The user attempted to enter a COSMOS command. However, Control-O COSMOS was not installed

Control-O ignores the command and processing continues.

Corrective Action: Install Control-O COSMOS.

MTO367E SMODE VALID VALUES ARE F, Y, AND NLink copied to clipboard

Explanation: An invalid value was specified for the SMODE parameter in an operator command.

Valid values for SMODE (stand alone mode) are:

F (Forced) - Each Control-O copy is responsible for updating the IOA Log file. Default. BMC recommends that you do not change this default.
Y (Yes) - Each Control-O copy passes requests to write to the IOA Log file to Control-M by means of the communications file, except for requests initiated by the New Day procedure (which are treated as if SMODE is set to F). Setting SMODE to Y causes less ENQ contention for the IOA Log file but increases pressure on the Control-M monitor.
N (No) - Control-O always passes requests to write to the IOA Log file to Control-M by means of the communications file.

The operator command is ignored.

Corrective Action: Specify a valid value for the SMODE parameter and reissue the command. For more information, see SMODE in the INCONTROL for z/OS Administrator Guide.

MTO36GW CTOWTO CANNOT BE RELOADED BECAUSE XES SYSTEM-MANAGED REBUILD IS IN PROGRESS. TRY TO RELOAD LATER.Link copied to clipboard

Explanation: CTOWTO cannot be reloaded until the system-managed process ends.

The RELOAD command is rejected.

Corrective Action: Wait for the system-managed process to end and reissue the RELOAD command.

MTO36HE INVALID MODULE NAME SPECIFIED IN RELOAD COMMAND.Link copied to clipboard

Explanation: A REALOD modify command has been issued for an invalid module name. The module name is either not a module or not a reloadable module. The invalid module name appears in the previous MTO356I message, which echoed the modify command.

The command is ignored.

Corrective Action: Issue the command again with the correct reloadable module name.

Messages MTO600 through MTO6xxLink copied to clipboard

This group includes messages for the Control-O product.

MTO600E ERROR RUNNING CTOCMCK RC= `rc`Link copied to clipboard

Explanation: The CTOGATE communication facility failed to initialize.

CTOMTO called the CTOCMCK module and then ended with an error. This message follows a CTOGATE error message generated by the CTOCMCK module.

CTOGATE aborts.

Corrective Action: Correct and re-initialize CTOGATE.

MTO614I COMMUNICATION STOPPEDLink copied to clipboard

Explanation: This information message indicates that communication stopped due to an operator request.

Control-O communication stops.

Corrective Action: No action is required.

MTO615I COMMUNICATION STARTED.Link copied to clipboard

Explanation: This information message indicates that communication started due to an operator request.

Control-O communication starts.

Corrective Action: No action is required.

MTO616I COMMUNICATION WAS ALREADY STARTED.Link copied to clipboard

Explanation: The user attempted to start communication. However, it was already operating.

Corrective Action: No action is required.

MTO617I COMMUNICATION WAS ALREADY STOPPED.Link copied to clipboard

Explanation: The user attempted to stop communication. However, it had already been stopped.

Corrective Action: No action is required.

MTO619I COMMUNICATION CANNOT BE ACTIVATED.Link copied to clipboard

Explanation: This information message indicates that the user was unable to activate Control-O communication.

STARTCOMM modify command cannot be performed. Control-O was started with the CTOGATE parameter set to NO.

Control-O communication is not activated.

Corrective Action: Start Control-O with the CTOGATE parameter set to YES in the CTOPARM member.

MTO61FI CONTROL-O COMMUNICATION IS ACTIVE. NETWORK NAME= `sysname`, NETWORK MAP= `memName'`Link copied to clipboard

Explanation: This information message indicates that Control-O communication initialization is complete.

Communication is operating using system name sysname and communication network map memName.

Corrective Action: No action is required.

Messages MTO700 through MTO7xxLink copied to clipboard

This group includes messages for the Control-O product.

MTO780I INITIALIZATION OF OPENEDITION ENVIRONMENT STARTEDLink copied to clipboard

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor detected an environment which supports the MVS OpenEdition interface with Control-O and began initializing the OpenEdition environment.

Corrective Action: No action is required.

MTO781I OPENEDITION INTERFACE MODULE SUCCESSFULLY LOADEDLink copied to clipboard

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor loaded the OpenEdition interface module into storage. This message is issued only for the first Control-O or CMEM monitor in the system.

Corrective Action: No action is required.

MTO782I SUBSYSTEM REGISTERED WITH OPENEDITION INTERFACELink copied to clipboard

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

The current Control-O or CMEM subsystem has registered itself (meaning, recorded its name) with the OpenEdition interface in order to receive OpenEdition events from the interface.

Corrective Action: No action is required.

MTO783I INITIALIZATION OF OPENEDITION ENVIRONMENT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message is the normal start message issued during initialization of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

OpenEdition support for the current Control-O or CMEM monitor is successfully installed. Control-O or CMEM will trigger rules based on OpenEdition events.

Corrective Action: No action is required.

MTO784W OS/390 VERSION IS 2.4 OR HIGHER BUT PTF LEVEL IS TOO LOWLink copied to clipboard

Explanation: Control-O or CMEM tried to install OpenEdition support but found an incompatible PTF level.

Control-O or CMEM support for OpenEdition events is required for OS/390 version 2.4 and later. The PTF level in MVS is too low to install the OpenEdition interface.

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action: Install IBM PTF for APAR OW36163, which enables Control-O or CMEM support for OpenEdition.

MTO785W UNABLE TO REGISTER WITH OPENEDITION INTERFACE: `rsn`Link copied to clipboard

Explanation: The Control-O or CMEM subsystem could not register with the OpenEdition interface during initialization.

Possible values for rsn are:

TOO MANY SUBSYSTEMS - The OpenEdition interface already registered the maximum number of subsystems.
LOCK CANNOT BE OBTAINED - Control-O or the CMEM monitor cannot acquire the OpenEdition interface lock, which is needed for registration.
NO SUPPORT FOR DYNAMIC CTOSSI - The fixes (PTFs) that are required to support Control-O or CMEM interface for USS (UNIX Services for OS/390) where Control-O or CMEM is installed are missing.

Initialization of the OpenEdition interface fails. Initialization of Control-O or the CMEM monitor continues. Control-O or the CMEM monitor will not be able to handle OpenEdition events, such as data set triggering based on FTP transmissions. If the value of rsn is NO SUPPORT FOR DYNAMIC CTOSSI, the Control-O or CMEM interface for USS is disabled.

Corrective Action: If the value of rsn is TOO MANY SUBSYSTEMS, shut down a different Control-O or CMEM monitor and restart the current monitor.

If the value of rsn is LOCK CANNOT BE OBTAINED, restart the current monitor. If the problem persists, call your INCONTROL administrator.

(version 6.1.00) If the value of rsn is NO SUPPORT FOR DYNAMIC CTOSSI, apply the following fixes to all environments: PA01142, PA01143, PA01144 and PA01147.

MTO786W LOAD OF OPENEDITION INTERFACE MODULE FAILED: `rsn`Link copied to clipboard

Explanation: During initialization of the OpenEdition interface, Control-O or CMEM could not load the OpenEdition support module.

In this message, rsn is one of the following:

LOAD TO PRIVATE REGION FAILED
CSA GETMAIN FAILED
LOAD TO CSA FAILED

If the value of rsn is LOAD TO PRIVATE REGION FAILED: Control-O or CMEM monitor could not load the OpenEdition support module in its own private region.

If the value of rsn is CSA GETMAIN FAILED: Control-O or the CMEM monitor could not acquire storage in the Common Service Area (CSA) for the OpenEdition support module.

If the value of rsn is LOAD TO CSA FAILED: Control-O or the CMEM monitor could not load the OpenEdition support module to the Common Service Area (CSA).

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action: If the value of rsn is LOAD TO PRIVATE REGION FAILED: determine the cause of the failure using previous messages. Possible causes are:

The Control-O or CMEM region is too small.
The CTOAODT module is not in the Control-O CMEM STEPLIB.

If the value of rsn is CSA GETMAIN FAILED, make sure that the CSA has at least 8K of free storage, then restart the Control-O or CMEM monitor.

If the value of rsn is LOAD TO CSA FAILED, use the contents of previous messages to determine the cause of the failure.

MTO787E INITIALIZATION OF OPENEDITION ENVIRONMENT FAILEDLink copied to clipboard

Explanation: Control-O or CMEM tried to install the OpenEdition interface but an error occurred during initialization of the interface.

The following system actions occur:

Initialization of the OpenEdition interface fails.
Initialization of Control-O or the CMEM monitor continues.
Control-O or the CMEM monitor will not be able to handle OpenEdition events such as data set triggering based on FTP transmissions.

Corrective Action: Look for previous messages which explain the cause of the failure. Call your INCONTROL administrator.

MTO788I SUBSYSTEM ALREADY REGISTERED WITH OPENEDITION INTERFACELink copied to clipboard

Explanation: This information message indicates that Control-O or the CMEM monitor tried to register with the OpenEdition interface but found the subsystem was already registered.

A possible cause is a previous uncompleted termination of CMEM or Control-O.

Initialization of the OpenEdition interface continues.

Corrective Action: No action is required.

MTO789W OPENEDITION ADDRESS SPACE HAS NOT COMPLETED INITIALIZATIONLink copied to clipboard

Explanation: During Control-O startup, Control-O tried to activate OPENEDITION (UNIX for MVS) support. The attempt failed for one of the following reasons:

The system is earlier than OS/390 version 2.4.
IBM APAR OW36163 is missing.

The preconditions for using Control-O/ OPENEDITION (UNIX for MVS) are:

The system must be at OS/390 version 2.4 or later.
IBM APAR OW36163 must be applied.

The Control-O startup process completes but does not support OPENEDITION.

Corrective Action: If the system is earlier than OS/390 version 2.4, ignore this message. Otherwise, apply IBM APAR OW36163.

MTO790I DEACTIVATION OF OPENEDITION ENVIRONMENT STARTEDLink copied to clipboard

Explanation: This information message is the normal message issued during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor detected an active OpenEdition interface environment and started its termination procedure.

Corrective Action: No action is required.

MTO791I SUBSYSTEM REMOVED FROM OPENEDITION INTERFACELink copied to clipboard

Explanation: This information message is the normal message generated during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

The current Control-O or CMEM subsystem removed itself from the OpenEdition interface in order to stop receiving OpenEdition events.

Corrective Action: No action is required.

MTO792I OPENEDITION INTERFACE MODULE REMOVEDLink copied to clipboard

Explanation: This information message is the normal message issued during termination of Control-O or the CMEM monitor when using OS/390 version 2.4 or later.

Control-O or the CMEM monitor removed the OpenEdition support module from storage. This message is displayed only during termination of the last Control-O or the CMEM monitor in the system.

Corrective Action: No action is required.

MTO793I DEACTIVATION OF OPENEDITION ENVIRONMENT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message is the normal message issued during termination of the CMEM monitor or Control-O when using OS/390 version 2.4 or later.

The OpenEdition interface for the current Control-O or CMEM monitor has been successfully removed.

Corrective Action: No action is required.

MTO794W DEACTIVATION OF OPENEDITION ENVIRONMENT FAILEDLink copied to clipboard

Explanation: Control-O or CMEM tried to remove OpenEdition support but encountered an error.

An error occurred during termination of the OpenEdition interface.

Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.

Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.

MTO795W OPENEDITION INTERFACE MODULE NOT INSTALLEDLink copied to clipboard

Explanation: Control-O or the CMEM monitor could not find the OpenEdition interface module during termination.

During termination Control-O or CMEM detected an environment which supports the OpenEdition interface but could not find the OpenEdition support module which should have been installed during initialization.

Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.

Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.

MTO796W SUBSYSTEM NOT REMOVED FROM OPENEDITION INTERFACE: `rsn`Link copied to clipboard

Explanation: Control-O or CMEM could not remove its subsystem name from the OpenEdition interface during termination.

If the value of rsn is SUBSYSTEM NOT FOUND, Control-O or CMEM could not find its subsystem name registered with the OpenEdition interface.

If the value of rsn is LOCK CANNOT BE OBTAINED, Control-O or the CMEM monitor could not get the OpenEdition interface lock it needs to remove its name.

Termination of Control-O or the CMEM monitor continues. Warnings may be issued the next time Control-O or CMEM is activated.

Corrective Action: Look for previous messages which explain the cause of the failure. Verify successful initialization the next time Control-O or CMEM is activated.

MTO797E INVALID MODIFY-REFRESH SUBPARAMETERS. VALID PARAMETERS ARE: XCFLink copied to clipboard

Explanation: The user issued the command F Control-O, REFRESH= parm to refresh the Control-O communication definitions, but the value of parm was invalid.

The valid value of the subparameter is XCF.

Refresh of the Control-O communication definition fails.

Corrective Action: Correct and reenter the command.

MTO798E ERROR IN MODIFY-REFRESH PROCESSINGLink copied to clipboard

Explanation: An error was detected while attempting to refresh the XCF configuration map of Control-O, which defines the MVS image names with which Control-O can work.

Refresh of the Control-O communication definition by the REFRESH command fails.

Corrective Action: Refer to the earlier accompanying messages in the Control-O JOBLOG or SYSLOG.

Messages MTO800 through MTO8xxLink copied to clipboard

This group includes messages for the Control-O product.

MTO820I INITIALIZATION OF SMS SUPPORT STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-O started initializing SMS support.

Corrective Action: No action is required.

MTO821I SMS INTERFACE MODULE SUCCESSFULLY LOADEDLink copied to clipboard

Explanation: This information message indicates that a Control-O subsystem loaded the SMS interface module into storage.

The first Control-O subsystem to initialize itself loads the SMS interface.

Corrective Action: No action is required.

MTO822I SUBSYSTEM REGISTERED WITH SMS INTERFACELink copied to clipboard

Explanation: This information message indicates that the current Control-O subsystem registered itself with the SMS interface.

Control-O subsystems must be registered with the SMS interface to receive SMS events from it.

Corrective Action: No action is required.

MTO823I INITIALIZATION OF SMS SUPPORT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that SMS support for the current Control-O subsystem was installed successfully.

Control-O requires SMS ACS exit routines to trigger rules based on SMS events.

Corrective Action: No action is required.

MTO824W LOAD OF CAB ALLOCATOR MODULE FAILEDLink copied to clipboard

Explanation: Control-O could not load IOACAB.

Control-O needs the IOACAB program to install the SMS interface module.

The following system actions occur:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Check the IOA load library.

MTO825W UNABLE TO REGISTER WITH SMS INTERFACE `rsn`Link copied to clipboard

Explanation: Control-O could not register with the SMS interface during initialization.

Valid values for rsn are:

rsn	Explanation
TOO MANY SUBSYSTEMS	The SMS interface had already registered the maximum number of subsystems.
LOCK CANNOT BE OBTAINED	Control-O could not get the SMS interface lock that it needs for registration.

The following system actions occur:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Do one of the following:

If the value of rsn is TOO MANY SUBSYSTEMS, shut down a different Control-O monitor and restart the current one.
If the value of rsn is LOCK CANNOT BE OBTAINED, restart the current Control-O monitor.

If the problem persists, call your INCONTROL administrator.

MTO826W LOAD OF SMS INTERFACE FAILED: `rsn`Link copied to clipboard

Explanation: Control-O could not load the SMS interface module.

In this message, rsn may be one of the following:

LOAD TO PRIVATE REGION FAILED - Control-O could not load the SMS interface module into its own private region.
CSA GETMAIN FAILED - Control-O could not get the storage in the Common Service Area (CSA) that it needs for the SMS interface module.
LOAD TO CSA FAILED - Control-O could not load the SMS interface module into the CSA.

The following system actions occur:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Do one of the following:

If the value of rsn is LOAD TO PRIVATE REGION FAILED, check earlier messages to determine the cause of failure. The following are possible causes:
- The region allocated for Control-O is too small.
- The CTOACS module is not in the Control-O STEPLLIB library.
If the value of rsn is CSA GETMAIN FAILED, make sure that at least 8KB are allocated for the CSA and restart Control-O.
If the value of rsn is LOAD TO CSA FAILED, check earlier messages to determine the cause of failure.

MTO827E INITIALIZATION OF SMS SUPPORT FAILEDLink copied to clipboard

Explanation: An initialization error occurred when Control-O tried to install the SMS interface.

The following system actions occur:

SMS interface initialization fails.
Control-O initialization continues.
Control-O does not handle SMS events.

Corrective Action: Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

MTO828I SUBSYSTEM ALREADY REGISTERED WITH SMS INTERFACELink copied to clipboard

Explanation: This information message indicates that the current Control-O subsystem did not register with the SMS interface because it was already registered.

This may be because a previous Control-O subsystem did not end correctly.

SMS interface initialization continues.

Corrective Action: No action is required.

MTO829E ALLOCATION OF CVT CUSTOMER ANCHORED BLOCK FAILEDLink copied to clipboard

Explanation: Control-O could not allocate a block of storage anchored to the z/OS communication vector table (CVT).

Even through the block of storage has not yet been allocated, Control-O could not allocate it.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

MTO82AW LOAD OF SMS INTERFACE MODULE FAILED: CSA GETMAIN FAILEDLink copied to clipboard

Explanation: During the Control-O monitor initialization, Control-O failed to GETMAIN the storage in E/CSA, which is required for the CTOACS module, and as a result the Control-O/DFSMS interface is disabled.

Corrective Action: Contact your systems programmer for assistance. Control-O requires about 1024 bytes. If the problem is not resolved, call BMC Customer Support for assistance and provide the step name indicated in the message.

MTO82BW LOAD OF SMS INTERFACE MODULE FAILED: LOAD TO CSA FAILEDLink copied to clipboard

Explanation: During the Control-O monitor initialization, Control-O failed to load the CTOACS module into E/CSA, and as a result the Control-O/DFSMS interface is disabled.

Corrective Action: Contact your systems programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

MTO82CW UNABLE TO REGISTER WITH SMS INTERFACE: NO PROPER ENTRY IN SSTABLELink copied to clipboard

Explanation: This warning message indicates that Control-O detected an internal problem. The Control-O/DFSMS interface is disabled.

Corrective Action: Contact BMC Customer Support.

MTO830I DEACTIVATION OF SMS SUPPORT STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-O started deactivating an SMS interface.

Corrective Action: No action is required.

MTO831I SUBSYSTEM REGISTRATION REMOVED FROM SMS INTERFACELink copied to clipboard

Explanation: This information message indicates that Control-O removed its registration from the SMS interface.

When a Control-O subsystem is not registered with the SMS interface, it cannot receive SMS events from the SMS interface.

Corrective Action: No action is required.

MTO832I SMS INTERFACE MODULE REMOVEDLink copied to clipboard

Explanation: This information message indicates that Control-O removed the SMS interface module from storage.

The last Control-O subsystem removed unloads the SMS interface module.

Corrective Action: No action is required.

MTO833I DEACTIVATION OF SMS SUPPORT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that SMS support for the current Control-O subsystem was removed successfully.

Corrective Action: No action is required.

MTO834W DEACTIVATION OF SMS SUPPORT FAILEDLink copied to clipboard

Explanation: An error occurred when Control-O tried to remove the SMS interface module.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO835W SMS INTERFACE MODULE NOT INSTALLEDLink copied to clipboard

Explanation: Control-O could not find the SMS interface module to delete it.

Control-O detected an environment that supports the SMS interface. However, it could not find the SMS interface module that should have been installed during initialization.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO836W SUBSYSTEM NOT REMOVED FROM SMS INTERFACE: `rsn`Link copied to clipboard

Explanation: Control-O could not remove its subsystem name from the SMS interface.

The value of rsn may be one of the following:

SUBSYSTEM NOT FOUND - The name of the current Control-O subsystem is not registered in the SMS interface.
LOCK CANNOT BE OBTAINED - Control-O could not get the SMS interface lock that it needs to remove its registration.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO837W SUBSYSTEM NOT REMOVED FROM SMS INTERFACE: SUBSYSTEM NOT FOUNDLink copied to clipboard

Explanation: Control-O could not remove its subsystem name from the SMS interface because the name of the current Control-O subsystem is not registered in the SMS interface.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO83AI INITIALIZATION OF AUTOOPERATOR SUPPORT STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-O started initializing AutoOPERATOR support.

Corrective Action: No action is required.

MTO83BW UNABLE TO REGISTER WITH AUTOOPERATOR INTERFACE: LOCK CANNOT BE OBTAINEDLink copied to clipboard

Explanation: Control-O could not register with the AutoOPERATOR interface during initialization because Control-O could not obtain the AutoOPERATOR interface lock that it needs for registration.

The following system actions occur:

AUTOOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Restart the current Control-O monitor. If the problem persists, call your INCONTROL administrator.

MTO83CI AUTOOPERATOR INTERFACE MODULE SUCCESSFULLY LOADEDLink copied to clipboard

Explanation: This information message indicates that Control-O successfully loaded the AutoOPERATOR interface module.

Corrective Action: No action is required.

MTO83DW UNABLE TO REGISTER WITH AUTOOPERATOR INTERFACE: NO PROPER ENTRY IN SSTABLELink copied to clipboard

Explanation: Control-O could not register with the AutoOPERATOR interface during initialization because Control-O could not locate its entry in the INCONTROL internal subsystems table.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Restart the current Control-O monitor. If the problem persists, call your INCONTROL administrator.

MTO83EI SUBSYSTEM REGISTERED WITH AUTOOPERATOR INTERFACELink copied to clipboard

Explanation: This information message indicates that the current Control-O subsystem registered itself with the AutoOPERATOR interface.

Corrective Action: No action is required.

MTO83FI INITIALIZATION OF AUTOOPERATOR SUPPORT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that Control-O initialization of the AutoOPERATOR support ended successfully.

Corrective Action: No action is required.

MTO83GE INITIALIZATION OF AUTOOPERATOR SUPPORT FAILEDLink copied to clipboard

Explanation: An initialization error occurred when Control-O tried to initialize the AutoOPERATOR interface.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

MTO83HW LOAD OF AUTOOPERATOR INTERFACE MODULE FAILED: LOAD TO PRIVATE FAILEDLink copied to clipboard

Explanation: Control-O could not load the AutoOPERATOR interface module because it could not load the module into its own private region.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure. The following are possible causes:

The region allocated for Control-O is too small.
The CTOAAO module is not in the Control-O STEPLLIB library.

MTO83IW LOAD OF AUTOOPERATOR INTERFACE MODULE FAILED: CSA GETMAIN FAILEDLink copied to clipboard

Explanation: Control-O could not load the AutoOPERATOR interface module because it could not get the storage in the Common Service Area (CSA) that it needs for the AutoOPERATOR interface module.

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure.

MTO83JW LOAD OF AUTOOPERATOR INTERFACE MODULE FAILED: LOAD TO CSA FAILEDLink copied to clipboard

Explanation: Control-O could not load the AutoOPERATOR interface module because it could not load the AutoOPERATOR interface module to the Common Service Area (CSA).

The following system actions occur:

AutoOPERATOR interface initialization fails.
Control-O initialization continues.
Control-O does not handle AutoOPERATOR events.

Corrective Action: Check earlier messages to determine the cause of failure.

MTO83KI DEACTIVATION OF AUTOOPERATOR SUPPORT STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-O started deactivating the AutoOPERATOR interface.

Corrective Action: No action is required.

MTO83LW AUTOOPERATOR INTERFACE MODULE NOT INSTALLEDLink copied to clipboard

Explanation: Control-O could not find the AutoOPERATOR interface module to delete it. Control-O detected an environment that supports the AutoOPERATOR interface. However, it could not find the AutoOPERATOR interface module that is usually installed during initialization.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO83MW SUBSYSTEM NOT REMOVED FROM AUTOOPERATOR INTERFACE: LOCK CANNOT BE OBTAINEDLink copied to clipboard

Explanation: Control-O could not remove its subsystem name from the AutoOPERATOR interface because Control-O could not get the AutoOPERATOR interface lock that it needs to remove its registration.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO83NW SUBSYSTEM NOT REMOVED FROM AUTOOPERATOR INTERFACE: NO PROPER ENTRY IN SSTABLELink copied to clipboard

Explanation: When Control-O tried to remove the AutoOPERATOR interface module it could not find its entry in the internal INCONTROL subsystem table.

Control-O termination continues.

Corrective Action: Check earlier messages to determine the cause of the error.

MTO83OI SUBSYSTEM REGISTRATION REMOVED FROM AUTOOPERATOR INTERFACELink copied to clipboard

Explanation: This information message indicates that Control-O unregistered the AutoOPERATOR interface.

Corrective Action: No action is required.

MTO83PI AUTOOPERATOR INTERFACE MODULE REMOVEDLink copied to clipboard

Explanation: This information message indicates that Control-O removed the AutoOPERATOR interface module from Common Service Area (CSA).

Corrective Action: No action is required.

MTO83QI DEACTIVATION OF AUTOOPERATOR SUPPORT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that the Control-O deactivation of the AutoOPERATOR support ended successfully.

Corrective Action: No action is required.

MTO83RW DEACTIVATION OF AUTOOPERATOR SUPPORT FAILEDLink copied to clipboard

Explanation: An error occurred when Control-O tried to remove the AutoOPERATOR interface module.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O might produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO840E INITIALIZATION OF SUBSYSTEM TABLE FAILED: `text`Link copied to clipboard

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems if they were not already defined. During the definition process, an error occurred.

In this message, text identifies the nature of the error. Valid values for text are:

text	Explanation
LOAD OF CTOSSI FAILED	The Control-O interface was not successfully loaded.
CSA GETMAIN FAILED	Control-O failed to GETMAIN in CSA.
LOCK CANNOT BE OBTAINED	Control-O failed to obtain LOCK.
TOO MANY SUBSYSTEMS	Control-O failed to define the subsystem, because the SSVT subsystem table already contained the maximum permitted number of subsystems.

Control-O terminates with a return code of 8.

Corrective Action: The necessary action depends on the value of text.

If the value of text is LOAD OF CTOSSI FAILED, ensure that the Control-O STC is using the correct STEPLIB library, then restart Control-O.
If the value of text is CSA GETMAIN FAILED, ensure that Control-O has sufficient storage. Control-O requires about 50K in CSA. It may be necessary to restart the system.
If the value of text is LOCK CANNOT BE OBTAINED, the error may be a Control-O internal error. Try again to start Control-O. If the same error occurs, contact BMC Customer Support.
If the value of text is TOO MANY SUBSYSTEMS, reduce the number of subsystems that are active, and try again to start Control-O. It may be necessary to deactivate one or more active subsystems, or to restart the system, before trying to restart Control-O.

MTO841I MAINVIEW INTERFACE MODULE SUCCESSFULLY LOADEDLink copied to clipboard

Explanation: This information message indicates that a Control-O subsystem loaded the MAINVIEW interface module into storage.

The first Control-O subsystem to initialize itself loads the MAINVIEW interface.

Corrective Action: No action is required.

MTO842I SUBSYSTEM REGISTERED WITH MAINVIEW INTERFACELink copied to clipboard

Explanation: This information message indicates that the current Control-O subsystem registered itself with the MAINVIEW interface.

Control-O subsystems must be registered with the MAINVIEW interface to receive MAINVIEW events from it.

Corrective Action: No action is required.

MTO843I INITIALIZATION OF MAINVIEW SUPPORT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that MAINVIEW support for the current Control-O subsystem was installed successfully.

Control-O requires MAINVIEW ACS exit routines to trigger rules based on MAINVIEW events.

Corrective Action: No action is required.

MTO844W LOAD OF CAB ALLOCATOR MODULE FAILEDLink copied to clipboard

Explanation: Control-O could not load IOACAB.

Control-O needs the IOACAB program to install the MAINVIEW interface module.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check the IOA load library.

MTO845W UNABLE TO REGISTER WITH MAINVIEW INTERFACE `rsn`Link copied to clipboard

Explanation: Control-O could not register with the MAINVIEW interface during initialization.

Valid values for rsn are:

rsn	Explanation
TOO MANY SUBSYSTEMS	The MAINVIEW interface had already registered the maximum number of subsystems.
LOCK CANNOT BE OBTAINED	Control-O could not get the MAINVIEW interface lock that it needs for registration.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Do one of the following:

If the value of rsn is TOO MANY SUBSYSTEMS, shut down a different Control-O monitor and restart the current one.
If the value of rsn is LOCK CANNOT BE OBTAINED, restart the current Control-O monitor.

If the problem persists, call your INCONTROL administrator.

MTO846W LOAD OF MAINVIEW INTERFACE FAILED: `rsn`Link copied to clipboard

Explanation: Control-O could not load the MAINVIEW interface module.

Valid values for rsn are:

rsn	Explanation
LOAD TO PRIVATE REGION FAILED	Control-O could not load the MAINVIEW interface module into its own private region.
CSA GETMAIN FAILED	Control-O could not get the storage in the Common Service Area (CSA) that it needs for the MAINVIEW interface module.
LOAD TO CSA FAILED	Control-O could not load the MAINVIEW interface module into the CSA.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Do one of the following:

If the value of rsn is LOAD TO PRIVATE REGION FAILED, check earlier messages to determine the cause of failure. The following are possible causes:

The region allocated for Control-O is too small.
The CTOACS module is not in the Control-O STEPLLIB library.

If the value of rsn is CSA GETMAIN FAILED, make sure that at least 8KB are allocated for the CSA and restart Control-O.
If the value of rsn is LOAD TO CSA FAILED, check earlier messages to determine the cause of failure.

MTO847E INITIALIZATION OF MAINVIEW SUPPORT FAILEDLink copied to clipboard

Explanation: An initialization error occurred when Control-O tried to install the MAINVIEW interface.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check earlier messages to determine the cause of failure. If necessary, call your INCONTROL administrator.

MTO848I SUBSYSTEM ALREADY REGISTERED WITH MAINVIEW INTERFACELink copied to clipboard

Explanation: This information message indicates that the current Control-O subsystem did not register with the MAINVIEW interface because it was already registered.

A possible cause is that a previous Control-O subsystem did not end correctly.

MAINVIEW interface initialization continues.

Corrective Action: No action is required.

MTO84AI INITIALIZATION OF MAINVIEW SUPPORT STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-O started initializing MAINVIEW support.

Corrective Action: No action is required.

MTO84BI DEACTIVATION OF MAINVIEW SUPPORT STARTEDLink copied to clipboard

Explanation: This information message indicates that Control-O started deactivating an MAINVIEW interface.

Corrective Action: No action is required.

MTO84CI SUBSYSTEM REGISTRATION REMOVED FROM MAINVIEW INTERFACELink copied to clipboard

Explanation: This information message indicates that Control-O removed its registration from the MAINVIEW interface.

When a Control-O subsystem is not registered with the MAINVIEW interface, it cannot receive MAINVIEW events from the MAINVIEW interface.

Corrective Action: No action is required.

MTO84DI MAINVIEW INTERFACE MODULE REMOVEDLink copied to clipboard

Explanation: This information message indicates that Control-O removed the MAINVIEW interface module from storage.

The last Control-O subsystem removed unloads the MAINVIEW interface module.

Corrective Action: No action is required.

MTO84EI DEACTIVATION OF MAINVIEW SUPPORT ENDED SUCCESSFULLYLink copied to clipboard

Explanation: This information message indicates that MAINVIEW support for the current Control-O subsystem was removed successfully.

Corrective Action: No action is required.

MTO84FW DEACTIVATION OF MAINVIEW SUPPORT FAILEDLink copied to clipboard

Explanation: An error occurred when Control-O tried to remove the MAINVIEW interface module.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO84GW MAINVIEW INTERFACE MODULE NOT INSTALLEDLink copied to clipboard

Explanation: Control-O could not find the MAINVIEW interface module to delete it.

Control-O detected an environment that supports the MAINVIEW interface. However, it could not find the MAINVIEW interface module that should have been installed during initialization.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO84HW SUBSYSTEM NOT REMOVED FROM MAINVIEW INTERFACE: `rsn`Link copied to clipboard

Explanation: Control-O could not remove its subsystem name from the MAINVIEW interface.

Valid values of rsn are:

rsn	Explanation
SUBSYSTEM NOT FOUND	The name of the current Control-O subsystem is not registered in the MAINVIEW interface.
LOCK CANNOT BE OBTAINED	Control-O could not get the MAINVIEW interface lock that it needs to remove its registration.

The following system actions occur:

Control-O termination continues.
The next attempt to activate Control-O may produce warnings.

Corrective Action: Do both of the following:

Check earlier messages to determine the cause of the error.
Check that the next Control-O initialization succeeds.

MTO84IE INITIALIZATION OF SUBSYSTEM TABLE FAILED: CSA GETMAIN FAILEDLink copied to clipboard

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems if they were not already defined. During the definition process, the Control-O failed to GETMAIN in CSA.

Control-O terminates with a return code of 8.

Corrective Action: Ensure that Control-O has sufficient storage. Control-O requires about 50K in CSA. It might be necessary to restart the system.

MTO84JE INITIALIZATION OF SUBSYSTEM TABLE FAILED: LOCK CANNOT BE OBTAINEDLink copied to clipboard

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems if they were not already defined. During the definition process, the Control-O failed to obtain LOCK.

Control-O terminates with a return code of 8.

Corrective Action:The error might be a Control-O internal error. Try to start Control-O again. If the same error occurs, contact BMC Customer Support.

MTO84KE INITIALIZATION OF SUBSYSTEM TABLE FAILED: TOO MANY SUBSYSTEMSLink copied to clipboard

Explanation: When Control-O starts, it defines the IOA and Control-O subsystems, if they were not defined previously. During the definition process, the Control-O failed to define the subsystem, because the number of Control-O and Control-M Event Manager (CMEM) environments defined on the LPAR exceeded the maximum of 20.

Control-O terminates with a return code of 8.

Corrective Action: Stop all active Control-O and CMEM monitors, run the IOACABPR (Emergency CAB Control Block Disconnect) utility, and then restart the Control-O and CMEM monitors.

MTO84LW UNABLE TO REGISTER WITH MAINVIEW INTERFACE: NO PROPER ENTRY IN SSTABLELink copied to clipboard

Explanation: Control-O could not register with the MAINVIEW interface during initialization because Control-O could not locate its entry in the INCONTROL internal subsystems table.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Restart the current Control-O monitor. If the problem persists, call your INCONTROL administrator.

MTO84MW LOAD OF MAINVIEW INTERFACE FAILED: CSA GETMAIN FAILEDLink copied to clipboard

Explanation: Control-O could not load the MAINVIEW interface module because Control-O could not get the storage in the Common Service Area (CSA) that it needs for the MAINVIEW interface module.

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Make sure that at least 8KB are allocated for the CSA and restart Control-O.

MTO84NW LOAD OF MAINVIEW INTERFACE FAILED: LOAD TO CSA FAILEDLink copied to clipboard

Explanation: Control-O could not load the MAINVIEW interface module because Control-O could not load the MAINVIEW interface module into the Common Service Area (CSA).

The following system actions occur:

MAINVIEW interface initialization fails.
Control-O initialization continues.
Control-O does not handle MAINVIEW events.

Corrective Action: Check earlier messages to determine the cause of failure.

MTO84OW SUBSYSTEM NOT REMOVED FROM MAINVIEW INTERFACE: NO PROPER ENTRY IN SSTABLLink copied to clipboard

Explanation: When Control-O tried to remove the MAINVIEW interface module it could not find its entry in the internal INCONTROL subsystem table.

Control-O termination continues.

Corrective Action: Check earlier messages to determine the cause of failure.

Messages MTO900 through MTO9xxLink copied to clipboard

This group includes messages for the Control-O product.

MTO910W PARAMETER NUMCONS IN CTOPARM FORCED TO '0', DUE TO OPERATING SYSTEM RESTRICTIONSLink copied to clipboard

Explanation: Control-O changes the NUMCONS parameter, in the CTOPARM member, to zero.

The Control-O startup process continues.

Corrective Action: If the CTOPARM member is only used for Control-O, set NUMCONS=0 in the CTOPARM member.

MTO915S ERROR IN CONTROL-O INSTALLATION PARAMETERSLink copied to clipboard

Explanation: During the startup of the Control-O monitor, an error is encountered in the Control-O installation parameters. The nature of the error is detailed in an accompanying message or messages.

The Control-O monitor terminates.

Corrective Action: Contact your INCONTROL administrator.

MTO916S ERROR OCCURRED DURING CONTROL-O INITIALIZATIONLink copied to clipboard

Explanation: During the startup of the Control-O monitor, an error occurred during Control-O initialization. The nature of the error is detailed in an accompanying message or messages.

The Control-O monitor terminates.

Corrective Action: Contact your INCONTROL administrator.

MTO917W PARAMETER JCMDSSN SHOULD DIFFER FROM SSNAME; REPLACED WITH BLANKSLink copied to clipboard

Explanation: During the startup of the Control-O monitor, the values of the JCMDSSN and the SSNAME parameters were found to be identical.

The JCMDSSN parameter identifies the JES2 command suppression subsystem name, and is in the CTOPARM member.

The SSNAME parameter identifies the IOA subsystem, and is in the IOAPARM parameter.

The value of the JCMDSSN parameter is replaced with blanks. Monitor startup continues.

Corrective Action: Contact your INCONTROL administrator.

MTO918S INSUFFICIENT MEMORY TO RUN CONTROL-O. COMPONENT: `component` LENGTH=`getmain_length`Link copied to clipboard

Explanation: The Control-O component could not be initialized because the getmain in length getmain_length failed.

The specified monitor will shut down.

Corrective Action: Increase the REGION size of the specified monitor.

MTO919E `monitor_type name` FROM VERSION `version` IS USING SUBSYSTEM `subsys`. BRING IT DOWN BEFORE STARTING THIS MONITORLink copied to clipboard

Explanation: During Control-O or CMEM monitor initialization, it was discovered that the existing subsys subsystem is already activated for the version version of the monitor. The active monitor is shut down.

Corrective Action: Determine which monitor (the active one or the newly started) should use the subsystem and act accordingly.

K–M

KOA MessagesLink copied to clipboard

Messages KOA0 through KOA0xxLink copied to clipboard

KOA003E VTAM APPLICATION IS NOT RESPONDINGLink copied to clipboard

KOA004E A LOGICAL OR PHYSICAL ERROR OCCURRED. SENSE= rc. fdb2.fdbk2Link copied to clipboard

KOA005E VTAM CANNOT ESTABLISH THE REQUESTED SESSIONLink copied to clipboard

KOA008E INSUFFICIENT STORAGE. INCREASE THE REGION SIZELink copied to clipboard

KOA009E THE SPECIFIED LU IS ALREADY BEING USEDLink copied to clipboard

KOA00AE THE SPECIFIED LU IS NOT DEFINEDLink copied to clipboard

KOA00BE ALL THE DEFINED APPLICATIONS ARE BEING USEDLink copied to clipboard

KOA00CE THE SPECIFIED APPLICATION IS NOT AVAILABLELink copied to clipboard

KOA00EE FUNCTION func FAILED. SENSE= rc. fdb2. fdbk2Link copied to clipboard

KOA00FE NON-LU2 TYPE HAS BEEN DEFINEDLink copied to clipboard

KSL MessagesLink copied to clipboard

Messages KSL300 through KSL3xxLink copied to clipboard

KSL320E MAXIMUM NUMBER OF ARGUMENTS IN A CALL COMMAND IS 9Link copied to clipboard

The KeyStroke Language Report will terminate with a condition code of 08 or 12.Link copied to clipboard

KSL321E CALLMEM MEMBER IS EMPTYLink copied to clipboard

KSL322E ARGUMENT REPLACEMENT WILL EXPAND THE CARD OVER ITS MAXIMUM LENGTHLink copied to clipboard

KSL337I textLink copied to clipboard

KSL338E INVALID VALUE OF %RC - valLink copied to clipboard

KSL339E LINE IDENTIFIER id IS NOT DEFINEDLink copied to clipboard

KSL340E SCREEN SIZE ALREADY SET, OR SCREEN COMMANDS ALREADY ACTIVATEDLink copied to clipboard

KSL341E PAGE SIZE ALREADY SET, OR PRINT/HEADER/BOTTOM COMMANDS ALREADY ACTIVATEDLink copied to clipboard

KSL342E INTERNAL PRINTING ERROR. RC= rcLink copied to clipboard

KSL343E LABEL ALREADY DEFINEDLink copied to clipboard

KSL344E GOTO TO AN UNDEFINED LABEL labelLink copied to clipboard

KSL345E IFSCREEN COMMAND NOT IN SCREEN RANGELink copied to clipboard

KSL346E MAXCOMMAND ALREADY SETLink copied to clipboard

KSL347E HEADERSIZE/BOTTOMSIZE MUST BE ACTIVATED BEFORE A HEADERLINE/BOTTOMLINE COMMANDLink copied to clipboard

KSL348E UNDEFINED VARIABLE - varNameLink copied to clipboard

KSL349E ERROR WHILE EXECUTING COMMAND - cmdTextLink copied to clipboard

Messages KSL400 through KSL4xxLink copied to clipboard

KSL401I A KEYSTROKE REPORT STARTEDLink copied to clipboard

KSL402I A KEYSTROKE REPORT ENDED SUCCESSFULLYLink copied to clipboard

KSL403E TEXT EXPECTED BETWEEN QUOTES IN THE COMMANDLink copied to clipboard

KSL404E REDUNDANT PARAMETERS IN THE REPORT COMMANDLink copied to clipboard

KSL405E MISSING/INVALID PARAMETERS IN THE REPORT COMMANDLink copied to clipboard

KSL406E INVALID LINE/COL NUMBER - num (OR OUT OF RANGE)Link copied to clipboard

KSL407E INTERNAL COMMAND HANDLER ERROR RC rcLink copied to clipboard

KSL408E MAXIMUM NUMBER OF COMMANDS EXCEEDED. REPORT IS TERMINATEDLink copied to clipboard

KSL409E A KEYSTROKE REPORT ENDED WITH ERROR(S)Link copied to clipboard

KSL410E TYPING IN A "SCREEN" PROTECTED AREA IS NOT PERMITTED - THE REPORT IS TERMINATEDLink copied to clipboard

Messages KSLA00 through KSLAxxLink copied to clipboard

KSLA60I EXCEPTIONAL CONDITION RC=rc, ERROR=err, FEEDBACK=feedback, APPLID= applIdLink copied to clipboard

KSLA61E SCREEN COMMAND EXECUTED WITH NO SCREEN AVAILABLELink copied to clipboard

KSLA62E CONTROL-O IS NOT ACTIVE. GLOBAL VARIABLES CANNOT BE USEDLink copied to clipboard

KSLA63E SPECIFIED SESSION ID IS NOT ACTIVELink copied to clipboard

KSLA64E KEYSTROKE UTILITY DETECTED INTERNAL ABEND abCodeLink copied to clipboard

KSLA65E ALLOC OF DDNAME ddName FAILED, RC = rc, ERROR= err, DSN= dsnLink copied to clipboard

KSLA66E FREE OF DDNAME ddName FAILEDLink copied to clipboard

KSLA67E OPEN OF DDNAME ddName FAILEDLink copied to clipboard

KSLA68E CLOSE OF DDNAME ddName FAILEDLink copied to clipboard

KSLA69E I/O ERROR WHEN READING FROM DDNAME ddNameLink copied to clipboard

KSLA6AE I/O ERROR WHEN WRITING TO DDNAME ddNameLink copied to clipboard

KSLA6BE UNSUPPORTED DCB CHARACTERISTICS FOR DDNAME ddNameLink copied to clipboard

KSLA6CE ENQ ERR RC= rc, Q= queueName, R= resourceNameLink copied to clipboard

KSLA6DE RSV ERR RC= rc, Q= queueName, R= resourceNameLink copied to clipboard

KSLA6EE DDNAME ddName NOT FOUNDLink copied to clipboard

KSLA6FE SETOLOC/SETOGLB ERROR CODE = rc REASON = rsn, TEXT=AutoEdit_expressionLink copied to clipboard

KSLA70E THERE IS AN ERROR IN IOAKPRM MEMBER. PLEASE CHECK THE SMFID FIELD.Link copied to clipboard

LDT MessagesLink copied to clipboard

Messages LDT500 through LDT5xxLink copied to clipboard

LDT500I RULE= rule TYPE= rule_typ TABLE= tableName LIB= libLink copied to clipboard

LDT501I func OF RULE TABLE(S) STARTEDLink copied to clipboard

LDT502E MEMBER IN USE= memb DSN= dsnLink copied to clipboard

LDT503S RULE ORDER LIST IS EMPTY. DDNAME= {DARULLST | DACTMLST}Link copied to clipboard

LDT504S INVALID DATA IN RULE ORDER LIST CARDSLink copied to clipboard

LDT505S MEMBER memName NOT FOUND IN LIBRARY libLink copied to clipboard

LDT506S ORDER OF TABLE tableName RULE ruleName FAILEDLink copied to clipboard

LDT507I LOAD ENDED FOR TABLE table LIBRARY libLink copied to clipboard

LDT508I {ORDER | FORCE} OF RULES’ TABLE(S) ENDEDLink copied to clipboard

LDT509I NUMBER OF TABLES numtbl PROCESSED. numrul1 RULES LOADED AND numrul2 RULES REJECTEDLink copied to clipboard

LDT50AI NUMBER OF TABLES numtbl RULES numrul DELETEDLink copied to clipboard

LDT50BE HOLD BY jobId ASID asid ON SYSTEM systemIdLink copied to clipboard

LDT50CE LIBRARY WAS MIGRATED BY HSM DSNAME=Link copied to clipboard

LDT50FI textLink copied to clipboard

LDT516S ERROR IN RULE DATA - MANDATORY stmt_type CARD IS EITHER MISSING OR IN AN INCORRECT ORDERLink copied to clipboard

LDT517S RULE DATA NOT AVAILABLE: MEMBER memName IS EMPTYLink copied to clipboard

LDT518S INVALID SCHEDULING DATE - dateLink copied to clipboard

KOA004E A LOGICAL OR PHYSICAL ERROR OCCURRED. SENSE= `rc. fdb2.fdbk2`Link copied to clipboard

KOA00EE FUNCTION `func` FAILED. SENSE= `rc. fdb2. fdbk2`Link copied to clipboard

KSL337I `text`Link copied to clipboard

KSL338E INVALID VALUE OF %RC - `val`Link copied to clipboard

KSL339E LINE IDENTIFIER `id` IS NOT DEFINEDLink copied to clipboard

KSL342E INTERNAL PRINTING ERROR. RC= `rc`Link copied to clipboard

KSL344E GOTO TO AN UNDEFINED LABEL `label`Link copied to clipboard

KSL348E UNDEFINED VARIABLE - `varName`Link copied to clipboard

KSL349E ERROR WHILE EXECUTING COMMAND - `cmdText`Link copied to clipboard

KSL406E INVALID LINE/COL NUMBER - `num` (OR OUT OF RANGE)Link copied to clipboard

KSL407E INTERNAL COMMAND HANDLER ERROR RC `rc`Link copied to clipboard

KSLA60I EXCEPTIONAL CONDITION RC=`rc`, ERROR=`err`, FEEDBACK=`feedback`, APPLID= `applId`Link copied to clipboard

KSLA64E KEYSTROKE UTILITY DETECTED INTERNAL ABEND `abCode`Link copied to clipboard

KSLA65E ALLOC OF DDNAME `ddName` FAILED, RC = `rc`, ERROR= `err`, DSN= `dsn`Link copied to clipboard

KSLA66E FREE OF DDNAME `ddName` FAILEDLink copied to clipboard

KSLA67E OPEN OF DDNAME `ddName` FAILEDLink copied to clipboard

KSLA68E CLOSE OF DDNAME `ddName` FAILEDLink copied to clipboard

KSLA69E I/O ERROR WHEN READING FROM DDNAME `ddName`Link copied to clipboard

KSLA6AE I/O ERROR WHEN WRITING TO DDNAME `ddName`Link copied to clipboard

KSLA6BE UNSUPPORTED DCB CHARACTERISTICS FOR DDNAME `ddName`Link copied to clipboard

KSLA6CE ENQ ERR RC= `rc`, Q= `queueName`, R= `resourceName`Link copied to clipboard

KSLA6DE RSV ERR RC= `rc`, Q= `queueName`, R= `resourceName`Link copied to clipboard

KSLA6EE DDNAME `ddName` NOT FOUNDLink copied to clipboard

KSLA6FE SETOLOC/SETOGLB ERROR CODE = `rc` REASON = `rsn`, TEXT=`AutoEdit_expression`Link copied to clipboard

LDT500I RULE= `rule` TYPE= `rule_typ` TABLE= `tableName` LIB= `lib`Link copied to clipboard

LDT501I `func` OF RULE TABLE(S) STARTEDLink copied to clipboard

LDT502E MEMBER IN USE= `memb` DSN= `dsn`Link copied to clipboard

LDT505S MEMBER `memName` NOT FOUND IN LIBRARY `lib`Link copied to clipboard

LDT506S ORDER OF TABLE `tableName` RULE `ruleName` FAILEDLink copied to clipboard

LDT507I LOAD ENDED FOR TABLE `table` LIBRARY `lib`Link copied to clipboard

LDT509I NUMBER OF TABLES `numtbl` PROCESSED. `numrul1` RULES LOADED AND `numrul2` RULES REJECTEDLink copied to clipboard

LDT50AI NUMBER OF TABLES `numtbl` RULES `numrul` DELETEDLink copied to clipboard

LDT50BE HOLD BY `jobId` ASID `asid` ON SYSTEM `systemId`Link copied to clipboard

LDT50FI `text`Link copied to clipboard

LDT516S ERROR IN RULE DATA - MANDATORY `stmt_type` CARD IS EITHER MISSING OR IN AN INCORRECT ORDERLink copied to clipboard

LDT517S RULE DATA NOT AVAILABLE: MEMBER `memName` IS EMPTYLink copied to clipboard

LDT518S INVALID SCHEDULING DATE - `date`Link copied to clipboard

LDT526S ** ERROR IN RULE CARDS. CHECK THE FOLLOWING CARDS *Link copied to clipboard

LDT527S CARD = `stmt`Link copied to clipboard

LDT528I RULE `ruleName rule_type` TABLE `tableName` LIBRARY `lib` ODATE `odate` LOADEDLink copied to clipboard

LDT529I TABLE `tableName` LIBRARY `lib` DELETEDLink copied to clipboard

LDT530E DELETE OF TABLE `tableName` LIBRARY `lib` FAILED, TABLE NOT FOUNDLink copied to clipboard

LDT531I NO RULE WAS LOADED - TABLE `tableName` LIBRARY `lib`Link copied to clipboard

LDT532E MASK `mask` DOES NOT MATCH IN DSN= `dsn`Link copied to clipboard

LDT539W ORDER CANCELLED BY USER EXIT: RULE `ruleName` TABLE `tableName` LIBRARY `lib`Link copied to clipboard

LDT548E SEVERE ERROR IN CALENDAR `calName` OR YEAR NOT FOUND IN CALENDARLink copied to clipboard

LDT54CW LOAD REQUEST IGNORED. TABLE `tableName` LIBRARY `lib` ALREADY LOADEDLink copied to clipboard

LDT54DE RULE TYPE IS INCORRECT. TABLE `tableName` LIBRARY `lib`Link copied to clipboard

LDT54FW RULE WAS NOT LOADED: {SYSTEM | SMF ID} { `rul_sysname`|`rul_smfid`} DOES NOT MATCH { `cur_sysname`|`cur_smfid`}Link copied to clipboard

LNR063E NO MORE PLACE IN MANUAL CONDS FILE FOR COND `cond` ODATE `odate`Link copied to clipboard

LNR064E INVALID PARAMETER:- `parm`Link copied to clipboard

LNR065E MISSING PARAMETER AFTER:- `parm`Link copied to clipboard

LNR066E REDUNDANT PARAMETER: - `parm`Link copied to clipboard