N–Z

This group includes messages for the Control-M/Analyzer, 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 and Control-M/Restart), Control-O, Control-V and IOA (infrastructure) products.

NRC Messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages NRC900 through NRC9xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

NRC930I NOTE AND RULER CONVERSION STARTED.

Explanation: This information message is issued routinely when the CTDNRC utility started.

Corrective Action: No action is required.

NRC931I WD1164 IS SET TO `status`

Explanation: This information message shows the current WD1164 optional wish status.

Possible values are:

JOBNAME
REPORT
CATEGORY

Corrective Action: No action is required.

NRC932I NOTE AND RULER CONVERSION ENDED

Explanation: This information message indicates that the CTDNRC utility finished successfully.

Corrective Action: No action is required.

NRC933E NOTE AND RULER CONVERSION ENDED WITH ERROR

Explanation: This information message indicates that the CTDNRC utility finished with errors.

Corrective Action: Examine other messages relating to the CTDNRC utility to identify and fix the problem, and then rerun the utility.

NRC934I `record_type` RECORDS: `n`

Explanation: This information message issue displays the number of records read and processed by the CTDNRC utility.

Possible record_type values are:

READ
NOT UPDATED NOTE
NOT UPDATED RULER
UPDATED NOTE
UPDATED RULER

Corrective Action: No action is required.

NRC935S SORT ERROR RC=`rc`

Explanation: During execution of the CTDNRC utility, a sort program was activated internally, but the sort program ended with an unexpected internal return code.

In this message, rc is the unexpected internal return code.

The CTDNRC utility ends with a condition code of 08.

Corrective Action: Examine the messages issued by the sort program and the documentation relating to that program to determine the cause of the error, and take appropriate corrective action.

NRC936S OPEN FILE `ddname` ERROR

Explanation: During execution of the CTDNRC utility, the opening of a file failed.

Possible causes are:

The ddname DD statement is missing.
The data set described by the ddname DD statement contains incorrect DCB parameters.
The data set described by the ddname DD statement cannot be opened for sequential read or write operations.

In this message, ddname is the name of the problematic DD statement.

The CTDNRC utility ends with a condition code of 08.

Corrective Action: Correct the JCL of the CTDDIP utility and rerun the job.

NRC937S INSUFFICIENT STORAGE

Explanation: There is insufficient available storage to run the CTDNRC utility.

The CTDNRC utility ends with a condition code of 08.

Corrective Action: Increase the REGION size of the utility, and rerun the utility.

NSC Messages

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 NSC300 through NSC3xx

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.

NSC391I NIGHT SCHEDULE REPORT STARTED

Explanation: This information message is the regular start message of the Night Schedule Report.

Corrective Action: No action is required.

NSC392S MAXIMUM NUMBER OF INCLUDE PARAMETERS EXCEEDED

Explanation: Too many INCLUDE statements have been specified for the current run of the utility.

Up to ten INCLUDE statements may be specified for each individual run of the utility.

The report cannot be produced for the specified number of groups. Processing is terminated.

Corrective Action: Decrease the number of INCLUDE statements. To produce the report for more than ten groups, use multiple runs of the utility with each run having less than ten INCLUDE statements.

NSC393I NIGHT SCHEDULE REPORT ENDED

Explanation: This information message is the regular termination message of the Night Schedule Report.

Corrective Action: No action is required.

NTP Messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages NTP0 through NTP0xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

NTP001E SECURITY VIOLATION. YOU ARE NOT AUTHORIZED TO EDIT THE NOTE

Explanation: The user attempted to add or change a note without security authorization, but was prevented from doing so by Control-D security exit CTDX004.

Corrective Action: If you think you should be authorized to add or change this note, contact your INCONTROL administrator.

NTP002E PLEASE FILL IN A VALID OPTION - "Y" OR "N"

Explanation: An invalid SAVE option was specified for the note.

Valid SAVE options are:

Y - Save the changes.
N - Do not save the changes.

Corrective Action: Specify a valid SAVE option.

NTP003E NOTE PAD FILE IS IN USE, TRY AGAIN LATER

Explanation: The user tried to edit a note that is currently in use by another user.

A note that is currently in use by a user can only be browsed by other users.

The requested action is not performed.

Corrective Action: Try again later.

OGR messages

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 OGR0 through OGR0xx

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.

OGR004E NO MATCHING RECORDS FOUND IN THE LOG FILE

Explanation: No records which match the specified parameters were found in the Log file.

The specified log file is either the IOA Log file or the Simulation Log file. No executions were found in the file for the specified groups during the specified time range (and intervals).

Corrective Action: Check the specified group, time range and interval parameters. Correct if necessary, and run the report again.

Messages OGR300 through OGR3xx

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.

OGR391I OVERNIGHT EXECUTION REPORT STARTED

Explanation: This information message indicates that processing of the Overnight Execution Report has begun.

Corrective Action: No action is required.

OGR393I OVERNIGHT EXECUTION REPORT ENDED

Explanation: This information message indicates that processing of the Overnight Execution Report has ended.

Corrective Action: No action is required.

OGR394S MAXIMUM NUMBER OF INTERVALS EXCEEDED

Explanation: There are too many intervals for the report to be run.

Within the specified time range, job executions are checked periodically at the interval determined by the specified interval parameter. The total number of intervals in which a check is to be made depends on the length of the time range and the size of the interval. However, the maximum number of intervals may occur within a specified time range is 210 intervals.

The report is not run.

Corrective Action: Either decrease the allotted time in the time range, or increase the interval value, so that the total number of intervals does not exceed 210.

OPL messages

This group includes messages for the Control-O product.

Messages OPL300 through OPL3xx

This group includes messages for the Control-O product.

OPL341S OPERLOG NOT AVAILABLE UNDER MVS/ESA 5.2

Explanation: The user tried to access the MVS OPERLOG with a system level lower than MVS/ESA 5.2.

The system rejects the request and continues.

Corrective Action: Update the system to MVS/ESA 5.2 or higher.

OPL342S ERROR OPENING OPERLOG FILE

Explanation: The user tried to access the OPERLOG in a SYSPLEX environment. However, the OPERLOG could not be opened.

The system rejects the request and continues.

Corrective Action: Record the message and contact your system programmer.

OPL346S ABEND `abCode` INTERCEPTED WHILE PROCESSING THE OPERLOG

Explanation: The user tried to access the OPERLOG in a SYSPLEX environment but an abend was generated.

For information about abCode, see the IBM Abend Codes manual.

The system terminates the requested action.

Corrective Action: Take appropriate corrective action.

OPL347S ERROR RETURN CODE FROM A SYSTEM LOGGER REQUEST `rc`

Explanation: The user issued the OPER command in the OL screen to access the OPERLOG in a SYSPLEX environment. However, the request failed and the rc SYSTEM LOGGER return code was issued.

The system rejects the request.

Corrective Action: For information about the error, note the value of rc and refer to IBM LOGGER services (IXGxxx macros) in the Sysplex service manual.

OPL348S OPERLOG IS EMPTY

Explanation: The user issued the command OPER in the OL screen to access the OPERLOG in a SYSPLEX environment. In response, the system logger informed Control-O that the OPERLOG was empty.

The system rejects the request.

Corrective Action: For more information about the error, note the message and contact your system programmer.

OPL349S OPERLOG END OF FILE IS REACHED

Explanation: The user attempted to access the OPERLOG in a SYSPLEX environment and reached the end of the OPERLOG. However, no more data was available in the OPERLOG.

The system rejects the request.

Corrective Action: Reattempt access to the OPERLOG.

OSM messages

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

Messages OSM100 through OSM1xx

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

OSM150E `mediaName` - DYNAMIC ALLOCATION ERROR FOR DDNAME=SORTIN RC= `rc`, REASON CODE= `rsn`

Explanation: An error occurred while trying to allocate an OSS Extract Database file.

This error causes the dynamic allocation of the SORTIN DD statement to fail.

For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

The mediaName media is terminated.

Corrective Action: Use the return code (rc) and reason code (rsn) to determine the problem and correct it. If you cannot resolve the problem, record the DD statement, return code and reason code, and contact BMC Customer Support.

OSM151E `mediaName` - SORT OF OSS EXTRACT DATABASE FILE FAILED. RC=`rc`

Explanation: The internal sort of the OSS Extract Database file failed.

The mediaName media activates the regular sort program at the site. The system log should contain additional messages about specific errors.

The mediaName media is terminated.

Corrective Action: Check the system log for messages describing the error. Contact the system programmer for assistance, if needed. If the problem is not resolved, contact BMC Customer Support.

OSM152E `mediaName` - VOLSER `volser` NOT FOUND IN OSS EXTRACT DATABASE FILE

Explanation: An attempt was made to view a report but the mediaName media was not be able to find the volser volume serial number on which this report resides.

When media mediaName media detects a user request to view a report, it searches the OSS Extract Database to find the volume on which the requested report resides. The OSS Extract Database does not contain an entry for volume volser.

The user request is not executed.

Corrective Action: Check the OSS Extract Database and make any appropriate corrections. Contact the system programmer for assistance, if needed.

OSM153E `mediaName` - PLATTER `platterId` NOT FOUND FOR VOLSER `volser`

Explanation: The mediaName media was not be able to find the platterId for the volser volume on which this report resides.

When the mediaName media detects a user request to view a report, it searches the OSS Extract Database to find the volser and platter on which this report resides. The OSS Extract Database does not contain an entry for the required volser and platterId.

The user request is not executed.

Corrective Action: Check the OSS Extract Database and make appropriate corrections. Contact the system programmer for assistance, if needed.

OSM154E `mediaName` - INTERNAL ERROR RC= `rc`

Explanation: Media mediaName encountered an internal error.

The user request is not executed. Depending on internal error severity, one of the following actions occurs:

Media mediaName terminates. The 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 the system programmer for assistance, if needed. If the problem is not resolved, record the return code and contact BMC Customer Support.

PAS messages

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

Messages PAS0 through PAS0xx

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

PAS046S BLDL/LOAD FAILED FOR THE MODULE `modName`

Explanation: Loading of the modName module failed.

Possible causes are:

The IOA Load library is not in the load modules search list (STEPLIB + Linklist).
There is insufficient memory.
There is some other system-oriented reason, which may be found in the syslog.

Execution might stop.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

Messages PASF00 through PASFxx

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

PASF90I THE PASSWORD OF CONTROL- `x` IS AUTHORIZED

Explanation: This information message indicates that the password for Control-x has been authorized.

Corrective Action: No action is required.

PASF90S OPEN OF DDCARD `ddName` FAILED

Explanation: The ddName DD statement pointing to the password member failed to open.

Possible causes are:

The ddName DD statement is missing.
The file allocated to the ddName DD statement is not a sequential file nor a member in a PDS.

Authorization to access the product is denied.

Corrective Action: Correct the JCL statement for the procedure or the allocations for the CLIST.

PASF91S PASSWORD MEMBER TOO LARGE (DD `ddName`)

Explanation: The password member (or sequential data set) has too many lines.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Remove unnecessary lines from the member.

PASF91W Control- `x` IS NOT INSTALLED !

Explanation: Control-x has not been installed.

Corrective Action: No action is required.

PASF92S SYNTAX ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A syntax error was found in the password member. When this message is issued by the monitor, it is generally followed by message PASF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

PASF93S VALUE ERROR IN PASSWORD MEMBER (DD `ddName`)

Explanation: A field in the password member contains invalid data. When this message is issued by the monitor, it is generally followed by message PASF9DS, which describes the erroneous line in the member.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the text in the password member.

PASF94S PASSWORD INVALID, PLEASE RECHECK PASSWORD MEMBER (DD `ddName`)

Explanation: Data in the password member was not consistent with the specified password.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from BMC Customer Support. If it checks, contact the representative.

PASF95S PASSWORD FOR CONTROL- `x` IS ABOUT TO EXPIRE IN `n` DAYS

Explanation:Highlighted, unrollable message.

Password expiration period is about to end.

An expiration date is specified in the password member for the product.

Corrective Action: Contact BMC Customer Support for a new password.

PASF96S PASSWORD FOR CONTROL- `x` HAS EXPIRED

Explanation: Highlighted, unrollable message.

Password expiration period has ended.

An expiration date is specified in the password member for the product.

Authorization to access the product is denied.

Corrective Action: Contact BMC Customer Support for a new password.

PASF97S INTERNAL ERROR OCCURRED ON DD `ddName`, PLEASE NOTIFY THE IOA ADMINISTRATOR

Explanation: An internal error has occurred while analyzing the password member pointed to by the ddName DD statement.

Authorization to access the product is denied.

Corrective Action: Notify the IOA administrator.

PASF98S OBLIGATORY FIELD MISSING FROM PASSWORD MEMBER (DD `ddName`)

Explanation: An obligatory field is missing from the password member.

The ddName DD statement points to the password member. The PROD, START, CPUID, PASS, and TYPE fields should appear at least once in a password member. For Control-D/WebAccess Server, the CTD_PC_USERS field is also obligatory.

Authorization to access the product is denied.

Corrective Action: Check the contents of the password member against the text received from your INCONTROL administrator.

PASF9AS PASSWORD FOR CONTROL-`x` NOT DEFINED IN MEMBER (DD `ddName`)

Explanation: The member pointed to by the ddName DD statement does not contain the password for the appropriate product.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this product.

PASF9BS AUTHORIZATION PERIOD HAS NOT STARTED YET (DD `ddName`)

Explanation: The start date of the password has not yet arrived.

In this message, ddName is the identity of the DD statement that points to the password member. The START field contains the starting date of the password.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this period.

PASF9CS CPUID/MODEL NOT FOUND IN AUTHORIZED CPU LIST (DD `xxxxxxxx`)

Explanation: The current CPU is not defined in the CPU list.

In this message, ddName is the identity of the DD statement that points to the password member. Each entry in the CPU list in the password member contains the CPUID of the CPU and its model.

Authorization to access the product is denied.

Corrective Action: Check that the specified password member is the correct member for this CPU.

PASF9DS CARD = `text`

Explanation: This message supplies additional information for a previous error message.

This message may appear after message PASF92S or PASF93S which indicates an error has occurred in one of the lines of the password member. Message PASF9DS displays the erroneous line.

Corrective Action: See messages PASF92S or PASF93S.

PASF9ES PASSWORD DDCARD `ddName` POINTS TO A NON EXISTING MEMBER (ABEND S013-18)

Explanation: The ddName DD statement is allocated to a nonexisting member in a PDS file.

In this message, ddName is the identity of the DD statement that points to the password member.

Authorization to access the product is denied.

Corrective Action: Correct the name of the member in the DD statement or create a member with the specified name.

PASF9FS PASSWORD FOR CONTROL- `x` EXPIRED, TEMPORARY AUTHORIZATION GRANTED

Explanation: The password for Control-x has expired. Nonetheless, Control- x can be run on the current date.

Despite password expiration, Control-x can be run on the 28th, 29th, 30th, 31st, 1st, 2nd, and 3rd days of each month for special purposes.

Control- x processing continues.

Corrective Action: Contact BMC Customer Support to obtain password renewal.

PDA messages

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 PDA400 through PDA4xx

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.

PDA482S OPEN OF USER DATE CONTROL RECORD FAILED. DDNAME "DACHK"

Explanation: Opening of the file containing the User Dates Control record failed (the DACHK DD statement). This message is issued by the New Day procedure.

This is due to one of the following:

The DACHK DD statement is missing.
The data set (member) described by the DACHK DD statement does not exist.

The New Day procedure stops executing.

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

PDA483S OPEN OF IOA LOG FILE FAILED

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

This is due to one of the following:

Data set described by the DALOG DD statement is not the IOA Log file.
Data set described by the DALOG DD statement is the IOA Log file, but is of a different version or of a different IOA Installation. See the syslog of the job/TSO user for additional messages.

The New Day procedure stops executing.

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

PDA484I POST DAILY CHECKPOINT WRITTEN

Explanation: This information message indicates that Post-daily checkpoint was written.

Indicates that the New Day procedure ended normally.

Corrective Action: No action is required.

PLN messages

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 PLN0 through PLN0xx

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.

PLN020I THE MEMBER `memName` IS NOT SCHEDULED ACCORDING TO DATE-CRITERIA, AND WILL BE EXCLUDED

Explanation: This information message indicates that the following situation has occurred. The scheduling table member was scheduled with MINUMUM and PDS parameter specifications. The table is therefore not scheduled according to date and will not be taken into account by the CTMRPLN utility.

The CTMRPLN utility assists in planning scheduling according to date. Jobs whose scheduling does not depend on date are not relevant to this utility.

The table is ignored.

Corrective Action: No action is required.

PLN021E ACCESS OR ANALYZING OF CALENDAR `calName` FOR MEMNAME `memName` FAILED

Explanation: Either the CTMRPLN utility could not access calendar calName, or the format of the calendar member is invalid.

The job scheduling definition included a reference to a calendar member in the DCAL or WCAL or CONFCAL parameter. However, the calendar member could not be accessed, or it has an invalid format.

The job scheduling definition is ignored in the plan.

Corrective Action: Please check that CTMRPLN has access authority to the calendar library. If there is access authority, try to access the calendar by means of the IOA online interface and check its validity. If the format is invalid, define a new calendar.

PMM messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages PMM300 through PMM3xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PMM350I PRINTING MISSIONS MANAGER STARTED

Explanation: This information message indicates that the Control-D monitor internal Printing Missions Manager task has started.

Normal message when a Printing Missions Manager task is started.

Corrective Action: No action is required.

PMM351S INCORRECT NUMBER OF EXPECTED SUBTASKS

Explanation: Control-D monitor internal Printing Missions Manager task has determined that one of the print tasks under its control has abended.

The Control-D monitor is shut down.

Corrective Action: Contact BMC Customer Support.

PMM352S GETMAIN ERROR FOR PRINTING MISSIONS MANAGER INTERNAL WORK VECTOR

Explanation: Internal error.

An internal error has occurred in the Control-D monitor internal Printing Missions Manager task.

The Control-D monitor is shut down.

Corrective Action: Contact BMC Customer Support.

PMM354S INTERNAL ERROR - CS FAILED IN ADD OF PRINT MISSIONS MANAGER VECTOR

Explanation: Internal error.

An internal error has occurred in the Control-D monitor internal Printing Missions Manager task.

The Control-D monitor is shut down.

Corrective Action: Contact BMC Customer Support.

PMM355S INTERNAL ERROR - CS FAILED IN MOVE OF PRINT MISSIONS MANAGER VECTOR

Explanation: Internal error.

An internal error has occurred in the Control-D monitor internal Printing Missions Manager task.

The Control-D monitor is shut down.

Corrective Action: Contact BMC Customer Support.

PMM357S INTERNAL ERROR - ATTACH FOR CTDPMS FAILED

Explanation: Internal error.

An internal error has occurred in the Control-D monitor internal Printing Missions Manager task.

The Control-D monitor is shut down.

Corrective Action: Contact BMC Customer Support.

PMM358S INTERNAL ERROR - PRINT MISSION ALREADY POSTED

Explanation: An internal error has occurred in the Control-D monitor internal Printing Missions Manager task.

The Control-D monitor is shut down.

Corrective Action: Contact BMC Customer Support.

PMM359S INTERNAL ERROR - WAIT LIST HAS BEEN EXCEEDED

Explanation: An internal error has occurred in a Control-D monitor internal Printing Missions Manager task.

The Control-D monitor shuts down.

Corrective Action: Contact your INCONTROL representative.

PMM360S ONE OF THE PRINT MISSION SUBTASKS HAS ABENDED

Explanation: Control-D monitor internal Printing Missions Manager task has determined that one of the print tasks under its control has abended.

The Control-D monitor is shut down.

Corrective Action: Contact BMC Customer Support.

PMM361S INTERNAL ERROR - PMV

Explanation: Internal error in the operation of the Control-D monitor.

The Control-D monitor is shut down.

Corrective Action: Call BMC Customer Support for assistance. Keep the dump.

PMM362W MAX NUMBER OF LOGICAL PRINTERS IS REACHED. ONLY FIRST 100 ARE USED

Explanation: During the processing of a PRINT mission, the maximum number of logical print monitors has been reached. This occurs in either of the following circumstances:

The number of logical printers defined in a PRINT mission exceeds 100.
No printer is defined in the PRINT mission itself, but the number of logical printers defined in CTDPARM exceeds 100.

The PRINT mission continues using the first 100 logical printers.

Corrective Action: Correct the PRINT mission definition.

PMM363I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message indicates that Control-D monitor has shut down.

Shut down of Control-D internal Printing Missions Manager task by request of the Control-D main task.

The Control-D monitor is shut down.

Corrective Action: No action is required.

PMM364I WAITING FOR ACTIVE PRINTING MISSION(S) IN ORDER TO SHUT DOWN

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-D monitor was shut down, but is waiting for print tasks to finish in order to complete the shut down.

The Control-D internal Printing Missions Manager task received a request from the Control-D monitor to shut down. However, one or more of the print tasks under the control of the Printing Missions Manager is still printing. As soon as all the print tasks are completed, the Printing Missions Manager task will shut itself down.

Corrective Action: No action is required.

PMM365E PRINTING MISSION ENDED NOT OK

Explanation: The Control-D internal Printing Missions Manager task has determined that the Printing Mission ended NOTOK.

This is a general message which is produced when a Printing Mission finished executing NOTOK. The IOA Log should contain prior messages detailing the reasons.

Corrective Action: No action is required.

PMM397S INTERNAL ERROR - PRINTER IS BUSY

Explanation: Internal error in the operation of the Control-D monitor.

The Control-D monitor will shut down.

Corrective Action: Call BMC Customer Support for assistance. Keep the dump.

PMM398I PRINTING MISSION ENDED OK

Explanation: This information message indicates that the Printing Mission ended OK.

Corrective Action: No action is required.

PMM399I PRINTING MISSION SUSPENDED - PUT ON HOLD

Explanation: This information message indicates that a HOLD request, issued in the Active Missions screen, has been accepted by Control-D.

The status of the Printing Mission is changed from REQUESTED HELD to HOLD.

The Printing Mission will stop printing at the end of the current report and will enter a HELD status.

Corrective Action: In order to resume printing of the Printing Mission remove it from the HOLD status by issuing the F (FREE) command in the Active screen. The mission will resume printing after the last printed report.

Messages PMM400 through PMM4xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PMM400E HOLD NOT PERFORMED - ERROR IN CTDCIO

Explanation: An internal error has occurred in the Control-D monitor internal Printing Missions Manager task. A HOLD request, issued in the Active Missions screen, has been rejected by the CTDCIO internal Control-D module.

The status of the Printing Mission remains unchanged.

Corrective Action: Contact BMC Customer Support. There should be additional error messages on the IOA Log and system log.

PMS messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages PMS400 through PMS4xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PMS401I PRINTING MISSION STARTED

Explanation: This information message is the normal start message of a Printing Mission.

Corrective Action: No action is required.

PMS402I PRINTING MISSION ENDED

Explanation: This information message is the normal end message of a Printing Mission.

Corrective Action: No action is required.

PMS403E PRINT MISSION HAS NOT STARTED DURING APPROPRIATE TIME FRAME.

Explanation:Highlighted, unrollable message.

The Control-D monitor issued a MODIFY command for a Printing monitor to start processing a Printing Mission. The Printing monitor did not answer during the time frame defined by optional wish WD2344 (whose default is five minutes).

The problem can occur because the Printing monitor has a low priority and the computer is heavily loaded. Therefore, the Printing monitor does not get control during the time allowed for a response.

The Control-D monitor terminates the mission NOT-OK.

Corrective Action: Assign a higher priority and/or change the performance group of the Printing monitor to provide better response time from this address space. In case of a batch printing mission, make sure that enough initiators are available for handling batch printing jobs. If this is impossible or undesirable, define a higher value for the time frame defined by optional wish WD2344 in the IOADFLTS member in the DOC library or specify an appropriate time-out in the Printing Mission Definition screen (screen M.S).

PMS404I SHUTDOWN IN PROGRESS

Explanation: This information message indicates that the Control-D monitor has requested all the subtasks under its control to shut down.

The IOA Log should contain additional messages concerning the reason for the shutdown.

Control-D monitor shuts down.

Corrective Action: No action is required.

PMS405I NO REPORTS ARE WAITING TO BE PRINTED BY THIS PRINTING MISSION

Explanation: This information message indicates that a Printing Mission has executed. However, there are no reports waiting to be printed by the mission.

No reports were found in the Active User Report List file to which all the following apply:

They were decollated by a decollating mission which specified this Printing Mission name in its DO PRINT parameter.
They belong to the users specified in the Printing Mission’s INCLUDE USER parameters.
They are in WAIT (RE)PRINT status.
The decollating mission which has processed them is in the Active Missions file and is not HELD.
They are not currently selected by another Printing Mission.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: No action is required.

PMS406E RECIPIENT `recipName` IGNORED. RECIPIENT NOT FOUND IN THE TREE

Explanation: The recipient recipName specified in the Printing Mission’s INCLUDE USER parameter is not found in the Recipient Tree; or the Printing Mission tried to select a user (from the Active User Report file) who is not in the tree.

No reports will be printed for this recipient.

Corrective Action: Add the recipient to the Recipient Tree or delete the recipient from the INCLUDE USER parameter of the Printing Mission.

PMS408E PRINTING PLAN FILE ALLOCATION ERROR. RC= `rc`, ERROR= `errCode`

Explanation: An error occurred in allocating a Print Plan file for this Printing Mission.

One of the following probably occurred during dynamic allocation of the Print Plan file:

The Printing Mission was restarted, but the Print Plan file was manually erased.
An attempt to allocate a new Print Plan file failed, for a reason such as lack of space, security.
An attempt to delete a Print Plan file failed.

The expressions RC= rc and ERROR= error_code indicate the return and reason codes from the dynamic allocation. For an explanation of these codes, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

This Printing Mission will not print any reports and will end with a NOTOK status.

Corrective Action: Check the IOA Log, the Control-D monitor syslog, and system log for additional clarification messages.

PMS409E PRINTING PLAN FILE CRITICAL ALLOCATION ERROR

Explanation: Internal error. In attempting to allocate a Print Plan file, an unknown return code was received from the CTDALC Control-D utility module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS40AW SOME REPORTS ARE LOCKED BY ANOTHER PRINT MISSION

Explanation: The current print mission did not place one or more reports in the print plan although these reports have status WAIT PRINT and should be printed by this mission.

Each print mission checks each report to be included into the print plan against print plans of other print missions (excluding missions ended OK/NOTOK). If this report is included into another print plan, the current mission will not print it in order to avoid duplicate printouts.

The print mission continues processing.

Corrective Action: If the skipped reports will be printed by another mission, no action is needed. If these reports should be printed by the current mission, find the other active missions whose print plan includes these reports. Delete the other missions or allow them to terminate.

PMS40BW SOME REPORTS ARE SUPPRESSED BY USER EXIT 20

Explanation: The printing mission did not include some reports in the print plan because user exit CTDX020 suppressed them.

Function PUT is used to call user exit CTDX020. This exit creates the print plan for each report that is eligible for printing. If this exit returns a return code of 4, the report is not included in the print plan.

The printing mission continues.

Corrective Action: If the suppressed report should have been added to the print plan, determine why the report was suppressed.

PMS40CW SOME REPORTS ARE NOT SET FOR THE CURRENT PRINTING MISSION

Explanation: The printing mission found some reports originally set for the current mission. However, they were later reset for another mission.

This can occur if the user manually changes the printing mission name in the report entry in the U screen.

The printing mission continues normal work flow. Invalid reports are skipped.

Corrective Action: No action is required.

PMS40DW SOME REPORTS ARE NOT SET FOR CONTROL-D/PC

Explanation: DEST=CTDPC was specified for the printing mission. However, some reports were found to be ineligible for this mission.

The reports were not eligible because they did not specify either DEST=CTDPC[PRT] or a corresponding recipient authorized to use Control-D/PC.

When DEST=CTDPC is specified for a printing mission, all reports selected by this mission must specify DEST=CTDPC or DEST=CTDPCPRT. Recipients for these reports must be authorized to use Control-D/PC by means of the recipient tree.

The printing mission continues normal work flow. Reports that are not eligible are skipped.

Corrective Action: For reports to be transferred to Control-D/PC, do the following:

Specify DEST=CTDPC or DEST=CTDPCPRT during decollation. See the section on specifying report destinations in the Control-D and Control-V User Guide.
Verify that report recipients are authorized to use Control-D/PC.

PMS40EW INDEX REPORT IS NOT SET FOR STORE=YES MISSION

Explanation: A printing mission specifying STORE=YES did not select Control-V index report setting for Deferred printing. Printing missions specifying STORE=YES select only whole reports. Control-V index reports are not selected by a printing mission with parameter STORE=YES.

Corrective Action: Do not specify a name of a printing mission when STORE=YES is specified in the PRINT statement in DO INDEX.

PMS40GW REPARTITION COPY STAGE IS IN PROCCESS

Explanation: This warning message indicates that the repartition utility CTDUFMPR is running with the COPY function when print mission tries to print a migrated report. The print mission continues normal work flow but the migrated reports are not printed and remain in WAIT PRINT status.

Corrective Action: Submit the CTDBLXRP utility after the CTDUFMPR repartition utility with the COPY function ends. Then rerun the Print mission.

PMS40HW CTDBLXRP WAS NOT SUBMITTED AFTER REPARTITION COPY STAGE ENDED

Explanation: This warning message is issued when a print mission printing migrated reports is started after the CTDUFMPR with COPY function is ended, but the CTDBLXRP utility was not submitted previously. The print mission continues normal work flow but the migrated reports are not printed and remain in WAIT PRINT status.

Corrective Action: Submit the CTDBLXRP utility and then rerun the print mission.

PMS40IW MIGRATED REPORTS ARE NOT PRINTED

Explanation: This warning message follows the PMS40GW and PMS40HW messages and indicates that the migrated reports are not printed.

Corrective Action: Perform actions described for the previous message.

PMS410E OPEN OF PRINTING PLAN FILE FAILED

Explanation: Internal error. The open of the Print Plan file failed.

The dynamic allocation of the Print Plan file was successful, but the open of the file failed.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS411E PRINTING PLAN FILE - WRITE ERROR

Explanation: Internal error. An error occurred in writing to the Print Plan file.

The dynamic allocation and open of the Print Plan file were successful, but an error occurred while writing to the file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS412E INTERNAL ERROR - INVALID RC FROM CTDWTF

Explanation: Internal error. Invalid return code from the internal program CTDWTF while writing the Print Plan file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS413E SYSOUT ALLOCATION ERROR (INVALID DEST) PRINTING STOPPED

Explanation: The DEST (destination) parameter for this Printing Mission is incorrect (meaning, not recognized by MVS/JES).

The DEST parameter specifies the JES destination for printing the report. See also remarks about JES3 in the PRINTER parameter in the Control-D and Control-V User Guide, and in “Set Control-D Installation Parameters” in the Control-D chapter in the INCONTROL for z/OS Installation Guide. If this parameter is omitted, the DEST is assumed to be the main computer printer. Specify the DEST parameter in one of the following ways:

User Report List screen - refer to “User Reports - Report List” in the Control-D and Control-V User Guide.
Report Decollating Definition screen - refer to “Report Decollating Parameters” in the Control-D and Control-V User Guide. Additional details are in Chapter 3, “Report Decollating Mission Parameters”.
Printing Mission Definition screen - refer to “Specific Mission Parameters, PRINTER (DEST)” in the Control-D and Control-V User Guide.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Correct the DEST parameter, and rerun the Printing Mission.

PMS414E PRINTING PLAN FILE - CANNOT BE OPENED BY THE PRINTERS CONTROL MONITOR

Explanation: Internal error. The Printers Control monitor could not open the Print Plan file.

The Print Plan file was successfully created by the Control-D monitor, and passed the name of the Print Plan file to the Printers Control monitor. However, the Printers Control monitor was unable to open the file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS415E OPEN OF SYSOUT FOR PRINT FAILED

Explanation: Internal error. The Printers Control monitor could not open the sysout file for printing.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Look for additional messages on the system log. If you cannot find the problem, have your system programmer call BMC Customer Support for assistance.

PMS416E PRINT - UNKNOWN INTERNAL ERROR

Explanation: Internal error in Printers Control monitor. An unknown return code was received from the CTDPRT module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS417E MEMORY SHORTAGE OR INTERNAL ERROR MAY CAUSE DUPLICATE PRINT OF SOME REPORTS

Explanation: An error occurred in main memory during the building of the Print Plan List.

The Print Plan List is checked during the building of a Print Plan file to verify that the same report is not included for printing by other Printing Missions that may be processing in parallel.

The Printing Mission continues processing; however, another Printing Mission may possibly process the same reports.

Corrective Action: Enlarge the REGION size for the Control-D monitor. If this does not solve the problem, contact BMC Customer Support.

PMS418S PRINT - INTERNAL ERROR WHILE READING ACTIVE REPORTS FILE INDEX

Explanation: Internal error in the CTDCLS module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS419S INTERNAL ERROR WHILE PREPARING USER LIST FOR THE PRINT PLAN

Explanation: Internal error in the CTDPM2 module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS420S INSUFFICIENT STORAGE TO BUILD PRINTING PLAN

Explanation: There is insufficient storage to build the Print Plan file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Increase the REGION size of the Control-D monitor, and rerun this Printing Mission.

PMS421S PRINT - INTERNAL ERROR IN CTDPM1

Explanation: Internal error in the CTDPM1 module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS422I START COMMAND HAS BEEN ISSUED FOR PROCEDURE `procName`, COM `number`

Explanation: This information message indicates that a batch print mission has been started as a started task.

A batch print mission runs as a started task when its skeleton member does not contain a JCL statement (starts with //) but an operator command.

Corrective Action: No action is required.

PMS423S PRINT - INTERNAL ERROR IN CTDCOL

Explanation: Internal error in the CTDCOL module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS424S ERROR WHILE READING THE ACTIVE USER FILE FOR PRINTING PARAMETERS

Explanation: An error occurred while accessing the Active User file during a print mission run.

Message CTD908S preceding this message contains the reason code of the error and other information.

The current print mission terminates NOT-OK.

Corrective Action: Using the information in message CTD908S, correct the problem, and reprint the corresponding reports.

PMS425S SYSOUT ALLOCATION ERROR - PRINTING STOPPED

Explanation: Internal error in the Printers Control monitor.

The CTDSYS module was unable to allocate a sysout file.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Look for additional messages on the System Log. If you cannot find the problem, have your system programmer call BMC Customer Support for assistance.

PMS426E OPEN OF DAINTRDR FAILED

Explanation: An error occurred during the dynamic allocation of the INTRDR internal reader while a batch printing mission was starting a batch print job as a started task.

No reports are printed by this batch printing mission. The mission ends with the status NOT OK.

Corrective Action: Examine the system log for further error messages that may help identify the problem. If the problem persists, ask your system programmer to contact BMC Customer Support.

PMS427S PRINTING PLAN FILE CANNOT BE ALLOCATED - NO SPACE ON DISK

Explanation: There is no disk space for allocating the Print Plan file.

The Installation Parameters WRKUNIT and WRKVOL, described in “Set Control-D Installation Parameters” in the Control-D chapter of the INCONTROL for z/OS Installation Guide, specify the unit and volume serial number for the printing plan file. The WRKVOL disk does not have disk space for allocating the printing plan file.

This Printing Mission does not print any reports, and ends with a NOTOK status.

Corrective Action:

Delete unneeded files from the WRKVOL disk, or change the WRKUNIT/WRKVOL parameters on CTDPARM.
Bring Control-D down.
Start the Control-D monitor.
The Printing Mission can then be rerun.

PMS428S INSUFFICIENT STORAGE FOR INCLUDE/EXCLUDE LIST

Explanation: There is insufficient storage for Control-D to handle all the INCLUDE/EXCLUDE USER statements in the Printing Missions Definition.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action:

Remove some INCLUDE/EXCLUDE USER statements from this Printing Mission Definition and create new Printing Missions to put them in, or (preferably)
Increase the REGION size of the Control-D monitor.
Bring Control-D down, then up.
The Printing Mission can then be rerun.

PMS429S ABEND IN THE PRINTERS CONTROL MONITOR

Explanation: Print mission failed with an abend. A detailed description of the failure appears in the preceding message.

The current print mission ends NOT-OK.

Corrective Action: Check the dump and any relevant messages in the system log. For an explanation of the abend code, refer to the relevant IBM manual. Correct the problem and restart the problematic PRINT mission.

PMS42AE PRINT JOB IS NOT SUBMITTED DUE TO ERROR

Explanation: Print mission failed to submit print job.

A detailed description of the failure appears in the preceding message.

The current print mission ends NOT-OK

Corrective Action: Proceed according to the description of the failure in the preceding message.

PMS42BE ERROR READING SKELETON. CTMMEM RC= `rc`

Explanation: Print mission skeleton cannot be read from the SKL library.

The current print mission ends NOT-OK.

Corrective Action: Proceed according to the CTMMEM return code identified in the message. A description of the CTMMEM return codes can be found in the DOCIMEM member in the IOA DOC library.

Rerun the print mission.

PMS42CE MESSAGE=MEMBER `memName` IS NOT FOUND IN THE SKELETON LIBRARY

Explanation: The SKELETON parameter specified in the Print mission definition does not exist in the SKL library.

The current print mission ends NOT-OK.

Corrective Action: Correct the SKELETON parameter in the print mission definition, or if it is correct, add it to the SKL library. Rerun the print mission.

PMS42DE CTDX009 REJECTED PRINT JOB SUBMISSION

Explanation: Exit 9 (CTDX009) rejected submitting a print job.

The current print mission ends NOT-OK.

Corrective Action: If it is required that the job be submitted, check Exit 9 for a return code of 8 and modify the exit accordingly. Rerun the print mission.

PMS42EI PRINT JOB `name` / `jobId` HAS BEEN SUBMITTED

Explanation: This information message indicates that the print job name has been successfully submitted.

Corrective Action: No action is required.

PMS42FE PRINT MISSION CANNOT BE STARTED. PRTMON#=0 IS DEFINED IN CTDPARM

Explanation: No print monitors are defined in CTDPARM.

The PRTMON# field must be defined in CTDPARM so that a print mission can be executed as a subtask of the print monitor.

The current print mission terminates NOT-OK.

Corrective Action: Specify PRTMON# parameter in CTDPARM, or define the SKELETON field in the print mission definition to run the mission as a batch job.

PMS430S PRINT - INTERNAL ERROR IN CTDCIO

Explanation: An error occurred in the CTDCIO Control-D communication file I/O module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Bring down Control-D, then follow these steps:

Check the DACOM DD statement in the Control-D monitor and Printers Control monitor JCL, and correct the JCL if required.
Check the COMSIZE Installation Parameter. For more information, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.
If this parameter is modified, then the CTDFRCOM Control-D utility will have to be run in order to create a new communications file.
Bring up Control-D, and rerun this Printing Mission.

If following the steps specified above does not solve the problem, have your system programmer call BMC Customer Support for assistance.

PMS431S INTERNAL SYNCHRONIZATION ERROR - SHUTTING DOWN

Explanation: An internal error has occurred in the Printers Control monitor.

An error occurred in the CTDPMS module--the synchronization with the Printers Control monitor failed.

Control-D monitor shuts down.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS432I NOTHING LEFT TO PRINT (THERE ARE USERS, BUT COP=0 OR REPORTS DELETED)

Explanation: This information message indicates that there are no reports for this Printing Mission to print.

There are a few possibilities:

All the SYSDATA entries to be printed were deleted.
All the CDAM files to be printed were deleted.
The copy count of all reports to be printed was set to 0 in the Active User Reports file.
The relevant decollation entries in the Active Missions file were deleted or are in HOLD status.

The Printing Mission will not print any reports, and will end up with a NOTOK status.

Corrective Action: Change the copy count to a value other then zero and/or free the Active Missions file report entries and/or rerun the Report decollating mission if the reports were accidentally deleted. The Printing Mission can then be rerun.

PMS433S ALLOC OF `dd_stmt` FAILED ON `rsn`

Explanation: An internal error has occurred in the Control-D monitor.

An error occurred in the CTDPSR utility module that sorts the printing plan file. The dynamic allocation of dd_stmt failed because of the reason identified in the message.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS434S FREE OF `dd_stmt` FAILED ON `rsn`

Explanation: An internal error has occurred in the Control-D monitor.

An error occurred in the CTDPSR utility module that sorts the printing plan file. The dynamic allocation and read/write to dd_stmt was successful. However, the attempt to free dd_stmt failed because of the reason identified in the message.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

PMS435S SORT OF BUNDLE FAILED. RC= `rc`

Explanation: An internal error has occurred in the Control-D monitor.

An error occurred in the CTDPSR utility module that sorts the printing plan file. The installation sort routine returned a condition code of rc to the CTDPSR module.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Check the system log and the Control-D monitor sysout in order to determine why the installation sort routine returned a condition code of rc. RC is the SORT RC, so check it in the SORT manual. If you cannot resolve the problem, have your system programmer call BMC Customer Support for assistance.

PMS437E SORT OF BUNDLE FAILED. PRINTING MISSION ENDED NOTOK

Explanation: The sort of the Printing Plan file failed.

Corrective Action: Check the IOA Log for additional clarification messages.

PMS438E RESTART OF PRINTING MISSION FAILED. COMMUNICATION FILE WAS FORMATTED

Explanation: Restart of Printing Mission failed.

The Control-D Communication file was formatted, making automatic restart impossible.

This Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Rerun the Printing Mission without rebuilding the Printing Plan file.

PMS439I ONLY (`number`) FREE ENTRIES ARE LEFT ON THE COMMUNICATION FILE - PLEASE INCREASE ITS SIZE

Explanation: The Control-D Communication file is almost full.

This is an informational message only.

The printing of the reports will continue.

Corrective Action: At the earliest possible time, bring down Control-D, then follow these steps:

Increase the COMSIZE Installation Parameter. For more information, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.
Run the CTDFRCOM utility in order to create a new communication file.
Bring up Control-D.

PMS43AE NO FREE RECORDS IN COM FILE. PRINT MISSION TERMINATES ABNORMALLY

Explanation: The current print mission cannot obtain a free record in the communications file.

Each print mission requires one record in the COM file for communicating between the Control-D monitor and the print task. A free record is obtained before the print task is started released when it ends.

The print mission terminates NOTOK.

Corrective Action: Increase the size of the COM file by increasing the value of the COMSIZE parameter in CTDPARM. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 2, Control-D Dataset Parameters.
Increase the size of the COMSIZE parameter.
Return to the Minor Steps Selection screen, and select Minor Step 3, Save Parameters into Product Libraries.
Select Minor Step 5, Format the Communication File.

You can now rerun the print mission.

PMS43BE ERROR STORING REPORTS IN DATASETS

Explanation: Control-D detected an error while processing a printing mission with the STORE parameter set to YES.

This message is usually preceded by other messages that describe the problem. These other messages may be issued to the IOA Log file and/or the job log of the Control-D Printers monitor.

The printing mission ends with a status of NOTOK and a reason code of 56.

Corrective Action: Check the IOA Log file for other printing mission errors. Check the job log in the Control-D Printers monitor. If you cannot resolve the problem, call BMC Customer Support.

PMS440I MISSION RESTARTED. PRINTING WILL START FROM NEXT REPORT

Explanation: A stopped Printing Mission has been restarted

The user has previously put this Printing Mission on HOLD (while printing), and has now FREEd this mission.

Printing will start again from the next report.

Corrective Action: No action is required.

PMS441I MISSION RESTARTED (FROM START OF PRINT PLAN)

Explanation: This information message indicates that a stopped Printing Mission was restarted using the printing plan built during the previous run of the mission

Corrective Action: No action is required.

PMS442I PRINTING MISSION RESTARTED

Explanation: Normal message when a stopped Printing Mission has been restarted.

The user had previously put this Printing Mission on HOLD (while printing), and has now freed this mission.

The printing of the reports continues.

Corrective Action: No action is required.

PMS443E SOME REPORTS WERE NOT PRINTED

Explanation: The print mission processed all the reports in the print plan, but some of them were not successfully printed.

Detailed messages appear during this print mission execution.

The problematic reports are marked as NOT-PRINTED in the Active User File.

Corrective Action:

Correct the cause of the problem that prevented the printing of the reports, using the messages that appear during the execution of the print mission.
Reprint the reports by ordering Deferred Print in the User Reports screen (U Screen).
Rerun the print mission with a rebuild of the print plan.

PMS443S INSUFFICIENT STORAGE TO LOAD PRINT PLAN MODULE

Explanation: There is insufficient storage to load the CTDPLN print plan module.

The Printing Mission will not print any reports, and will end with a NOTOK status.

Corrective Action: Increase the REGION size for the Control-D monitor.

PMS444S DELIVERY ERROR - PRINTING STOPPED

Explanation: Delivery error in the Printers Control monitor.

An error was encountered while attempting to connect to the Control-D/Delivery Server. Printing to the CTDS destination failed, because the Control-D printing monitor did not manage to establish a connection to the Control-D/Delivery Server.

This Printing Mission will not continue distribution reports and will end with status NOTOK.

Corrective Action: Look for additional messages on the System and IOA Logs. Fix the problem and restart the PRINT mission.

Messages PMS700 through PMS7xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PMS79BI THE SPECIFIED PRINTER MONITOR DOES NOT EXIST. PARAMETER "MONITOR" IS IGNORED

Explanation: This information message indicates that an executing Printing Mission’s MONITOR parameter is set to more than the maximum number of existing Printing monitor address spaces. The invalid parameter specifies a Printing monitor address space that does not exist.

The MONITOR Printing Mission parameter specifies the number of the Control-D Printing monitor to which the mission will be directed for printing.

The Printing Mission’s MONITOR parameter is ignored. Control-D will direct the Printing Mission to the next available Printing monitor.

Corrective Action: Change the Printing Mission MONITOR parameter to a value not exceeding the number of available Printing monitors and save the Printing Mission Definition. If necessary, reorder the Printing Mission.

PTS messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages PTS900 through PTS9xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PTS990I PRINTING MISSION `mission_nam` STARTED PRINTING CATEGORY `category_num`

Explanation: This information message indicates that the Control-D Printers Control monitor started printing for mission mission_nam.

Corrective Action: No action is required.

PTS991I PRINTING MISSION `mission_nam` FINISHED PRINTING CATEGORY `category_num`

Explanation: This information message indicates that the Control-D Printers Control monitor completed printing mission mission_nam successfully.

Corrective Action: No action is required.

PTS992S DEST `dest` in FOR USER `user` IS INVALID - PRINTING ON MAIN PRINTER

Explanation: A dynamic allocation error for a sysout data set was encountered during Printing Mission execution due to an invalid destination in the Active List screen.

Invalid destination may have been specified in the Recipient Tree or in the decollating mission Definition.

The Printing Mission attempts to allocate a sysout file with a default destination (from the Printing Mission definition or from the logical printer definition in CTDPARM). If this attempt fails, the Printing Mission terminates with a status of NOTOK.

Corrective Action: Find the source of the invalid destination and correct it.

PTS993E ERROR IN CTDCIO FUNCTION `func` RC `rc` - PRINTING STOPPED

Explanation: Internal error.

An internal error occurred in the CTDCIO internal module. The error occurred within the Control-D Printers Control monitor.

The printing for this mission will stop. The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the values of FUNCTION and RC.

PTS994E ERROR IN CTDRSV FUNCTION `func` RC `rc` - PRINTING STOPPED

Explanation: Internal error.

An internal error occurred in the CTDRSV internal module. The error occurred within the Control-D Printers Control monitor.

The printing for this mission will stop. The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the values of FUNCTION and RC.

PTS995E ERROR IN CTDALC RC `rc` S99RC `s99rc` FUNCTION `func` - PRINTING STOPPED

Explanation: Internal error. The allocation of the PLAN file failed.

An internal error occurred in the CTDALC internal module. The error occurred within the Control-D Printers Control monitor.

The printing for this mission will stop. The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the values of RC, S99RC, and FUNCTION.

PTS996I PRINTING ENDED. INTERNAL RC `rc`

Explanation: The printing for this mission has finished.

This is a general message when the printing for a mission finished. If rc is not 0, the IOA Log should contain prior messages detailing the reasons.

Corrective Action: No action is required.

PTS997E ERROR IN UPDATE OF PRINTED USERS, STATUS OF USER REPORTS MAY BE INVALID

Explanation: Internal error.

After printing a bundle, Control-D updates the status of all printed user reports in the Active User Report List file from WAIT PRINT to PRINTED. This message is produced if an error occurs in this update process.

The status of this Printing Mission is changed to NOTOK. All the reports are printed, but the entries in the Active Report List file have not been updated. This could result in duplicate printing.

Corrective Action: Look for VSAM related messages on the system log or on the syslog of the Control-D monitor. Contact BMC Customer Support.

PTS998E ALLOC FAILED FOR `fileName` - FILE WAS NOT FOUND

Explanation: Internal error.

The Control-D Printers Control monitor was unable to dynamically allocate file fileName.

The status of this Printing Mission is changed to NOTOK.

Corrective Action: Contact BMC Customer Support. Please provide the value of file.

PTS999E ERROR READING COMPRESSED DSN. RC= `rc`

Explanation: An error occurred while attempting to read a compressed data set.

In the process of printing a report, an error occurred while attempting to read a compressed data set.

The report is not printed. The status of the Printing Mission will be set to NOTOK.

Corrective Action: Please notify the INCONTROL administrator. Additional messages are present on the system log.

Messages PTSB00 through PTSBxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PTSB01S SYSOUT ALLOCATION FAILED, RC= `rc`, ERROR= `errCode`

Explanation: Dynamic allocation of a sysout during a Printing Mission failed.

RC and error codes are the standard system return codes returned when dynamic allocation of a sysout chunk occurs.

The Printing Mission stops printing and ends NOTOK.

Corrective Action: For information regarding the diagnostics of dynamic allocation error codes, see to the IBM manual MVS Programming: Authorized Assembler Services Guide.

PTSB02E CANNOT PRINT WITH MIXED AFP PARAMETERS WHILE CHUNKSIZE IS SET TO ZERO OR ONE

Explanation: The PAGEDEF and/or FORMDEF printing parameters were specified for reports which are printed with a Printing Mission having a CHUNKSIZE of 0 or 1.

The PAGEDEF and/or FORMDEF printing parameters can only be used in a bundle that uses the chunking mechanism. When CHUNKSIZE is specified with a value of 0 or 1, the chunking mechanism is not active.

Printing continues without processing the PAGEDEF and FORMDEF printing parameters.

Corrective Action: To print reports that require the special printing parameters PAGEDEF and FORMDEF, either change the CHUNKSIZE parameter in the Printing Mission definition to a value other than 0 or 1, or use a different Printing Mission which uses the chunking mechanism.

PTSB03E PRINTING MISSION `mission_nam` FAILED WHILE TRYING TO LOAD PAGEDEF `pagedef` OR FORMDEF `formdef`. DEFAULTS ARE USED INSTEAD

Explanation: An error was encountered while trying to read a PAGEDEF or FORMDEF value from the corresponding library.

Either the PAGEDEF or FORMDEF specified does not exist in the libraries defined for Control-D, or the CHUNKSIZE parameter was specified as 0 or 1. The PAGEDEF and/or FORMDEF printing parameters must print in a bundle using the chunking mechanism. When CHUNKSIZE is specified with a value of 0 or 1, the chunking mechanism is not active.

Printing continues without processing the PAGEDEF and FORMDEF printing parameters.

PTSB04E THERE IS NO PC INFORMATION IN THE TREE FOR USER `user`

Explanation: No PC information was found for the specified user during the process of building PC files.

User PC information must be defined in the Control-D Recipient Tree. If a report was assigned a destination of CTDPC but there is no PC information in the Recipient Tree for this user, it cannot be routed to the PC.

The report is not printed. Processing continues.

Corrective Action: Either define the user PC information in the Control-D Recipient Tree, or do not route the report to the PC.

PTSB05E CTDPC DEST WAS IGNORED FOR USER `user` (NO PC INFO)

Explanation: Destination CTDPC was specified for the user. The report should be transferred to the PC, but the user definition in the Recipient Tree does not contain PC parameters.

Only a user with PC parameters specified in the tree can receive reports on the PC.

The report will be routed to a mainframe printer instead of a PC.

Corrective Action: Define PC parameters for the user. The user must be authorized to access the CTDPC component.

PTSB06E OUTGRP INFORMATION IS UNAVAILABLE

Explanation:Highlighted, unrollable message.

The OUTGRP parameter is specified in CTDPARM, but the function cannot be performed.

An attempt to get the GROUPID parameter failed due to one of the following:

The OUTGROUP OUTPUT statement was not specified in the CTDPRINT procedure.
The corresponding control blocks cannot be found in the current release of MVS.

A special snap is sent to the DADUMP DD name.

Corrective Action: Check that the OUTGROUP OUTPUT statement is specified in the CTDPRINT procedure. If the error persists, contact your INCONTROL administrator and supply the snaps.

PTSB07E OUTGRP COULD NOT BE SET

Explanation:Highlighted, unrollable message.

The GROUPID parameter could not be set for the current chunk according to the OUTGROUP parameter in CTDPARM.

Corrective Action: Notify your INCONTROL administrator.

PTSB08E ERROR ACCESSING BARCODE TRACKING FILE RC= `rc`

Explanation: A print mission failed to access the Barcode Tracking (BTR) file.

The current print mission terminates NOT OK.

Corrective Action: Correct the source of the problem using message IOAF70I or IOAF71I to be found in the JES log. Rerun the mission.

PTSB09E ERROR CREATING PC FILES FOR USER `recipName` RC= `rc`

Explanation: An error occurred in the processing of a report to be transferred to Control-D/WebAccess Server for the recipient specified in the message.

An error was encountered while Control-D attempted to create PC packet files for a report whose printing destination is CTDPC.

The report is not made available for transfer to Control-D/WebAccess Server. Certain errors allow the print mission to continue processing with the next report. Most errors, however, cause the print mission to terminate immediately. In both cases, the print mission ends with a NOTOK status.

Corrective Action: If the return code is 28, verify that the recipient is authorized to use Control-D/WebAccess Server. This authorization is defined in the Control-D Recipient Tree. For all other return codes, check the IOA LOG and the MVS system log for previously issued messages describing the error in detail.

PTSB0AE MISSING OUTPUT STATEMENT `stmtName`

Explanation: Control-D attempted to dynamically allocate a sysout file for printing the report. Allocation failed because the output statement displayed in the message was missing from the JCL of Control-D Print monitor’s started task.

A reference to an output statement name to be used for printing a report is defined in Control-D by one of the following:

Decollation Mission PRINT/CDAM PARM, subsys parameter in report’s job JCL, or OUTPARMS library member
Internal output statement references assigned by Control-D, such as CONTROLD, CONTROLF and OUTGROUP

The report is not printed. The Print Mission continues with the next report to be printed, but ends with a NOTOK status.

Corrective Action: Define a JCL output statement for the report in the JCL of all Control-D Print monitors started tasks. Restart Control-D monitor to cause JCL changes to take effect.

PTSB0BE ERROR STORING REPORT IN DATASET. USER `usernam`, RC= `rc`

Explanation: Control-D detected an error while processing a printing mission in which the STORE parameter was set to YES.

This message is usually preceded by other messages that describe the problem. These other messages may be issued to the IOA Log file and/or the job log of the Control-D Printers monitor.

The variables in this message are:

userName - User name
rc - Printing mission return code

The printing mission ends with the status NOTOK and the return code 56.

Corrective Action: Check the IOA Log file for other printing mission errors. Check the job log in the Control-D Printers Monitor. If you cannot resolve the problem, call BMC Customer Support.

PTSB0CE ERROR IN CTDPRPS RC= `rc`

Explanation: An internal error occurred during the printing of an AFP report.

In this message, rc is the internal return code of the error.

The printing mission skips the problematic report, and printing continues.

Corrective Action: Do the following:

Check the IOA and job logs for any additional messages associated with the error, and try to resolve the problem. Rerun the program.
If the problem persists, note the value of rc and contact BMC Customer Support.

PTSB0DE OUTPUT CARD DYNAMIC ALLOCATION FAILED, RC= `rc`, REASON= `rsn`, KEY= `keycode`

Explanation: The dynamic allocation (pursuant to optional wish WD3133) of an output statement during a printing mission failed.

The variables in this message are:

rc - the return code
rsn - the reason code
keycode - the key code

These codes are the standard system return, reason, and key codes that are returned when dynamic allocation of an output statement fails. For more information on these codes, see the description of the OUTADD macro in the IBM manual MVS Programming: Authorized Assembler Services Reference.

The printing mission does not use the dynamic allocation of an output statement for the current report.

Corrective Action: Examine the values of the return, reason, and key codes, and take appropriate corrective action.

PTSB10E "FE" PRINT SUPPORT ERROR. RETURN CODE `rc`

Explanation: An executing Printing Mission failed to delete an internal Printing Mission record in the Active User Report file.

If the DO PRINT parameter is specified in a Decollation Mission Definition, the Control-D Decollation monitor writes an internal Printing Mission record to indicate that there are reports waiting to be printed by the Printing Mission specified in the DO PRINT parameter.

These records have the following key:

X‘FE’,C‘PRINTMS’,Printing-Mission-Name

In this message, rc is the return code from the CTDXRP routine.

Control-D encountered an error when attempting to delete the record for the current Printing Mission during Printing Mission termination processing.

The Printing Mission continues.

Corrective Action: If the problem persists, report the return code to BMC Customer Support.

Messages PTSG00 through PTSGxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

PTSG90E OPEN FAILED FOR `dsn` - RC= `rc`

Explanation: Control-D or Control-V failed to open the (sequential) index file.

The data set dsn cannot be accessed for reading.

Reports will be downloaded to the Control-D/WebAccess Server without index information.

Corrective Action: Record the data set name and return code. Contact your system administrator.

PTSG91E CLOSE FAILED FOR `dsn` - RC= `rc`

Explanation: A sequential index file failed to close.

The data set dsn did not close successfully.

Reports will be downloaded to the Control-D/WebAccess Server without index information.

Corrective Action: Record the data set name and return code. Contact your system administrator.

PTSG92E SVC 99 ALLOC RC `rc` RSNC `rsn` DS `dsn`

Explanation: Control-D or Control-V encountered a problem when attempting to dynamically allocate the dsn index file.

Reports will be downloaded to the Control-D/WebAccess Server without index information.

Corrective Action: For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the data set name, internal rc and reason code rsn. Contact BMC Customer Support.

PTSG93E SVC 99 UNALLOC RC `rc` RSNC `rsn` DS `dsn`

Explanation: Control-D or Control-V failed to dynamically deallocate index file data set name.

Reports will be downloaded to the Control-D/WebAccess Server without index information.

PTSG94S INSUFFICIENT MEMORY - GETMAIN ERROR. RC= `rc`

Explanation: There is insufficient memory to download index information to the PC.

The Printing Mission that downloads reports to the PC terminates.

Corrective Action: Increase the REGION size of the Control-D Print monitor.

PTSG95S INTERNAL ERROR - FREEMAIN ERROR. RC= `rc`

Explanation: An internal error was encountered during the execution of a FREEMAIN macro.

The Printing Mission that downloads reports to the PC terminates.

Corrective Action: Record the return code and contact BMC Customer Support.

PTSG96E INDEX `index` NOT FOUND IN FILE `dsn` - NO INDEX FOR THIS REPORT

Explanation: Index index was not found in the dsn file due to an internal error.

Reports will be downloaded to the Control-D/WebAccess Server without index information.

Corrective Action: Record the index name and data set name. Contact BMC Customer Support.

PTSG97S INTERNAL ERROR - INCORRECT PARAMETERS PASSED TO CTVDPC

Explanation: Incorrect parameters were passed from the printing module to the routine creating Control-V indexes for the D/WebAccess Server viewer.

The current print mission terminates NOT-OK.

Corrective Action: Supply BMC Customer Support with the sysout of the Control-D print monitor.

PTSG98S ERROR IN PROGRAM `pgm` FUNCTION `func` RC = `rc` INTERNAL RC = `int_rc` REASON CODE = `rsn`

Explanation: Control-V was unable to create an index file for the printed report.

If the error is in the CTVIXC program, look at message REPG01E for a complete explanation of all return codes.

If the error is in the IOATAE program, possible causes are:

rc	Explanation
4	Member with translation table from ASCII to EBCDIC was not read. A default translation table was used.
8	Not enough storage available. Increase region size.
12	Data is invalid. Check and correct the translation table data.
16	Too many data lines in the translation table. Check and correct the translation table data.
20	Not enough data lines in the translation table. Check and correct the translation table data.

The translation tables are found in the IOA PARM library referenced by the DACMDLIB DD statement.

The TRNA2E member translates from ASCII to EBCDIC. The TRNE2A member translates from EBCDIC to ASCII.

The Control-V index is not created.

Corrective Action: Take appropriate action to correct the problem based on the return code.

PTSG99E DATASET NAME `dsn`

Explanation: Data set name dsn could not be created.

The data set for the Control-V index could not be allocated.

The Control-V index is not created.

Corrective Action: Record the data set name and contact your system administrator.

PTSG9AE CONTROL-V INDEXES COULD NOT BE CONVERTED TO FIT THE REPORT AFTER ACIF, `num` RESOURCE PAGES

Explanation: The ACIF process split one or more pages of the report.

If an original report page is split into more than one AFP page during the ACIF process, the original Control-V index for the report cannot be converted to fit the AFP report.

In this message, num is the number of resource pages.

The Control-V indexes are not created.

Corrective Action: Change the ACIF parameters so that no report page will be split by the ACIF process.

PTSG9BS INTERNAL ERROR - PAGE NUMBER `pagenum` WAS NOT FOUND IN THE REPORT PAGE TABLE

Explanation: An internal error occurred while creating Control-V indexes for a STORE=Y report.

In this message, pagenum is the page number of the page that is missing from the report page table.

Control-V indexes are not created.

Corrective Action: Provide the following information to the INCONTROL Administrator:

Message code and the text of the message.
Total number of pages in the report.
Number of pages in the report created after STORE=Y is specified.

PTSG9CE CONTROL-V INDEX/ES COULD NOT BE CONVERTED BECAUSE INDEX/ES WERE CREATED BEFORE RELEASE IOA 5.0.4

Explanation: Control-V attempted to convert indexes to fit a new STORE=Y report. However, the existing indexes were created in a non-supported version, and cannot be converted to fit a new STORE=Y report.

The Control-V indexes are not created.

Corrective Action: Redecollate the report using a supported version of Control-V.

PTSG9DS INTERNAL ERROR - CONTINUATION RECORD WAS NOT FOUND IN THE ACTIVE USER FILE

Explanation: The printing mission attempted to access a continuation record that did not exist in the Active User Report file.

Control-V indexes are not created.

Corrective Action: Contact your INCONTROL administrator.

PTSG9EW CTV INDEX TABLE ERROR. INDEX `index` CHANGED, REASON `rc`

Explanation: An internal error occurred during the creation of Control-V indexes for a report created by a Print Mission with STORE set to Y.

A level of the problematic Control-V index is changed.

Corrective Action: Contact BMC Customer Support.

PTSG9FE INDEXES NOT CONVERTED DUE TO DIFF NO OF PAGES IN ORIG/TRANSFORMED REP

Explanation: During the rendering to PDF, if an original report page is split into more than one PDF page, the original Control-V index for the report cannot be converted to fit the PDF report.

Corrective Action: If possible, change the rendering parameters (for example, CLIQUE, resources) so that no report page will be split by the rendering process.

PTSG9GW REPORT TRANSFORMATION DELAYED DUE TO LIMIT OF CONCURRENT TRANSFORMATIONS

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

PTSG9HI REPORT TRANSFORMATION RESUMED

Explanation: This information message indicates that the print monitor resumed processing a mission that was postponed (see the PTSG9GW message).

Corrective Action: No action is required.

REP messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages REP200 through REP2xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

REP250I REPORT DECOLLATOR STARTED

Explanation: This information message is the normal message when the Control-D monitor internal decollating task is started.

Corrective Action: No action is required.

REP251I DECOLLATION ENDED "OK"

Explanation: This information message is the normal end message of a job decollation.

Corrective Action: No action is required.

REP252I DECOLLATION ENDED "NOT OK"

Explanation: This information message indicates that the decollation of a report/job was not successful.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look at the IOA Log for additional error messages relating to this decollating mission.

REP253E INSUFFICIENT MEMORY TO DECOLLATE THE JOB

Explanation: Insufficient memory to decollate the job.

Corrective Action: Increase the Control-D monitor REGION size, then rerun the decollating mission.

REP254E INTERNAL ERROR - INVALID FORMAT OF AMF RECORD. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: This problem is caused by incompatibility between what can be defined in the Report Decollating screen, and the actual decollating mechanism under the Control-D monitor. There is no need to reformat the Active Missions file. Print the mission definition and send it to your IOA Administrator in order to solve the bug. In the meantime try to bypass the problem by modifying the mission definition (try a different ON WHEN DO combination). If you cannot bypass it, call your IOA Administrator.

REP255E INTERNAL ERROR IN AMF CONVERSION. DECOLLATION ABORTED

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the IOA Log. Call BMC Customer Support for assistance.

REP256E ERROR WHILE READING SYSOUT FROM SPOOL OR FROM CDAM FILES

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the IOA Log. Call BMC Customer Support for assistance.

REP257E INTERNAL ERROR IN RECIPIENT TREE STRUCTURE

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the system log. Call BMC Customer Support for assistance.

REP258E DEFAULT PRIMARY USER NOT FOUND IN TREE OR NO DEFAULT USER SPECIFIED

Explanation: The user (recipient) specified in the DEF USER parameter of the Report Decollating Definition screen is not found in the Recipient Tree or no DEF USER is specified.

A page has been found in the job’s reports which is not identified by a WHEN/DO/USER statement, and no default user is specified.

Control-D assigns the root of the tree as the default, and the mission ends NOTOK.

Corrective Action: Correct the decollation mission, and schedule it again.

REP259E DECOLLATING JOB WITHOUT ANY SUPPLIED DEFAULTS

Explanation: No defaults are supplied in this decollation mission.

A page has been found which is not identified by a WHEN/DO/USER statement. Defaults are required in order to perform the decollation.

The mission ends NOTOK.

Corrective Action: Correct the decollation mission, and schedule it again.

REP25AE VARIABLE LIST ERROR IN FUNCTION `func` FOR VARIABLE `varName`

Explanation: An error was detected in the variable list structure.

The variables in this message are:

func - the variable process function (GET, GETU, PUT, CONC) under which the problem occurred.
varName - the name of the variable that was being processed when the problem arose.

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Check all the statements in the decollation definition that contain the varName variable, correct them as appropriate, and run this mission again. If the problem persists, contact BMC Customer Support.

REP25BE INVALID PARAMETER `parm` IN FUNCTION `func` FOR VARIABLE `varName`

Explanation: The program that handles the CTDVAR variables received control from Exit CTDX022, but the value of a parameter was invalid.

The variables in this message are:

parm - the name of the parameter with an invalid value
func - the variable process function (GET, GETU, PUT, CONC) under which the problem occurred
varName - the name of the variable that was being processed when the problem arose

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Correct the User Exit CTDX022, and rerun the mission.

REP25CE SYNTAX ERROR IN VARIABLE DEFINITION `varDef`

Explanation: The definition of the variable in the decollation mission is not correct.

In this message, varDef is the invalid string in the decollation definition.

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Correct the decollation mission definition and rerun the mission.

REP25DE XPATH SYNTAX ERROR FOR VARIABLE `varName` IN DEFINITION `string`

Explanation: The DO SET statement in the decollation mission contains an invalid definition of the variable containing the XPATH value.

The variables in this message are:

varName - the name of the variable that was being processed when the problem arose
string - the invalid string in the decollation mission definition

The decollation mission is terminated with the status ENDED NOTOK.

Corrective Action: Correct the decollation mission definition and rerun the mission.

REP25EE INVALID TAG WAS DETECTED IN XML REPORT. TAG= `string`

Explanation: An error was detected in the XML report page.

In this message, string is the invalid string in the XML report.

The status of this decollating mission is set to ENDED NOTOK. Control-D continues processing. All variable values extracted from the page containing the invalid string will be treated as null.

Corrective Action: Correct the XML report, and decollate it again.

REP25FE ERROR IN VARIABLE PROCESS DURING DECOLLATION IN PROGRAM `progName`

Explanation: This message is issued after one of the following messages:

REP25AE
REP25BE
REP25CE
REP25DE

In this message, progName is the name of the program that was executing when the problem occurred.

The status of this decollation mission is set to ENDED NOTOK.

Corrective Action: Check the IOA Log for additional error messages relating to this decollation mission.

REP260E ERROR IN ACTIVE USER REPORTS LIST FILE. USER UPDATE FAILED

Explanation: The update to the Active User Report List file failed. Perhaps the Active User Report List file is full or the Index component is corrupted.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Examine relevant CTDU99E and CTD908S messages, take appropriate corrective action, and then rerun the decollating mission. Use the CTDDIG utility to check the integrity of the user file. If the problem persists, contact BMC Customer Support.

REP261E SEVERE ERROR WHILE LOCATING SYSOUT PARAMETERS FROM JES

Explanation:Highlighted, unrollable message.

An internal test of the JES control blocks failed.

Control-D retrieves data set characteristics from the JES2 control blocks. These blocks are release-dependent. To avoid abends, Control-D tests the blocks at the beginning of its process. If the test fails, message REP261E is displayed.

This error is often caused by MSGCLASS for started tasks being set to PURGE or DUMMY. Control-D uses the settings of MSGCLASS for started tasks for test SYSOUT.

Snaps are produced and put in the DADUMP DD statement. Control-D continues to process without retrieving characteristics from the JES Control Blocks.

Corrective Action: Do the following:

Ensure that the MSGCLASS output class for the started task (STC) in the JES2PARM member of the SYS1.PARMLIB library is not set to PURGE or DUMMY.
If MSGCLASS is set correctly, collect the relevant snaps from the DADUMP DD statement and contact BMC Customer Support.

REP262E ADDITIONAL USER `usr` NOT FOUND IN TREE

Explanation: The Active User Report List file contains an ADDITIONAL USER that was not found on the Recipient Tree. The ADDITIONAL USER must be defined in the Recipient Tree.

The report will not be directed to that user. Processing continues.

Corrective Action: Add this ADDITIONAL USER to the Recipient Tree, or delete this ADDITIONAL USER from the Active and Permanent User Report List file.

REP263E A "DO NOTOK" HAS BEEN ACTIVATED FOR THIS JOB

Explanation: Informational message - the identifying string for a DO NOTOK statement in the decollating mission was found in the report.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: No action is required.

REP264E NO REPORTS WERE SELECTED FROM SPOOL AND/OR FROM DSNS. CHECK THE "ON" DEFINITIONS

Explanation: No reports matched the decollating mission ON statement parameters.

If the current decollating mission contains the IN QUEUE parameter set to Y, and the job is not processed by another decollating mission, the decollation monitor takes the job ID from the last executed job with the matching job name, and accesses sysout files from the spool using this job ID.

This job ID appears in the Active Missions screen on the line corresponding to the mission. Note also that for jobs decollated from the spool, the mission always contains the IN QUEUE parameter set to Y.

One or more ON statements are defined in the decollating mission, but no reports were present that matched even one ON statement. Note that the reports can be from the spool and/or from compressed data sets.

Assume that job XYZ produces the following reports:

REPORT CLASSAR1 ATOTAC W

The following parameters are present in the decollating mission for this job:

ON CLASS X DO ....... ON CLASS Y DO .......

When this decollating mission is executed, none of the ON statements will work, since the job did not produce any output on class X or class Y.

If the decollating mission contains ON DSN statements, then the No CDAM data set matched the CDAM retrieval parameters which were supplied.

Control-D does not select sysouts that have the HOLD=OPER characteristic which can result in the issuing of this message as well.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Do the following:

Check the decollating parameters to make sure that the ON statements are correct, and match the expected outputs from the job.
If the ON statements are OK, check all the outputs of the job. Verify that all the expected reports were produced on the proper classes, or on the CDAM files.

After the problem has been determined and corrected, rerun the job and/or the decollating mission if necessary.

REP265S ERROR WHILE ALLOCATING A CDAM DATASET

Explanation: Internal Control-D error, or some CDAM error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Check the IOA Log and the system log for additional clarification messages.

REP266E CTDPARM GENOTFND SETTING INVALID FOR CURRENT ENVIRONMENT
REP266E GENERIC DECOLLATION PROCESSING STOPPED

Explanation: The setting of the GENOTFND parameter in CTDPARM is not supported by the MVS/JES configuration of the computer. These two messages are always issued together.

Some options of the GENOTFND parameter in CTDPARM are valid only in certain MVS/JES configurations. For example, JES3 only supports GENOTFND when set to CLASS or DELETE.

The unmatched sysout file remains unchanged.

Corrective Action: Do the following:

Manually remove the problematic sysout from the generic class.
Correct the GENOTFND parameter in CTDPARM. For a description of the GENOTFND parameter, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.
Restart the Control-D monitor after compiling CTDPARM.

REP267I DECOLLATION FROM SPOOL STARTED

Explanation: This information message is the normal start message when a decollating mission starts decollating reports from Spool.

Corrective Action: No action is required.

REP268I DECOLLATION FROM COMPRESSED DSN STARTED

Explanation: This information message is the normal start message when a decollating mission starts decollating reports from compressed data sets.

Corrective Action: No action is required.

REP269I DECOLLATION FROM MQ QUEUE STARTED

Explanation: This information message is the normal start message when a decollating mission begins decollating reports from the IBM WebSphere MQ queue.

Corrective Action: No action is required.

REP269S ERROR WHILE DECOLLATING A GENERIC MISSION

Explanation: The attempt to read sysout from the spool failed.

Control-D has started to read sysout from the spool but a nonzero return code was received from JES.

Control-D continues processing.

Corrective Action: Please check whether JES is up or down.

REP26AE MISSION ABENDED `syscode usrcode`

Explanation: Highlighted, unrollable message.

The decollation mission abended with either the system code syscode, or the user code usrcode, or both.

The decollation mission finishes NOTOK. Control-D tries to process other missions.

Corrective Action: If Control-D cannot process other missions, stop and restart the Control-D monitor. Save the job log of the Control-D decollation monitors and the output referenced by the IOADUMP DD statement of the decollation monitor which processed the problematic mission. Contact BMC Support.

REP26BE SUBSYSTEM REQUEST FAILED FOR JOB `jobName`. RC15=`rc`, SSOBRETN=`ssobretn_rc`

Explanation: A “sysout processing” request caused an unexpected return code to be received from JES.

JES was unable to satisfy the request.

The variables in this message are:

jobName - the name of the job in which the request failed
rc - the code returned in register 15
ssobretn_rc - the contents of the SSOBRETN field of the request block

Corrective Action: Verify that JES is active and functions normally. If JES is functioning normally, save all sysouts of this execution of the Control-D monitor and contact BMC Customer Support. Request RESTORE of the problematic report again.

REP26DW `variableTextMsg`

Explanation: A text message is issued from the DAL transformer while a report is being decollated with transformation. The text, which may be information, a warning, or an error message, is directly related to the event that produced it, and provides specific information about that event.

The action that the system implements is included in the message text.

Corrective Action: The required user response is included in the message text.

For documentation of the following transformer messages listed under the current message, see, “Control-D Transformation Messages”:

BMCDAL0009E TCL.Size : Missing resource resourceName (Type: resourceType)
BMCDAL0614E TransformObject.ConvertObject: ConvObject_Create Create resource failed: resourceName (Type resourceType), rc= returnCode
BMCDAL0678W Xerox warning cdpXerox returnCode : messageText
BMCDAL0679E Xerox error cdpXerox returnCode : messageText

REP26EE ERROR IN DAL TRANSFORMER

Explanation: The DAL transformer found an error while a report was being decollated with transformation.

The decollating mission ends NOTOK.

Corrective Action: Examine the IOA Log for REP26DW messages relating to this decollating mission.

REP26FE APPROVAL `approval` NOT FOUND IN APPROVAL TREE

Explanation: The Approval name specified in the DO APPROV statement of the Report Decollation Definition screen is not found in the Approval Tree. The mission ends NOTOK.

Corrective Action: Correct the decollation mission and reschedule the mission.

REP26GW MASK RULER `Ruler_name` NOT FOUND IN PERMANENT FILE FOR RECIPIENT

Explanation: The Mask Ruler Ruler_name specified in the DO MASKRUL statement of the Report Decollation Definition is not found in the Permanent User File.

The information about the report is provided in message CTDI0CI, which follows this message.

The mission ends OK WITH ERRORS.

Corrective Action: Correct the decollation mission or create the Mask Ruler and reschedule the mission.

REP26HE GENERIC MISSION ABENDED SXXX UXXXX. GENERIC DECOLLATION PROCESSING STOPPED

Explanation:Highlighted, unrollable message.

The generic decollation mission abended with the system code or the user code or both these codes displayed in this message. The decollation mission finishes NOTOK. CONTROL-D deactivates the Generic decollation process.

Corrective Action: Save the job log of the CONTROL-D decollation monitors and the output referenced by DD statement IOADUMP of the decollation monitor that processed the problematic mission. Call BMC Software Customer Support.

REP270E SYSOUT PURGED. GENERIC DECOLLATING MISSION NOT FOUND FOR THE JOB

Explanation: Control-D found a non-held output on one of the Classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission (on the Active Missions file) which matches the job name. If a match is not found, the sysout is processed according to the Control-D installation the GENOTFND parameter. For more information, see the INCONTROL for z/OS Administrator Guide.

Control-D continues processing.

Corrective Action: No action is required.

REP271I GENERIC JOB DECOLLATION IS INACTIVE

Explanation: This information message indicates that Generic Processing is not active. The reason the message is issued depends in which of the following formats the message is issued.

regular, rollable message - indicates that the corresponding Control-D monitor does not perform the Generic Processing. The Control-D monitor issues the message when it is started and after new day processing.
highlighted, unrollable message - indicates that a job is waiting to be decollated in one of the Generic classes, but Generic Processing is not active. This message will appear every 10 minutes, until Generic Processing is activated.

Control-D continues processing, but no Generic Processing will be done.

Corrective Action: Use the following guidelines to resolve the problem:

If you have Generic Missions that CTDNDAY processing should order , ensure that the GENLIST member contains the library and table name for your Generic Missions
If you have a Library and table names in the GENLIST member, ensure that the MEMBERS really exist in the library. Also verify that the library is the correct name.
Check to see if CTDNDAY processing had an error during the ordering of GENLIST. If an error occurred the deactivation of Generic Processing is automatic.
Check to see if someone issued the STOPGEN command.

Issue the following command, to activate Generic Processing:

F CONTROLD,STARTGEN

The application will respond by displaying the following message:

CTD139I GENERIC JOB DECOLLATION IS ACTIVE ON CLASSES (claslist)

To verify your classes, check the GENCLAS= parameter in the CTDPARM member.

If there are NO Generic Missions being ordered during the CTDNDAY processing, you need to manually activate Generic Processing if you are manually Forcing/Ordering Generic Missions.

For more information on activating and deactivating generic processing, see the INCONTROL for z/OS Administrator Guide.

REP272W SYSOUT REMOVED FROM QUEUE
REP272I GENERIC DECOLLATING MISSION NOT FOUND FOR JOB `jobName`

Explanation: Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout. These two messages are always issued together.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission (on the Active Missions file) which matches the job name. If a match is not found, the sysout is processed according to the GENOTFND Control-D installation parameter. Refer to the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

Control-D continues processing.

Corrective Action: Check to see if the Generic decollating mission for this job should be on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

REP273I SYSOUT CLASS CHANGED FROM CLASS `x` TO ESCAPE CLASS `y`

Explanation: This information message indicates that Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission on the Active Missions file that matches the job name. If a match is not found under JES3, Control-D changes the sysout’s class to an Escape Class as specified in the GENOTFND Control-D installation parameter and the output remains on the spool. Refer to the INCONTROL for z/OS Administrator Guide.

Control-D continues processing.

Corrective Action: Check to see if the Generic decollating mission for this job should be Active on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

REP274W MQ DECOLLATING MISSION NOT FOUND FOR THE MESSAGE FROM MQ QUEUE `mqQueueName`

Explanation: There is no appropriated mission with matched selection parameters for this message from the IBM WebSphere MQ queue.

This message will be moved to the IBM WebSphere MQ escape queue. The name of the escape queue must be defined in the CTDMQPRM parameter of the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

REP275E ERROR WHILE DECOLLATING FROM MQ `mqQueueName`

Explanation: The decollation was started, but a nonzero code was returned.

Control-D continues processing.

Corrective Action: Check any additional messages received during this IBM WebSphere MQ decollation.

REP276I MESSAGE MOVED TO MQ ESCAPE QUEUE `queueName`

Explanation: This information message indicates that the message was moved to the queueName queue that was defined in the CTDMQPRM parameter of the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

REP277W THE DATA LENGTH IS ZERO IN THE MESSAGE FROM MQ QUEUE queueName

Explanation: The message from the IBM WebSphere MQ queue cannot be decollated because the message data length is zero. The message will be moved to the IBM WebSphere MQ escape queue.

The name of the escape queue must be defined with the CTDMQPRM parameter in the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

REP278E SYSOUT ALLOCATION FAILED, `JobName`,`JobId`,`DDName`, RC=`rc`, ERROR=`rsn`

Explanation: An error was encountered when Control-D tried to allocate a sysout for decollation.

The variables in this message are:

jobName - the name of the job with the problematic sysout
jobId - the job ID of the job with the problematic sysout
DDName - the name of the DD statement with the problematic sysout
rc - dynamic allocation return code
rsn - dynamic allocation reason code

Corrective Action: Try to correct the sysout. If the problem persists, contact your system programmer for assistance. Keep all sysouts from this execution of the Control-D monitor, and contact BMC Customer Support.

REP279E MULTIPLE APPROVAL PROCESS WAS DEFINED INCORRECTLY FOR REPORT `rename`

Explanation: This message can be issue in the following conditions:

Control-D has detected that a report that was defined for multiple approval processing (MULTI=S) was not created. The status of the related reports created from the same SYSOUT is set to Candidate.
A report that was defined for multiple approval processing (MULTI=S) refers to more than one CDAM. Control-D does not expand multiple approval processing on secondary CDAMs. Reports referring to these CDAMs cannot be approved.

Corrective Action: Check the decollation mission or the original report to assure that all reports and corresponding approval components have been created correctly.

REP27AE `ERROR` ERROR IN APPROVAL PROCESSING

Explanation: This message is issued after the REP279E or REP26FE message.The status of this decollation mission is set to ENDED NOTOK.

Corrective Action: Check the IOA log for additional error messages relating to this decollation mission.

REP27BE APPROVAL `aprvname` HAS INCORRECT APPROVAL TREE DEFINITION

Explanation: The aprvname Approval name is defined incorrectly in the Approval Tree.

This message is issued if the WDN051 Optional wish is applied (APPLY=YES) in the following conditions:

The aprvname Approval name has no authorized users and has no child items (incorrect Parallel Approval).
The aprvname Approval name has child items that have no authorized users.
The aprvname Approval name for a Parallel Approval process has more than 15 child items.

Corrective Action: Check the Approval Tree and adjust the relevant Approval items.

REP27CW `jobId,jobName,ddName` FROM `numSpool` LINES ON SPOOL
REP27CI `numRead` LINES ARE READ

Explanation: During decollation of SYSOUT, Control-D checks the number of read lines and the number of lines in SSOB (SSSOLNCT or SSS2LNCT). If the number of lines read from the spool is equal to or greater than the number from SSOB, Control-D decollates the SYSOUT. These two messages are issued if the number of read lines is less than the number in SSOB, as Control-D considers the SYSOUT corrupted due to lost information. SYSOUT remains in the spool.

The variables in these messages are:

jobName - the name of the job with the sysout in which the mismatch occurred
jobId - the job ID of the job with the sysout in which the mismatch occurred
ddName - the name of the DD statement with the sysout in which the mismatch occurred
numSpool - the number of lines of sysout on the spool
numRead - the number of lines of sysout read from the spool

The decollation mission finishes NOTOK.

Corrective Action: Try to correct the sysout. If it is not possible to correct the sysout, and you want Control-D to process such corrupted sysouts, temporarily specify APPLY=Y for the optional wish WD3597. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

BMC recommends not to specify APPLY=Y for the optional wish WD3597 as a permanent setting.

REP27EW `jobId,jobName,ddName` FROM `numRead` LINES READ FROM SPOOL
REP27EI `numLines` LINES IN `numPages` PAGES PASSED TO CDAM

Explanation: The number of lines of sysout read from the spool is not the same as the number of lines of sysout written to CDAM. These two messages are always issued together.

The variables in these messages are:

jobName - the name of the job with the sysout in which the mismatch occurred
jobId - the job ID of the job with the sysout in which the mismatch occurred
ddName - the name of the DD statement with the sysout in which the mismatch occurred
numRead - the number of lines of sysout read from the spool
numLines - the number of lines of sysout written to CDAM
numPages - the number of pages of sysout written to CDAM

The Control-D monitor terminates with the user code U027.

Corrective Action: If there is an urgent reason to temporarily bypass the U027 abend, specify APPLY=Y for the optional wish WD3597. (Note that some lines from the spool might be lost.) Keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

BMC recommends not to specify APPLY=Y for the optional wish WD3597 as a permanent setting.

REP27FI `jobId,jobName,ddName` SYSOUT IS HELD IN GENERIC CLASS `clss`

Explanation: The sysout of the identified job cannot be decollated by a generic decollation mission. The reason is an error identified in a previous message.

The variables in this message are:

jobName - the name of the job with the problematic sysout
jobId - the job ID of the job with the problematic sysout
ddName - the name of the DD statement with the problematic sysout
clss - the spool class of the sysout

Processing continues, but the status of the sysout is set to HELD.

Corrective Action: Examine the log for the previous message that identifies the error, and proceed according to the User Response for that message.

REP27GE `jobId,jobName,ddName` JES I/O ERROR RSN `rsn` FOR SYSOUT CLASS `clss`

Explanation: A JES I/O error occurred during the reading of sysout from the spool.

The variables in this message are:

jobName - the name of the job with the sysout that was being read when the mismatch occurred
jobId - the job ID of the job with the sysout that was being read when the mismatch occurred
ddName - the name of the DD statement with the sysout that was being read when the mismatch occurred
rsn - the reason code from the FDBK field of JES
clss - the spool class of the sysout

The decollation mission finishes NOTOK.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

REP27HI ZIIP ISN'T USED

Explanation: This information message indicates that the zIIP processor is not being used by the Control-D decollation monitor, as it is defined in the CTDPARM.

Additional messages identify the specific reason why the zIIP processor is not being used.

Corrective Action: Check the IOA log file and the system log for the reason. Contact your system programmer for assistance if needed.

REP27II ZIIP IS USED

Explanation: This information message indicates that the zIIP processor is being used by the Control-D decollation monitor.

Corrective Action: No action is required.

REP27JE `jobName, jobId, ddName` OPEN ERROR RS `rs` ERFLG `err` FOR SYSOUT CLASS `clss`

Explanation: An error occurred while attempting to open a SYSOUT for decollation.

The variables in this message are:

jobName - the name of the job with the sysout that caused the problem
jobId - the job ID of the job with the sysout that caused the problem
ddName - the name of the DD statement with the sysout that caused the problem
rc - the return code from the OPEN
err - the reason code from the ACBERFLG field
clss - the spool class of the sysout

The decollation mission finishes NOTOK. The REP27FI message, which follows, indicates that the status of the problematic SYSOUT is set to HELD.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

Messages REP300 through REP3xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

REP304E `xxxxxxx` NOT OK WITH `cc` Y REASON CODE `zzzz` MQ NAME `uuuuuuu`

Explanation: An error was detected during interface with IBM WebSphere MQ Series.

The variables in this message are:

xxxxxxxx - which can be one of the following interface functions:
- MQCONN
- MQDISC
- MQOPEN
- MQGET
- MQPUT
- MQCLOS
- MQCOMMT
cc - the completion code, which can be
- 0
- 1,,,
- 2
zzzz - the reason code, which can have many different values. More detailed information about reason codes is included in the IBM WebSphere MQ Series documentation set.

System action is determined by the completion code and reason code combination. More detailed information about these codes is included in the IBM WebSphere MQ Series documentation set.

Corrective Action: User response to a particular completion and reason code combination is determined by that combination. More detailed information about these codes is included in the IBM WebSphere MQ Series documentation set.

REP305E INSUFFICIENT MEMORY TO DECOLLATE MESSAGE FROM MQ

Explanation: Insufficient memory to decollate the message from the IBM WebSphere MQ queue.

Corrective Action: Increase the Control-D monitor REGION size.

REP306E IOAUCODE INITIALIZATION FAILED RC `rc` REASON `rsn`

Explanation: An error was detected during initialization of the table used in the translation of an XML report or in the checking of Xpath values of the mission definition. The message can be issued from

the R screen
the A.Z screen
the Control-D monitor

Possible causes of this error are:

the ENCODTBL member was not found in the IOA IOAENV library
the ENCODTBL member contains more than 100 entries
some other internal error

The following system actions occur:

Mission definition edition is terminated. Message IOAE2FS issues on the R.S and A.Z screens.
The translation of the XML report does not proceed. Control-D continues processing.

Corrective Action: Perform the following actions:

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate the IOA Online facility, and continue the mission definition edition.
Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate Control-D, and run this mission again.

If the problem persists contact BMC Customer Support.

REP307E UNICODE TRANSLATION FAILED RC `rc` REASON `rsn`

Explanation: An error was detected during translation of an XML report to EBCDIC or during the checking of Xpath-values of the mission definition for XML reports. The message can be issued from

the R screen
the A.Z screen
the Control-D monitor

The variables in this message are:

rc - the return codeValid values are:
- 4 - incomplete translation, due to separator (FF)
- 8 - the encoding pair that was specified in ENCODTBL is not supported
- 12 - the input data in the XML report was incorrect
- 16 - internal error: incorrect parameters
- 20 - one of the members that was specified in ENCODTBL was not found in the IOA IOAENV library
rsn - the code that disclosed the detailed reason for the internal error

The following system actions occur:

Mission definition edition is terminated. Message IOAE2FS issues on the R.S and A.Z screens.
The translation of the XML report does not proceed. Control-D continues processing.

Corrective Action: Perform the following actions:

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate the IOA Online facility, and continue the mission definition edition.
Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate Control-D and run this mission again.

If the problem persists contact BMC Customer Support.

REP308I SYNCHRONIZATION WITH BACKUP/CTDDELRP ENDED

Explanation: This information message indicates that the synchronization process has finished.

Control-D received notification from the CTDDELRP utility or from the Backup Mission that the synchronization ended; therefore the decollating task on the monitor may resume. See message MONA59I for an explanation of the synchronization process.

Control-D continues the previously interrupted decollating tasks.

Corrective Action: No action is required.

REP309I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message indicates that Control-D monitor has been shut down.

Shut down of Control-D internal decollating task by request of the Control-D main task.

The Control-D monitor will shut down.

Corrective Action: No action is required.

REP30AI MQ DECOLLATION IS STOPPED

Explanation: The MQ interface process has stopped.

This message can appear for two reasons:

The STOPMQ modify command was issued
Errors occurred during MQ interface

Corrective Action: If errors occurred during MQ interface, review the LOG to determine the cause, make appropriate corrections, and issue the STARTMQ modify command.

REP30BE LOADING OF MODULE OF MQ STUB IS FAILED, THE NAME IS `mmmmmmmm`

Explanation: The prefix.prefixLOAD library is not installed or the IBM WebSphere MQ Series is not installed for the user, but an MQ decollation mission was defined.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Corrective Action: If the IBM WebSphere MQ Series is not installed, delete the MQ mission. Otherwise correct your installation configuration and then issue the STARTMQ modify command.

REP30CE ANY OF MQ QUEUES CAN NOT BE OPENED

Explanation: Control-D tried to retrieve a message from every IBM WebSphere MQ queue, but all attempts failed.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Review previous messages and issue appropriate responses. After you perform the necessary corrections, issue the STARTMQ modify command.

Corrective Action: No action is required.

REP30DI MQ QUEUE IS BEING CLOSED BECAUSE PUT/GET IS FAILED, QUEUE NAME `queueName`

Explanation: The access to the IBM WebSphere MQ Series queue queueName is being closed because of failure of MQPUT for the ESCAPE MQ queue, or failure of MQGET for the MQ queue.

Control-D continues processing MQ decollations until this message is issued for all MQ queues.

Corrective Action: For additional information see the IBM WebSphere MQ Series documentation set.

REP30EE MEMBER CTDMQPRM IS NOT FOUND IN CTD PARM OR VALUE OF MQNOTFIND PARAMETER IS NOT DEFINED

Explanation: The CTDMQPRM member was not found in CTD PARM, or the value of the MQNOTFIND parameter has not been defined.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Corrective Action: Define the CTDMQPRM member or add the name of the MQNOTFIND parameter; then issue the STARTMQ modify command.

Messages REPB00 through REPBxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

REPB10E "FE" PRINT SUPPORT ERROR. RETURN CODE `rc`

Explanation: An executing Decollation Mission failed to create or update a Printing Mission record in the Active User Report file.

When the DO PRINT parameter is specified in a decollating mission Definition, the Control-D Decollation monitor writes an internal Printing Mission record to indicate that reports specified in the DO PRINT parameter are waiting to be printed by the Printing Mission. These records have the following key:

X‘FE’,C’PRINTMS’,Printing_Mission_Name

In this message, rc is the return code from routine CTDXRP.

The decollating mission completes decollating the reports but terminates with status NOT-OK. Reports created by this decollating mission cannot be selected by any Printing Mission specified in the DO PRINT parameter of this decollating mission.

Corrective Action: The reports can be manually scheduled for Deferred Printing by using option (line command) P to display the Print Window in the Active User Reports List and then specifying the Printing Mission name. If the problem persists, record the return code and contact BMC Customer Support.

REPB11W DEFAULT PRINT MISSION IS NOT DEFINED FOR SUBSCRIBED REPORT `jobName / username /reportName`

Explanation: The default PRINT mission was not defined when the report was set for subscription. Subscription will not be performed.

Corrective Action: Do one of the following:

Define parameter PRINT-NOTIFY=default_PRINT_mission in the CTDSPARM member in the in CTD PARM library.
Change the decollation mission definition by adding a DO PRINT statement with MUST=S (for full subscribed reports) and/or define a PRINT mission with TYPE=S (for subscribed reports by index).

Messages REPG00 through REPGxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

REPG01E INDEX CREATION ERROR. RC = `rc,` INTERNAL RC = `int_rc,` REASON = `rsn`

Explanation: Control-V was unable to create an index file.

Even though the index file is not created, the decollated report is produced.

Possible causes are:

Return Code	Explanation
4	RDJFCB of INDEX file error
8	OPEN INDEX file error
12	CLOSE INDEX file error
16	Insufficient memory.
20	Insufficient space on the volumes to create the index file.
28	Size of the index file calculated internally is not big enough for all entries.
40	Dynamic allocation error.
44	Dynamic deallocation error.
48	Sort error.
Other	Internal error.

This message is followed by message REPG06E.

The index is not created.

Corrective Action: Take appropriate actions to correct the problem associated with the specified return code:

Return Code	Explanation
4	The problem is caused by SMS or DASD failure. Check for additional messages and contact the System Administrator.
8	The problem is caused by SMS or DASD failure. Check for additional messages and contact the System Administrator.
12	The problem is caused by SMS or DASD failure. Check for additional messages and contact the System Administrator.
16	Increase the REGION size of the Control-D or Control-V Decollation monitor.
20	Clear space on the volumes defined for index files in Control-V Installation Parameters or add another volume to the Control-V Installation Parameters.
28	First check that definition of every subindex is correctly defined in the decollation mission. If this is not the source of the problem, turn to BMC Customer Support, supplying the decollation mission definition and sample pages of the report.
40	For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the return code, internal return code and reason code. Contact BMC Customer Support.
44	Take the same action outlined for return code 40 above.
48	Check the sort messages in the Control-D or Control-V Decollation monitor sysout. If you cannot resolve the problem, record the sort messages and contact BMC Customer Support.
other	Record the return code, internal return code and reason code and contact BMC Customer Support.

REPG02E INDEX CREATION ERROR - INDEX SPANS OVER MORE THAN ONE CDAM DATASET

Explanation: A Report Decollation Mission attempted to index a report which spanned more than one Compressed Dataset Access Method (CDAM) data set.

Different CDAM data sets are created for each sysout of a report. An index file cannot index more than one CDAM data set. Use separate indexes, meaning, indexes with different names, to index different CDAM data sets.

The index is not created.

Corrective Action: Determine how many sysouts the job has and create an index for each, or alternately modify the decollation mission so that it creates indexes with different names for each CDAM data set by using the DCAM expression ALLOCTOPT=ONEDSN. See the Control-D and Control-V User Guide.

REPG03E INDEX CREATION ERROR - NO INDEXES CREATED

Explanation: The creation of the index file was not successful.

The index is not created. The status of the decollating mission is set to ENDED NOTOK.

Corrective Action: Check the IOA Log file and the Control-D or Control-V monitor job log for additional messages relating to this decollating mission.

REPG04W TOO MANY RESIDENT INDEXES FOR REPORT `report` - MAXIMUM 3

Explanation: An attempt was made to create more than three DASD-resident indexes for a single report. The maximum number of resident indexes for one report is three.

The index is created but is not designated DASD-resident. It will be deleted from DASD when the corresponding report is deleted and will be available on migrated media, if the report is migrated.

Corrective Action: Redefine the Report decollating mission to specify not more than three indexes that will remain DASD-resident.

REPG05E TOO MANY INDEXES FOR REPORT `report` - ONLY 9 CREATED

Explanation: An attempt was made to create more than nine indexes for a single report.

A maximum of nine indexes can be defined for one report.

Only the first nine indexes are created.

Corrective Action: Redefine the Report decollating mission to specify a maximum of nine indexes for this report.

REPG06E INDEX DSNAME=`dsn` BLOCKS=`blk`

Explanation: An error occurred during the creation of the dsn index file containing blk blocks.

This message is preceded by message REPG01E. See message REPG01E for more information.

Corrective Action: No action is required.

REPG07E "DDNAMES" INDEX NOT CREATED - ALLOCOPT "ONEDSN" OR "JOBSDSN1" REQUIRED

Explanation: The user attempted to create a DDNAMES index for a report created by a decollating mission whose ON CLASS statement does not contain ALLOCOPT=ONEDSN or JOBSDSN1 in the PRINT/CDAM PARMS field.

The index is not created.

Corrective Action: Add the expression ALLOCOPT=ONEDSN or ALLOCOPT=JOBSDSN1 to the decollation mission definition. For more information on the ALLOCOPT parameter, see the CDAM chapter in the Control-D and Control-V User Guide.

REPG08W MORE THAN ONE SUBINDEX WITH THE SAME NAME. ONLY THE FIRST ONE IS DEFINED

Explanation: The user attempted to specify the same name for more than one subindex of a main index.

All subindexes of a main index must have unique names. It is recommended that all indexes specified for a report have unique names.

When a subindex is encountered whose name was specified for a previously specified subindex, that subindex and all the indexes under it (if any) are not created.

Corrective Action: Change the subindex’s name.

REPG09W INCONSISTENT INDEX TREE STRUCTURE. SOME INDEXES/VALUES ARE NOT CREATED.

Explanation: The index tree defined for the report in the decollation mission is not consistent in structure.

During a run of a decollation mission, a main index was encountered that does not have the same subindexes defined throughout the mission definition. The topology of the index tree must be consistent.

Some of the subindexes are not created because of this inconsistency. Other subindexes may have incorrect values.

Corrective Action: Correct the index definition in the decollation mission and rerun the mission.

REPG0EE GLOBAL INDEX CREATION ERROR - NO GLOBAL INDEXES CREATED.

Explanation: This message is issued when loading the Global Index database immediately during the decollation mission run, if the database is not loaded successfully. This message is preceded by CTD and GIX messages explaining the cause of the problem.

Control-D decollates the reports without loading the index values into the Global Index database.

Corrective Action: Perform the following:

Examine the preceding messages to find out reason for the problem, and fix the problem.
Use the CTDGBILD job to load index values from reports decollated by this mission to the Global Index database.

REPG0GW UNSUPPORTED MULTI-VALUE INDEX STRUCTURE. SOME VALUES ARE NOT CREATED.

Explanation: The indexing report has the value structure of a multi-value index that is not supported by the current implementation of Control-V.

Corrective Action: Contact your INCONTROL administrator.

REPG0HE SYSTEM VARIABLE `%%var` ISN'T SUITABLE FOR CURRENT ENVIRONMENT.

Explanation: This message is issued when the current environment does not provide the ability to use the %%var system variable in SET/DO SET statements in decollation missions. The reason for the problem is due to the value of %%var.

Variable and value	Possible reason
$MEMORY=ABOVEBAR	The environment does not support 64-bit addressing mode

The Control-D monitor terminates the mission with the status of NOTOK.

Corrective Action: Start the CONTROL -D monitor in another environment, or remove the SET/DO SET statement for the %%var system variable from the decollation mission definition.

RFR messages

This group includes messages for the Control-O product.

Messages RFR800 through RFR8xx

This group includes messages for the Control-O product.

RFR8E9I {CONTROL-O|CTMCMEM} LOADER TASK STARTED

Explanation: In Control-O, this information message indicates that the task responsible for loading rules and Global variables has begun.

In Control-M, this information message indicates that the task responsible for loading CMEM rules has begun.

Corrective Action: No action is required.

RFR8EAE CTORFR DETECTED AN INVALID CHAIN STRUCTURE

Explanation: Control-O detected invalid structure for internal control blocks.

This message indicates an internal error.

The Control-O monitor terminates.

Corrective Action: Contact BMC Customer Support.

RFR8EBI {CONTROL-O | CTMCMEM} LOADER TASK ENDED

Explanation: In Control-O, this information message indicates that the task responsible for loading rules and Global variables has terminated successfully.

In Control-M, this information message indicates that the task responsible for loading CMEM rules has terminated successfully.

Corrective Action: No action is required.

RFR8ECS ERROR ATTACHING CTOCPS - GLOBAL VARIABLES COMPRESSION FEATURE INACTIVE

Explanation: The CTOCPS program, which is responsible for automatic compression of the Global AutoEdit library, could not be loaded.

The Automatic Compression Facility is not activated.

Corrective Action: Check associated MVS messages for the reason and for possible corrective actions, for example, wrong load library concatenation, or region too small.

RFR8EDS ERROR VERIFYING GLOBAL VARIABLES LIBRARY - GLOBAL COMPRESSION FEATURE INACTIVE

Explanation: The CTOCPS program detected an error while verifying that the previous LOADGLOBAL/WRITEGLOBAL action ended successfully.

When automatic compression is activated, the $$COMPST member in the Global AutoEdit library is checked to see if the previous compress ended successfully. An error was detected by the program that performs the check on the $$COMPST member. This message is preceded by messages that describe the cause of the error.

The LOADGLOBAL/WRITEGLOBAL operation that prompted the verification process is terminated.

Corrective Action: Check preceding messages for the cause of the error and possible corrective actions.

RFR8EES ERROR COMPRESSING GLOBAL VARIABLES LIBRARY

Explanation: Compression of the Global AutoEdit library failed.

This message is preceded by messages describing the cause of the error.

The compression process is terminated.

Corrective Action: Check preceding messages for the cause of the error and possible corrective actions.

RFR8EFS cmd COMMAND FAILED

Explanation: The CTORFR program detected an error while executing the cmd command.

This message can result from problems while loading variables or tables, or (in Control-O) while writing variables to the Global AutoEdit library. This message is preceded by messages describing the cause of the error.

The command specified in this message is terminated.

Corrective Action: Check the preceding messages for the cause of the error and possible corrective actions.

RLR messages

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 RLR600 through RLR6xx

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.

RLR621E THE UTILITY CTMRELRS MAY BE ACTIVATED ONLY FROM BATCH JOBS

Explanation: The CTMRELRS utility (the CTMRLR program) has been activated from a started task or from a TSO session. The CTMRELRS utility may be activated only from batch jobs which are submitted by the Control-M monitor.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: See the INCONTROL for z/OS Utilities Guide for usage restriction of the utility.

RLR622E THIS JOB WAS NOT SUBMITTED FROM CONTROL-M. THE RESOURCE IS NOT RELEASED

Explanation: The CTMRELRS utility (the CTMRLR program) was activated from a job that was not submitted by the Control-M monitor. Only a job that is submitted by the Control-M monitor can release its own quantitative resources.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: For more information on usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide..

RLR623I QUANTITATIVE RESOURCE `res - quantity action`

Explanation: This information message indicates that the quantity of the specified quantitative resource has been released for general use or changed by the CTMRLRES utility.

The specified action is either RELEASED or CHANGED.

Corrective Action: No action is required.

RLR625S INVALID FUNCTION. USE "RELEASE" OR "CHANGE"

Explanation: Invalid function supplied as a parameter to the CTMRELRS utility.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released or changed.

Corrective Action: Specify either function RELEASE or CHANGE for the utility.

RLR627E YOU CANNOT RELEASE MORE `res` THAN THOSE ALLOCATED TO THIS JOB

Explanation: The quantity of the res resource requested to be released by the job using the CTMRELRS utility is greater than the quantity of the resource currently allocated to the job.

The utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: Correct the parameters of the utility.

RLR628E RESOURCE `res` IS NOT ALLOCATED TO THIS JOB

Explanation: The res quantitative resource to be released by the CTMRELRS utility is not allocated at all to the job that activates the utility.

A job can only release resources which are allocated to it.

The CTMRELRS utility stops executing with a condition code of 04. The resource is not released.

Corrective Action: For more information on usage restriction of the utility, see the INCONTROL for z/OS Utilities Guide..

RLR629S OPEN OF PARAMETER LIST FAILED. DDNAME "DARELIN"

Explanation: Open of the control statements file failed (the DARELIN DD statement in the CTMRELRS utility).

Possible causes are:

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

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job and run it again.

RLR630E YOU CANNOT INCREASE THE NUMBER OF `quantResourceName` ALLOCATED TO THIS JOB

Explanation: The quantity requested to be changed using the CTMRELRS utility is greater than the quantity of the resource currently allocated to the job. The CTMRELRS utility can only be used to decrease the quantity of the resource allocated to a job.

The utility stops executing with a condition code of 4. The resource amount allocated to the job is not changed.

Corrective Action: Correct the parameters of the job.

RLR631E RESOURCE `quantResource` WAS NOT FOUND IN THE RESOURCE FILE

Explanation: The quantResource Quantitative resource does not exist. The missing resource was named as input to the CTMRLR program.

Corrective Action: Ensure that the name of the resource specified as input to the program matches the resource name in the job scheduling definition.

RLR632I JOB RELEASED `num` UNITS OF RESOURCE `quantResource`

Explanation: This information message indicates that the CTMRLR program released the specified quantity (num) of quantResource Quantitative resources while a job was still in progress.

Usually, resources are released only when a job is finished.

Corrective Action: No action is required.

RSC messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages RSC600 through RSC6xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

RSC690I CHECKING RESULTS OF MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime`

Explanation: This information message indicates that the restore job that executes the pointed out mission started to check the result of the restore utility.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission

Corrective Action: No action is required.

RSC691E INVALID PARAMETERS FOR RESTORE ANALYZE PROGRAM

Explanation: An invalid parameter was passed to the restore job. This message is produced by the last step of the restore job, which executes the CTDRSC program. CTDRSC analyzes the output of the restore process. The parameters passed to this program are wrong. For further details please refer to the INCONTROL for z/OS Administrator Guide.

The restore of the requested data sets will not be performed. The status of the Restore Mission will remain RESTORE IN PROCESS.

Corrective Action: Do the following:

Check the last step of the restore job which can be found on the library allocated to the DADJOB DD statement. This step executes the CTDRSC program, and has two parameters; timestamp and mission name. Refer to the sample skeleton job RSTDFDSS on the Control-D SKL library for the correct format of these two parameters, modify the JCL, and rerun the job. The status of the Restore Mission will then change to ENDED OK.
In order to prevent this problem from occurring again, modify the last step of the restore job which can be found on the library allocated to the DADSKL DD statement.

RSC692E DATASET: `dsn` NOT FOUND AFTER RESTORE. RC FROM LOCATE IS `rc`

Explanation: One or more CDAM extents were not found during the ANALYZE step of the RESTORE procedure.

Contact your local INCONTROL administrator.

Corrective Action: No action is required.

RSC693E DATASET WAS NOT RESTORED: `dsn`

Explanation: A CDAM data set that should have been restored by the restore job was not restored.

A CDAM data set that should have been restored by a certain Restore Mission, was not restored when the restore job finished. The restore failure might have been caused by security problems, insufficient space in disk, and so on.

An error message is issued, and the Restore Mission ends NOTOK.

Corrective Action: Check the sysout of the restore job, locate the appropriate DF/DSS or FDR error messages, and solve the problem. After the problem has been solved, rerun the Restore Mission.

RSC694E MISSION `misName` TIMESTAMP=`misTime` FAILED TO OPEN RESTORE UTILITY MESSAGES FILE

Explanation: The restore job executing the specified restore mission was unable to open the messages file of the invoked restore utility.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Check the additional messages issued from the restore job.

RSC695E NO PENDING RESTORE MISSION `misName` TIMESTAMP=`misTime` FOUND IN ACTIVE MISSION FILE

Explanation: The restore job intended for execution of the specified restore mission did not find that mission in the Active Mission file.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

This may occur because the restore mission was removed from the Active Mission file or was reset by the CTDRESET utility before the job finished.

The restore job only prints the restore utility log.

Corrective Action: Check the IOALOG.

RSC696E MISSION `misName` TIMESTAMP=`misTime` FAILED TO OPEN ACTIVE MISSION FILE

Explanation: The restore job executing the specified restore mission was unable to open the Active Mission file.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

The restore job only prints the restore utility log.

Corrective Action: Call your INCONTROL Administrator.

RSC698I RESULT OF MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` IS OK

Explanation: This information message indicates that the restore mission finished successfully.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission

Corrective Action: No action is required.

RSC699E RESULT OF MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` IS NOT OK

Explanation: An error was encountered in the restore mission execution. The detailed description of the error is given in the previous displayed messages.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Check the report of mission execution in the IOALOG and in the output of the restore job.

RSC69DI RESTORED REPORT: ID=`recordId jobname/recipient/report`

Explanation: This information message indicates that backed up (migrated) report is successfully restored in the Active User Reports file.

The variables in this message are:

recordId - the internal database identifier of the report
jobname - the name of the job that created the report
recipient - the user for whom the report was created
report - the name of the report

Corrective Action: No action is required.

RSC69EE FAILED TO RESTORE REPORT: ID=`recordId jobname/recipient/report`

Explanation: The restore job was unable to restore the backed up (migrated) report in the Active User Reports file due to an error in the restore job execution.

The variables in this message are:

recordId - the internal database identifier of the report
jobname - the name of the job that created the report
recipient - the user for whom the report was created
report - the name of the report

The restore mission ends NOTOK.

Corrective Action: Check the output of the restore job.

RSC69FW FAILED TO RESTORE NOTE OF REPORT: ID=`recordIdjobname/recipient/report`

Explanation: The restore job successfully restored the backed up (migrated) report in the Active User Reports file, but was unable to restore the notes of the report due to an error occurred in the restore job execution.

The variables in this message are:

recordId - the internal database identifier of the report
jobname - the name of the job that created the report
recipient - the user for whom the report was created
report - the name of the report

Corrective Action: Call your INCONTROL Administrator.

RSC69HW PENDING MISSION `misName` TIMESTAMP=`misTime` NOT FOUND IN AMF. ONE MORE ATTEMPT WILL BE PERFORMED.

Explanation: The restore job intended for execution of the specified restore mission did not find that mission in the Active Mission file.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

This warning message might be issued because the restore mission was removed from the Active Mission file or was reset by the CTDRESET utility before the job finished.

The restore job only prints the restore utility log. Ten attempts will be performed then message RSC695E will be issued.

Corrective Action: No action is required.

Messages RSCA00 through RSCAxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

RSCA50I MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` WAIT FOR ANOTHER RESTORE/CTDDELRP TO TERMINATE

Explanation: This information message indicates that the restore job executing the misName mission has been suspended until the CTDDELRP utility or another restore job being executed finishes.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission

Corrective Action: No action is required.

RSCA51W MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` NO APPROPRIATE RESTORE REQUEST FOUND ON HIS/MIG FILE

Explanation: The restore job did not find any restore request assigned to the mission being executed.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: No action is required.

RSCA52E MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` FAILED TO UPDATE THE MISSION STATUS. RC=`rc`

Explanation: The restore job failed to update status of the restore mission that it executed.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission
rc - the return code passed back from the program that processed the Active Mission file.

The restore mission remains in RESTORE IN PROCESS status.

Corrective Action: Call your INCONTROL Administrator.

RSCA53E "FE" PRINT SUPPORT ERROR. RETURN CODE `rc`

Explanation: An executing Restore Mission failed to created or update an internal Printing Mission record in the Active User Report file.

When a record with status WAITING FOR PRINT is restored, the Control-D Decollation monitor writes an internal Printing Mission record to indicate that there are reports waiting to be printed by the Printing Mission specified in the DO PRINT parameter. These records are produced with the following key:

X’FE’,C’PRINTMS’,Printing-Mission-Name. rc is the return code from routine CTDXRP.

The Restore Mission restores the reports but terminates with NOTOK status. The restored reports will not be selected by any Printing Mission whose name is specified in Decollation Mission parameter DO PRINT.

Corrective Action: These reports can be manually scheduled for Deferred Printing by using line command P to display the Print Window under option U and then specifying the Printing Mission name. If the problem persists, report the return code to BMC Customer Support.

RSCA53W MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` FAILED IN PRINTING MANAGEMENT. RC=`rc`

Explanation: The restore job successfully restored reports assigned to the executed mission, but failed to assign those of them which have not yet been printed to the corresponding print missions.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission
rc - the return code passed back from the program that manages the print requests.

Corrective Action: Use the CTDBLXRP utility to reset the print requests management.

RSCA54I RSTRESET PROCESSING STARTED

Explanation: This information message denotes the normal start of the RSTRESET Control-D utility.

The RSTRESET utility changes the status of all active restore missions to ENDED NOT OK, and changes the status of all reports selected for restoring to BACKED UP.

Corrective Action: No action is required.

RSCA55I RSTRESET PROCESSING ENDED

Explanation: This information message indicates that the RSTRESET Control-D utility ended normally.

Corrective Action: No action is required.

RSCA56E MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` CANNOT CONTINUE WORKING

Explanation: : This message indicates that due to an error that occurred when processing the User Reports file, the restore job cannot continue. The detailed description of the error is given in the previous displayed message CTD908S.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Call your INCONTROL Administrator.

RSCA57W FAILED TO ASSIGN REPORT FOR PRINTING: ID=`recordIdjobname/recipient/report`

Explanation: The restore job successfully restored the specified report, but failed to assign it to a print mission.

The variables in this message are:

recordId - the internal database identifier of the report
jobname - the name of the job that created the report
recipient - the user for whom the report was created
report - the name of the report

Corrective Action: Use the CTDBLXRP utility to reset the print requests management.

RSCA58S OPEN OF ACTIVE MISSIONS FILE FAILED.

Explanation: The CTDRESET utility has failed to open the Active Mission file.

The utility does not reset reports restore processing.

Corrective Action: Call your INCONTROL Administrator.

RSCA59I RESTORE MISSION `misName` ODATE=`modate` TIMESTAMP=`misTime` IS RESET

Explanation: This information message indicates that the CTDRESET utility successfully reset the pending restore mission.

The variables in this message are:

misName - the name of the restore mission
modate - the original scheduling date of the restore mission
misTime - the time stamp of the restore mission

Corrective Action: No action is required.

RSCA5AI REPORT: ID=`recordIdjobname/recipient/report` IS RESET TO STATUS 'WAIT RESTORE / BACKED UP'

Explanation: This information message indicates that the CTDRESET utility reset the status of the report to WAIT RESTORE or to BACKED UP in correspondence with parameter specified in the utility call.

The variables in this message are:

recordId - the internal database identifier of the report
jobname - the name of the job that created the report
recipient - the user for whom the report was created
report - the name of the report

Corrective Action: No action is required.

RSCA5BI RESTORE RESET PROCESSING TERMINATED

Explanation: Due to a severe error during the execution of the CTDRESET utility, its execution has terminated. The detailed description of the error is given in the previous displayed messages.

The utility did not reset reports restore processing.

Corrective Action: Call your INCONTROL Administrator.

RSCA5CE MISSION `misName` ODATE=`misoDate` TIMESTAMP=`misTime` FAILED TO UPDATE ITS STATUS (SECURITY VIOLATION)

Explanation: The restore mission indicated in the message cannot update its status in the Active Mission file because of a security violation.

The mission remains in status IN PROCESS.

Corrective Action: Perform the following actions:

Run the CTDRESET utility to reset the mission status.
Correct the security rules related to the restore mission job.
Rerun the mission.

RSCA5DE MISSION `misName` ODATE=`misoDate` TIMESTAMP=`misTime` FAILED TO UPDATE ITS STATUS (UPDATE QUEUE OVERFLOW)

Explanation: The restore mission indicated in the message cannot update its status in the Active Mission file because of update queue overflow in the Active Mission file service.

The mission remains in status IN PROCESS.

Corrective Action: Perform the following actions:

Run the CTDRESET utility to reset the mission status.
If the mission ended NOTOK, rerun the mission.

RSCA5EE STATUS OF MISSION `misName` ODATE=`misoDate` TIMESTAMP=`misTime` CANNOT BE RESET (RC=`rc`)

Explanation: where rc is the return code of the Active Mission file service.

Utility CTDRESET cannot reset, in the Active Mission file, the status of the mission indicated in the message.

The mission remains in status IN PROCESS.

Corrective Action: Prepare the IOA LOG and contact BMC Customer Support.

RSCA5FE STATUS OF MISSION `misName` ODATE=`misoDate` TIMESTAMP=`misTime` CANNOT BE RESET (SECURITY VIOLATION)

Explanation: Utility CTDRESET cannot reset the status of the mission indicated in the message because of a security violation.

The mission remains in status IN PROCESS.

Corrective Action: Perform the following actions:

Correct the security rules related to the utility job.
Rerun the utility.

RSCA5QE STATUS OF MISSION `misName` ODATE=`misoDate` TIMESTAMP=`misTime` CANNOT BE RESET (UPDATE QUEUE OVERFLOW)

Explanation: Utility CTDRESET cannot reset the status of the mission indicated in the message overflow because of the update queue in the Active Mission file service.

The mission remains in status IN PROCESS.

Corrective Action: Perform the following actions:

Rerun the utility.
If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.

RST messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages RST400 through RST4xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

RST499I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message indicates that shutdown of the Control-D monitor has been requested.

Shutdown of Control-D internal restore task by request of Control-D main task.

The Control-D monitor shuts down.

Corrective Action: No action is required.

RST49AE CONTROL-D JOB LIBRARY FULL. COMPRESS THE JOB LIBRARY AND RERUN THE MISSION

Explanation: This information message indicates that a restore mission failed to update a job member in the JOB library of Control-D because the library was full.

The restore mission ends with status NOTOK.

Corrective Action: Compress the Control-D JOB library, and rerun the restore mission.

Messages RST600 through RST6xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

RST676I RESTORE MISSION {STARTED | RESTARTED} WITH TIMESTAMP=`misTime`

Explanation: This information message indicates which restore mission is starting (re-starting), and its time stamp.

In this message, misTime is the identity of the restore mission that is starting (restarting).

Corrective Action: No action is required.

RST678I RESTORE MISSION `misName` TIMESTAMP=`misTime` ENDED OK

Explanation: This information message indicates that the restore mission finished OK.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

Corrective Action: No action is required.

RST679E RESTORE MISSION `misName` TIMESTAMP=`misTime` ENDED NOT OK

Explanation: The restore mission finished NOTOK.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

Corrective Action: No action is required.

RST67BI RESTORE `jobId` SUBMITTED WITH TIMESTAMP=`misTime`

Explanation: This information message indicates that the restore job generated by the restore mission was submitted for execution.

In this message:

jobId - the system identifier of the submitted job.
misTime - the identity of the restore mission. It is copied to the generated job.

Corrective Action: No action is required.

RST67CI RESTORE JOB PLACED IN CONTROL-D JOB LIBRARY WITH TIMESTAMP=`misTime`

Explanation: This information message indicates that the restore job generated by the restore mission was placed to the Control-D JOB library.

In this message, misTime is the identity of the restore mission. It is copied to the generated job.

Corrective Action: No action is required.

RST67DI `misNamejobname/recipient` REPORT ID=`recordId` PICKED UP FOR RESTORE. TIMESTAMP=`misTime` NAME=`report`

Explanation: This information message indicates that report requested to be restored is picked up by the misName restore mission.

The variables in this message are:

misName - the name of the mission
jobname - the name of the job that created the report
recipient - the user for whom the report was created
recordId - the internal database identifier of the report
misTime - the time stamp of the mission
report - the name of the report

Corrective Action: No action is required.

RST680E THERE ARE NO RESTORE REQUESTS FOR MISSION `misName` (TIMESTAMP=`misTime`)

Explanation: The started restore mission did not find any report assigned to it.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: No action is required.

RST681E RC=`rc` FROM CTDX011.MISSION `misName` TIMESTAMP=`misTime` TERMINATED

Explanation: This error message indicates that user's Exit program CTDX011 passed back the rc return code to Control-D, which prevents the restore mission from continuing execution.

The variables in this message are:

misName - the name of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Call your INCONTROL Administrator.

RST682E RC=`rc` FROM CTMMEM. MISSION `misName` TIMESTAMP=`misTime` TERMINATED

Explanation: An error preventing a restore mission from continuing execution occurred during the process of Control-D SKL or JOB library.

In this message:

rc - the return code passed back from the program that was processing the library
misName - the name of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Call your INCONTROL Administrator.

RST683E RC=`rc` FROM CTMCND. MISSION `misName` TIMESTAMP=`misTime` TERMINATED

Explanation: An error preventing a restore mission from continuing execution occurred during the process of the condition coded in the restore job skeleton.

In this message:

rc - the return code passed back from the program that was processing the condition
misName - the name of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Call your INCONTROL Administrator.

RST684E SKELETON `sklName` NOT FOUND. MISSION `misName` TIMESTAMP=`misTime` STOPPED

Explanation: The sklName restore job skeleton required by the executing restore mission was not found in the Control-D SKL library.

In this message:

sklName - the name of the restore job skeleton
misName - the name of the restore mission
misTime - the time stamp of the restore mission

The restore mission ends NOTOK.

Corrective Action: Call your INCONTROL Administrator.

RST688I RESTORE TASK STARTED.

Explanation: This information message indicates that Control-D internal restore task has started.

Normal message when a restore task is started.

Corrective Action: No action is required.

Messages RSTI00 through RSTIxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

RSTI01S `pgm` UNABLE TO OPEN FILE `ddName`

Explanation: The pgm program is unable to open the file referenced by the specified DD name.

The ddName file may be missing. This message is accompanied by a system message explaining the cause of the problem.

The program terminates.

Corrective Action: Supply the required DD name if it is missing. Otherwise, see the accompanying system message and take appropriate action.

RSTI02S `pgm` UNABLE TO LOAD `modName`

Explanation: The specified program is unable to load the modName module.

The modName module is probably missing from the IOA Load library.

The program is terminated.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

RSTI03I AJF/CONDITIONS JOURNAL INITIALIZED: BLOCKSIZE `num`

Explanation: This information message indicates that the Control-M Journal file was successfully initialized during New Day processing.

The first record of the Journal file contains information relevant to the Control-M current working day.

In this message, num is the blocksize of the Journal file.

Corrective Action: No action is required.

Messages RSTM00 through RSTMxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

RSTM01W AJF/CONDITIONS JOURNALING TERMINATED - RESTORATION BEYOND THIS TIME NOT POSSIBLE

Explanation: Logging to the journal file was terminated due to a detected error.

This message is preceded by a message indicating the cause of the error.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W, which asks the operator how the monitor should proceed.

Corrective Action: Respond to message CTML12W.

RSTM02I AJF/CONDITIONS JOURNALING STARTED

Explanation: This information message indicates that Control-M started logging updates to the Journal file.

Changes made to the Active Jobs file and to prerequisite conditions in the IOA Conditions file are recorded in the Journal file.

Corrective Action: No action is required.

RSTM03E `text`

Explanation: This message is produced if an abend occurs while Control-M is writing to the Journal file.

The Control-M monitor displays data about the abend, meaning the text in this message.

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

RSTM04I AJF/CONDITIONS JOURNALING CLOSED NORMALLY

Explanation: This information message indicates that Control-M Journaling ended normally.

The Journaling facility was terminated in response to an operator command, or as part of Control-M shutdown.

Corrective Action: No action is required.

RSTM05S AJF/CONDITIONS JOURNALING INITIALIZATION FAILURE

Explanation: The Control-M journaling facility could not be started because the Journal file or another file required for journaling could not be opened.

The above message describes the reason for the problem.

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W, which asks the operator whether to continue without journaling or shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

RSTM06S JOURNAL FILE RECORD 0 FORMAT ERROR

Explanation: The record length of the Control-M journal file was incorrect.

This message is preceded by a message describing the specific cause of the problem.

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W, which asks the operator whether to continue without journaling or to shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

RSTM07S JOURNAL/AJF MISMATCH: FIELD=`fldname`

Explanation: The Control-M Journaling facility could not be started because the specified journal file does not match the Active Jobs file used by the Control-M monitor.

In this message, fldname is the name of the field in the Active Jobs file which does not match the corresponding field in the Journal file.

The Control-M monitor terminates the Journaling facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

RSTM08S GETMAIN FAILURE IN PROGRAM CTMRSTM

Explanation: Sufficient storage could not be obtained for Journal file processing.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W. CTML12W asks the operator to either continue without journaling or shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

RSTM09S BUFFER OVERFLOW ERROR

Explanation: An internal error was detected during Journal file processing.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W. Prepare the Control-M monitor full output and contact BMC Customer Support.

RSTM10S LUW RECORD GENERATION ERROR

Explanation: A error occurred while writing the LUW syncpoint record to the Journal file.

The LUW syncpoint record is the last synchronization point in the Journal file and verifies the completion of all records previously recorded in the Journal file. Without the LUW syncpoint record, records in the Journal file cannot be verified as complete.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

RSTM12E JOURNAL FILE DCB ABEND EXIT INVOKED: SYSTEM CC=X’`sys`’, RC=`rc`

Explanation: An abend occurred while writing to the Journal file.

sys and rc are the system codes and return codes which describe the abend.

The Control-M monitor terminates the Journal facility and displays WTOR message CTML12W.

Corrective Action: Respond to message CTML12W.

RSTM15I AJF/CONDITIONS JOURNALING ACTIVITY SUSPENDED

Explanation: This information message indicates that journaling has been suspended due to New Day processing.

During New Day processing, Control-M always suspends writing to the Journal file.

Journaling is automatically resumed after completion of New Day processing.

Corrective Action: No action is required.

RSTM16I AJF/CONDITIONS JOURNALING ACTIVITY RESTORED

Explanation: This information message indicates that Control-M resumed writing to the Journal file after completing New Day processing.

Corrective Action: No action is required.

RSTM17S AJF/CONDITIONS JOURNAL SEARCH FAILURE

Explanation: An error was encountered during a search of the Control-M Journal file.

During Control-M monitor startup, the journal file is searched for data that may have been added to the Active Jobs File while the Control-M monitor was down.

The Control-M monitor stops journaling and displays WTOR message CTML12W.

Corrective Action: Reply to message CTML12W, which follows.

Messages RSTU00 through RSTUxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

RSTU01I AJF/CONDITIONS RESTORATION STARTED

Explanation: This information message indicates that the CTMRSTR restoration utility has begun processing.

Corrective Action: No action is required.

RSTU02I AJF/CONDITIONS RESTORATION ENDED

Explanation: This information message indicates that the CTMRSTR restoration utility has completed processing.

Corrective Action: No action is required.

RSTU03S AJF/CONDITIONS RESTORATION NOT ENABLED

Explanation: Journaling was not activated because JRNL is set to N in the CTMPARM member in the IOA PARM library. In such a case, the Control-M monitor does not record events in the journal file. Consequently, restoration of the Active Jobs File from the journal file is not possible.

The restoration utility terminates processing.

Corrective Action: To use the restoration utility, the Control-M monitor must be run with the JRNL parameter set to Y in CTMPARM.

RSTU05E INVALID RESTORATION PARAMETER - `parm`

Explanation: An unrecognized parameter was specified for the CTMRSTR utility.

The CTMRSTR utility terminates.

Corrective Action: Correct the specified parameter and rerun the CTMRSTR utility.

RSTU06E INVALID FORMAT OF ENDTIME PARAMETER. "YYYYMMDDHHMMSSTH" EXPECTED

Explanation: An invalid format was used for the value specified for the ENDTIME parameter in the CTMRSTR utility.

The ENDTIME parameter indicates when to restore the Control-M Active Jobs file and/or the IOA Conditions file.

The CTMRSTR utility terminates.

Corrective Action: Correct the value for the ENDTIME parameter and rerun the CTMRSTR utility.

RSTU07S MULTIPLE SPECIFICATION OF INPUT PARAMETER NOT ALLOWED

Explanation: A parameter was specified more than once for a run of the CTMRSTR utility. Each parameter for this utility can be specified only once for each run of the utility.

The CTMRSTR utility terminates.

Corrective Action: Correct the parameters for the CTMRSTR utility and rerun the utility.

RSTU08S NO PARAMETER INPUT DATA FOUND

Explanation: No input parameters were specified for the CTMRSTR utility.

The CTMRSTR utility terminates.

Corrective Action: Specify the necessary parameters following the SYSIN DD statement and rerun the utility.

RSTU09S REQUIRED STORAGE NOT AVAILABLE

Explanation: Insufficient storage is available for the CTMRSTR utility.

The CTMRSTR utility terminates.

Corrective Action: Increase the region size and rerun the utility.

RSTU10W END OF FILE REACHED PRIOR TO SYNCPOINT - LAST ENTRIES IGNORED

Explanation: The last record in the Journal file was not a syncpoint record.

Syncpoint records are used to verify all records added to the Journal file,. Only data records written to the Journal file prior to a syncpoint record are considered valid for restoration. The last syncpoint record is missing (due to an MVS system crash, cancellation of the Control-M monitor, or the like).

Records written after the last syncpoint record are not restored.

Corrective Action: No action is required.

RSTU11I RESTORATION PROCESSING TERMINATED

Explanation: This information message indicates that the CTMRSTR utility ended due to an error. This message follows error messages that describe the error that caused the utility to terminate.

Corrective Action: Consult previous error messages, correct the error if possible, and rerun the restoration job. If CTMRSTR terminated due to a severe error (as indicated by message RSTU12E above), contact BMC Customer Support.

RSTU12E SEVERE PROCESSING ERROR - REASON `rsn`

Explanation: The CTMRSTR utility terminated due to an internal error.

In this message, rsn is the code that indicates the reason for the error.

Corrective Action: Rerun the CTMRSTR utility with DEBUG set to (73:74) as specified in the restoration procedure. Contact BMC Customer Support. Provide the IOA representative with the message, the reason code, and any data produced by the rerun procedure.

RSTU13I RESTORATION PROCESSING COMPLETED SUCCESSFULLY

Explanation: This information message indicates that the CTMRSTR utility completed the restoration successfully. Restoration of the Active Jobs file and/or the IOA Conditions file was successful.

Corrective Action: No action is required.

RSTU14W END OF JOURNAL FILE REACHED BEFORE SPECIFIED TIME LIMIT

Explanation: The ENDTIME parameter for the CTMRSTR utility specified a time value that was older than the last time value found in the Journal file.

The CTMRSTR utility processes all records in the Journal file and execution proceeds normally.

Corrective Action: No action is required.

RSTU15E JOURNAL FILE - AJF MISMATCH: `fldname`

Explanation: The journal used by the CTMRSTR restoration procedure does not match the Active Jobs file used by the Control-M monitor to produce journal records.

In this message, fldname is the field name in the Active Jobs file that did not match the corresponding field in the Journal file.

The CTMRSTR utility terminates.

Corrective Action: Specify the correct Active Jobs file procedure for the CTMRSTR utility and rerun the utility.

RSTU16E JOURNAL FILE - CTMPARM MISMATCH: `fldname`

Explanation: The journal file used by the CTMRSTR restoration utility is not compatible with one of the following parameters specified in the CTMPARM member in the IOA PARM library:

QNAME
the IOA version
the Active Jobs file (AJF) size

In this message, fldname identifies the problematic parameter.

The CTMRSTR utility terminates.

Corrective Action: Specify the correct CTMPARM parameters for the CTMRSTR utility and rerun the utility.

RSTU17E ENDTIME PARAMETER VALUE INCONSISTENT WITH RESTORATION FILE TIMESTAMP

Explanation: The ENDTIME parameter specified a time earlier than the earliest timestamp in the Journal file.

The CTMRSTR utility terminates.

Corrective Action: Specify a value for the ENDTIME parameter which is consistent with the data in the journal file. This value must be later than the most recent New Day processing.

RSTU18I JOURNAL FILE VERIFICATION COMPLETE

Explanation: This information message indicates that the specified Journal file corresponds to the Active Jobs file defined in the CTMRSTR restoration procedure.

The restoration process begins.

Corrective Action: No action is required.

RSTU20E CONDITION RESTORATION ERROR: RC=`rc` REASON=`rsn`

Explanation: The CTMRSTR restoration utility encountered an error while attempting to restore a prerequisite condition.

The error is described in the sysout referenced by the DAPRINT DD statement.

The CTMRSTR utility terminates.

Corrective Action: The message in file DAPRINT describes the cause of the error. If the problem cannot be fixed, notify BMC Customer Support.

RSTU21E CONTROL-M MONITOR IS ACTIVE

Explanation: The CTMRSTR utility could not run because the Control-M monitor was active.

The CTMRSTR restoration utility terminates.

Corrective Action: Shut down the Control-M monitor and rerun the restoration utility.

RSTU22W AJF/CONDITIONS RESTORATION UTILITY WAITING FOR ACTIVE JOBS FILE

Explanation: The restore utility could not access the Active Jobs File because it was being used by another job.

The restoration utility waits until the file is accessible.

Corrective Action: No action is required.

RSTU23E CONTROL-M APPLICATION SERVER GATEWAY IS ACTIVE

Explanation: The restoration utility terminated processing because Control-M Application Server Gateway is active.

Corrective Action: Shut down the Control-M Application Server Gateway and rerun the restoration utility.

RUN messages

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 RUN100 through RUN1xx

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.

RUN100I CONTROL-M MONITOR `monName` STARTED

Explanation: This information message is a general message issued when the identified Control-M monitor (monName) is started.

Corrective Action: No action is required.

RUN101I NEWCONLIST COMMAND ACCEPTED. SUB SYSTEM(S) WILL BE NOTIFIED

Explanation: This information message appears after the operator issued a NEWCONLIST modify command to Control-M.

The Control-M monitor will notify all the console subsystems on all the computers of the required change.

Corrective Action: No action is required.

RUN102E CONTROL-M MONITOR NOT APF-AUTHORIZED

Explanation: The Control-M monitor is not APF-authorized. The CTMRUN module is not in an APF-authorized library, or not with attribute AC set to 1.

The Control-M monitor terminates with a return code of 8.

Corrective Action: Add the library name in which CTMRUN resides to the IEAAPF00 member in SYS1.PARMLIB.

RUN103E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

Explanation: An erroneous parameter was passed to Control-M monitor by an operator modify command (F). A list of valid modify parameters is displayed on the console after this message.

The modify command is rejected.

Corrective Action: Enter a correct modify parameter.

RUN104S BLDL/ATTACH CTMMRUN FAILED FOR TASK `taskName`

Explanation: Initialization of the identified Control-M monitor internal task (taskName) failed.

Possible causes are:

The taskName task is not found in the IOA Load library.
There is insufficient memory for the Control-M monitor.

The exact reason (system code) can be found on the computer log.

Control-M monitor shuts down.

Corrective Action: Call your system programmer for assistance. If necessary, increase the Control-M monitor REGION size.

RUN105S UNRECOVERABLE ERROR ENCOUNTERED

Explanation: Unrecoverable error in the operation of the Control-M monitor.

The IOA Log should contain a previous message concerning the error.

The Control-M monitor will shut down with user abend 0006 or end with a return code of 8.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

RUN106S SUBTASK `subtaskName` HAS ABENDED

Explanation: The Control-M monitor internal subtask subtaskName has abended.

Control-M monitor will shut down with user abend 0006. A dump of the abending task will be included in the output.

This message may be followed by the RUN114E message, which provides more information on the cause of the error.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, prepare the Control-M monitor full output and contact BMC Customer Support.

RUN107I SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message is the Control-M monitor shut down message upon request from the operator.

Control-M monitor shuts down.

Corrective Action: No action is required.

RUN108S INITIALIZATION ROUTINE FAILED. RC= `rc`

Explanation:Highlighted, unrollable message.

Error encountered when initializing the Control-M monitor.

The exact cause of the error is indicated by the return code (rc).

The Control-M monitor shuts down.

Corrective Action: If the return code (rc) is 4, verify that the JES subsystem name as defined in IEFSSNxx is either JES2 or JES3, and that the JESTYPS parameter in the IOAPARM member is either JES2 or JES3.

If the return code is 8, certain load modules are missing from the IOA LOAD library. Restore the original LOAD library.

If the return code is 24, the IOADEST table (the dynamic destination table for group Shout messages) is missing from the IOA PARM library.

RUN109I THE NUMBER OF INTERVALS TO WAIT FOR THE CONTROL-M DAILY IS SET TO `numberIntervals`

Explanation: This information message indicates that after a Control-M monitor issues message CTM113I, it is waiting for the displayed number of Control-M sleeping intervals for the New Day procedure to start executing. If the New Day procedure does not start executing, message CTML03W is issued, followed by message CTML06W.

Corrective Action: No action is required.

RUN111I JOURNAL COMMAND ACCEPTED: `cmd`

Explanation: This information message indicates that a JOURNAL=ENABLE or JOURNAL=DISABLE modify command was accepted. The command is echoed in the message as cmd.

Corrective Action: No action is required.

RUN112I `fileName` SUPPORT NOT ACTIVATED

Explanation: This information message indicates that History/Journal support is not set to Y in the CTMPARM member.

This message is generated in response to a HISTALOC/JOURNAL=ENABLE or HISTALOC/JOURNAL=DISABLE modify command. This command could not be processed because History/Journaling is not enabled.

Corrective Action: Set HIST/JRNL to Y in the CTMPARM member.

RUN113I CONTROL-M MONITOR `monName` NEW DAY PROCEDURE STARTED

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-M monitor has begun performing a number of housekeeping tasks prior to submitting the New Day procedure.

Control-M suspends processing at the time specified in CTMPARM to allow the New Day procedure to run.

The Control-M monitor remains suspended until the New Day procedure is successfully completed. At the successful completion of the New Day procedure, the monitor resumes normal execution.

Corrective Action: No action is required.

RUN114E JOB HANDLED AT TIME OF ABEND: ID=`id` MEMBER=`memName` USER-ID=`userId`

Explanation: A subtask abended.

As a result of the subtask abend, message RUN106S is issued. This message follows RUN106S with additional information. The ID, member name and user ID displayed in the message are from the Master Index file (MIT) that was handled by the subtask when it abended.

This message may be followed by the RUN123E message.

Corrective Action: No action is required.

RUN116S OPEN OF ACTIVE JOBS FILE FAILED - DDNAME "DACKPT"

Explanation:Highlighted, unrollable message.

Open of Control-M Active Jobs file failed (the DACKPT DD statement).

Possible causes are:

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 Control-M monitor will shut down.

Corrective Action: Correct the JCL for the Control-M monitor.

RUN117S ACTIVE JOBS FILE IS BEING FORMATTED NOW

Explanation:Highlighted, unrollable message.

The Control-M monitor was started while the Active Jobs file was being formatted.

The Control-M New Day procedure did not finish formatting the file, either because it (the New Day procedure) is still working, or because it abended. The Control-M monitor cannot be started until the New Day procedure finishes executing successfully.

The Control-M 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-M monitor.

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

If the Control-M New Day procedure is abended, it may be necessary to set all dates in the date control record (the DATREC member in the CTM PARM library) to one day prior to the current day and rerun the New Day procedure. If the procedure ends successfully, you will be able to restart the Control-M monitor.

RUN118S FILE ALLOCATED TO DDNAME "DACKPT" IS NOT THE EXPECTED ACTIVE JOBS FILE

Explanation:Highlighted, unrollable message.

The data set described by the DACKPT DD statement is not the expected Control-M Active Jobs file.

This could 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 Control-M monitor will shut down.

Corrective Action: Correct the JCL for the Control-M monitor.

RUN119S ACTIVE JOBS FILE IS DAMAGED - NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

The contents of the Active Jobs file have been corrupted.

The Active Jobs file is marked as FORMAT during New Day processing, and marked as FREE at successful completion. Currently, the file is not marked as FORMAT, nor as FREE.

The Control-M monitor will shut down.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, call your INCONTROL Administrator.

RUN120I CONTROL-M MONITOR `xxxxxxxx` SHUTTING DOWN

Explanation:Highlighted, unrollable message.

This information message is a Control-M/D message issued when shutting down the Control-M monitor by a P command, or on certain internal Control-M events.

The IOA Log should contain additional messages concerning the reason for shutting down.

The Control-M monitor shuts down.

Corrective Action: No action is required.

RUN121S CONTROL-M MONITOR ENDED WITH ERROR

Explanation:Highlighted, unrollable message.

The Control-M monitor ended with an error.

The IOA Log should contain additional messages concerning the specific error.

The Control-M monitor will shut 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-M monitor again as soon as possible.

RUN122W YOUR CONTROL-M IS ALREADY ACTIVE. QNAME "`qName`"

Explanation:Highlighted, unrollable message.

Someone has attempted to start a Control-M monitor which is already active. Two Control-M monitors with the same QNAME cannot run at the same time.

The newly-started Control-M monitor will shut down.

Corrective Action: No action is required.

RUN123I CONTROL-M INTERVAL IS SET TO `nn.nn` SECONDS

Explanation: This information message is a result of setting a Control-M sleeping interval by an operator command. For more details please refer to the INCONTROL for z/OS Administrator Guide.

Control-M monitor wakes up every nn.nn seconds, and checks what to do.

Corrective Action: No action is required.

RUN124E VALID PARAMETERS FOR KEYWORD `keyword` ARE: `parms`

Explanation: A MODIFY command containing invalid syntax was entered for the Control-M monitor. The message displays the valid parameters.

Corrective Action: Enter one of the parameters displayed in the message.

RUN125I `valid_operator_command`

Explanation: This information message indicates a valid operator command. It is part of the Control-M response to an invalid operator command issued to Control-M.

In response to an invalid command, Control-M issues the RUN103E message, which identifies the error, and a series of RUN125I messages, each containing a valid operator command.

The invalid operator command is ignored.

Corrective Action: Issue a valid operator command.

RUN126I NEW EXIT CTMX004 LOADED

Explanation: This information message indicates successful execution of the CTMX004 operator modify command.

A new Control-M resource acquisition user exit was loaded.

Corrective Action: No action is required.

RUN127I NEWDEST COMMAND ACCEPTED: NEWDEST=`tableName`

Explanation: This information message indicates that a NEWDEST operator command has successfully been passed to the Control-M monitor.

The Control-M monitor replaces the current destination table with the destination table identified in the message (tableName).

Corrective Action: No action is required.

RUN128S OPEN OF DUAL ACTIVE JOBS FILE FAILED-DDNAME "DAALTCKP"

Explanation:Highlighted, unrollable message.

Open of the Control-M Alternate (dual) Active Jobs file failed (the DAALTCKP DD statement).

Possible causes are:

The DAALTCKP DD statement is missing.
The data set described by the DAALTCKP DD statement is not a Control-M Active Jobs file.

This message will be produced only if Control-M is working in dual file mode (selected by setting the DUALDB parameter in the IOAPARM member in the IOA PARM library to Y).

The Control-M monitor shuts down with an error message.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again. If you do not wish to run in dual file mode, correct the Control-M Installation Parameters (IOAPARM).

RUN12AE CONTROL-M EXTENDED MCS INITIALIZATION FAILED. RC=`rc`, MCSOPER RC=`mcs_rc` REASON=`rsn`

Explanation: Initialization of the extended MCS console component of Control-M failed.

Valid values for the first return code in the message are:

Return Code	Explanation
8	Authorization failed
12	Version of operating system not supported
16	The second return code (`mcs_rc`) and the reason code (rsn) from the MCSOPER facility are displayed.
20	The second return code (`mcs_rc`) and the reason code (rsn) from the MCSOPER facility are displayed.
24	Insufficient memory
32	ENQ for the console already held.

All services relying on an extended MCS console function are inoperable.

Corrective Action: Correct the problem according to the return code displayed in the message.

For the meanings of the MCSOPER return and reason codes that are displayed if the first return code is 16 or 20, refer to the MCSOPER macro description in the IBM manual Application Development Reference - Services for Authorized Assembler Language Programs.

Once the cause of the problem has been corrected, bring the Control-M monitor down and up again.

RUN130E SYNTAX ERROR. "QUIESQRES" COMMAND IGNORED

Explanation: The Control-M monitor attempted to evaluate the QUIESQRES command identified in the preceding CTML18I message, but found invalid command syntax.

For a detailed description of the command syntax, see the section on activating and deactivating quiesced quantitative resources in the Control-M chapter of the INCONTROL for z/OS Administrator Guide.

The Control-M monitor ignores the command.

Corrective Action: Enter another QUIESQRES command using valid syntax.

RUN131I NO QUIESCE TIME ASSIGNED TO RESOURCE `resourceName`

Explanation: The following command was given:

F CONTROLM,QUIESQRES=resourceName,DISPLAY|NOW|OFF|hhmm

with the parameter DISPLAY or OFF. However, no QUIESCE time was assigned to the resourceName resource.

Corrective Action: No action is required.

RUN132I NO QUIESCE TIME ASSIGNED TO ANY RESOURCE

Explanation: The following command was given:

F CONTROLM,QUIESQRES=resourceName,DISPLAY|NOW|OFF|hhmm

with the parameter DISPLAY or OFF. However, no resource had a QUIESCE time assigned.

Corrective Action: No action is required.

RUN133I `yyyy-mm-dd hh:mm` QUIESCE TIME ASSIGNED TO RESOURCE `resourceName`

Explanation: This information message displays the action of the Control-M monitor in response to the following command:

F CONTROLM,QUIESQRES=resourceName,DISPLAY|NOW|OFF|hhmm

The date and time assigned in response to this command depend on the setting of the DISPLAY | NOW | OFF parameter, as follows:

DISPLAY - the time that is currently assigned
NOW - the time assigned is the time current at the time the command is processed
hh:mm - the time assigned is the time specified in the command

Corrective Action: No action is required.

RUN183E JOB WAS PUT ON HOLD BY THE AUTOMATIC RECOVERY FEATURE

Explanation:Highlighted, unrollable message.

A job was put into Held status after a subtask abended.

As a result of the abending of the subtask, the RUN114E message is issued. If the MAXJBHLD parameter in the CTMPARM member is set to a value greater than zero, this message is issued following the RUN114E message.

The MAXJBHLD parameter sets the maximum number of jobs that can be put into Held status.

Corrective Action: No action is required.

RUN184E MAXIMUM NUMBER REACHED FOR AUTOMATIC RECOVERY FEATURE - DISABLED

Explanation: A job was previously put into Held status after a subtask abended. As a result of the abending of the subtask, the RUN114E and RUN183E messages are issued.

This message is issued following the RUN183E message if both the following conditions are satisfied:

the MAXJBHLD parameter in the CTMPARM member is set to a value greater than zero
the number of jobs already put into Held status is equal to the value set in the MAXJBHLD parameter

The MAXJBHLD parameter sets the maximum number of jobs that can be put into Held status.

Corrective Action: No action is required.

RUN188W `subtaskName` IS PROCESSING JOB `jobName` ORDID `orderId` FOR MORE THAN `number` MINUTES

Explanation: The subtaskName subtask has been processing the job for an unreasonable amount of time. The task is most likely hung or in a loop.

Possible causes are:

If CPU utilization by the Control-M monitor is not unusually high, most probably the subtask is waiting for completion of a system action (for example, recall of migrated data set), or it may point to a problem in MVS or JES.
If CPU utilization by the Control-M monitor is unusually high, it may indicate a loop (in the base code or in a user exit).

The Control-M monitor continues processing as usual. The subtask continues processing of the indicated job.

Corrective Action: Review the system log for additional messages related to the problem.

If the reason for the problem is unclear, take the system (SVC) dump of the Control-M monitor's address space using the DUMP console command. Specify parameter SDATA=(CSA,GRSQ,SUM,RGN,TRT).

If the problem is outside Control-M, holding the job being processed and restarting the Control-M monitor may have only temporary effect.

Messages RUN200 through RUN2xx

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.

RUN280W OPTIMIZE SUPPORT NOT ACTIVATED

Explanation: A Load-Index-related modify command has been issued but the Control-M Workload Optimization feature is not enabled.

Corrective Action: Enable the Workload Optimization feature by setting the OPTMODE parameter to Y, as discussed in Optimization section in the INCONTROL for z/OS Installation Guide: Customizing.

RUN284I DEST TABLE LOAD SUCCESSFUL: NEWDEST=`tableName`

Explanation: This information message indicates that as a result of an operator NEWDEST command, the Control-M monitor successfully loaded the destination table identified in the message.

Corrective Action: No action is required.

RUN285E NEWDEST PARAMETER MISSING OR INVALID

Explanation: The destination table passed to the Control-M monitor by means of an operator NEWDEST command is invalid or missing.

The specified destination table is not loaded.

Corrective Action: Enter the NEWDEST command specifying a destination table which has been previously defined in a library concatenated to the STEPLIB DD statement of the Control-M procedure.

Messages RUNL00 through RUNLxx

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.

RUNL00I CONTROL-M MONITOR `monName` PROCESSING SUSPENDED

Explanation: This information message indicates that the Control-M monitor has stopped processing jobs temporarily to allow the New Day procedure to begin execution.

Control-M suspends processing at the time specified in CTMPARM to allow the New Day procedure to run.

The Control-M monitor remains suspended until the New Day procedure ends. At the successful completion of the New Day procedure, the monitor resumes normal execution.

Corrective Action: No action is required.

RUNL01I CONTROL-M MONITOR `monName` PROCESSING RESUMED

Explanation: In general, this message indicates that the Control-M monitor resumed processing jobs after the New Day procedure completed successfully. However, under the Control-M monitor operator command /F CTMTROLM,NEWDAY=NOW,ORDERONLY, this message can appear before the Newday procedure ends.

Corrective Action: No action is required.

RUNL02I CONTROL-M MONITOR `monName` NEW DAY PROCESSING COMPLETE

Explanation: This message indicates that all phases of New Day Processing for the specified monitor ended successfully. However, under the Control-M monitor operator command /F CTMTROLM,NEWDAY=NOW,ORDERONLY, this message can appear before the Newday procedure ends.

The Control-M monitor resumes execution.

Corrective Action: No action is required.

RUNL03W NEW DAY PROCEDURE NOT DETECTED

Explanation:Highlighted, unrollable message.

The Control-M monitor received no indication that the New Day procedure began processing.

The Control-M monitor requests the start of the New Day procedure, and periodically checks the progress of the procedure. This message is issued when the monitor does not receive any indication that the New Day procedure started executing.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: No action is required.

RUNL04W NEW DAY END OF AJF FORMATTING NOT DETECTED

Explanation:Highlighted, unrollable message.

The Control-M monitor detected that the formatting of the Active Jobs file (AJF) did not complete successfully within a specified time interval.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: No action is required.

RUNL05W NEW DAY PROCEDURE ERROR - PHASE phase number

Explanation:Highlighted, unrollable message.

During follow-up of the New Day procedure, the Control-M monitor detected an abnormal condition.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: Reply R for retry. If the message is reissued, note the phase number and reply E to terminate the monitor. To reactivate the monitor, run the Control-M New Day procedure, and when it completes successfully, restart the monitor. Give BMC Customer Support the phase number specified in this message and the Control-M monitor full output.

RUNL06W REPLY "R" FOR RETRY OR "E" FOR END

Explanation:Highlighted, unrollable message.

While checking the progress of the New Day procedure execution, the Control-M monitor detected an error.

This message is accompanied by a message explaining the cause of the problem.

The Control-M monitor waits for a reply to this message.

Corrective Action: Type R or E and press Enter, with the following results:

R - the Control-M monitor waits an additional intervalIssue this reply after all problems with the New Day procedure are resolved so that the monitor will resume normal execution.
E - the Control-M monitor stops execution

RUNL07W CONTROL-M MONITOR `monName` WAITING FOR NEW DAY PROCEDURE

Explanation: Normal message of Control-M monitor when it stops processing jobs temporarily to allow the New Day procedure to begin execution.

Control-M suspends processing at the time specified in CTMPARM to allow the New Day procedure to run.

The Control-M monitor remains suspended until the New Day procedure is successfully completed. Upon successful completion of the New Day procedure, the monitor resumes normal execution.

Corrective Action: No action is required.

RUNL08W END OF NEW DAY PROCEDURE NOT DETECTED

Explanation:Highlighted, unrollable message.

Control-M monitor found no indication that New Day procedure completed execution.

The Control-M monitor issues message CTML06W or RUNL06W to ask the operator how to proceed.

Corrective Action: No action is required.

RUNL09E DUAL FILES ALLOCATION ERROR. PROCESSING CONTINUES DUE TO SYSTEM PARAMETERS

Explanation:Highlighted, unrollable message.

Allocation of the dual IOA Conditions file or the dual Active Jobs file (AJF) failed, but processing continues because system parameters have indicated that this condition should be ignored.

Wish WM1944 in the IOADFLTS member of the DOC library was activated to allow an allocation error for dual files to be ignored. (If the wish has not been applied when an allocation error occurs, Control-M terminates execution.)

The Control-M monitor continues normal execution.

Corrective Action: If you require dual file processing, do the following:

Bring down the Control-M monitor.
Determine the cause of the allocation error and correct it
Bring up and reactivate the Control-M monitor.

RUNL0AI RUNL0AI NEWDAY PARAMETERS SET: `expression`

Explanation: This message is issued in response to the following operator command:

F CONTROLM,NEWDAY= expression

Special NEWDAY processing is performed as specified in expression. For more information, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Corrective Action: No response required.

RUNL0BI NEWDAY PROCESS SCHEDULED FOR `hh:mm` WILL BE BYPASSED

Explanation: In response to the F CONTROLM,NEWDAY=SKIP operator command, Newday processing is skipped.

NEWDAY processing normally scheduled to begin at hh:mm is bypassed due to the special NEWDAY command. For more information regarding the special NEWDAY commands, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Corrective Action: No response required.

RUNL0CI NEWDAY PROCESS HAS BEEN BYPASSED

Explanation: This informational message is issued at the time scheduled for Newday processing (according to the DAYTIME parameter in CTMPARM). Newday processing is skipped as a result of one of the following commands:

F CONTROLM,NEWDAY=SKIP
S CONTROLM,NEWDAY=SKIP

Newday processing is skipped. For more information regarding the special NEWDAY commands, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Corrective Action: No response required.

RUNL0DE NEWDAY COMMAND NOT 'SKIP' - IGNORED

Explanation: The S CONTROLM,NEWDAY=expression command was entered with an invalid value of expression. In this command, the only valid value for expression is SKIP. For more information, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

The command is ignored

Corrective Action: Correct and re-enter the NEWDAY command.

RUNL10I RESUME REQUEST ACCEPTED

Explanation: This information message indicates that the RESUME request submitted by the user has been accepted.

Corrective Action: No action is required.

RUNL11W AJF/CONDITION JOURNALING DISABLED

Explanation: The Control-M monitor stopped journaling updates to the Active Jobs file due to a detected error.

The error which caused journaling to be terminated is described in earlier messages.

WTOR message RUNL12W is displayed, enabling the user to continue without the Journal facility or to shut down the Control-M monitor.

Corrective Action: Respond to message CTML12W.

RUNL12W REPLY ‘C’ CONTINUE WITHOUT JOURNALING, ‘I’ INITIALIZE, OR ‘E’ END

Explanation: This WTOR message is displayed when the Control-M Journaling facility is shut down.

This message may be preceded by messages explaining the reason for Journaling facility shutdown. This message also appears after running the restoration utility successfully to provide an opportunity to reset the journal file. The user can run the restoration utility repeatedly (perhaps to different end times) before initializing the journal file.

Responses to this WTOR message allow the user to continue Control-M without journaling, or to shut down Control-M so that a problem can be fixed.

The Control-M monitor waits for a reply to this message.

Corrective Action: See preceding messages for information describing why journaling was stopped.

Specify one of the following values as a response to this message:

C - Continue normal execution without updating the Journal file. Restoration of the Active Jobs file will not include updates made after Journaling was stopped.
I - Re-initialize the journal file. The Control-M monitor continues normal processing, including journaling.
E - Stop execution of the Control-M monitor.

RUNL13I CONTROL-M MONITOR CONTINUING WITHOUT JOURNALING

Explanation: This information message is issued when the user specified C in response to WTOR message CTML12W.

The Control-M monitor continues normal execution. The Journal file is no longer updated.

Corrective Action: No action is required.

RUNL16E COMMAND IGNORED - CURRENT `fileName` STATUS: `fileStatus`

Explanation: The user attempted to enable/disable the Control-M Journal or History allocation for space reuse functions. However, the current fileStatus status of this facility already complies with the user request.

The command is ignored.

Corrective Action: No action is required.

RUNL17I CURRENT ACTIVE JOBS FILE UTILIZATION: `nn%`

Explanation: This information message is issued in conjunction with message CTM863W, which indicates that the Active Jobs file (AJF) is nearly full. Both messages are issued when the threshold value specified by the AJFTHRSH CTMPARM parameter is reached.

Corrective Action: Increase the size of the AJF using the CTMCAJF utility.

RUNL18I COMMAND RECEIVED: `cmd` RUNL18I

Explanation: This information message displays the MODIFY command (cmd) entered for the Control-M monitor.

Corrective Action: No action is required

RUNL19I QUIESTIME IS SET: `yyyy`

Explanation: This information message displays the current value of QUIESTIME (the Control-M monitor planned shutdown time), where yyyy is one of the following values:

hhmm - the planned shutdown time (based on a 24-hour clock) set by the QUIESTIME command
NOW - the submission of any job has been stopped
OFF - all QUIESTIME requests have been cancelled

This message is added to the System Log.

Corrective Action: No action is required.

SAR messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages SARM00 through SARMxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SARM40E {CA-View | CA-DISPATCH} CONVERSION - TAPE I/O ERROR `text` (78 chars max)

Explanation: An I/O error occurred while the report was being read from the archive tape.

Creation of the CDAM report file is halted.

Corrective Action: Analyze the message to determine the reasons for the I/O error. If possible, use external means for recovery. If recovery is completed successfully, run the restore job again.

SARM41E {CA-View | CA-DISPATCH} CONVERSION - REPORT NOT FOUND `reportName`, JOB: `jobName` (`job_num`), DATE: `date`, TIME: `time`

Explanation: The requested report could not be located in the tape.

The CA-VIEW (SAR) archive directory indicates that the report resides on a specific tape, but the report could not be located on that tape.

The restore request for the report is denied.

Corrective Action: Investigate the CA-VIEW (SAR) archive for potential corruption, or locate the report on other tapes.

SARM42E {CA-View | CA-DISPATCH} CONVERSION - COULD NOT OPEN TAPE WITH FILE `dsn`

Explanation: The report restore program could not open the tape that hold the archive reports.

The CA-VIEW (SAR) archive directory indicates that the report resides on a specific tape, but the report could not be located on that tape.

The request to restore the report is denied.

Corrective Action: Investigate the CA-VIEW (SAR) archive for potential corruption, verify that the tape is not damaged, or locate the report on other tapes.

SARM43E {CA-View | CA-DISPATCH} CONVERSION - COULD NOT CREATE CDAM DATASET

Explanation: The restore report could not be written to the CDAM subsystem.

An error occurred while the report was being restored to a CDAM file.

The request to restore the report is terminated.

Corrective Action: Check the CDAM subsystem and its allocation parameters to ensure that the CDAM subsystem can accept new files.

SARM44E {CA-View | CA-DISPATCH} CONVERSION - CDAM FILE `dsn` CREATED

Explanation: This information message indicates that a CDAM file was successfully created to satisfy the restore request.

The restored report is ready for insertion in the Active User Reports file.

Although the message code ends with E, this message does not indicate that an error occurred.

Corrective Action: No action is required.

SARM45E INFOPAC CONVERSION - REPORT NOT FOUND `reportName`, FILE: `dsn`

Explanation: The report that was requested cannot be located on the tape.

The RESTORE request for the report is rejected.

Corrective Action: Do the following:

Check if the correct INFOPAC archive volume was mounted.
If the correct tape was mounted, examine the tape for possible corruption.

SCD messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages SCD200 through SCD2xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SCD201I CONTROL-D SCHEDULER STARTED

Explanation: This information message indicates that the Control-D monitor internal scheduler task started.

Normal message when Control-D monitor is started.

Corrective Action: No action is required.

SCD202S INSUFFICIENT MEMORY FOR CONTROL-D MONITOR

Explanation: Insufficient memory for the initiation of Control-D monitor.

Control-D monitor will shut down.

Corrective Action: Increase the Control-D monitor region size.

SCD203I ELIGIBLE FOR PROCESSING

Explanation: This information message indicates that the mission has been given permission to run.

All the runtime conditions for mission execution have been met, and all the resources have been acquired for the mission. The mission will soon be executed by Control-D.

Corrective Action: No action is required.

SCD204E OUTPUT CONDITION `condname_date` NOT ADDED/ DELETED - SECURITY VIOLATION

Explanation: User is not authorized to add or delete the condition condname_date to or from the conditions file. The date is in mmdd format.

The mission definition contains an OUT statement or a DO COND statement (or both) for the referenced condition. The condition was not added or deleted because the user ID of the mission is not authorized to add or delete the condition.

Output condition is not added or deleted, but processing continues.

Corrective Action: Consult your INCONTROL administrator.

SCD208I PROCESSING ENDED "OK"

Explanation: This information message indicates that the mission finished executing OK.

Control-D determined that the mission ended OK because other events were marked OK in the mission’s parameters, and no other event was either unexplained or marked NOTOK.

Corrective Action: No action is required.

SCD218I RECYCLED FOR POSSIBLE REPROCESSING

Explanation: This information message indicates that the cyclic task was recycled for possible execution.

If all runtime conditions are met, the mission will be immediately eligible.

Corrective Action: No action is required.

SCD219I PROCESSING ENDED "NOT OK"

Explanation: This information message indicates that the Control-D monitor determined that the mission ended NOTOK.

The general Control-D message when a mission finishes executing NOTOK. The IOA Log should contain prior messages detailing the reasons.

Corrective Action: No action is required.

SCD220I `missionType missionName` WILL BE REPROCESSED

Explanation: This information message is issued because a manual request to rerun a mission was accepted.

The mission will be placed in WAIT SCHEDULE state again. If all runtime conditions are met, the mission will be started immediately.

Corrective Action: No action is required.

SCD229S OPEN FAILED FOR DDNAME "DARES"

Explanation: Open of a debugging output file failed (the DARES DD statement).

This is probably because the DARES DD statement is missing in the Control-D procedure.

The Control-D monitor will shut down with error message.

Corrective Action: Correct the JCL for the Control-D monitor procedure and start it again.

SCD230S OPEN FAILED FOR DDNAME "DARESC" OR "DASINC"

Explanation: Open of IOA Conditions file failed (the DARESC or DASINC DD statement).

Possible causes are:

The DARESC DD statement is missing.
The DASINC DD statement is missing.
The data set described by the DARESC DD statement is not the IOA Conditions file.
The data set described by the DASINC DD statement is not the IOA Conditions synchronization file.
The data set described by the DARESC DD statement is the IOA Conditions file, but it is of a different version or of a different Control-D monitor.

Control-D monitor shuts down with error message.

Corrective Action: Correct the JCL for the Control-D procedure, and start the procedure again.

SCD231E REP Q23AREP1 MISSION IS NOT PROCESSED BECAUSE OF CONDITION ERROR

Explanation: The mission was not processed because an error which was detected for an IN condition. See the corresponding error message in Screen 5. The status of this condition is unknown and this mission is not processed, but processing continues.

Corrective Action: Consult your INCONTROL administrator.

SCD241W OUTPUT CONDITION `cond_date` NOT UPDATED - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

No more space to add output conditions to the conditions file. The date is in mmdd format.

The record for that specific day of the month is full. For example, if a condition with date reference of January 3rd cannot be added, an entry in the Conditions file that contains conditions for January 3rd, February 3rd, March 3rd, and so on, is full.

The condition is not added, and a highlighted message is displayed on the operator console. Control-D continues to function, but missions that depend on the condition are not submitted.

Corrective Action: Immediate action:

Enter Control-D Online Facility Resource Map (screen 4). By changing the date range limit, look for conditions with the same day (but of a different month) as the condition that could not be added, and delete them manually - providing that they are not needed.
Add the failing condition manually in order to maintain production flow.
Report the event to your system programmer.

Long term action:

You should run the IOACLCND Control-M utility more often.
You may want to increase the record length of the IOA Conditions file. For more information on how to do this, see the section on expanding IOA files in the INCONTROL for z/OS Administrator Guide.

SCD249I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message announces the shutdown of the Control-D monitor.

Shutdown of Control-D internal selector task by request of Control-D main task.

The Control-D monitor will shut down.

Corrective Action: No action is required.

Messages SCDA00 through SCDAxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SCDA95E VALUE OF CNDREC# PARAMETER IN IOAPARM IS NOT EQUAL TO ACTUAL FILE SIZE

Explanation: The CNDREC# parameter in IOAPARM has been changed but the IOA Conditions file has not been rebuilt.

A difference was detected between the length of the IOA Conditions file and the length specified in the IOAPARM member of the PARM library.

This is usually due to using the IOAPARM member (read from the IOA Load library) for the wrong monitor.

The monitor shuts down.

Corrective Action: To correct this situation, do one of the following:

Rebuild the IOA Conditions file, so that its length is as specified in IOAPARM.
Modify the CNDREC# parameter in IOAPARM so that its length is the length of the existing IOA Conditions file.

After correcting the problem, restart the monitor.

SEL messages

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 SEL100 through SEL1xx

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.

SEL15CI `memName`... THE MEMBER HAS BEEN COPIED INTO OVERLIB `lib`

Explanation: The memName member has been copied from the MEMLIB library into the OVERLIB library, because the COPMEM20 installation parameter was set to Y.

Corrective Action: No action is required.

SEL15CW `memName`... THE MEMBER HAS NOT BEEN COPIED INTO OVERLIB. REASON: `rc-rsn`. LIBRARY: `lib`

Explanation: Although the COPMEM20 Control-M installation parameter was set to Y, Control-M failed to copy the memName member into the OVERLIB library.

The variables in this message are:

memName - the name of the member that was not copied
rc - the return code from the IOAMEM program
rsn - the reason code from the IOAMEM program
lib - the name of the OVERLIB library

For explanation of the values of rc and rsn, see the description of the IOAMEM Assembler Macro in the INCONTROL for z/OS Administrator Guide.

Corrective Action: Take corrective action on the basis of the values of rc and rsn.

SEL15DI `memName`... THE MEMBER HAS BEEN DELETED FROM OVERLIB `lib`

Explanation: The memName member has been deleted from the lib OVERLIB library, because either the DELOVRER or the DELOVRUN Control-M installation parameter was set to Y.

Corrective Action: No action is required.

SEL15DW `memName`... THE MEMBER HAS NOT BEEN DELETED FROM OVERLIB. REASON: `rc-rsn`. LIBRARY: `lib`

Explanation: Although either the DELOVRER or the DELOVRUN Control-M installation parameter was set to Y, Control-M failed to delete the memName member from the OVERLIB library.

The variables in this message are:

memName - the name of the member that was not deleted
rc - the return code from the IOAMEM program
rsn - the reason code from the IOAMEM program
lib - the name of the OVERLIB library

For explanation of the values of rc and rsn, see the description of the IOAMEM Assembler Macro in the INCONTROL for z/OS Administrator Guide.

Corrective Action: Take corrective action on the basis of the values of rc and rsn.

Messages SEL200 through SEL2xx

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.

SEL201I SELECTOR STARTED

Explanation: This information message is issued when Control-M is started and indicates that the Control-M monitor internal selector task has started.

Corrective Action: No action is required.

SEL202S INSUFFICIENT MEMORY FOR CONTROL-M MONITOR

Explanation:Highlighted, unrollable message.

Insufficient memory for the initiation of Control-M monitor.

Control-M monitor will shut down.

Corrective Action: Increase the Control-M monitor region size.

SEL203I `taskType memName jobName/jobId` OID=`orderId` ELIGIBLE FOR RUN

Explanation: This information message indicates that the job/started task has been given permission to run.

All the runtime conditions for job submission have been met, and all the resources have been acquired for the job. The job will soon be submitted by Control-M.

Corrective Action: No action is required.

SEL204E `taskType memName jobName/jobId` OID=`orderId` OUTPUT CONDITION `condNameDate` NOT ADDED/ DELETED - SECURITY VIOLATION

Explanation: User is not authorized to add/delete the condition condNameDate to/from the conditions file. The date is in mmdd format.

The job definition contains OUT statements or ON STEP/DO COND statements (or both) for the referenced condition. The condition was not added/deleted because the user ID of the job order is not authorized to add or delete the condition.

Output condition is not added/ deleted, but processing continues.

Corrective Action: Consult your INCONTROL administrator.

SEL205I OID=`orderId` RERUN IN PROCESS USING MEMBER `memName`

Explanation: This information message indicates that a DO RERUN instruction has been activated.

An event which requires a rerun has been triggered. Control-M will place the job again in wait schedule state. If all the runtime conditions are met the job will be submitted immediately.

Corrective Action: No action is required.

SEL206W `taskType memName jobName /jobId` OID=`orderId` ABENDED CC `abCode` STEP `pgmStep /procStep`

Explanation: The job abended with abend code abCode in step pgmStep/procStep.

Corrective Action: No action is required.

SEL207E `taskType memName jobName /jobId` OID=`orderId` NOT SUBMITTED. REASON `rsn`

Explanation: Submission of job failed for the reason identified in the message.

Valid values for rsn are:

rsn	Explanation
CANCL	Submission cancelled by user exit or by the AutoEdit Facility.
ERAJF	Error while reading the jobs dsn list from the AJF.
GETER	Error while reading the job from the JCL library.
INUSE	The JCL library is allocated exclusively to another task (DISP=OLD). The Control-M monitor tries to repeat the processing according to the INUSE#WI and INUSE#RT parameters. For information about these parameters, see the INCONTROL for z/OS Installation Guide.
NOARC	Restart was requested, but the archived sysout of the job could not be accessed.
NOJOB	A job statement was not found in the member.
NOLIB	Problem with access to the JCL library.
NOMEM	Member not found in the library.
WRITE	Write error while writing a line to the JES internal reader.

Look for more details in the previous log messages of this job.

Corrective Action: No action is required.

SEL208I `taskType memName jobName/jobId` OID=`orderId` ENDED "OK" RUN-NO=`<run number>`

Explanation: This information message indicates that a job finished executing OK. The Control-M run number is incremented each time a cyclic task is executed or a job is rerun.

The job ended successfully in one of the following ways:

The job ended with a condition code from 00 through 04, which is the Control-M default for ended OK.
Other events were marked OK in the production parameters and no event was unexplained or marked NOTOK.
If text is FORCED OK, the job was terminated upon request and therefore marked as ended OK.
If text is CLEANUP, the run was a Control-M/Restart Cleanup run.
If text is (DUMMY JOB), the job that was run was a Control-M dummy job.

For more information, see the Control-M for z/OS User Guide.

Corrective Action: No action is required.

SEL209E `taskType memName jobName/jobId` OID=`orderId` SYSOUT DISAPPEARED

Explanation: The job sysout disappeared. The Control-M monitor could not check the sysout to analyze job execution results.

Possible causes are:

Someone purged the output of the job before the Control-M monitor was able to read it.
Someone released the job from Held status and the job was printed before the Control-M monitor was able to read it.
In the case of a started task, if the JES parameters signify that the STCMCLAS is not to be printed, then sysouts of STCs will always disappear.

The job finishes executing NOTOK, and the code JLOST is used to describe the event.

Corrective Action: Check the exact reason for the disappearance of the job and try to prevent it from happening again. See a description of sending a job to a held output class in the INCONTROL for z/OS Installation Guide, and sending a job SYSDATA to a held output class in the INCONTROL for z/OS Administrator Guide for additional considerations regarding the Control-M held class.

SEL20AE ERROR IN CTMPPE RC=`rc`, INFORM YOUR IOA ADMINISTRATOR

Explanation: An internal error was detected in MAINVIEW Batch Optimizer (MVBO) support.

Control-M ends with an error and shuts down.

Corrective Action: Perform the following steps:

Activate debug level 75.
Restart the Control-M monitor.
Recreate the error.
Send full output of the Control-M monitor to your INCONTROL Administrator.

SEL20BE OID=`orderId`, MAXIMUM PIPES IN COLLECTION EXCEEDED (255), PIPES IGNORED

Explanation: Too many pipes were specified for the collection or the job added too many pipe definitions to the collection.

This message is issued by Control-M. This message may occur if:

The job definition includes more than 255 pipe definitions.
The collection contains the maximum number of pipes and the job tries to add additional pipe definitions.

The pipe definitions in the job (and in other jobs belonging to the same collection) will be ignored.

Corrective Action: Ensure that no more than 255 pipes are defined in the collection.

SEL20CI `taskType memName jobName/ jobId` OID= `orderId` FOLLOWING IGNORED DUE TO BYPASS REQUEST: `list-of-definitions-that-will-be-ignored`

Explanation: This information message indicates that the Control-M monitor has accepted a request to bypass some selection criteria and/or post-processing actions.

Corrective Action: No action is required.

SEL20DI `taskType memName jobName/ jobId` OID= `orderId` WORKLOAD `workloadPolicyName` JOBS UTILIZATION IS NOW `workloadPolicyUtilization` (LIMIT=w`orkloadPolicyLimit`)

Explanation: This information message indicates the concurrent jobs limit and the currently active jobs count for every Workload Policy that is associated with this job. LIMIT=N/A means that the Workload Policy is active but is not currently limiting job execution.

Corrective Action: No action is required.

SEL20EI `taskType memName jobName/ jobId` OID= `orderId` WORKLOAD `workloadPolicyName` RESOURCE `resourceName` JOBS UTILIZATION IS NOW `workloadPolicyUtilization` (LIMIT=w`orkloadPolicyLimit`)

Explanation: This information message indicates the resource quantity limit and the current resource utilization for every Workload Policy that is associated with this job. LIMIT=N/A means that the Workload Policy is active but is not currently limiting the use of the resource.

Corrective Action: No action is required.

SEL210E `taskType memName jobName/jobId` OID=`orderId` NOT RUN- JCL ERROR

Explanation: Job not run because of a JCL error.

The job failed on JCL before execution.

The code JNRUN is used to describe the event.

Corrective Action: Correct the JCL for the job and rerun it.

SEL211W `taskType memName jobName/jobId` OID=`orderId` FAILED- JCL ERROR IN STEP `pgmStep/procStep`

Explanation: Job failed on JCL error during execution in step pgmStep/ procStep.

The code JFAIL is used to describe the event.

Corrective Action: Correct the reason for the failure and rerun the job if necessary.

SEL212W `taskType memName jobName/jobId` OID=`orderId` UNEXPLAINED COND CODE: `code`

Explanation: Job failed because of unexplained condition code in one of the job’s steps.

Job ended with a condition code of code greater than 04 which is not referred to in the CODES parameter as OK.

Corrective Action: No action is required.

SEL213W `taskType memName jobName/jobId` OID=`orderId` FAILED REASON UNKNOWN. CC `problem_code` STEP `pgmStep/procStep`

Explanation: Job failed with problem code problem_code in step pgmStep/procStep for an unknown reason.

The code *UKNW is used to describe this event.

Corrective Action: If this message is issued for all jobs, ensure that the OUT180 DD statement is still in the Control-M monitor procedure.

SEL214I OID=`orderId` RERUN NEEDED

Explanation: This information message indicates that a DO RERUN instruction has been activated.

Control-M detected an event which requires a rerun. The rerun attempt will be performed according to Control-M production parameters: RERUNMEM, MAXRERUN and INTERVAL.

Corrective Action: No action is required.

SEL215W OID=`orderId` NO (MORE) RERUNS

Explanation: The number of reruns specified in the MAXRERUN parameter has been exhausted.

An automatic rerun will not be performed. You can still rerun the job manually.

Corrective Action: No action is required.

SEL216W `taskType memName jobName/jobId` OID=`orderId` UNEXPLAINED COND CODE `condCode` STEP `pgmStep/procStep`

Explanation: An unexplained condition code (condCode) has been returned in relation to the pgmStep/procStep step.

The job ended with a condition code (condCode) that was greater than 04, and the condition code and pgmStep/procStep are not referred to in the CODES parameters of the job production data as OK.

Corrective Action: No action is required.

SEL217W `taskType memName jobName/jobId` OID=`orderId` FAILED- JCL ERROR (AFTER UNEXPECTED COND CODE: `code`)

Explanation: Job failed on JCL error during execution, while a previous step ended with a “bad” condition code.

This usually represents a situation where a file which should have been created in the previous step is not found (meaning that a JCL error has occurred), because the previous step failed (bad cc).

The code JFAIL is used to describe the event.

Corrective Action: No action is required.

SEL218I `taskType memName jobName/jobId` OID=`orderId` RECYCLED FOR POSSIBLE EXECUTION `text`

Explanation: This information message indicates that the cyclic task was recycled for possible execution.

If all runtime conditions are met, the job/STC will be submitted/started immediately.

This is the general Control-M message when a cyclic task is recycled for possible execution.

If text is AFTER CLEANUP, the run was a Control-M/Restart Cleanup run.

Corrective Action: No action is required.

SEL219I `taskType memName jobName/jobId` OID=`orderId` ENDED "NOT OK" RUN-NO=`<run number>`

Explanation: This information message indicates that the Control-M monitor determined that the job ended NOTOK.

This is the general Control-M message when a job finishes executing NOTOK. The IOA Log file should contain prior messages detailing the reasons. The Control-M run number is incremented each time a cyclic task is executed or a job is rerun.

The job ended unsuccessfully in one of the following ways:

The job ended with a condition code greater than 04 which is the Control-M default for ended NOTOK.
Other events were marked NOTOK in the production parameters or some event was unexplained and marked NOTOK.
If text is FORCED OK, the job was terminated upon request and therefore marked as ended OK.
If text is CLEANUP, the run was a Control-M/Restart Cleanup run.

See the Control-M for z/OS User Guide for more information.

Corrective Action: No action is required.

SEL220I `taskType memName jobName/jobId` OID=`orderId` WILL BE RERUN

Explanation: This information message is issued because a manual request to rerun a job/STC was accepted.

The job/STC will be placed in WAIT SCHEDULE state again. If all runtime conditions are met, the job/STC will be submitted/started immediately.

Corrective Action: No action is required.

SEL221I OUTPUT CONDITION `cond` WAS `func` BY THE ON CONTROL-M CMEM FACILITY

Explanation: This information message indicates that the Control-M On Spool Jobs Facility added or deleted a prerequisite condition.

Corrective Action: No action is required.

SEL223I OID=`orderId` JOB `jobName` MAXRERUN LIMIT REACHED

Explanation: This information message indicates that the last run of a cyclic job ended.

Control-M resubmits each cyclic job for execution until it has run the number of times defined by MAXRERUN in the job definition.

Corrective Action: No action is required.

SEL224I CYCLING STOPPED BY "DO STOPCYCL" STATEMENT

Explanation: This information message indicates that a cycling of a cyclic task, cyclic job, or cyclic Started task, stopped as a result of the execution of a DO STOPCYCL statement.

Corrective Action: To reactivate the cycling, rerun or restarting the cyclic task.

SEL225I `taskType memName jobName/jobId` OID=`orderId` DO FORCEJOB `table /job` ALREADY PERFORMED

Explanation: This information message indicates that Control-M did not execute the DO FORCEJOB request even though the corresponding ON PGMST condition was satisfied. This happens when a job is RESTARTed, the corresponding DO FORCEJOB was already performed during original job run (or one of following RESTARTs) and the Control-M/Restart installation parameter FORCONCE is specified as Y (Yes).

Corrective Action: No action is required.

SEL229S OPEN FAILED FOR DDNAME "DARES"

Explanation: Open of a debugging output file failed (the DARES DD statement).

This is probably because the DARES DD statement is missing in the Control-M procedure.

Control-M monitor will shut down with error message.

Corrective Action: Correct the JCL for the Control-M monitor procedure and start it again.

SEL230S OPEN FAILED FOR DDNAME "DARESF"

Explanation: Open of Control-M Resources file failed (the DARESF DD statement).

Possible causes are:

The DARESF DD statement is missing.
The data set described by the DARESF DD statement is not the Control-M Resources file.
The data set described by the DARESF DD statement is the Control-M Resources file of a different version or a different Control-M monitor.

Control-M monitor shuts down.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again.

SEL231S OPEN FAILED FOR DDNAME "DARESFJNL"

Explanation: Open of Control-M Resources journal file failed (the DARESFJNL DD statement).

Possible causes are:

The DARESFJNL DD statement is missing.
The data set described by the DARESFJNL DD statement is not the Control-M Resources journal file.
The data set described by the DARESFJNL DD statement is the Control-M Resources journal file of a different version or a different Control-M monitor.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again.

SEL241W `taskType memName jobName /jobId` OID=`orderId` OUTPUT CONDITION `condNameDate` NOT UPDATED - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR

Explanation: Highlighted, unrollable message.

No more space to add output conditions to the conditions file. The date is in mmdd format.

The record for the specified day of the month is full. For example, if a condition with date reference of January 3 cannot be added, then an entry in the conditions file that contains conditions for the third day of every month is full.

The condition is not added, and a highlighted message is displayed on the operator console. Control-M continues to function, but the jobs that depend on the condition are not submitted.

Corrective Action: Immediate actions:

Enter the Control-M Online Facility Resource Map (screen 4). By changing the date range limit, find conditions with the same day (but a different month) as the condition that could not be added, and manually delete those that are not needed.
Add the failing condition manually, to maintain production flow.
Report the event to your system programmer.

Long term actions:

Run the IOACLCND Control-M utility more often.
Increase the record length of the IOA Conditions file. For more information on how to do this, see the description of expanding IOA files in the INCONTROL for z/OS Administrator Guide.

SEL244S OPEN OF DD NAME "DAALTRES" AND/OR "DAALTSNC" FAILED. DUAL RESOURCE FILE IS NOT AVAILABLE.

Explanation: Open of IOA alternate (dual) Conditions file (the DAALTCND DD statement) failed.

Possible causes are:

The DAALTCND DD statement is missing.
The DAALTSNC DD statement is missing.
The data set described by the DAALTCND DD statement is not an IOA Conditions file.

This message will be produced only if Control-M is working in dual file mode (indicated in IOAPARM).

The Control-M monitor will shut down with an error message.

Corrective Action: Correct the JCL for the Control-M procedure, and start it again. If you do not wish to run in dual file mode, correct the Control-M Installation Parameters (IOAPARM).

SEL249I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message announces the shut down of the Control-M monitor.

Shut down of Control-M internal selector task by request of Control-M main task.

The Control-M monitor will shut down.

Corrective Action: No action is required.

SEL250I CONDITION cond {DELETED | ADDED}: RUNNUMBER=num

Explanation: This information message indicates that a condition has been added or deleted by Control-M as the result of job processing options.

This message is issued at sites where the MSEL250I parameter is set to Y. For more information, see the section on customizing Control-M in the INCONTROL for z/OS Installation Guide.

The variables in this message are:

cond - the condition that was added or deleted
num - the run number

The program adds or deletes the cond condition.

Corrective Action: No action is required.

SEL251S ENQ FAILED FOR FILE DARESF

Explanation: ENQ of the Control-M Resources file failed. The file is probably enqueued by another process that is not releasing it.

The Control-M monitor does not start or stop running.

Corrective Action: Cancel the address space of the process that is not releasing the Control-M Resources file. Control-M must access this file.

SEL252S INIT FAILED FOR FILE DARESF

Explanation: The Control-M monitor failed to initialize the Control-M Resources file. The reason appears in the accompanying message.

The Control-M monitor does not start.

Corrective Action: Use the information in the accompanying message to correct the cause of the failure.

SEL253I OID=`orderId` JOB IS HOLDING `num` UNITS OF RESOURCE `quantResource`

Explanation: This information message indicates that a job got control of the specified number (num) of quantResource Quantitative resources.

When a job is ready to run, the system gives it the resources it requested.

The variables in this message are:

orderId - the order ID of the job
num - the specified number of units
quantResource - the name of the Quantitative resource

The system reduces the number of available units of this resource until the job finishes and the resources become available again.

Corrective Action: No action is required.

SEL254I OID=`orderId` JOB RELEASED `num` UNITS OF `quantResource`

Explanation: This information message indicates that a job released the specified quantity (num) of quantResource Quantitative resources.

When a job finishes, it releases the resources it used.

The variables in this message are:

orderId - the order ID of the job
num - the specified number of units
quantResource - the name of the Quantitative resource

The system returns the resources the job used to the list of available resources.

Corrective Action: No action is required.

SEL255I OID=`orderId` JOB ACQUIRED CONTROL `contResource` MODE {E | S | R}

Explanation: This information message indicates that a job got control of the contResource Control resource in the specified mode (Exclusive, Shared, or Requested).

The variables in this message are:

orderId - the order ID of the job
contResource - the name of the Control resource

Corrective Action: No action is required.

SEL256I OID=`orderId` JOB RELEASED CONTROL `contResource` MODE {E | S | R}

Explanation: This information message indicates that a job released the contResource Control resource that was held in the specified mode (Exclusive, Shared, or Requested).

When a job finishes, it releases the resources it used.

The variables in this message are:

orderId - the order ID of the job
contResource - the name of the Control resource

Corrective Action: No action is required.

SEL259I JOB DECREASED `num` UNITS FROM RESOURCE `resourceName` DEFINITION

Explanation: This information message indicates that the job ENDED OK, and according to its definition, Control-M decreased the value of the resourceName quantitative resource by num units.

Corrective Action: No action is required.

SEL286I OID=`orderId` WAITING FOR CONFIRMATION

Explanation: This information message indicates the job is eligible to be run by Control-M, but the job is waiting for manual restart decision confirmation.

The job has a status of WAIT CONFIRMATION. For the job to run, the user must confirm that this job can be restarted. For information about the CONFIRM command, see the Control-M for z/OS User Guide.

Corrective Action: No action is required.

SEL28TE CNDJNL FILE SIZE DOES NOT MATCH CND FILE SIZE -- JOURNALING DISABLED

Explanation: The size of the IOA Conditions base image file differs from the size of the production Conditions file.

The IOA Conditions base image file CNDJNL is created after New Day processing and is used by the CTMRSTR restore utility. The size of this file must be identical to that of the production Conditions file.

The Control-M monitor deallocates the file and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W.

SEL28UE RESJNL FILE SIZE DOES NOT MATCH RES FILE SIZE -- JOURNALING DISABLED

Explanation: The size of the Control-M Resource file base image file differs from the size of the production Resource file.

The Control-M Resource file RESJNL is created after New Day processing and is used by the CTMRSTR restore utility. The size of this file must be identical to that of the production Resource file.

The Control-M monitor deallocates the file and waits for instructions as described in message CTML12W.

Corrective Action: Reply C, I, or E to message CTML12W.

SEL28VE FILE `fileName` DEALLOCATED. RESIZE FILE AND USE JOURNAL=ENABLE COMMAND TO REALLOCATE

Explanation: This message accompanies message CTM921E, CTM287E, or CTM288E and indicates that the problematic base image file has been deallocated.

Corrective Action: Define a file of correct size matching the corresponding production file and use the ENABLE command to allocate the new file to the Control-M monitor.

Messages SELC00 through SELCxx

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.

SELC60I QUANTITATIVE RESOURCE `resourceName` action

Explanation: This information message displays the results of a DO RESOURCE action in a Control-O rule. The quantitative resource has been added, deleted, or changed in the Control-M Resources file.

Corrective Action: No action is required.

SELC61I QUANTITY OF RESOURCE `resourceName` CHANGED `old_qty ===> {+ | -} delta_qty`

Explanation: This information message displays the results of a Control-O DO RESOURCE request. The quantity of resource is increased (+) or decreased (-) from old_qty by the amount in delta_qty. If no sign is indicated, the quantity has been set to the amount specified in delta_qty.

The variables in this message are:

resourceName - the name of the resource
old_qty - the original quantity
delta_qty - the amount increased or decreased

Corrective Action: No action is required.

SELC62E QUANTITATIVE RESOURCE `resourceName` TO BE CHANGED DOESN’T EXIST

Explanation: The quantitative resource resourceName which was specified in a Control-O DO RESOURCE action does not exist in the Control-M Resources file.

Someone may have deleted the quantitative resource from the Control-M Resources file or it may never have been added.

Corrective Action: Scan the IOA Log to see why the resource may have been deleted. Check that the syntax of the resource in the Control-O DO RESOURCE action is correct.

SELC63E CANNOT ADD QUANTITATIVE RESOURCE `resourceName`. FILE IS FULL

Explanation: The quantitative resource resourceName specified in a Control-O DO RESOURCE action, cannot be added to the Control-M Resources file because the file is full.

The quantitative resource is not added to the file.

Corrective Action: Contact your systems programmer about the possibility of increasing the capacity of the Control-M Resources file.

SELC64E QUANTITATIVE RESOURCE `res` NOT `action` - SECURITY VIOLATION

Explanation: The Control-O resource action that was requested (add/change) was not performed due to security restrictions at the site.

The resource action is not performed.

Corrective Action: If you think the user that owns the rule should be authorized to issue resource requests, please contact your INCONTROL administrator. You may need to adapt your Control-M security criteria.

SELC65I OUTPUT CONDITION `cond` WAS action BY CONTROL-O

Explanation: The information message displays the results of a Control-O DO COND action.

The Control-M monitor adds/deletes the prerequisite condition.

Corrective Action: No action is required.

SELC66E OUTPUT CONDITION `condition/date` NOT `action` - SECURITY VIOLATION

Explanation: Control-O issued a DO COND request, but the Prerequisite Condition was not added/deleted.

User is not authorized to add/delete this condition from the IOA Conditions file.

Corrective Action: If you think the user that owns the rule should have the authority to perform DO COND actions, contact your INCONTROL administrator. You may need to adapt your Control-M security criteria.

SELC68E VALUE OF CNDREC# PARAMETER IN IOAPARM IS NOT EQUAL TO ACTUAL FILE SIZE

Explanation: The CNDREC# parameter in the IOAPARM member has been changed, but the IOA Conditions file has not been rebuilt.

A difference between the length of the IOA Conditions file and the CNDREC# value specified in the IOAPARM member of the PARM library was detected.

This is usually caused by using the IOAPARM member (read from the IOA Load library) for the wrong monitor.

The Control-M monitor shuts down.

Corrective Action: Correct the problem and restart the monitor.

SELC69E UPDATE OF QUANTITATIVE RESOURCE `resourceName` FAILED

Explanation: The action specified in a CONTRO-O DO RESOURCE statement failed, because it would have produced an illegal quantity.

Updating the resource would have produced either a negative quantity or a quantity greater than the maximum of 9999. Therefore it was rejected.

The system ignores the illegal statement and continues processing.

Corrective Action: Check and correct, if necessary, the definition of the quantitative resource to be updated and/or the rule defining how to update it.

SELC6AW QUANTITATIVE RESOURCE `resourceName` NOT CHANGED BECAUSE IT'S ALREADY HANDLED BY CONTROL-M

Explanation: DO RESOURCE statement in Control-M/Operator Rule was ignored by Control-M Monitor because the corresponding Rule was triggered by the message issued from a job submitted by Control -M and the Quantitative Resource (whose name specified in DO RESOURCE) is already allocated to the job by Control-M.

Corrective Action: No action is required.

SELC91E REMOTE FORCEJOB CANCELLED - NOT ENOUGH MEMORY

Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to insufficient storage allocated to the Control-M monitor.

Corrective Action: Increase the region size of the Control-M monitor.

SELC92E REMOTE FORCEJOB CANCELLED – INTERNAL ERROR

Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to an internal error.

Corrective Action: Contact BMC support.

SELC93E REMOTE FORCEJOB CANCELLED - INVALID RESPONSE FROM CTWWMF

Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to a problem in accessing the DAM2F file.

Corrective Action: Verify that DAM2F is allocated to a valid file. If it is, contact BMC support.

SELC95I `taskType memName jobName`/`jobId` OID=`orderId` WILL BE REACTIVATED

Explanation: This information message indicates that as a result of a user request, the job or STC is reactivated, and the Control-M monitor searches again for the sysout of the job or STC.

When option A (Reactivate) is specified for a job or STC in the Active Environment screen, the status of that job or STC changes from DISAPPEARED to SUBMITTED, and the Control-M monitor searches again for the sysout of the job to analyze job execution results.

Corrective Action: No action is required.

SELC96I OID=`orderId` WILL RETRY SUBMIT LATER

Explanation: This information message indicates that submission of the job could not be completed because of a temporary problem (for example, data set in use).

This information message accompanies other messages which identify the reason for the submission failure.

Control-M will retry submission later, for a maximum of three attempts. After three attempts to submit the job, the submission is cancelled.

Corrective Action: Check previous error messages. Correct the error and rerun the job.

SELC97I REMOTE FORCE JOB REQUEST ISSUED - UNIQUE ID `unique_id`

Explanation: Control-M successfully performed a job’s DO REMFORCE statement. The unique ID can be used to track the remote force request on the remote Control-M.

Corrective Action: No action is required.

Messages SELL00 through SELLxx

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.

SELL31E NO SPACE FOR QUANTITATIVE RESOURCE resourceName. NOTIFY YOUR IOA ADMINISTRATOR

Explanation: A resource (resourceName) could not be acquired because the Quantitative Resource List is full.

Resource acquisition is delayed until enough space is regained in the Quantitative Resource List in the Control-M Resources file. This message is not issued more often than once a minute.

Corrective Action: Ask your INCONTROL administrator to increase the logical record length of the Control-M Resources file. If the logical record length is already set to the maximum length allowed, wait until previously acquired quantitative resource entries are freed when jobs end. A third alternative is to have the INCONTROL administrator make more room available by deleting unused quantitative resource definitions.

SHB messages

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

Messages SHB200 through SHB2xx

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

SHB282I `text` (`userId`)

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT facility.

In this message, userId is the user ID of the job order requesting the SHOUT.

Corrective Action: No action is required.

SHB284I NEW DYNAMIC DESTINATION TABLE LOADED

Explanation: This information message indicates that a new Dynamic Destination Table has been loaded by the IOA Runtime environment. This message is also generated when the SHOUT Facility is initialized under the IOA Runtime environment.

Corrective Action: No action is required.

SHB285W DYNAMIC DESTINATION TABLE NOT LOADED

Explanation: Loading of the Dynamic Destination Table by the IOA Runtime Environment failed.

This could be due to one of the following causes:

There is insufficient memory for loading the table.
The IOADEST table does not exist in the IOA PARM library.

If the failure occurs during the initialization of the IOA Runtime Environment, SHOUT notifications will not be controlled by the Dynamic Destination Table.

Corrective Action: Check the MVS Log for the reason for the failure (probably a system abend code). Correct the problem and then run the job again.

SHD messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages SHD200 through SHD2xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SHD282I `text` (`usr`).

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT Facility.

In this message, usr is the user ID of the job order requesting the SHOUT.

Corrective Action: No action is required.

SHD284I NEW DYNAMIC DESTINATION TABLE LOADED

Explanation: This information message indicates that a new Dynamic Destination Table has been loaded by the Control-D monitor. The message also appears on initialization of the SHOUT Facility under the Control-D monitor

Corrective Action: No action is required.

SHD285W DYNAMIC DESTINATION TABLE NOT LOADED

Explanation: Loading of the Dynamic Destination Table by the Control-D monitor failed.

It could be due to one of the following:

Insufficient memory for loading the table.
The IOADEST table does not exist in the IOA PARM library.

If the failure happens during the initialization of the Control-D monitor, then SHOUT notifications will not be controlled by the Dynamic Destination Table. If this happens as a result of an F CONTROLD,NEWDEST command (operator command instructing the Control-D monitor to load a new Destination Table), the old destination table will remain in effect.

Corrective Action: Check the MVS Log for the reason for the failure (probably a system abend code). Correct the problem and then, in order to load the table, issue the operator command F CONTROLD,NEWDEST.

SHT messages

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 SHT200 through SHT2xx

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.

SHT280I MAILDEST TABLE WAS {LOADED | RELOADED}

Explanation: This information message indicates that the MAILDEST table was LOADED during Control-M initialization, or was RELOADED as a result of a NEWMAILDST command.

The MAILDEST table must be loaded before shout messages can be sent to their specified addresses.

If there are jobs in the Active Jobs File (AJF) when a NEWMAILDST command is issued, the MAILDEST table is reloaded, this message is issued and shout messages are sent.

If the AJF is empty, when a NEWMAILDST command is issued, the MAILDEST table is not reloaded. As soon as a job is put into the AJF, MAILDEST is reloaded, this message is issued and shout messages are sent.

Corrective Action: No action is required.

SHT281W MAILDEST TABLE WAS NOT FOUND IN ANY LIBRARY REFERENCED BY DD STATEMENT DAPARM. UNABLE TO SEND SHOUT

Explanation: The MAILDEST member is not in the IOA PARM library.

The IOAMAIL module reads the MAILDEST member to prepare a full address for each name on the mail list.

This message is produced when a job scheduling definition or rule issues a SHOUT or DO MAIL action to a destination specifying an e-mail address that cannot be resolved due to the absence of a MAILDEST member in the IOA PARM library.

The MAILDEST member is not loaded and shout messages are not sent.

Corrective Action: Build a new MAILDEST member in the IOA PARM library and try again.

SHT282I `text` (`userId`)

Explanation:Highlighted, unrollable message.

This information message is activated by the SHOUT facility. The userId is for the job order requesting the SHOUT.

Corrective Action: No action is required.

SHT284I NEW DYNAMIC DESTINATION TABLE LOADED

Explanation: This information message indicates that a new Dynamic Destination Table has been loaded by the Control-M monitor. This message is also generated when the SHOUT Facility is initialized under the Control-M monitor.

Corrective Action: No action is required.

SHT285W DYNAMIC DESTINATION TABLE NOT LOADED

Explanation: Loading of the Dynamic Destination Table by the Control-M monitor failed.

It could be due to one of the following:

Insufficient memory for loading the table.
The IOADEST table does not exist in the IOA PARM library.

If the failure happens during the initialization of the Control-M monitor, then SHOUT notifications will not be controlled by the Dynamic Destination Table. If this happens as a result of an F CONTROLM,NEWDEST command (operator command instructing the Control-M monitor to load a new Destination Table), the old destination table will remain in effect.

SHT286E OPEN DAM2G FILE BY CTWWMG FAILED

Explanation: The CTWWMG program is unable to open the DAM2G communication file.

To send Shout messages to an Enterprise Controlstation, Control-M uses the CTWWMG program to first write those messages and their records to DAM2G.

Corrective Action: Ask your INCONTROL administrator to correct the problem.

SHT287E INVALID OPERATION CODE FROM CTWWMG

Explanation: The CTWWMG program cannot write Shout message records to the DAM2G communication file because an invalid operation code was used to write the record.

To send Shout messages to an Enterprise Controlstation, Control-M uses the CTWWMG program to first write those messages and their records to DAM2G.

Corrective Action: Ask your INCONTROL administrator to correct the problem.

SHT288E ERROR IN PREPARING SHOUT TO MAIL, RC = `rc`

Explanation: The rc error occurred during preparation to send Shout messages.

Valid values for rc are:

rc	Explanation
01	GETMAIN failure in IOAMAIL.
02	Error occurred while loading modules in IOAMAIL.
03	Error occurred in the PRPGRP routine during preparation of group addresses.
04	Error occurred while reading or writing to the buffers.
05	Error in DOMAIL routine.
06	Error in MAILDEST structure.
07	Error in FREEMAIN.
08	Error in input parms.
11	GETMAIN failure in CTMMAL.
12	Error occurred while loading modules in CTMMAL.
13	FREEMAIN error in CTMMAL.

Corrective Action: Do one of the following:

If rc is 03, 04 or 05, correct errors in the MAILDEST table.
For all other rc values, contact your INCONTROL administrator or system programmer for help.

SHT28EE IOASMTP - ALLOCATION FAILED FOR SYSOUT DATASET

Explanation: The system failed to allocate a dataset for the SYSOUT. The email will not be sent.

Corrective Action: Check for the reason for the allocation problem and resolve the problem.

SHT28FE IOASMTP - OPEN FAILED FOR SYSOUT DATASET

Explanation: IOASMTP failed to open SYSOUT for the message.

Corrective Action: Check the system messages and resolve the file access problems.

SHT28GE IOASMTP - "TO" ADDRESS IS MISSING

Explanation: The recipient email address was not supplied. No email was sent.

Corrective Action: Ensure that the recipient email is supplied. Define the TO email in the Recipient Tree or the MAILDEST member.

SHT28HE IOASMTP - ERROR READING MEMBER memName. IOAMEM RC=rc RSN=rsn

Explanation: The member could not be found in the IOA PARM library. No email was sent.

Corrective Action: Ensure that the listed members are accessible. If necessary, contact BMC support and provide the message with RC and RSN values.

SHT28JW IOASMTP - UNKNOWN PLACEHOLDER placeholder USED IN memName SKELETON MEMBER IGNORED.

Explanation: Warning message. An unknown placeholder was added to one of the skeleton members.

Corrective Action: Open the IOASMTPA member and remove the unknown placeholder.

SIM messages

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 SIM0 through SIM0xx

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.

SIM075S OPEN OF DDNAME "DASIMOUT" FAILED. SIMULATION STOPPED

Explanation: Open of simulation printout file failed (the DASIMOUT DD statement - the CTMSIM utility).

This is due to one of the following:

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

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

SIM076I SIMULATION STARTED

Explanation: This information message indicates that simulation started (the CTMSIM Control-M utility).

This message is issued by the CTMSIM Control-M utility, which activates the Simulation and Forecasting Facility.

Corrective Action: No action is required.

SIM077S OPEN OF DDNAME "DASIMPRM" FAILED. SIMULATION STOPPED

Explanation: Open of simulation parameters file failed (the DASIMPRM DD statement - the CTMSIM utility)

This could be due to one of the following:

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

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the JCL for the job.

SIM078I SIMULATION ENDED

Explanation: This information message indicates that simulation ended (the CTMSIM Control-M utility).

Corrective Action: No action is required.

SIM079S INVALID SIMULATION PARAMETER: - `parm`

Explanation: Invalid simulation parameter (the CTMSIM Control-M utility). For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the simulation parameters (the DASIMPRM DD statement).

SIM080S SIMULATION INTERVAL MUST BE FROM 3 TO 99 SECONDS

Explanation: Invalid interval parameter for Control-M simulation facility. Simulation interval must be from 3 to 99 seconds, inclusive. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the simulation interval (the DASIMPRM DD statement).

SIM081S INVALID DAYTIME FORMAT. "yymmddhhmm" EXPECTED

Explanation: Invalid format of SIMSTART SIMEND, ADD, DELETE or CHANGE simulation parameters. The SIMSTART and SIMEND simulation parameters or the ONDAYTIME subparameter (of the ADD, DELETE and CHANGE command) should be in day-time format yymmddhhmm. For more information, see the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct SIMSTART or SIMEND or ONDAYTIME simulation parameter (the DASIMPRM DD statement).

SIM082S MULTIPLE USE OF PARAMETER. ONLY ONE OCCURRENCE IS ALLOWED

Explanation: Result of multiple use of INTERVAL, SIMSTART or SIMEND simulation parameters (the CTMSIM Control-M utility).

Only one occurrence of INTERVAL, SIMSTART or SIMEND simulation parameters is allowed. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Please omit one of the multiple occurrences of the relevant simulation parameter (the DASIMPRM DD statement).

SIM083S SIMULATION START TIME IS GREATER THAN SIMULATION END TIME

Explanation: The daytime specified in the SIMEND simulation parameter is prior to the daytime specified in the SIMSTART parameter (the CTMSIM Control-M utility).

For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the SIMSTART or SIMEND simulation parameter (the DASIMPRM DD statement).

SIM084S MISSING OBLIGATORY SIMULATION PARAMETERS

Explanation: Missing obligatory simulation parameters: INTERVAL, SIMSTART or SIMEND. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the simulation parameters (the DASIMPRM DD statement).

SIM085S LOADING OF SIMULATION CONTROL TABLE FAILED. SIMULATION STOPPED

Explanation: Loading of simulation control table failed. The CTMSMT module is not in the IOA SIML library, or there is insufficient memory.

Corrective Action: Check the IOA SIML library or increase region size.

Simulation stops.

SIM086W MEMBER `memName` LIBRARY `lib` WILL NOT TAKE PART IN THE SIMULATION

Explanation: The status of the job on the simulation input Active Jobs file (AJF) is not WAIT SCHEDULE.

The Control-M simulation facility processes only jobs which have a WAIT SCHEDULE status on the simulation input Active Jobs file. Jobs with other status’s are ignored.

Control-M simulation continues processing.

Corrective Action: No action is required.

SIM087W MEMBER `memName` LIBRARY `lib` - DEFAULT ELAPSED TIME USED

Explanation: Result of request for execution of simulation for a Quick Submit job on which Control-M does not have statistical information in the Job Execution Statistics file (the DASTAT DD statement).

The default elapsed time of 3 minutes was used for a Quick Submit job. The job execution statistical data must be periodically accumulated from the Log file by the CTMJSA utility. You can specify expected execution time of a new job with the NEWJOB statement. For details, refer to the Control-M for z/OS User Guide.

Corrective Action: No action is required.

SIM088S INVALID RC WHILE READING JOBS EXECUTION STATISTICS FILE. RC=`rc` ERROR=`err`

Explanation: Invalid return code rc while reading the job execution statistics file.

The job execution statistics file is a VSAM file. The return code (rc) is the general VSAM return code, and the error (err) is the VSAM FDBK area.

The simulation stops executing with a condition code of 08.

Corrective Action: Check the relevant IBM literature for the meaning of the return code and FDBK area.

SIM089S INSUFFICIENT MEMORY TO PERFORM SIMULATION

Explanation: Insufficient memory to perform simulation.

The CTMSIM utility that activates the simulation may use a large amount of CPU and memory. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Increase the job region size (of the CTMSIM utility).

SIM090S VALID MEMBER NAME EXPECTED AFTER "NEWJOB"/"OLDJOB" STATEMENT

Explanation: Invalid missing member name after NEWJOB (or OLDJOB) statement (the DASIMPRM DD statement).

The NEWJOB statement is used to specify the expected execution time of the new job. The OLDJOB statement is used to specify the execution time of a job when it is different from the average. The member is the basis for identifying the job order in the Active Jobs file.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the member parameter in the NEWJOB (or OLDJOB) statement (the CTMSIM utility).

SIM091S VALID GROUP NAME OF 1-20 CHARACTERS IS EXPECTED AFTER "GROUP" SUB-COMMAND

Explanation: Invalid or missing GROUPNAME parameter in sub-command GROUP of the NEWJOB statement (the DASIMPRM DD statement).

The GROUPNAME should be from 1 through 20 characters. The NEWJOB parameters member and group name are the basis for identifying the job order in the Active Jobs file. For details, refer to the section on the Simulation and Forecasting facility in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the GROUP sub-command in the NEWJOB statement (the CTMSIM utility).

SIM092S CPU ID OF ONE CHARACTER IS EXPECTED AFTER "CPUID" SUB-COMMAND

Explanation: The CPUID parameter in CPUID sub-command of NEWJOB statement (the DASIMPRM DD statement) is invalid or missing.

In a multiple CPU environment, the job can have different execution times on different CPUs. Therefore it is necessary to specify the expected elapsed time for each CPU the job may run on. The CPUID parameter should be of one character - identical to the CPUID used by JES for this CPU. For details, refer to the simulation parameters in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the CPUID parameter in the CPUID sub-command of NEWJOB statement (the CTMSIM utility).

SIM093S INVALID EXECTIME FORMAT. "`mmmm.xx`" EXPECTED

Explanation: Invalid or missing EXECTIME parameter in NEWJOB statement. (the DASIMPRM DD statement).

The EXECTIME is given in minutes (mmmm) and hundredths of a minute (xx). For more information, see the NEWJOB statement in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the EXECTIME parameter in the NEWJOB statement (the CTMSIM utility).

SIM094S MISSING "EXECTIME" SUB-COMMAND AFTER "NEWJOB"/ "OLDJOB" COMMAND

Explanation: Missing EXECTIME sub-command after NEWJOB (or OLDJOB) command (the DASIMPRM DD statement).

EXECTIME sub-command is obligatory in NEWJOB (or OLDJOB) statement. For details, refer to the NEWJOB or OLDJOB statement in the Control-M for z/OS User Guide.

Corrective Action: Add the EXECTIME sub-command or omit the NEWJOB (or OLDJOB) statement (the CTMSIM utility).

SIM095S MISSING EITHER "CONDITION" OR "RESOURCE" IN COMMAND

Explanation: Missing either CONDITION or RESOURCE in simulation command (the DASIMPRM DD statement).

ADD, DELETE or CHANGE commands can be used either with CONDITIONS or with RESOURCES. For details, refer to the simulation parameters in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Correct the ADD, DELETE, or CHANGE simulation command.

SIM096S CONDITION/RESOURCE NAME MUST BE 1-20 CHARACTERS

Explanation: Invalid/missing CONDITION or RESOURCE name in simulation parameters (the DASIMPRM DD statement).

CONDITION or RESOURCE name must be 1-20 characters. For details, refer to the simulation parameters the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Please correct the CONDITION or RESOURCE name in the simulation parameters (the CTMSIM utility).

SIM097S MISSING "ONDAYTIME" SUB-COMMAND

Explanation: Missing ONDAYTIME sub-command in the simulation parameters (the DASIMPRM DD statement).

ONDAYTIME sub-command is obligatory in ADD, DELETE or CHANGE commands of the simulation parameters. For details, refer to the simulation parameters in the Control-M for z/OS User Guide.

The simulation stops executing with a condition code of 08.

Corrective Action: Please add an ONDAYTIME sub-command to the ADD, DELETE or CHANGE command of the simulation parameters.

SIM098I TASK `taskName` DID NOT FINISH EXECUTING

Explanation: This information message indicates that taskName task (job/started task) did not finish executing within simulation time limits (SIMEND).

The task started executing and was still executing at the end of the simulation.

Corrective Action: No action is required.

SIM099I TASK `taskName` STILL WAITS SCHEDULE

Explanation: This information message indicates that taskName task is still waiting to be scheduled after the simulation end time specified in the SIMIEND ONDAYTIME.

The job/started task was in wait schedule state at simulation end time. It probably did not execute.

Corrective Action: No action is required.

Messages SIM100 through SIM1xx

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.

SIM100W JOB `jobName` IS A QUICK-SUBMIT JOB - DEFAULT ELAPSED TIME USED

Explanation: The Control-M Simulation Facility encountered a Quick Submit job in the input for the simulation process.

The Quick Submit job is handled as a standard job. Default execution time is assumed for the job.

Corrective Action: No action is required.

SIM101S INVALID CHANGE REQUEST

Explanation: The number of elements in a quantitative resource could not be changed, because the resource is not defined in the Control-M Resources file.

The CHANGE RESOURCE command is ignored.

Corrective Action: Make sure a resource is defined in the Control-M Resources file before using the CHANGE RESOURCE command of the simulation utility to change it.

Messages SIM500 through SIM5xx

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.

SIM500I INPUT LEN=`len` REC=`inputRecordMsg`

Explanation: This information message is generated when the CTOTEST Control-O utility is invoked.

Corrective Action: This message is sent to CTOTEST. It echoes the input record.

SIM501S OPEN FAILED FOR DDNAME CMDMSGFL

Explanation: The attempt to open input file CMDMSGFL failed.

Possible causes are:

The CMDMSGLF DD statement is misspelled.
The data set (member) referenced by the CMDMSGFL DD statement does not exist.

CTOTEST execution terminates.

Corrective Action: Check if the CMDMSGFL DD statement is present in the JCL.

SIM502S INPUT PARAMETER ERROR

Explanation: The subsystem name input parameter is invalid or missing.

CTOTEST execution terminates.

Corrective Action: Check if PARM=subsystemName is present in the parameter string.

SIM503I RC `rc` LEN=`len` REC=`msgText`

Explanation: This information message is generated when the CTOTEST Control-O utility is invoked.

The variables in this message are:

rc - return code
len - new message length
msgText - new message text

Corrective Action: No action is required.

SLC messages

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 SLC0 through SLC0xx

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.

SLC001I CTMSLC STARTED

Explanation: This information message indicates that the CTMSLC utility, which enables you to remove old job scheduling definitions from the schedule library, has started.

Corrective Action: No action is required.

SLC00AI NO JOBS WERE DELETED BY LIBRARY CLEANUP PROCESS

Explanation: The CTMSLC utility completed successfully without deleting any job scheduling definitions from the scheduling library.

The utility terminates with a return code of 4.

Corrective Action: No action is necessary.

SLC025I CTMSLC ENDED

Explanation: This information message indicates that the CTMSLC utility ended normally. The CTMSLC utility enables you to remove old job scheduling definitions from the schedule library.

Corrective Action: No action is required.

SLG messages

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 SLG900 through SLG9xx

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.

SLG9B1E SYSTEM LOGGER CONNECT REJECTED, DASD-ONLY LOG STREAM IS ALREADY CONNECTED TO BY ANOTHER LOG STREAM IN THE SYSPLEX

Explanation: The System Logger rejected an attempt to connect to a DASD-only log stream because another log stream in the Sysplex is already connected. Only applications from the same system (LPAR) can connect simultaneously to the DASD-only log streams. If you are using DASD-only log streams, then Control-M, CMEM or Control-O, and IADDC (the CONNECT DIRECT interface) must all be running in the same LPAR.

The attempt to connect is rejected.

Corrective Action: Determine which system you want to connect to the log stream, and rerun the component that failed in the correct system.

If you want all members in a Sysplex to have access to the log stream, use coupling facility log streams rather than DASD-only log streams. For more information, see the description of sysplex configuration parameters in the INCONTROL for z/OS Installation Guide.

SLO messages

This group includes messages for the Control-O product.

Messages SLO100 through SLO1xx

This group includes messages for the Control-O product.

SLO160I {CONTROL-O | CTMCMEM} SELECTOR STARTED

Explanation: This information message indicates the start of the Control-O Selector task, which controls the runtime selection criteria for rules.

Corrective Action: No action is required.

SLO161I {CONTROL-O | CTMCMEM} SELECTOR ENDED

Explanation: This information message indicates normal termination of the Control-O Selector task that controls the runtime selection criteria for rules.

Corrective Action: No action is required.

SLO163S OPEN FAILED FOR DDNAME "DARESF" OR "DASINC"

Explanation: Open of IOA Conditions or Resources file failed (the DARESF or the DASINC DD statement).

Possible causes are:

The DARESF DD statement is missing.
The DASINC DD statement is missing.
The data set described by the DARESF DD statement is not the IOA Conditions or Resources file.
The data set described by the DASINC DD statement is not the Control-O Conditions or Resources Synchronization file.
The data set described by the DARESF DD statement is the Control-O Conditions or Resources file, but it is of a different version or of a different Control-O monitor.
The volume of this data set cannot be accessed by the Control-O monitor.
The data set is not on the volume specified in the Control-O procedure.

Control-O monitor shuts down with error message.

Corrective Action: Correct the JCL for the Control-O procedure, and restart the monitor.

SLO164S INTERNAL ERROR PROCESSING RESOURCE FILE FOR CONDITION cond

Explanation: An internal error occurred while the cond condition was being processed.

The Control-O monitor is terminated.

Corrective Action: Contact BMC Customer Support.

SLO165E COND `name date` NOT `action` BY CONTROL-O - SECURITY VIOLATION

Explanation: Control-O issued a DO COND request, but the user is not authorized by the security exit to add or delete this condition in the IOA Conditions file.

The prerequisite condition is not added or deleted.

Corrective Action: Contact your INCONTROL administrator.

SLO166W COND `name date` NOT UPDATED BY CONTROL-O - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR

Explanation:Highlighted, unrollable message.

There is no more space for adding output conditions to the IOA Conditions file.

The record for the specified day of the month is full. For example, if a condition with date reference of January 3rd cannot be added, an entry in the conditions file which contains conditions for January 3rd, February 3rd, March 3rd, and so on, is full.

The format for the date specified in this message is mmdd.

The condition is not added. A highlighted message is displayed on the operator console. Control-O or CMEM continues to function, but the rules that depend on the condition may not be triggered.

Corrective Action: Perform the following immediate actions and then perform the long term actions described below.

Immediate actions:

Enter the IOA Conditions list (Screen 4).
Look for conditions with the same day (but with a different month) as the condition that could not be added. Delete them manually if they are not needed.
Add the failing condition manually in order to maintain production flow.
Report the event to your System Programmer.

Long term actions:

Run the IOACLCND utility more often.
Increase the record length of the IOA Conditions file. For more information on how to do this, see the description of expanding IOA files in the INCONTROL for z/OS Administrator Guide.

SLO167I COND `name date` WAS `action` BY {CONTROL-O | CTMCMEM}

Explanation: This information message displays the results of a Control-O or CMEM DO COND request.

The Control-O or CMEM monitor adds/deletes the prerequisite condition.

Corrective Action: No action is required.

SLO168I COND name date ALREADY action

Explanation: This information message indicates that the user requested an action that has already been performed.

The user either tried to add a condition that already exists or tried to delete a condition that had already been deleted.

Corrective Action: No action is required.

SLO169W COND `name date` NOT ADDED BY {CONTROL-O | CTMCMEM} GLOBAL DATE ADDITION IS NOT SUPPORTED

Explanation: A DO COND statement in a rule requested the addition of the specified condition with date **** or $$$$. This date specification is valid only when conditions are being deleted.

The DO COND request is not performed.

Corrective Action: Correct the DO COND statement.

SMF messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages SMF0 through SMF0xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SMF041S SMFWTM RETURNED RC= 4 - SMF RECORD TOO LONG

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record which could not fit completely in an SMF data set.

The user modified Control-D Exit CTDX006, but moved an incorrect value to the SMFLEN field (DSECT CTDUSMF). This field contains the length of the SMF record.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, message SMF049I is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Correct the problem in CTDX006, assemble and link-edit this exit, and bring down Control-D. When Control-D is brought up again, SMF recording will resume.

SMF042S SMFWTM RETURNED RC= 8 - SMF RECORD TOO SHORT

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record which is smaller than 18 characters long.

The user modified the Control-D Exit CTDX006, but moved an incorrect value to the SMFLEN field (DSECT CTDUSMF). This field contains the length of the SMF record.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, message SMF049I is written to the Control-D log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Correct the problem in CTDX006, assemble and link-edit this exit, and bring down Control-D. When Control-D is brought up again, SMF recording will resume.

SMF043S SMFWTM RETURNED RC= 16 - SMF IS NOT ACTIVE

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but SMF is not active.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, the message SMF049I is written to the IOA Log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Initiate SMF recording, then bring down Control-D. When Control-D is brought up again, SMF recording will resume.

SMF044S SMFWTM RETURNED RC= 20 - SMF EXIT IEFU83 SUPPRESSED THE RECORD

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but SMF exit IEFU83 suppressed the record.

Corrective Action: Correct SMF exit IEFU83 to allow Control-D to write SMF records. When Control-D is brought up again, SMF records will resume.

SMF045S SMFWTM RETURNED RC= 24 - THE SMF FILES ARE FULL

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but the SMF files are full.

The SMF record is not written, but Control-D continues processing. Control-D will write message SMF049I to the IOA Log file. This log message is a replacement for SMF recording, and can be entered into SMF later.

Control-D will keep attempting to write to the SMF file. If the SMF file is still full, message SMF049I will be written to the log.

Please note that Control-D does not have to be taken down. As soon as room is found on an SMF file, SMF recording will take place automatically.

Corrective Action: The operator should clear SMF files according to the conventions of the site. As soon as this is done, Control-D will automatically continue with SMF recording.

SMF046S INTERNAL PROBLEM IN MVS. SMF RECORD NOT WRITTEN

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but there is an internal problem in MVS.

This is due to one of the following return codes from MVS:

Return Code	Explanation
26	Record is not currently being recorded.
40	Buffer storage caused data to be lost.
44	SVC 83 unable to establish recovery.

Refer to message SMF047S for the return code.

Corrective Action: Call the system programmer. After the problem is fixed by the system programmer, bring down Control-D. When Control-D is brought up again, SMF recording will resume.

SMF047S RC=`rc` RECEIVED FROM MACRO SMFWTM

Explanation:Highlighted, unrollable message.

Control-D is unable to write SMF records. Possible causes are:

Message SMF046S was issued. This message specifies the RC returned by SMF.
An unknown return code was issued by SMF. This message specifies the RC returned by SMF.

The SMF record is not written, but Control-D continues processing. Control-D sets an internal indication that a permanent error is present on SMF recording, and will not continue to attempt SMF recording. From this point on, instead of writing to SMF, message SMF049I is written to the Control-D log. This log message is a replacement for SMF recording, and can be entered into SMF after the problem is fixed.

Corrective Action: Call the INCONTROL administrator.

SMF048S CONTROL-D SMF RECORDING IS TERMINATED - PLEASE TAKE CORRECTIVE ACTION

Explanation:Highlighted, unrollable message.

Control-D is unable to write SMF records.

This message is issued whenever a permanent error is present on SMF recording. This message is issued for messages SMF041S through SMF050S.

The SMF record is not written, but Control-D continues processing.

In the case of a non-permanent SMF error under IOA Online, Control-D Decollation Monitor, or Control-D Application Server address space, the SMF recording is deactivated and the one time warning message SMF048S is issued.

Corrective Action: Refer to messages SMF041S through SMF050S. In the case where the message is issued due to a non-permanent SMF error under IOA Online, Control-D Decollation Monitor, or Control-D Application Server address space, refer to the SMF MODIFY command description in the SMF Accounting chapter of the INCONTROL for z/OS Administrator Guide. Eliminate the cause of the error and issue the SMF MODIFY command to an appropriate address space in order to re-activate SMF writing.

SMF049I USER=`user` ODATE=`date` COP=`#copies` P=`#pages` L=`#lines`

Explanation: If STAT is set to Y in CTDPARM, this information message is issued when a Printing Mission prints a report.

date is in either mmdd or ddmm format, depending on the site standard.

# copies - the number of copies to produce for this report.
# pages - the number of pages in this report.
# lines - the number of lines in this report.

Corrective Action: No action is required.

SMF04AI CONTROL-D SMF RECORDING IS ACTIVE

Explanation: The SMF recording is active for this Control-D address space.

The message is issued in one of the following cases:

after the address space has started if the SMF recording is activated by the corresponding SMFxxx parameter in the IOAPARM/CTDPARM of this Control-D address space
after the SMF modify command was issued to reactivate SMF recording after an error

Corrective Action: No action is required.

SMF04BI CONTROL-D SMF RECORDING IS NOT ACTIVE

Explanation: The SMF recording is not active for this Control-D address space.

The message is issued after the SMF modify command was issued for the Control-D address space, but the corresponding parameter SMFxxx=NO was defined the in IOAPARM/CTDPARM.

Corrective Action: In order to activate SMF recording, the user must define the corresponding SMFxxx parameter and then restart the Control-D address space.

SMF050S INVALID VALUE value IN THE INSTALLATION PARAMETER "SMF"

Explanation:Highlighted, unrollable message.

Control-D attempted to write an SMF record, but an invalid value is present on the SMF field in CTDPARM.

The SMF field in CTDPARM can contain the following values:

Character string, length of three, value NO.
A 3-digit number, value 128 through 255.

Corrective Action: Call your INCONTROL administrator.

SNM messages

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 SNMA00 through SNMAxx

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.

SNMA01W LENGTH OF SNMP MESSAGE EXCEEDED ALLOWED MAXIMUM(70), MESSAGE TRUNCATED

Explanation: An attempt was made to send an SNMP message the length of which exceeded the permitted maximum.

The length of an SNMP message must not exceed 70 characters.

The problematic SNMP message is truncated. Processing continues.

Corrective Action: Correct the rule that created the problematic message.

SNMA02E INVALID IP ADDRESS SPECIFIED IN HOST PARAMETER: `ipAdd`.

Explanation: The SNMP interface encountered a syntax error in the IP address specified in the HOST parameter.

In this message, ipAdd is the identity of the problematic IP address.

The entry in the SNMP Destination table that contains the invalid IP address is disabled. Processing continues.

Corrective Action: Correct the problematic IP address in the SNMP Destination table and issue a NEWSNMPDST modify command.

SNMA03S FAILURE TO READ SNMP DESTINATION TABLE, RC(`rc`) REASON(`rsn`)

Explanation: A severe error occurred when the SNMP interface was trying to read the SNMP Destination table from the IOA PARM library.

The variables in this message are:

rc - the return code that indicates the nature of the failure
rsn - a reason code that provides more information about the failure

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA04S INSUFFICIENT MEMORY TO READ SNMP DESTINATION TABLE

Explanation: A severe error occurred when the SNMP interface was trying to read the SNMP Destination table from the IOA PARM library.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA06E FAILURE TO RECOGNIZE THE LINE

Explanation: The SNMP interface failed to recognize a line in the SNMP Destination table. The sequential number of the problematic line is identified in the SNMA0NI message that precedes this SNMA06E message.

The problematic line in the SNMP Destination table is ignored. Processing continues.

Corrective Action: Correct the problematic line in the SNMP Destination table and issue a NEWSNMPDST modify command.

SNMA07S SNMP DESTINATION TABLE IS EMPTY

Explanation: The SNMP interface discovered that the SNMP Destination table does not contain any lines.

SNMP interface processing is discontinued.

Corrective Action: Fill the SNMP Destination table by adding lines and issue a NEWSNMPDST modify command.

SNMA09I SNMP DESTINATION TABLE `processed result`

Explanation: The SNMP interface successfully read and processed the SNMP Destination table.

The variables in this message are:

processed - the type of action Valid values are:
PROCESSED - The SNMP Destination table was read and processed when the SNMP interface was called for the first time.
REFRESHED - The SNMP Destination table was successfully refreshed in memory when the NEWSNMPDST Modify command was issued.
result - the result of the processingValid values are:
SUCCESSFULLY - The SNMP Destination table was read and processed successfully.
WITH ERRORS - Errors were encountered during the reading or processing of the SNMP Destination table.

Corrective Action: No action is required.

SNMA0AE FAILURE TO PROCESS SNMP DESTINATION TABLE, RC(`rc`) REASON(`rsn`)

Explanation: The SNMP interface failed to process the SNMP Destination table.

The variables in this message are:

rc - the return code that indicates the nature of the failure
rsn - a reason code that provides more information about the failure

SNMP interface processing is discontinued.

Corrective Action: Correct the SNMP Destination table and issue a NEWSNMPDST modify command.

SNMA0BE COMMA SHOULD NOT PRECEDE STATEMENT(HOST) IN A GROUP

Explanation: The SNMP interface encountered a syntax error while processing the SNMP Destination table. The sequential number of the problematic line is identified in the SNMA0NI message that precedes this SNMA0BE message.

The entry in the SNMP Destination table identified in the SNMA0NI message is ignored. Processing continues.

Corrective Action: Correct the identified entry in the SNMP Destination table, and issue a NEWSNMPDST modify command.

SNMA0CE COMMA MUST PRECEDE DEFINITION(PORT)

The PORT definition can only be used together with the HOST definition.

The entry in the SNMP Destination table identified in the SNMA0NI message is ignored. Processing continues.

Corrective Action: Correct the SNMP Destination table entry identified in the SNMA0NI message, and issue a NEWSNMPDST modify command.

SNMA0DE PARAMETER(`parm`) IS INVALID, ENTRY DISABLED

Explanation: An error was found in the parm parameter of the SNMP Destination table. The sequential number of the problematic line is identified in the SNMA0NI message that precedes this SNMA0DE message.

In this message, valid values for parm are:

PORT
HOST

The entry in the SNMP Destination table identified in the SNMA0NI message is ignored. Processing continues.

Corrective Action: Correct the identified entry in the SNMP Destination table, and issue a NEWSNMPDST modify command.

SNMA0EE UNDEFINED NICK=`nick` SPECIFIED IN GROUP=`grp`, ENTRY DISABLED

Explanation: A group of recipients in the SNMP Destination table refers to a nickname statement that is not defined in the nicknames section of the Destination Table.

The variables in this message are:

nick - the undefined nickname
grp - the name of the group that contains nick

The entry in the SNMP Destination table that contains grp is ignored. Processing continues.

Corrective Action: Correct the problematic entry in the SNMP Destination table, and issue a NEWSNMPDST modify command.

SNMA0FE INVALID HOST VALUE SPECIFIED IN `defn=host_val`, ENTRY DISABLED

Explanation: An invalid HOST value was discovered in the definition identified in the message.

The variables in this message are:

defn - the identity of the definition that contains the invalid HOST valueValid values are:
- NICK
- GROUP
host_val - the invalid HOST value

The entry in the SNMP Destination table that contains the invalid HOST value is ignored. Processing continues.

Corrective Action: Correct the problematic HOST value and issue a NEWSNMPDST modify command.

SNMA0GE `stmt` STATEMENT BELONGS TO NEITHER NICK NOR GROUP

Explanation: The identified statement in the SNMP Destination table is not a NICK statement, nor does it belong to any group.

In this message, stmt is the problematic statement. Valid values are:

HOST
PORT

The identified entry in the SNMP Destination table is disabled. Processing continues.

Corrective Action: Correct the identified entry in the SNMP Destination table and issue a NEWSNMPDST modify command.

SNMA0HE NICK STATEMENT MUST CONTAIN HOST DEFINITION, ENTRY DISABLED

Explanation: The identified NICK statement in the SNMP Destination table does not contain a HOST definition.

A NICK statement in a SNMP Destination table must contain a HOST definition.

The identified entry in the SNMP Destination table is disabled. Processing continues.

Corrective Action: Correct the identified entry in the SNMP Destination table and issue a NEWSNMPDST modify command.

SNMA0LS MODE=`mode` CALL CAN BE ISSUED AFTER MODE=INIT ONLY

Explanation: The SNMP interface encountered a severe internal error.

In this message, mode is the mode of the invalid call that was found. Valid values are:

SEND
LOAD
CLOSE

SNMP interface processing is discontinued.

Corrective Action: Note the value of mode and contact BMC Customer Support.

SNMA0MS INSUFFICIENT MEMORY(`mem_size`), FAILURE TO GETMAIN `area`

Explanation: The SNMP interface failed to acquire the storage necessary to create an area in memory of the size requested.

The variables in this message are:

mem_size - the requested size of area
area - the name of the requested area in memory

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0NI ERROR DETECTED IN SNMP DESTINATION TABLE, LINE=`lineNum`:

Explanation: This message precedes other messages, and identifies by number the line in which an error was detected.

In this message, lineNum is the number of the problematic line.

Corrective Action: Correct the problematic line in the SNMP Destination table, and issue a NEWSNMPDST modify command.

SNMA0OS FAILURE TO LOAD MODULE(`modName`)

Explanation: The SNMP interface encountered a severe error. The specified load module was not found in the IOA LOAD library.

In this message, modName is the name of the load module that could not be loaded.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0PS INTERNAL ERROR, INVALID OR MISSING MCT ADDRESS

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0QS INTERNAL ERROR, INVALID OR MISSING SNMV ADDRESS

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0RS FAILURE TO REFRESH SNMP DESTINATION TABLE

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0SS SNMP DESTINATION TABLE IS UNAVAILABLE

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0TS IOASNMC failed, SNMV vector is not initialized

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0UW INVALID PORT VALUE SPECIFIED, DEFAULT 162 IS USED

Explanation: An invalid port number was specified in the SNMP Destination table.

The default SNMP trap port number, 162, is assigned instead of the invalid port number.

Corrective Action: Correct the line in the SNMP Destination table that contains the problematic port number, and issue a NEWSNMPDST modify command.

SNMA0WS MISSING SNMP MESSAGE LENGTH

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0XS SNMP MESSAGE WAS NOT SPECIFIED

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0YS INTERNAL ERROR, INVALID OR MISSING MCT ADDRESS

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMA0ZS INTERNAL ERROR, INVALID OR MISSING SNMV ADDRESS

Explanation: The SNMP interface encountered a severe internal error.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

Messages SNMT00 through SNMTxx

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.

SNMT01S FAILURE TO SEND SNMP TRAP, TCP/IP STACK `stack` UNAVAILABLE

Explanation: ISTACK parameter was specified in the IOAPARM member and the system has TCP/IP dual stack mode, but the specified stack is not running.

The message reappears every time Control-O or Control-M attempt to send an SNMP message.

Corrective Action: Either bring up the started task named 'stack', or remove the ISTACK parameter from IOAPARM and recycle Control-M, or start a new Control-O monitor.

SNMT02S INTERNAL ERROR: FAILURE TO BUILD SNMP TRAP, DESTINATION(`dest`)

Explanation: The SNMP interface encountered a severe internal error.

In this message, dest is the identity of the SNMP listener to which the SNMP interface was to send the SNMP message that failed when being built.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMT03S FAILURE TO ALLOCATE STORAGE FOR SNMP TRAP, DESTINATION(`dest`)

Explanation: The SNMP interface encountered a severe internal error.

In this message, dest is the identity of the SNMP destination to which the SNMP interface was to send the SNMP message that failed when being built.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMT06E FAILURE TO OBTAIN LOCAL IP ADDRESS, ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed to determine the IP address of the sending machine.

The variables in this message are:

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of errno and errno_id, and contact BMC Customer Support.

SNMT07S SOCKET() CALL FAILED, DESTINATION(`dest`) ERRNO(`errno.errno_id`)

Explanation: The SNMP interface encountered a severe internal error.

The variables in this message are:

dest - the identity of the SNMP destination to which the SNMP interface failed to send the message.
errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of errno and errno_id, and contact BMC Customer Support.

SNMT08E FAILURE TO SEND SNMP TRAP TO DESTINATION(`dest`), ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed to send an SNMP message.

The variables in this message are:

dest - the identity of the SNMP destination to which the SNMP interface failed to send the message.
errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of dest, errno, and errno_id, and contact BMC Customer Support.

SNMT09E FAILURE TO RESOLVE HOSTNAME(`hostname`)

Explanation: The SNMP interface failed to resolve the host name hostname.

In this message, hostname is the identity of the SNMP destination.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMT0AE INVALID IPV6 SNMP DESTINATION ADDRESS `address`

Explanation: The destination address of a DO SHOUT SNMP or DO SNMP contains the colon (:) character, but the address is not a syntactically valid IPv6 address.

Corrective Action: Correct the address. If you specified an IPv4-mapped IPv6 address, change it to an IPv4 address. See message ECAP9UE for more examples.

SNMT0BE IPV6 NOT ACTIVE ON SYSTEM

Explanation: The destination address of a DO SHOUT SNMP or DO SNMP contains the colon (:) character, but TCP/IP IPv6 support is not active on the z/OS system.

Corrective Action: If IPv6 is not active, then specify only IPv4 addresses.

SNMT10S BIND() CALL FAILED, SNMP-MASTER-AGENT(`hostname`) ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed in the BIND() call.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.
hostname - the hostname of the SNMP Master Agent

SNMP interface processing is discontinued.

Corrective Action: Note the value of hostname, errno, and errno_id, and contact BMC Customer Support.

SNMT11S SNMP-DPI PORT-QUERY SEND FAILED TO SNMP-MASTER-AGENT(`hostname`) ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed in the SENDTO() call to the SNMP Master Agent. This call includes the QUERY_DPI_PORT request, which gives in the reply the port on which the Master SNMP Agent listens for connections.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.
hostname - the hostname of the SNMP Master Agent

SNMP interface processing is discontinued.

Corrective Action: Note the value of hostname, errno, and errno_id, and contact BMC Customer Support.

SNMT12S RECVFROM() CALL FAILED, SNMP-MASTER-AGENT(`hostname`) ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed in the RECVFROM() call to the SNMP Master Agent. This call receives the reply to the QUERY_DPI_PORT request, which gives in the reply, the port on which the Master SNMP Agent listens for connections.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.
hostname - the hostname of the SNMP Master Agent

SNMP interface processing is discontinued.

Corrective Action: Note the value of hostname, errno, and errno_id, and contact BMC Customer Support.

SNMT13S NO REPLY TO SNMP-DPI PORT-QUERY FROM SNMP-MASTER-AGENT(`hostname`), PORT(`udp-port`)

Explanation: The SNMP interface did not receive, within 3 seconds, a reply to the QUERY_DPI_PORT request, which gives the port on which the Master SNMP Agent listens for TCP/IP connections.

udp-port - the UDP port on which the SNMP Master Agent receives PORT-QUERY requests, which gives the port on which the Master SNMP Agent listens for TCP/IP connections.
hostname - the hostname of the SNMP Master Agent

SNMP interface processing is discontinued.

Corrective Action: Note the value of hostname and udp-port, and contact BMC Customer Support.

SNMT14S COULD NOT RESOLVE SNMP-MASTER-AGENT(`hostname`)

Explanation: The SNMP interface failed to resolve the hostname hostname. In this message, hostname is the identity of the SNMP Master Agent host.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMT15S INVALID SNMP-MASTER-AGENT IP ADDRESS(`ip_address`)

Explanation: The SNMP interface could not use the configured IP address of the SNMP Master Agent because it is an invalid IP address.

ip_address - the IP address of the SNMP Master Agent.

SNMP interface processing is discontinued.

Corrective Action: Configure a valid IP address.

SNMT16S SOCKET(`SOCK_STREAM`) FAILED, ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed in the SOCKET() call.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of errno and errno_id, and contact BMC Customer Support.

SNMT17S IOCTL(`FIONBIO`) FAILED, ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed in the IOCTL() call, which attempted to set the socket to non-blocking.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of errno and errno_id, and contact BMC Customer Support.

SNMT18S SELECT() FAILED, ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed in the SELECT() call.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of errno and errno_id, and contact BMC Customer Support.

SNMT19S CONNECT() TO SNMP-MASTER-AGENT FAILED, ERRNO(`errno.errno_id`)

Explanation: The SNMP interface failed in the CONNECT() call to the SNMP Master Agent.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of errno and errno_id, and contact BMC Customer Support.

SNMT20S CONNECT() TO SNMP-MASTER-AGENT TIMEDOUT

Explanation: The SNMP interface CONNECT() call to the SNMP Master Agent timed out.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMT21S SEND() DPI TO SNMP-MASTER-AGENT FAILED, ERRNO(`errno.errno_id`)

Explanation:The SNMP interface failed in the SEND() call to the SNMP Master Agent.

errno - the name of the internal TCP/IP event. For a description of possible values of errno, refer to the appropriate TCP/IP vendor documentation.
errno_id - the numeric identity of the internal TCP/IP event. For a description of possible values of errno_id, refer to the appropriate TCP/IP vendor documentation.

SNMP interface processing is discontinued.

Corrective Action: Note the value of errno and errno_id, and contact BMC Customer Support.

SNMT22S CONNECTION TO SNMP-MASTER-AGENT LOST

Explanation: The SNMP interface detected that the connection to the SNMP Master Agent has been lost. SNMP interface tries to re-establish connection with the SNMP Master Agent.

Corrective Action: No action is required.

SNMT23S UNEXPECTED RESPONSE FROM SNMP-MASTER-AGENT TO DPI PORT QUERY

Explanation: The SNMP interface received an un-recognized response from the SNMP Master Agent to the QUERY_DPI_PORT request.

SNMP interface processing is discontinued.

Corrective Action: Contact BMC Customer Support.

SNMT24I CONNECTION ESTABLISHED WITH SNMP-MASTER-AGENT ON HOST(`hostname`) PORT(`port`)

Explanation: The SNMP interface established a TCP/IP connection with the SNMP Master Agent.

hostname - the hostname of the SNMP Master Agent
port - the TCP/IP port of the SNMP Master Agent

Corrective Action: No action is required.

SPG messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages SPG0 through SPG0xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SPG008E INTERNAL ERROR - SPGB PARAMETER ADDRESS IS ZERO

Explanation: While a report was being viewed online during processing of the SPAGE command, an internal error occurred. The SPGB parameter address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG012E UNABLE TO OBTAIN STORAGE FOR INITIAL SPAGE BLOCK

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. Storage could not be obtained for the initial SPAGE block.

The SPAGE command is not processed.

Corrective Action: Increase the region size and retry the SPAGE command.

SPG016E UNABLE TO OBTAIN PROGRAM WORK AREA STORAGE

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. Storage could not be obtained for the program work area.

The SPAGE command is not processed.

Corrective Action: Increase the region size and retry the SPAGE command.

SPG020E INTERNAL ERROR - REPORT RECORD PARAMETER ADDRESS IS ZERO

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The RECORD parameter address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG024E SECURITY EXIT DENIED ACCESS TO THE SPAGE COMMAND

Explanation: You are not authorized to use the SPAGE command.

The SPAGE command is not processed.

Corrective Action: Notify your INCONTROL administrator.

SPG028E UNABLE TO RELEASE EXCESS STORAGE OF EXISTING SPAGE BLOCK

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The excess storage of the existing space block could not be released.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG032E UNABLE TO OBTAIN STORAGE FOR EXTENDED SIZE SPAGE BLOCK

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The excess storage of the extended size space block could not be released.

The SPAGE command is not processed.

Corrective Action: Increase the region size and retry the command.

SPG036E UNABLE TO RELEASE STORAGE OF COPIED SPAGE BLOCK

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The excess storage of the copied space block could not be released.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG040E INTERNAL ERROR - FUNCTION ID PARAMETER ADDRESS IS ZERO

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The function ID parameter address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG044E INTERNAL ERROR - FUNCTION ID CODE IS INVALID

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The function ID code was found to be invalid.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG048E INTERNAL ERROR - WORD COUNT PARAMETER ADDRESS IS ZERO

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The WORD COUNT parameter address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG052E INTERNAL ERROR - CURRENT PAGE PARAMETER ADDRESS IS ZERO

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The CURRENT PAGE parameter address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG056 `E` PARAMETER NOT RECOGNIZED - CORRECT THE COMMAND AND TRY AGAIN

Explanation: While a report was being viewed on line during processing of the SPAGE command, a parameter was not recognized.

The SPAGE command is not processed.

Corrective Action: Correct the parameter in the command and retry the command.

SPG060 `E` INTERNAL ERROR - WORD LIST PARAMETER ADDRESS IS ZERO

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The WORD LIST parameter address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG064E INVALID PARAMETER LENGTH - CORRECT THE COMMAND AND TRY AGAIN

Explanation: While a report was being viewed on line during processing of the SPAGE command, the length of a parameter was found to be invalid.

The SPAGE command is not processed.

Corrective Action: Correct the length of the problematic parameter and retry the command.

SPG068E INVALID PAGE NUMBER - SPECIFY A NUMBER FROM 1 TO 99999999

Explanation: While a report was being viewed on line during processing of the SPAGE command, the number of a page was found to be invalid.

Page numbers in the SPAGE command must be in the range from 1 through 99999999.

The SPAGE command is not processed.

Corrective Action: Correct the problematic page number and retry the command.

SPG072E START PAGE NUMBER MUST BE SPECIFIED BEFORE END PAGE NUMBER

Explanation: While a report was being viewed on line during processing of the SPAGE command, the number of the end page was found to have been specified before the number of the start page.

In the SPAGE command, the start page number must appear before the end page number.

The SPAGE command is not processed.

Corrective Action: Correct the problematic page number and retry the command.

SPG076E START PAGE NUMBER MUST NOT BE GREATER THAN END PAGE NUMBER

Explanation: While a report was being viewed on line during processing of the SPAGE command, the specified start page number was found to be greater than the specified end page number.

In the SPAGE command, the start page number must be less than the end page number.

The SPAGE command is not processed.

Corrective Action: Correct the problematic page number and retry the command.

SPG080E INTERNAL ERROR - SECURITY EXIT CALL ROUTINE ADDRESS IS ZERO

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The security exit call routine address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG084E INTERNAL ERROR - SECURITY EXIT FUNCTION ID ADDRESS IS ZERO

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The security exit function ID address was found to be 0.

The SPAGE command is not processed.

Corrective Action: Do the following:

Record the following information:
- the text of this message
- the IOA products that are installed at your site
- all the messages in the IOA log that relate to the report that was being viewed when the error occurred
- your actions while the report was being viewed, reconstructed as far as possible
Contact BMC Customer Support.

SPG088E START PAGE NUMBER GREATER THAN NUMBER OF PAGES IN THE REPORT

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command. The specified start page number was found to be greater than the number of pages in the report.

The SPAGE command is not processed.

Corrective Action: Correct the problematic page number and retry the command.

SPG092E INTERNAL ERROR - SPAGE COMMAND IS NOT SUPPORTED FOR $SYSDATA RECORDS

Explanation: An internal error occurred while a report was being viewed on line during processing of the SPAGE command.

The SPAGE command does not support $SYSDATA records.

The SPAGE command is not processed.

Corrective Action: Exit from the $SYSDATA record, reenter a User record, and retry the SPAGE command.

SPY messages

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 SPY100 through SPY1xx

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.

SPY1A0I JOB `jobName` OID=`orderId` JOBID CHANGED FROM `jobId1` TO `jobId2`

Explanation: This information message indicates that an NJE job was given a new JES job ID.

NJE jobs are sometimes given a new JES job ID which is different than the original one, because the original job id has been taken by another job, or by a spin-off data set of the same job.

The JES job ID of the job is updated to reflect the change.

Corrective Action: No action is required.

Messages SPY200 through SPY2xx

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.

SPY250I CONTROL-M IS TERMINATING. TERMINATION SHOULD BE COMPLETED IN LESS THAN TWO MINUTES

Explanation:Highlighted, unrollable message.

This information message indicates that the Control-M monitor is about to shut down because of an internal problem. Due to a unique situation, the termination process may take longer than usual.

Control-M monitor will shut down after approximately one minute.

Corrective Action: Do not cancel the Control-M monitor. If it does not shut down after 5 minutes, cancel it with DUMP, prepare the Control-M monitor full output, and notify BMC Customer Support. Find out why the Control-M monitor shut down and start it again as soon as possible.

SPY251I SPY STARTED

Explanation: This information message is generated when the Control-M monitor internal SPY task is started.

Corrective Action: No action is required.

SPY252S `taskType memName jobName /jobId` OID=`orderId` SEVERE INTERNAL ERROR

Explanation: Severe Control-M monitor internal error while processing the above mentioned job order.

Control-M monitor will abend with user code 0006. The internal task CTMSPY will abend with user code 0040.

Corrective Action: Control-M Log should contain additional messages describing the type of error.

SPY253E `taskType memName jobName /jobId` OID=`orderId` NOT FOUND IN QUEUE `num` TIMES

Explanation: Control-M monitor searched number times but did not find the job in the JES queue.

Possible causes are:

Someone has purged the job (before, during or after execution).
The user tried to activate a started task that does not exist in the Procedures library.
The user activated a started task, but the JES parameter STCMCLAS is directed to a non-print output class. See the section on Started Tasks in the Control-M Installation Considerations section in the INCONTROL for z/OS Installation Guide.
The job/STC has been sent to another NJE node while the Control-M NJE option has not been installed.
The jobs output has been read by an external writer before the Control-M monitor has managed to read it. See the section on the Control-M Operational Parameter - HLDCLAS, in the INCONTROL for z/OS Installation Guide.

The job will finish with status Disappeared. The event code is JLOST.

Corrective Action: Check the reason for the disappearance of the job/STC and correct it. Make sure that no-one purges the output of Control-M jobs. (Only cancel commands should be allowed.)

SPY254I `taskType memName jobName /jobId` OID=`orderId` SCANNED

Explanation: This information message is generated when the Control-M monitor finishes processing the job’s output.

Corrective Action: No action is required.

SPY255S `taskType memName jobName /jobId` OID=`orderId` CONTROL-M SHUTTING DOWN - SEVERE ERROR WHILE PROCESSING JOB SYSOUT

Explanation:Highlighted, unrollable message.

Control-M monitor had a severe error while reading the output of the job and is shutting down.

Control-M monitor will shut down.

Corrective Action: Check the contents of the IOA Log for prior messages that will clarify the picture. If you cannot correct the reason, and whenever you start the Control-M monitor, the monitor shuts down again for the same reason, then enter screen 3 of the Online Facility and hold the job order. Prepare the Control-M monitor full output and contact BMC Customer Support.

SPY256S `taskType memName jobName /jobId` OID=`orderId` CONTROL-M SHUTTING DOWN - COMMUNICATION TO "JES" NOT AVAILABLE

Explanation:Highlighted, unrollable message.

The Control-M monitor detected some problem in communication to JES, and shuts down as a precaution. The Control-M monitor is usually one of the first components of the computer environment to detect problems in JES operation. Usually this is because JES was brought down, or is about to get stuck because of an internal JES problem.

The Control-M monitor will shut down.

Corrective Action: Correct the JES problem and restart the Control-M monitor.

SPY257E `taskType memName jobName /jobId` OID=`orderId` DISAPPEARED BECAUSE OF CONTROL-M SHUT DOWN

Explanation: A started task had been started by the Control-M monitor, but had not yet been assigned a job number by the JES, when the Control-M monitor was forced to shut down. When the Control-M monitor was brought up, it considered the output as lost.

The status of the started task will be Disappeared.

Corrective Action: Check very carefully. Maybe the started task did run while the Control-M monitor was down. If so, you have to notify Control-M manually of the results.

SPY258S `taskType memName jobName/blank` OID=`orderId` INSUFFICIENT MEMORY FOR CONTROL-M MONITOR

Explanation: Highlighted, unrollable message.

Insufficient memory for Control-M monitor to trace a started task.

The started task has just been initiated by the Control-M monitor, and the Control-M monitor requires a small work area in order to try to locate the job ID assigned by JES to the started task. Unfortunately, there is insufficient memory for the required work area.

The Control-M monitor will try again after a few seconds (it is possible that memory will be released by other components of the Control-M monitor). Meanwhile, the started task will remain with a STARTED status and the job ID is “blank.” Under severe circumstances of this event, the Control-M monitor may shut down.

Corrective Action: Increase the Control-M monitor region size and start it again. You are working on the limits.

SPY259I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message announces the shut down of the Control-M monitor.

Shut down of Control-M internal spy task by a request of Control-M main task.

Control-M monitor will shut down.

Corrective Action: No action is required.

SPY270E `taskType memName jobName/jobId` OID=`orderId` SYSOUT `action` FAILED [FROM=`class`][DSN=`dsn`] [SECURITY VIOLATION]

Explanation: A sysout operation on the job’s output has failed. SECURITY VIOLATION is displayed if, during an ARCHIVE attempt, the IOASE32 security module does not allow the allocation of the archive data set specified by DSN=dsn.

The failing action can be:

Action	Description
RELEASE	Release the sysout.
DELETE	Delete (purge) the sysout.
NEWCLASS==>class	Change sysout class (to the specified class).
NEWDEST==>destination	Change sysout destination to the specified destination.
ARCHIV	Copy the sysout to a data set.

The FROM= class appears when the sysout operation will be limited to a specified class (not on all the held sysouts).
The DSN= dsn designates the data set name used for the archiving action.

The sysout operation will not be executed, but it will not affect the finishing status of the job (OK or NOTOK).

Corrective Action: Look for a previous message that will clarify the reason for the failure. You will have to execute the sysout operation manually (until next time).

If the action is ARCHIV, and Spool Encryption is in use, make sure that the Control-M monitor is authorized to read all encrypted spool output datasets of jobs submitted by Control-M.

SPY271E `taskType memName jobName/jobId` OID=`orderId` OPEN OF DDNAME "OUT180" FAILED

Explanation: Highlighted, unrollable message.

Open of Control-M work data set described by the OUT180 DD statement failed.

This may be due to the following:

The OUT180 DD statement is missing.
The OUT180 DD statement cannot be opened for sequential processing.

The Control-M monitor will shut down with an error message.

Corrective Action: Correct the JCL for the Control-M monitor and start it again.

SPY272E `taskType memName jobName/jobId` OID=`orderId` INTERNAL STACK CAPACITY OVERFLOW. SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Control-M monitor internal job events stack capacity exceeded.

When Control-M monitor analyzes the job’s output, all the execution events such as condition codes, abend codes, user defined codes, and so on, are accumulated in a stack (in memory). For some reason the stack became full, and Control-M monitor cannot finish analyzing the job’s results. This can happen because of:

A loop in user exit CTMX003 (which is capable of adding events to the stack).
An internal error in the Control-M monitor.

Message SPY278E will be issued. The job will finish with ENDED NOT OK - REASON UNKNOWN status.

Corrective Action: Ask your system programmer to check Control-M exit CTMX003. If this does not solve the problem, call BMC Customer Support. Keep the sysout of the job causing the problem in hold status so further testing can be carried out.

SPY273E `taskType memName jobName/jobId` INTERNAL ERROR. RBA=`rba` INVALID "CODES"- SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Internal error in the operation of Control-M monitor.

Invalid data discovered in the job order which resides in the rba in the Active Jobs file. It can be due to the following:

A Control-M user exit incorrectly modified the job order.
Someone incorrectly modified the Active Jobs file.
A chain of unexpected processing errors occurred prior to this event.
Internal Control-M monitor error.

SPY278E message will follow, and the job will finish with ENDED NOT OK - REASON UNKNOWN status.

Corrective Action: Check the IOA Log. If there are previous severe errors regarding this job, they are probably the cause of the problem. Correct them and the problem should be resolved. Otherwise, have your system programmer call BMC Customer Support for assistance. The IOA representative will need a copy of the Active Jobs file.

SPY275E OID=`orderId` NOT CATLGD `x` ON DSNAME `dsn`

Explanation: A NOT CATLGD 2 (or NOT RECTLGD 2) event has occurred during job execution on data set dsn.

The default of this event is NOTOK for the entire job. The user may specify an ON STEP ANYSTEP CODES *NCT2 DO OK to signify that the event NCT2 (NOT CATLGD 2) is considered OK for this job.

The status of the job will be according to user definition.

Corrective Action: No action is required.

SPY276E `taskType memName jobName/jobId` OID=`orderId` READING SYSOUT FAILED

Explanation: Reading of job’s sysout failed.

Control-M failed to read the job’s output.

The job will finish with status FAILED - REASON UNKNOWN (the event *UKNW).

Corrective Action: Check the IOA Log for additional messages which will clarify the reason for the problem.

SPY277E `taskType memName jobName/jobId` OID=`orderId` INTERNAL ERROR INVALID SYSOUT OPTION_opt. SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Internal error in the operation of Control-M monitor.

Invalid data discovered in the job order. It can be due to the following:

Control-M user exit incorrectly modified the job order.
Someone incorrectly modified the Active Jobs file.
A chain of unexpected processing errors occurred prior to this event.
Internal Control-M monitor error.

SPY278E message will follow, and the job will finish with ENDED NOT OK - REASON UNKNOWN status.

SPY278E `taskType memName jobName/jobId` OID=`orderId` OUTPUT PROCESSING FAILED

Explanation: General message when the processing of the output of the job fails.

The Control-M should contain additional messages concerning the reasons.

Determined by the problem which has caused the failure.

Corrective Action: Check the IOA Log for additional messages.

SPY279I `taskType memName jobName/jobId` OID=`orderId` SYSOUT `action` [FROM=`class`] [DSN=`dsn`]

Explanation: This information message is the result of a successful sysout operation on the job’s sysout.

The sysout operation can be:

Operation	Description
RELEASED	Release the sysout.
DELETED	Delete (purge) the sysout.
NEWCLASS==>class	Change sysout class (to the specified class).
NEWDEST==>destination	Change sysout destination (to the specified destination).
ARCHIVED	Copy the sysout to a data set

The FROM= class will appear when the sysout operation will be limited to a specified class (not on all the held sysouts).
The DSN= dsn will designate the data set name used for the archiving action.

Corrective Action: No action is required.

SPY27AI OID=`orderId` CYCLING STOPPED BY "DO STOPCYCL" STATEMENT

Explanation: A DO STOPCYCL statement in a job scheduling definition caused Control-M to stop cycling a job.

Control-M stops initiating the job at regular intervals when it encounters a DO STOPCYCL statement.

Control-M stops cycling the job and reports the status of the job as OK or NOTOK, depending on the last run of the job.

Corrective Action: To resume cycling of the job, issue a RERUN or RESTART statement for the job from the Active Environment screen.

SPY27CW `step/range stepName.procstepName / stepsRangeNname` REFERENCED BY "ON PGMST" DOESN'T MATCH ANY STEP IN JCL OF JOB

Explanation: The installation parameter DEFSTEP=Y is specified in the CTMPARM member and the step/range referenced by the ON PGMST statement in the job definition does not match any step in the job’s JCL.

The ' Post-Processing Failed' characteristic is added to the job's status in Control-M.

Corrective Action: Check the JCL of job and its corresponding job definition. If one of them was changed, the other one should be corrected accordingly.

SPY27DI SYSOUT ACTION REQUESTED TYPE= [CLASS=] [DEST=] [FROMCLASS=]

Explanation: This information message indicates that the processing of a sysout operation has begun. TYPE= values are: SYSREL (release), SYSPURG (delete), SYSCLAS (change class) and SYSNDST (change destination). CLASS= is the new output class, DEST= is the new destination, FROMCLASS= is the original output class specified in the request.

Corrective Action: No action is required.

SPY27EI SYSOUT ACTION REQUEST QUEUE INITIALIZED SUCCESSFULLY

Explanation: This information message indicates that the sysout action request queue has been initialized successfully.

Corrective Action: No action is required.

SPY27FW SYSOUT ACTION REQUEST QUEUE NOT INITIALIZED - MEMORY ALLOCATION FAILED

Explanation: Sysout action request queue not initialized due to lack of available storage. The enhanced spy feature will not be used.

Corrective Action: To use the enhanced spy feature, increase the REGION size of the Control-M monitor.

SPY27GW SYSOUT ACTION REQUEST QUEUE NOT INITIALIZED - RC FROM IOAREQ IS #

Explanation: Internal error during the initialization of the sysout action request queue. The enhanced spy feature will not be used.

Corrective Action: Report the message ID and return code to BMC Software Customer Support.

SPY27HW SYSOUT ACTION REQUEST QUEUE READ FAILED - RC FROM IOAREQ IS #

Explanation: Internal error during the processing of a sysout request.

Corrective Action: Report the message ID and return code to BMC Software Customer Support.

SPY27JW SYSOUT ACTION REQUEST PUT FREE ENTRY FAILED - RC FROM IOAREQ IS #

Explanation: Internal error during the processing of a sysout request.

Corrective Action: Report the message ID and return code to BMC Software Customer Support.

SPY27KW MULTI-SPY NOT ENABLED - DOES NOT SUPPORT SDSB=F OR SAPI=N

Explanation: The multi-spy feature was not enabled because either SDSB=F or SAPI=N (or both) were specified in CTMPARM.

Corrective Action: To use the enhanced spy feature, specify SDSB=Y and SAPI=Y in CTMPARM.

SPY280W `taskType memName jobName/jobId` OID=`orderIduser message`

Explanation: A user message to the Control-M Log.

The message is created by user exit CTMX003.

The exit is activated during the Control-M sysout scan. If you do not understand the meaning of the message, consult your INCONTROL administrator.

Corrective Action: No action is required.

SPY281I `taskType memName jobName/jobId` OID=`orderId` START `start_daytime` STOP `end_daytime` CPU `nnnn` MIN `ss` SEC SRB `nnnn` MIN `ss` SEC `elapsed_time initiator_num class systemId userData`

Explanation: This information message displays a statistical record containing job and group execution statistics.

Item	Description
`start_daytime`	Start time of the job as Julian date + hour + minutes.
`end_daytime`	Termination time of the job as Julian date + hour + minutes.
CPU	CPU time in minutes and seconds.
SRB	SRB time in minutes and seconds.

The information described above is taken from the job’s output statistical messages (IEF375I, IEF376I).

Item	Description
`elapsed-time`	Elapsed time in minutes and hundredths of a minute.
`initiator-num`	1-character initiator number.
`class`	1-character identifier of the Job class in which the job executed. If the Job class is longer than 1 character, this byte is filled by the "." Character.
`systemId`	4-character system identifier (where the job executed).
`userData`	Statistical information optionally added by user exit CTMX003.

If taskType is GRP, this message represents group execution statistics. However:

the CPU and SRB times will be zero,
the elapsed_time is the time between the start of the first job in the group entity until the end of the last job in the group entity, and
the class, initiator_num, systemId and user-data fields will be blank.

Corrective Action: No action is required.

SPY283I `taskType memName jobName/jobId` OID=`orderId` RE-QUEUED FOR EXECUTION ON STEP `step` ($EJ COMMAND)

Explanation: This information message indicates that the job has been requeued for execution by operator command $EJ (JES2) or has been restarted (JES3 message IAT2006).

This message is recorded for each “requeue” (restart) event during the lifetime of the job. It is an informative message.

Corrective Action: No action is required.

SPY287I OID=`orderId` JOB SYSOUT WAS PURGED SUCCESSFULLY

Explanation: This information message indicates that Control-M cancelled a job submission and purged the job sysout.

During AutoEdit resolution an in-use data set was encountered, such as a %%INCLUDE statement specified for a data set that is in use. Control-M purged the job sysout because an attempt will be made to resubmit the job.

Control-M will attempt to resubmit the job.

Corrective Action: No action is required.

SPY288W OID=`orderId` SUBSYSTEM REQUEST TO PURGE JOB SYSOUT FAILED

Explanation: Control-M cancelled a job submission, but did not manage to purge the job sysout.

During AutoEdit resolution an in use data set was encountered, such as a %%INCLUDE statement specified for a data set that is in use. Control-M tried to purge the job sysout because an attempt will be made to resubmit the job.

Control-M will attempt to resubmit the job.

Corrective Action: Manually purge the job sysout for the failed job.

SPY289E CONTROL-M EXTENDED MCS TRACKING STOPPED. RC=`rc`

Explanation:Highlighted, unrollable message.

A system error occurred when Control-M monitor attempted an extended MCS console operation.

Control-M stops using the extended MCS console.

Corrective Action: Check for a preceding system or IOA message related to this message, and proceed accordingly.

SPY28AE OID=`orderId` CTMCJI INTERNAL ERROR. RC=`rc`, REASON=`rsn`, JOBID=`jobId`

Explanation: An internal error occurred when an NJE job with a changed job ID was being processed.

The process of the job is aborted.

Corrective Action: Call BMC Customer Support with the following data: Job SYSDATA files (the first 3 files of the job created by the system), the IOA Log file for that job, and the message text showing the exact RC, REASON and JOBID.

SPY28GI OID=`orderId` TAPE DRIVE UNITS USED=`nn nn nn nn nn nn nn nn nn nn nn nn`

Explanation: This information message provides statistical information on the tape drive usage of a job.

At the end of each job execution, the job log is checked to evaluate tape drive usage. The UNITDEF member of the Control-M PARM library is used to associate logical names to physical resources (meaning tape drive units). UNITDEF sorts tape drive unit addresses into twelve groups or less.

The variables in this message are:

orderId - the order ID of the job
nn - The number of tape drives in each group used by the tape drive. In the message, each tape drive group is identified by its order after USED (for example, the first group corresponds to the first nn).

Corrective Action: No action is required.

SPY28HW OID=`orderId` AUTO TAPE DRIVE RESOURCE ADJUSTMENT IS BYPASSED DUE TO PREVIOUS MESSAGE

Explanation: Resource adjustment for the Automatic Tape Adjustment facility was bypassed for current job end processing.

An error occurred during resource adjustment for the Automatic Tape Adjustment facility. The reason is described in the preceding message.

Job end processing continues without tape drive adjustment.

Corrective Action: Check the reason described in the preceding message.

SPY28JE OID=orderId ERROR ANALYZING PARM MEMBER "UNITDEF" AT LINE lineNum

Explanation: An error was detected in the specified line of UNITDEF.

There is probably a syntax error.

The Automatic Tape Adjustment facility is turned OFF for the job, and processing continues.

Corrective Action: To implement automatic tape adjustment, correct the error in the specified line and restart Control-M.

SPY28KW OID=`orderId` DAUNITDF DD CARD MISSING

Explanation: There is no valid DD statement that points to UNITDEF.

Either the statement is missing or it contains a syntax error.

The Automatic Tape Adjustment facility is turned OFF for the current job, and processing continues.

Corrective Action: To implement automatic tape adjustment, correct the DD statement that points to UNITDEF and restart Control-M.

SPY28LS OID=`orderId` GETMAIN FAILED IN CTMATD AUTO TAPE PROCESSING

Explanation: There is not enough memory to perform Automatic Tape adjustment.

The region may be too small.

The Automatic Tape Adjustment facility is turned OFF for the current job, and processing continues.

Corrective Action: To implement automatic tape adjustment, increase the size of the region and restart Control-M. If there still is not enough memory, contact your local systems analyst.

SPY28ME OID=`orderId` TAPE UNIT `unitId` IS NOT DEFINED IN "UNITDEF" MEMBER

Explanation: During Automatic Tape Adjustment facility processing, a Tape Unit address was specified in the job log. However, this unit address was not defined in the UNITDEF member.

Resource adjustment for the Automatic Tape Adjustment facility of Control-M was unable to assign Tape Unit address unitId to a defined tape drive type.

The unknown tape drive is ignored for the job and processing continues.

Corrective Action: Check the UNITDEF member of the Control-M PARM library. Verify that the unit address is properly defined.

SPY28NI NEW TAPE DRIVE DEFINITION IS LOADED PER OPERATOR REQUEST

Explanation: This information message indicates that a fresh copy of the UNITDEF member is now in use.

A new copy of the UNITDEF member was loaded in response to modify command F.

Corrective Action: No action is required.

SPY28PW STEP stepname/procname ABENDED, CODE=abCode REASON=rsn

Explanation: This warning message indicates that a step ended abnormally (ABEND).

The ABEND code and the reason code are provided in the message.

Corrective Action: Investigate this JOB, as necessary.

Messages SPYD00 through SPYDxx

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.

SPYD55S OID=`orderId` SYSOUT ARCHIVING FAILED

Explanation:Highlighted, unrollable message.

The Control-M monitor failed to archive SYSDATA for the job. This message is preceded by other messages detailing the nature of the error.

Control-M terminates processing.

Corrective Action: Do the following:

Please refer to the preceding messages and follow the steps recommended in the description of those messages.
Start the Control-M monitor again. If the problem persists, report it to your INCONTROL administrator, who should prepare the Control-M monitor full output and contact BMC Customer Support.

SRV messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages SRV100 through SRV1xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SRV100I `srvr` - IOA ARCHIVE SERVER INITIALIZATION STARTED

Explanation: This information message indicates that the IOA Archive Server has started and is currently building the required internal environment.

Corrective Action: No action is required.

SRV101E `srvr` - IOA ARCHIVE SERVER INITIALIZATION FAILED RC `rc` IN STEP step

Explanation: The IOA Archive Server encountered an internal error.

The cross-memory environment could not be established.

The IOA Archive Server shuts down.

Corrective Action: Activate the Control-D subsystem. If it is already active, deactivate then reactivate it. Try to reactivate the IOA Archive server. If this does not help, check for other system messages that might clarify the cause of the problem and precede accordingly. If these measures are of no avail, record the return code, step name and all other related messages and contact BMC Customer Support.

SRV102E `srvr` - IOA ARCHIVE SERVER NOT APF-AUTHORIZED

Explanation: The IOA Archive Server is not APF (Authorized Programming Facility) authorized. The IOASSRV module is not in an APF authorized library or does not have attribute AC=1.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Add the name of the library in which the IOASSRV module resides to the IEAAPF00 member in the SYS1.PARMLIB library.

SRV103E `srvr` - COMMAND FAILED - `cmdText`

Explanation: An invalid command or parameter was passed to the IOA Archive Server by an operator MODIFY command. This message is accompanied by another message that indicates why the command failed.

The MODIFY command is not executed.

Corrective Action: See the accompanying message, which indicates why the command failed.

SRV104S `srvr` BLDL/LOAD FAILED FOR THE MODULE `modName`

Explanation: Loading of the modName module failed. Possible causes are:

There is insufficient memory.
Another system-oriented cause may be found in the system log.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Check the system job log for more information. If the problem persists, contact BMC Customer Support.

SRV105S `srvr` - UNRECOVERABLE ERROR ENCOUNTERED

Explanation: An unrecoverable error occurred in the operation of the IOA Archive Server.

The IOA Log file should contain a previous message about the error.

The IOA Archive Server shuts down.

Corrective Action: Check the accompanying message in the IOA Log file. Contact your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

SRV106S `srvr` - MEDIA `mediaName` HAS ABENDED

Explanation: An IOA Archive Server internal subtask abended.

The IOA Log file and system log should contain previous messages about this error.

The IOA Archive Server issues an implicit START command for this media. Attempts are made to initialize media mediaName and continue normal processing. If these attempts fail, the IOA Archive Server sets the status of the abended media to never active and this media becomes unavailable for use by the IOA Archive Server.

Corrective Action: Check the IOA Log file and system log for additional messages which may indicate why media mediaName abended. If the problem is not resolved, contact BMC Customer Support.

SRV107I `srvr` - SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message indicates that the IOA Archive Server is shutting down upon operator’s request.

Corrective Action: No action is required.

SRV108E `srvr` - REASON: COMMAND IS INVALID

Explanation: An invalid command was passed to the IOA Archive Server. This message follows message IOA103E or SRV103E, which contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: For more information, refer to the section that describes the IOA Archive Server in the Control-D and Control-V User Guide. Enter a valid MODIFY command.

SRV109S `srvr` - MEDIA TYPE `media_type` IS INVALID OR NOT SUPPORTED

Explanation: The IOA Archive Server encountered an invalid or unsupported media type specified in the IOASPRM member (IOA Archive Server Installation Parameters).

The media type specified in the IOASPRM member should match one of the supported media types specified in the IOA Archive Server Program List (the IOASPROG member).

The IOA Archive Server terminates with a return code of 8.

Corrective Action: For more information about currently supported media types, refer to the section on how to set IOA Archive Server Installation Parameters in the INCONTROL for z/OS Installation Guide. Correct the media type in the IOASPRM member (IOA Archive Server Installation Parameters). Start the IOA Archive Server again. If the problem is not resolved, contact BMC Customer Support.

SRV10AS `srvr` - SERVER NAME IS NOT EQUAL TO THE PROCNAME SPECIFIED IN IOASPRM

Explanation:Highlighted, unrollable message.

The name of IOA Archive Server does not match the value of the PROCNAME parameter in the IOASPRM member. The name of the IOA Archive Server must be the same as the value of the PROCNAME IOA Archive Server Installation Parameter in the IOASPRM member.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Use the correct IOA Archive Server name or correct the value of the PROCNAME parameter. Restart the IOA Archive Server.

SRV10BI `srvr` - IOA ARCHIVE SERVER SHUTTING DOWN

Explanation:Highlighted, unrollable message.

This information message indicates that the IOA Archive Server is shutting down due to operator command or due to internal events.

The IOA Log file should contain additional messages about the reason for shutting down the IOA Archive Server.

The IOA Archive Server shuts down.

Corrective Action: No action is required.

SRV10CS `srvr` - IOA ARCHIVE SERVER ENDED WITH ERROR

Explanation: An error caused the IOA Archive Server to terminate. The IOA Log file and system log file should contain additional messages identifying the specific error.

The IOA Archive Server shuts down.

Corrective Action: Check the IOA Log file and the system log for the reason. Contact your system programmer for assistance if needed.

SRV10DW `srvr` - YOUR IOA ARCHIVE SERVER IS ALREADY ACTIVE. QNAME `qName`

Explanation:Highlighted, unrollable message.

An attempt was made to start an IOA Archive Server which is already active. It is impossible to run two IOA Archive Servers with the same qName at the same time.

The newly-started IOA Archive Server with the same qName shuts down.

Corrective Action: No action is required.

SRV10EE `srvr` - REASON: PARAMETER IS INVALID

Explanation: An invalid parameter was passed to the IOA Archive Server by operator command MODIFY. This message follows the IOA103E or SRV103E message, 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. Reissue the MODIFY command with valid parameters.

SRV110E `srvr` - INSUFFICIENT STORAGE FOR INITIALIZATION RC=`rc`

Explanation: There is insufficient memory to initiate or operate the IOA Archive Server.

The IOA Archive Server shuts down.

Corrective Action: Increase the IOA Archive Server REGION size. If the problem persists, record the return code and contact BMC Customer Support.

SRV114S `srvr` - BLDL/ATTACH FAILED FOR MODULE `modName`

Explanation: Initialization of an IOA Archive Server internal task failed.

Possible causes are:

Insufficient memory to attach the task.
The modName module does not exist in the LOAD library.

The IOA Archive Server terminates.

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 IOA LOAD library does not contain the modName module, contact BMC Customer Support.

SRV115E `srvr` - OPEN OF DDNAME `ddName` FAILED

Explanation: Open of the ddName DD statement failed.

Possible causes are:

The ddName DD statement is missing.
The data set referenced by the ddName DD statement does not exist.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Correct the JCL and rerun the job.

SRV116W `srvr` - ALL MEDIA ARE INACTIVE

Explanation:Highlighted, unrollable message.

The IOA Archive Server issues this message when it determines that no active media are allocated to it.

Every media was terminated due to operator request or internal error. This message disappears when a START command is issued for any media.

The IOA Archive Server continues processing.

Corrective Action: If information about the status of a media is needed, issue a DISPLAY command.

SRV117I `srvr` - IOA ARCHIVE SERVER INITIALIZATION COMPLETE

Explanation: This information message indicates that the IOA Archive Server was successfully initialized.

Corrective Action: No action is required.

SRV118E `srvr` - REASON: MEDIA `mediaName` IS INCORRECT

Explanation: The media was specified in a MODIFY operator command, but was not defined in the IOASPRM member, which defines the IOA Archive Server Installation Parameters. This message follows message IOA103E or SRV103E, 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. Reissue the MODIFY command with the correct media name.

SRV11AE `srvr` - REASON: MEDIA `mediaName` ALREADY INACTIVE

Explanation: An attempt was made to stop media mediaName which was already inactive. This message follows message IOA103E or SRV103E, 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.

SRV11BE `srvr` - REASON: MEDIA `mediaName` ALREADY ACTIVE

Explanation: An attempt was made to start media mediaName which was already active. This message follows message IOA103Eor SRV103E, 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.

SRV11CE `srvr` - INITIALIZATION OF ALL MEDIA FAILED

Explanation: During initialization, the IOA Archive Server determined that initialization failed for all media specified in the IOASPRM member (IOA Archive Server Installation Parameters).

Every media was terminated due to an unrecoverable error. The IOA Log file should contain additional messages concerning specific errors.

The IOA Archive Server terminates with a return code of 8.

Corrective Action: Check the IOA Log file and the system log for messages describing the error. Contact the system programmer for assistance if needed. Start the IOA Archive Server again. If the problem is not resolved, contact BMC Customer Support.

SRV11DW `srvr` - `nn` CYCLES PERFORMED WHILE WAITING FOR MEDIA INITIALIZATION TO BE COMPLETED

Explanation:Highlighted, unrollable message.

The IOA Archive Server cannot complete the initialization phase. During IOA Archive Server initialization, a period of time equal to nn cycles elapsed before any media specified for use by the IOA Archive Server completed the initialization process. 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 the IOA Archive Server is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If the IOA Archive Server waits a long time for media to complete initialization, and the reason for the delay cannot be determined, issue the CANCEL command to stop the IOA Archive Server. Restart the IOA Archive Server. If the problem is not resolved, contact BMC Customer Support.

SRV11EW `srvr` - `nn` CYCLES PERFORMED WHILE WAITING FOR MEDIA TO TERMINATE

Explanation: The IOA Archive Server cannot complete the termination phase. During IOA Archive Server termination, a period of time equal to nn cycles elapsed before the media specified for use by the IOA Archive Server completed the termination process. 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 the IOA Archive Server is not completed.

Corrective Action: Check the IOA Log file and the system log for the cause of the problem. If the IOA Archive Server waits a long time for media to complete termination, and the reason for the delay cannot be determined, issue operator command CANCEL to stop the IOA Archive Server. If the problem is not resolved, contact BMC Customer Support.

SRV11FW `srvr` - REASON: MEDIA `mediaName` IS BUSY

Explanation: A command cannot be passed to media mediaName for execution because the media has not finished executing a previous command. This message follows message IOA103E or SRV103E, 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 later.

SRV120S `srvr` - INTERNAL ERROR RC=`rc`

Explanation: The IOA Archive Server encountered an internal error.

The IOA Archive Server terminates with abend code 0006. The output includes a dump of the abend.

Corrective Action: Report the message ID and return code to BMC Customer Support.

SRV121E srvr - REASON: MEDIA `mediaName` INACTIVE

Explanation: An attempt was made to start a device assigned to media mediaName while that media was inactive. Media mediaName must be started before issuing a START command for a device assigned to it. This message follows message IOA103E or SRV103E, which indicates that operator command MODIFY failed and contains the text of the failed command.

The MODIFY command is not executed.

Corrective Action: Issue the following operator command to start media mediaName: F IOASMON,START MEDIA=media-name

After media mediaName is initialized successfully, issue the MODIFY command to start a device. For more details, refer to the section that describes the IOA Archive Server in the Control-D and Control-V User Guide.

SRV122W `srvr` IOA ARCHIVE SERVER PARAMETERS CONTAIN NO MEDIA OR ONLY MEDIA TYPE DASD

Explanation: During the initialization phase, the IOA Archive Server determined that the IOASPRM member does not include a definition for any media or only includes definitions for media of the DASD type. Possible causes are:

The IOASPRM member in the IOA PARM library does not define any media.
The IOASPRM member in the IOA PARM library has definitions for only DASD media.

Do not activate the IOA Archive Server unless a media type other than DASD is defined in the IOASPRM member.

The IOA Archive Server shuts down.

Corrective Action: If the services of the IOA Archive Server are required, add appropriate media to the IOASPRM member in the IOA Archive Server Installation Parameters, and restart the IOA Archive Server.

SRV123W `cdam_srvr_name` - GETMAIN FAILED DURING SESSION OPENING OF USER `userId`

Explanation: An attempt to access a migrated index failed because there is insufficient memory in the IOA Archive server to open a session. A session is opened in the IOA Archive server when accessing a migrated index. This error occurs when there is not enough memory in the IOA Archive server to hold the RBA range table of the user, and the index record for that index.

The session is not opened and the migrated index cannot be viewed.

Corrective Action: Increase the region of the IOA Archive server.

SRV124W `cdam_srvr_name` - OSE TYPE PASSED TO SERVER BY USERID `userId` IS INVALID

Explanation: An internal error occurred when accessing a migrated index. A session is opened in the IOA Archive Server when accessing a migrated index.

The session is not opened and the migrated index cannot be viewed.

Corrective Action: Print the user record and index records of the report. Record the last actions of the user before the error occurred. Supply this information to BMC Customer Support.

SRV127E `srvr` - DEBUG LEVEL MUST BE A NUMBER BETWEEN 0-255

Explanation: The MODIFY operator command to activate the IOA Archive Server debug facility contains an invalid DEBUG level. Valid DEBUG levels are between 0 and 255. Zero specifies no debugging.

The MODIFY command is not executed. The DEBUG facility is not activated.

Corrective Action: Reissue the operator command with the correct debug level. The required debugging level should be supplied by BMC Customer Support.

SRV128I `srvr` - DEBUG LEVEL IS SET TO `num`

Explanation: This information message indicates that the IOA Archive Server debug level has been set to num by a MODIFY operator command.

Each debug level activates the trace option on different components of the IOA Archive Server.

The DEBUG level is set to level num.

Corrective Action: No action is required.

Messages SRV500 through SRV5xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SRV5A0E SERVER `serverId`, SECURITY ENVIRONMENT CREATION FAILED RC=`rc` REASON=`rsn`

Explanation: The IOASECUR security handling module failed to establish the security environment.

In rules in which value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

This message is often accompanied by message SRV5A1I/CTO281I which contains the error message returned by the locally active security product.

The KSL/TSO/SHELL request is not performed.

Corrective Action: See the DOCSECUR member in the IOA DOC library for a description of rc and rsn.

Correct the security definitions, and verify changes made to the IOASECUR security module. For more information, see the SRV5A1I/CTO281I message (if issued).

SRV5A1I ERROR MESSAGE = `text`

Explanation: This information message indicates that the IOASECUR security module failed to establish the security environment.

In rules in which value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

In this message, text is the error message returned by the security product active at the site.

The KSL/TSO/SHELL request is not performed.

Corrective Action: Depending on the message text, correct the security definitions and/or verify changes made to the IOASECUR security module.

SRV5A2W SERVER `serverId`, SECURITY ENVIRONMENT CLEANUP FAILED RC=`rc` REASON=`rsn`

Explanation: The IOASECUR security handling module failed to reset the security environment.

In rules in which value OWNER or TRIGGER has been specified for the RUNTSEC parameter, the IOASECUR module runs a security check on every DO KSL/TSO/SHELL request included in the rule.

This message is often accompanied by message SRV5A1I which contains the error message text returned by the locally active security product.

Depending on the values of rc and rsn, the DO KSL/TSO/SHELL request may or may not be performed.

Corrective Action: See the DOCSECUR member in the IOA DOC library for a description of rc and rsn.

Correct the security definitions, and/or verify changes made to the IOASECUR security module. For more information, see the SRV5A1I or CTO281I message (if issued).

SRV5A3I CONTROL-O SERVER `serverId` STARTED

Explanation: This information message indicates that the serverId Control-O server has been successfully started.

Corrective Action: No action is required.

SRV5A4I CONTROL-O SERVER serverId ENDED

Explanation: This information message indicates that the serverId Control-O server has been successfully terminated.

Corrective Action: No action is required.

SRV5A5E SERVER `serverId` SEVERE ERROR - `details`

Explanation: The specified server detected an internal error.

The server is terminated.

Corrective Action: Contact BMC Customer Support.

SRV5A6I SERVER `serverId`, request = `requestParms`

Explanation: This information message indicates that the specified server has begun executing the specified request.

Corrective Action: No action is required.

SRV5A7I SERVER `serverId`, request COMPLETION CODE = `rc` ELAPSED `elapsed` CPU `cpu` SRB `srb`

Explanation: This information message indicates that server serverId completed the specified request.

The variables in this message are:

serverId - the identity of the server that completed the request
request - the identity of the TSO request, KOA script, or shell script that was completed
rc - the completion code of request
elapsed - the time that elapsed during execution of request
cpu - the CPU time
srb - the number of SRB units

elapsed and cpu are expressed in the format mmm.ss.hh, where

mmm is the number of minutes
ss is the number of seconds
hh is the hundredths of seconds

Corrective Action: No action is required.

SRV5A8W SERVER `serverId`, TIMEOUT OCCURRED. REQUEST `request`

Explanation: The request performed by the server ran for an interval longer than the number of seconds specified in the TIMEOUT subparameter.

System action depends on the following:

If the rule issued the request and the WAITMODE subparameter is set to Y, the rule resumes with a %%TSORC, %%KSLRC, or %%SHELLRC of 522.
If the STOP subparameter was set to Y, the request is canceled.
Otherwise, the server continues performing the request.

Corrective Action: No action is required.

SRV5A9S CONTROL-O SERVER `serverId` HAS ABENDED. ABEND CODE = `abCode`

Explanation: The server detected an internal abend.

This message indicates an internal error.

The serverId server is terminated.

Corrective Action: Contact BMC Customer Support.

SRV5AIS SERVER TERMINATING DUE TO AN UNRECOVERABLE ERROR

Explanation: Control-O Server is terminating due to an unrecoverable error. A new server will be started on demand.

Corrective Action: Send the server’s full sysout to BMC Customer Support for investigation.

SRV5AJI SERVER TERMINATING DUE TO A CANCELLED TASK

Explanation: Control-O Server is terminating after it had cancelled a request because of a timeout or because of a modify command and SRVTERM is set to Y. A new server will be started on demand.

Corrective Action: No action is required.

Messages SRVH00 through SRVHxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

SRVH00I DOWNLOAD OF ACTIVE DATABASE STARTED

Explanation: Information message issued by the Control-M Application Server indicating that the download of the IOA and Control-M database is currently in progress.

Corrective Action: No action is required.

SRVH01I DOWNLOAD OF ACTIVE DATABASE ENDED SUCCESSFULLY

Explanation: Information message issued by the Control-M Application Server indicating that the download of the IOA and Control-M database has ended successfully.

Corrective Action: No action is required.

SRVH02I SERVER IS READY TO RECEIVE REQUESTS

Explanation: This information message indicates that the Enterprise Controlstation Workstation Gateway server has finished its initialization. The server is now ready to receive requests issued by the Enterprise Controlstation Workstation Gateway.

Corrective Action: No action is required.

SRVH03E DOWNLOAD OF ACTIVE DATABASE FAILED

Explanation: Download of the IOA and Control-M database failed.

The download of the IOA and Control-M database, performed by the Control-M Application Server, has ended with an error.

The Control-M Application Server shuts down.

Corrective Action: Look in the job log, SYSPRINT and IOA Log for messages containing the reason for the failure. After the problem has been resolved, restart the Control-M Application Server.

SRVH04E MODULE `modName` SHOULD BE REUSABLE

Explanation: This message indicates that an IOA module that should have been reusable, is not.

The modName module is supplied with the IOA installation tape with the reusable attribute bit on. However, the reusable attribute has become corrupted.

The program stops executing.

Corrective Action: Copy the modName module from the IOA installation tape to the IOA load library, refresh LLA, and rerun the program.

SRVH05E ERROR DETECTED BY WORKSTATION GATEWAY DURING DOWNLOAD

Explanation: Download of the Active Jobs file failed due to an error encountered by the Workstation Gateway.

Download of the Active Jobs file was initiated, but the Workstation Gateway indicated that an error was encountered on the workstation side.

Download of the Active Jobs file fails.

Corrective Action: Look for error messages issued by the workstation and correct the problem accordingly.

SRVH06I WORKSTATION DATABASE IS SYNCHRONIZED WITH THE MAINFRAME DATABASE

Explanation: This information message is issued after establishment of communication, and indicates either that download of the Active Jobs file has ended successfully, or that it is not required.

Corrective Action: No action is required.

SRVH07E KSL INTERNAL ERROR TYPE `err_type`, RC = `rc`

Explanation: The Control-M Application Server encountered problems interfacing with the KSL subtask.

In this message, err_type is one of the following:

Type	Description
0001TYPE 0001	Attempt to initialize KSL subtask.
TYPE 0002	Waiting for KSL subtask to perform a request.
TYPE 0003	KSL subtask ended abnormally.

The return code contains the system abend code.

The Control-M Application Server shuts down.

Corrective Action: Check the messages in the job log and the output in file DAKSLOUT. If message CTM555S appears, increase the REGION size. If no relevant messages appear, contact BMC Customer Support.

SRVH08I DOWNLOAD OF {CONTROL-M ACTIVE JOBS FILE | RES. FILE AND IOA COND. FILE} {STARTED | ENDED}

Explanation: This information message indicates that downloading of the specified file started or ended.

The specified file is being downloaded from Control-M on the mainframe to an Enterprise Controlstation. This message indicates which phase of the download process was reached.

Corrective Action: No action is required.

SRVH09E OPEN OF KSL COMMUNICATION FILE FAILED. DDNAME "KSLCOMM"

Explanation: Open of the KSL Communication file failed (the KSLCOMM DD statement). This error message is issued by the Control-M Application Server and may be due to one of the following:

The KSLCOMM DD statement is missing.
The Control-M Application Server JCL procedure has been modified.

The Control-M Application Server shuts down.

Corrective Action: Correct the Control-M Application Server JCL procedure, and restart the Control-M Application Server.

SRVH0AI REMOTE FORCEJOB PROCESSED OK ON REMOTE CTM, ID: `remote_Control-M_ID`

Explanation: This information message indicates that a remote FORCEJOB request that was sent to the remote Control-M was processed OK. It is followed by a sequence of SRVH0EI messages detailing the response from the remote Control-M.

Corrective Action: No action is required.

SRVH0BE REMOTE FORCEJOB PROCESSED WITH ERRORS ON REMOTE CTM, ID: `remote_Control-M_ID`

Explanation: Indicates that a remote FORCEJOB request that was sent to the remote Control-M failed (the remote Control-M could not force that job). It is followed by a sequence of SRVH0EI messages detailing the response from the remote Control-M.

Corrective Action: Correct the problem indicated by the messages and then re-attempt to force the job.

SRVH0EI `<message from remote Control-M>`

Explanation: Follows a SRVH0BE message, providing details from the remote Control-M of why the remote Control-M could not force that job.

Corrective Action: Correct the problem indicated by the messages and then re-attempt to force the job.

SRVH10I {CTWSRVE | CTWDET} {STARTED | ENDED}

Explanation: This information message indicates that the Control-M Application Server initiated or shut down subtasks.

Corrective Action: No action is required.

SRVH12E SERVER INTERNAL ERROR TYPE `type`

Explanation: The server program detected an internal error.

This error message is issued by the CTWSRVR program, which is activated as part of the Control-M Application Server, and is due to reasons beyond the user’s control.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

SRVH14E ABEND `sysAbend-userAbend` DURING DOWNLOAD - MEMBER: `memName` ORDERID: `orderId`

Explanation: A system or user abend occurred while downloading a member.

The variables in this message are:

sysAbend - the number of the system abend
userAbend - the number of the user abend
memName - the member’s name
orderId - the member’s order ID

The Control-M Application Server terminates processing.

If DWNLDERR=LOG is specified in the CTMPARM member, this message is written to the IOA log file and no further action is taken. If DWNLDERR=EMX is specified in the CTMPARM member, the memName member is excluded from the download process when the Control-M Application Server is restarted.

Corrective Action: Contact BMC Customer Support and provide the error information.

SRVH15W POSSIBLE LOOP DURING DOWNLOAD - MEMBER: `memName` ORDERID: `orderIdnumSeconds`

Explanation: The Control-M Application Server detected a possible loop during download in the processing of the memName member.

The variables in this message are:

memName - the member’s name
orderId - the member’s order ID
numSeconds - the number of seconds that have passed since the loop possibility was first detected

Corrective Action: Determine whether the problem is transient or whether it is necessary to shut down the Control-M Application Server and possibly exclude the memName member from the download process when the Control-M Application Server is restarted.

SRVH16I MEMBER: `memName` ORDERID: `orderId` EXCLUDED FROM DOWNLOAD

Explanation: This information message indicates that the memName member was not downloaded during the current downloading of jobs from the AJF to Control-M/EM because it was previously excluded from this process.

The member may have been automatically excluded because it caused an abend during a prior download and DWNLDERR=EMX is specified in the CTMPARM member, or because it was intentionally excluded using the CTMAPI command EMDOWNLD EXCLUDE MEMBER= memName.

The variables in this message are:

memName - the member’s name
orderId - the member’s order ID

Corrective Action: No action is required.

SRVH17I MEMBER: `memName` ORDERID: `orderId` WILL BE EXCLUDED FROM NEXT DOWNLOAD

Explanation: This information message indicates that the memName member will not be downloaded during the next downloading of jobs from the AJF to Control-M/EM.

This action is taken because the exclude action is indicated in the CTMPARM member by the parameter DWNLDERR=EMX.

Corrective Action: No action is required.

SRVH18E MEMBER: `memName` ORDERID: `orderId` NOT FLAGGED FOR EXCLUSION: `rc rsn`

Explanation: Indicates that a job, which caused an abend while downloading to Control-M/EM, and was therefore supposed to be flagged for exclusion from the next download, could not be flagged. The full message details the return code and reason code, which specify why the job could not be flagged.

Corrective Action: If the problem occurring during download persists, contact Control-M support.

SRVH1GE ABEND DURING UPLOAD OF TABLE `tableName`

Explanation: Upload of a job table from Control-M/EM failed because of invalid data sent from Control-M/EM.

Corrective Action: Contact BMC Support and provide the details of the problematic job table.

SSO messages

This group includes messages for the Control-O product.

Messages SSO200 through SSO2xx

This group includes messages for the Control-O product.

SSO230E SUBSYSTEM `cto_subsys_name` INITIALIZATION FAILED - JES COMMAND SUPPRESSION NOT ACTIVATED

Explanation: During Control-O initialization, Control-O failed to activate the Control-O subsystem (cto_subsys_name) that is used to suppress JES2 commands.

To suppress JES2 commands, Control-O uses the subsystem identified in the JCMDSSN parameter in the CTOPARM member in the IOA PARM library. That subsystem must be defined in SYS1.PARMLIB(IEFSSN xx), and must be activated in the last IPL before Control-O is started.

Control-O initialization continues, but the JES2 command suppression function is disabled.

Corrective Action: Notify the INCONTROL administrator.

SSO231E SUBSYSTEM `cto_subsys_name` WAS NOT PRE-DEFINED - JES COMMAND SUPPRESSION NOT ACTIVATED

Explanation: During Control-O initialization, Control-O failed to activate the Control-O subsystem (cto_subsys_name) that is used to suppress JES2 commands, because the subsystem was not properly predefined.

Control-O initialization continues, but the JES2 command suppression function is disabled.

Corrective Action: Notify the INCONTROL administrator.

SSO234W SUBSYSTEM `subsys` ALREADY INACTIVE

Explanation: During Control-O termination, Control-O deactivates the IOA subsystem and the Control-O subsystem currently in use. On this occasion, the subsystem identified in the message was already inactive.

Control-O termination continues.

Corrective Action: Notify the INCONTROL administrator.

SSO235W `subsys` ALREADY ACTIVE

Explanation: During Control-O initialization, Control-O tried to activate the IOA subsystem and the Control-O subsystem, but detected that the subsys subsystem was already active.

Control-O initialization continues.

Corrective Action: Notify the INCONTROL administrator.

SSO236E ERROR WHILE ATTEMPTING TO OPEN THE STEPLIB DATASET

Explanation: Control-O could not open file STEPLIB.

Control-O encountered an error opening the STEPLIB file while attempting to activate the alternate subsystem.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that a STEPLIB library or concatenation of libraries exists. Reactivate Control-O.

SSO237E ERROR WHILE ATTEMPTING TO LOCATE (BLDL) ONE OF THE SUBSYSTEM FUNCTION ROUTINES

Explanation: Control-O could not find at least one of the alternate subsystem function routines.

While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries and reactivate Control-O.

SSO238E ERROR WHILE ATTEMPTING TO LOAD ONE OF THE SUBSYSTEM FUNCTION ROUTINES

Explanation: Control-O could not load at least one of the alternate subsystem function routines.

While attempting to activate the alternate subsystem, Control-O could not find at least one of the alternate subsystem function routines in the STEPLIB library or concatenation of libraries.

Control-O continues without activating the alternate subsystem.

Corrective Action: Verify that these modules exist in the STEPLIB library or concatenation of libraries and reactivate Control-O.

SSO239E ERROR WHILE ATTEMPTING TO ACQUIRE STORAGE FOR SUBSYSTEM FUNCTION ROUTINES OR THE SSVT

Explanation: Control-O could not acquire enough CSA (Common Service Area) storage to load alternate subsystem function routines or to build the SSVT for the alternate subsystem.

Control-O continues without activating the alternate subsystem.

Corrective Action: If storage defined for CSA is not large enough, increase the CSA size and perform an IPL.

SSO23AI ALTERNATE SUBSYSTEM subsys SUCCESSFULLY INITIALIZED

Explanation: This information message indicates that the CTOSSO module successfully activated the alternate subsystem.

Corrective Action: No action is required.

STM messages

This group includes messages for the Control-O product.

Messages STM700 through STM7xx

This group includes messages for the Control-O product.

STM741S ERROR IN CONTROL STATEMENT - `err`

Explanation: An invalid control statement was encountered.

The CTORSTM statistics reports utility encountered one of the following errors:

INVALID SORTBY STATEMENT A SORTBY statement contains an invalid sort key.
NO PARAMETER SPECIFIED No operand was specified in the control statement.
INVALID STATEMENT An unrecognized control statement was encountered.
MASK TOO LONG An INCLUDE/EXCLUDE statement contains a mask which is longer than 12 characters.

The CTORSTM utility terminates with a return code of 08.

Corrective Action: Correct the invalid statement and rerun the job.

STM742S ERROR IN OPEN OF INPUT FILE

Explanation: The CTORSTM statistics report utility could not open the input file specified in the DAREPIN DD statement.

An OPEN request was issued to the input file, but was unsuccessful. A possible cause of the problem is that the DAREPIN DD statement may not have been specified in the job stream.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the input file. Correct the error and rerun the job.

STM743S INTERNAL ERROR - `errorText`

Explanation: The CTORSTM statistics report utility encountered the errorText internal error.

The utility terminates with return code of 08.

Corrective Action: Contact BMC Customer Support.

STM744S ERROR IN OPEN OF REPORT FILE

Explanation: The CTORSTM statistics report utility could not open the report file specified in the SYSPRINT DD statement.

An OPEN request was issued to the REPORT file, but was unsuccessful. A possible cause of the problem is that the SYSPRINT DD statement may not have been specified in the job stream.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the report file. Correct the error and rerun the job.

STM745S ERROR IN OPEN OF STATISTICS FILE

Explanation: The CTORSTM statistics report utility could not open the Statistics file.

Failure to open the Statistics file may have been caused by one of the following:

The data set allocated to the DASTF DD statement was not formatted as a Control-O Statistics file.
The data set allocated to the DASTF DD statement was formatted as a Control-O Statistics file by a different version of Control-O.
The data set allocated to the DASTF DD statement belongs to a different installation of Control-O.

The utility terminates with a return code of 08.

Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.

STM746S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`

Explanation: Dynamic allocation of the dsn Statistics file failed with a return code of rc and a reason code of rsn.

The CTORSTM statistics report utility terminates with a return code of 08.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide to determine the cause of the error and correct the error accordingly. If not successful, contact BMC Customer Support.

STM747W ERROR IN CLOSE OF STATISTICS FILE

Explanation: The CTORSTM statistics report utility could not successfully close the Statistics file.

The utility terminates with a return code of 08.

Corrective Action: If no MVS error messages clarifying the error were issued, this is probably an internal error. In this case, please report it to BMC Customer Support.

STM748I NO INPUT CONTROL STATEMENTS WERE SPECIFIED. DEFAULT REPORT WILL BE PRODUCED

Explanation: This information message indicates that no report control statements were specified in the input data set.

The input data set is empty. The report is produced using the following default control statements:

SORTBY COUNTINCLUDE *

The default report is produced.

Corrective Action: No action is required.

STO messages

This group includes messages for the Control-O product.

Messages STO100 through STO1xx

This group includes messages for the Control-O product.

STO171S STATISTICS FILE OVERFLOW

Explanation: All Statistics file index entries are in use. No new statistics can be accumulated.

The Statistics Facility could not accumulate statistics because the number of message IDs exceeds the maximum number of allowable entries in the Statistics file.

Statistics accumulation stops.

Corrective Action: Please review the following recommendations; then format the Statistics file and restart the Statistics Facility:

Enlarge the Statistics file by using the following procedure: a. Increase the value of the STREC# parameter in CTOPARM.b. Delete or rename the old Statistics file to allow a new Statistics file allocation.c. Allocate and format a new Statistics file.
Use AutoEdit option %%$STATID to customize message ID determination. This option can be used to decrease the number of message IDs that are generated. See the INCONTROL for z/OS Administrator Guide for more information.

STO172S STATISTICS FILE IS NOT FREE

Explanation: The Statistics file is locked.

Either the Statistics file is in use by another Control-O monitor or utility, or Control-O abended previously while updating the Statistics file.

Statistics accumulation is not performed.

Corrective Action: Check if another Control-O monitor or utility uses this Statistics file. If this is not the case, then reformat the Statistics file and restart the Statistics Facility.

STO173S OPEN OF STATISTICS FILE FAILED

Explanation: The Control-O Statistics facility attempted to open the Statistics file but did not succeed.

Failure to open the Statistics file may be due to the following:

The data set allocated to the DASTF DD statement was not formatted as a Control-O Statistics file.
The data set allocated to the DASTF DD statement was formatted as a Control-O Statistics file by a different version of Control-O.
The data set allocated to the DASTF DD statement belongs to a different installation of Control-O.

Statistics accumulation is not performed.

Corrective Action: Look for previous MVS error messages regarding the opening of the Statistics file. Correct the error and rerun the job.

STO174S FILE ALLOCATED TO DDNAME "DASTF" IS NOT A CONTROL-O STATISTICS FILE

Explanation: The Control-O Statistics Facility attempted to read the file allocated to DD name DASTF, but it is not a formatted Statistics file.

Statistics accumulation is not performed.

Corrective Action: Format the Statistics file and restart the Statistics Facility.

STO175E RELEASE OF THE STATISTICS FILE IS NOT SUPPORTED BY THIS RELEASE

Explanation: The format of the Statistics file is not supported by the current release of Control-O. The Statistics file could not be read by the Control-O Statistics Facility.

The Statistics file was formatted by an earlier release of Control-O.

Statistics accumulation is not performed.

Corrective Action: Format the Statistics file in the currently supported format, and restart the Statistics Facility.

STO176E THE STATISTICS FILE BELONGS TO A DIFFERENT CONTROL-O MONITOR

Explanation: The assigned ID of the Statistics file does not match the ID of the Control-O monitor.

When a Statistics file is formatted, it is associated with a particular Control-O monitor. The CTOMFST Statistics Formatting utility takes the ID of the Control-O monitor from the QNAME parameter in CTOPARM, and assigns it to the Statistics file.

The ID of the active Control-O monitor does not match the assigned ID of the Statistics file. The probable cause of the error is that the value of QNAME was changed without reformatting the Statistics file.

Statistics accumulation is not performed.

Corrective Action: Format the Statistics file with the correct Control-O ID and restart the Statistics Facility.

STO177S CONTROL-O STATISTICS SEVERE INTERNAL ERROR, ID=`code`

Explanation: The Control-O Statistics Facility encountered an internal error.

In this message, code is the internal error code.

Statistics accumulation stops.

Corrective Action: Look for previous messages to identify the cause of the problem and contact BMC Customer Support.

STO178S STORAGE ALLOCATION FOR STATISTICS FAILED

Explanation: Storage allocation for the Control-O Statistics Facility failed because the Statistics Facility could not obtain enough working storage for processing.

Statistics accumulation is not performed.

Corrective Action: Increase the Control-O region size and restart a new Control-O monitor.

STO179S I/O ERROR ACCESSING THE STATISTICS FILE

Explanation: A READ/WRITE error occurred when accessing the Statistics file.

Statistics accumulation stops.

Corrective Action: Look for previous MVS error messages regarding Statistics file I/O errors, and correct accordingly. If MVS messages do not clarify the error, please contact BMC Customer Support.

STO180S CONTROL-O STATISTICS FILE INTERNAL ERROR. RECORD TYPE MISMATCH

Explanation: The Statistics Facility has encountered a corruption in the Statistics file. The Statistics file cannot be processed.

Statistics accumulation stops.

Corrective Action: Contact BMC Customer Support.

STO181S CONTROL-O STATISTICS INTERNAL ERROR. WRITE FAILED FOR SECTION `section`

Explanation: Due to an internal error, update of the Statistics file failed while writing a section of the Statistics file.

Statistics accumulation stops.

Corrective Action: Contact BMC Customer Support.

STO182S CLOSE OF CONTROL-O STATISTICS FILE FAILED

Explanation: During termination, the Control-O Statistics Facility failed to close the Statistics file.

The Statistics Facility continues terminating without closing the Statistics file.

Corrective Action: Check the system log for previous error messages. If none are found, please contact BMC Customer Support.

STO184I CONTROL-O STATISTICS ACCUMULATION STARTED

Explanation: This informative message indicates that the Control-O Statistics Facility initialization completed successfully and that Control-O statistics are being accumulated.

Corrective Action: No action is required.

STO185S CONTROL-O STATISTICS INITIALIZATION ERROR

Explanation: Control-O Statistics Facility did not initialize successfully.

Statistics accumulation is not performed.

Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

STO186E STATISTICS ACCUMULATION ERROR WHILE PROCESSING SUBSYSTEM REQUESTS

Explanation: The Statistics Facility detected an error while processing requests from the Control-O subsystem.

Statistics accumulation stops.

Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

STO187E STATISTICS ACCUMULATION ERROR DURING FILE UPDATE

Explanation: The Statistics Facility detected an error while updating the Statistics file.

Statistics accumulation stops.

Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

STO189I CONTROL-O STATISTICS ACCUMULATION ENDED

Explanation: This informative messages is issued after normal termination of the Statistics Facility. Statistics accumulation is discontinued.

Corrective Action: No action is required.

STO190S CONTROL-O STATISTICS TERMINATION ERROR

Explanation: Control-O Statistics Facility did not terminate successfully.

The Statistics Facility continues the termination process.

Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and then correct accordingly.

STO191S STATISTICS ACCUMULATION ERROR WHILE PROCESSING USER REQUESTS

Explanation: The Statistics Facility detected an error while processing a SHOW, EXCLUDE or RESET online user request.

Statistics accumulation stops.

Corrective Action: Look for previous error messages in the IOA Log to determine the cause of the error, and correct accordingly.

STO192E STATISTICS REQUEST FOR MESSAGE ID `msgId` FAILED - MESSAGE ID NOT FOUND

Explanation: A SHOW, EXCLUDE or RESET request for message ID msgId failed.

An online user requested a SHOW/EXCLUDE/RESET for message ID msgId. This message ID was not found in the Statistics file.

The online request is not performed. The Statistics Facility continues processing.

Corrective Action: Notify BMC Customer Support of the problem.

STO193E STATISTICS REQUEST FOR MESSAGE ID `msgId` FAILED - INVALID REQUEST

Explanation: Due to an internal error, the user’s online request regarding message ID msgId was not recognized.

The request is not performed. The Statistics Facility continues processing.

Corrective Action: Notify BMC Customer Support.

STO194W WAITING FOR THE STATISTICS FILE - FILE IN USE

Explanation: Control-O is attempting to access the Statistics file, but it is in use by another Control-O monitor or Control-O utility.

Control-O waits and attempts to access the Statistics file again.

Corrective Action: This message is not necessarily the result of an error. It may be issued while generating a statistics report or when the Online Facility attempts to access the Statistics file. If the Statistics file is not freed in a reasonable period of time, check what job is using it and free it.

STO195E RESET OF STATISTICS FOR MESSAGE ID `msgId` FAILED

Explanation: An online user requested a RESET of the statistics for message ID msgId, but due to internal error, the request could not be performed by Control-O.

The RESET request is not performed. The Statistics Facility continues processing.

Corrective Action: Notify BMC Customer Support.

STO196S STATISTICS FILE DYNAMIC ALLOCATION ERROR `rc/rsn/dsn`

Explanation: Dynamic allocation of Statistics file dsn failed with return code rc and reason code rsn.

Statistics accumulation is not performed.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide to determine this cause of the error, and correct the error accordingly. If not successful, contact BMC Customer Support.

STO197I CONTROL-O STATISTICS GLOBAL RESET COMPLETE

Explanation: This information message indicates that a global statistics reset was completed successfully.

Global statistics reset command F CONTROLO, RESETSTAT was issued and performed successfully.

Corrective Action: No action is required.

STO198E RESET OF DATE FOR MESSAGE ID `msgId` FAILED

Explanation: Statistics for message ID msgId were reset as requested, but due to an internal error, update of the last reset date was not successful.

Statistics are reset. The Statistics Facility continues processing, but the indicated last reset date is incorrect.

Corrective Action: Notify BMC Customer Support.

STO199I STATISTICS OF MESSAGE ID `msgId` RESET

Explanation: This informative message indicates that the requested statistics reset for message ID msgId was successfully performed.

Corrective Action: No action is required.

Messages STO200 through STO2xx

This group includes messages for the Control-O product.

STO240W STATISTICS FILE NEARLY FULL - percentage USED

Explanation:Highlighted, unrollable message.

The Statistics file is approaching its maximum capacity.

The Statistics file continues accumulating statistics until it becomes full.

Corrective Action: The user can take one of three actions:

Reformat the Statistics file using installation job DEFSTAT. This deletes all saved statistics and restarts the tracking process.
Enlarge the Statistics file using the CTOCSF utility. This retains the existing statistics and increases the space available for the tracking of new message IDs.
Do nothing. If the Statistics file becomes full, statistics of message IDs which exist in the file will continue to be tracked, but new message IDs will not be added to the file.

STO241E STATISTICS FILE IS FULL. NEW MESSAGE IDS WILL BE LOST

Explanation:Highlighted, unrollable message.

The Statistics file is full.

All statistics records according to the number (STREC#) set in the CTOPARM parameter file have been utilized.

Control-O continues to collect statistics for existing messages, but the statistics for new message IDs are not saved.

Corrective Action: The user can take one of three actions:

Reformat the Statistics file using installation job DEFSTAT. This deletes all saved statistics and restarts the tracking process.
Enlarge the Statistics file using the CTOCSF utility. This retains the existing statistics and enables new message IDs to be tracked.
Do nothing. Statistics of message IDs which exist in the file will continue to be tracked. Statistics of new message IDs will not be tracked.

SUB messages

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 SUB100 through SUB1xx

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.

SUB130I `jobName/jobId` OID=`orderId` RELEASED

Explanation: This information message indicates that the Control-M monitor released a job for execution.

Jobs ordered by the On Spool Facility are not submitted by Control-M. They are released for execution by Control-M using an operator command.

Corrective Action: No action is required.

SUB131I SUBMITTER STARTED

Explanation: This information message is generated when the Control-M monitor internal submitter task starts.

Corrective Action: No action is required.

SUB132I `taskType memName stcname` OID=`orderId`/STARTED

Explanation: This information message indicates that the started task specified in the member parameter started.

Normal message when starting a started task.

Corrective Action: No action is required.

SUB133I `taskType memName jobName/jobId` OID=`orderId` SUBMITTED FROM LIBRARY `lib`

Explanation: This information message indicates that a job has been submitted.

Corrective Action: No action is required.

SUB134E `taskType memName jobName/jobId` OID=`orderId` OPEN OF MEMBER FAILED

Explanation: Open of the memName member for submission failed.

This could be due to one of the following:

The member does not exist in the specified library.
Insufficient memory to open the memName member.

The job will not be submitted and the job will finish with NOT SUBMITTED status for reason NOMEM.

Corrective Action: Perform the following actions:

Check for the existence of the member in the library.
Increase the Control-M monitor REGION size.

SUB135E `taskType memName jobName/jobId` OID=`orderId` SUBMIT FAILED

Explanation: Submission of job failed.

Control-M Log should contain a prior message concerning the reason for failure.

Corrective Action: Check the Control-M Log for the failure reason.

SUB136E `taskType memName jobName/jobId` OID=`orderId` NO JOB CARD

Explanation: A job statement is missing in the member.

The member specified in the member parameter does not contain a job statement.

Corrective Action: No action is required.

Check the contents of the memName member. If necessary, correct and rerun.
Check if the JCL member is in ISPF format. Control-M does not support this format.

SUB137W `taskType memName jobName/jobId` OID=`orderId` MORE THAN ONE JOB CARD

Explanation: The memName member contains more than one job statement.

Control-M submits all the jobs in the member but controls the first one only.

Corrective Action: It is highly recommended to put only one job statement (one job) in a member.

SUB138E OID=`orderId` READING OF THE SYSOUT OF PREVIOUS RUN(S) OF ORDERID `orderId` FAILED

Explanation: Control-M was unable to read the archived sysout of previous runs of the job.

For restarted jobs only, Control-M/Restart retrieves all the required information from the sysout of the job. For restarted NJE jobs, the Control-M monitor must read the sysout since it may not be available on the remote processor. The likely reason that the sysout was not found is that it was manually deleted.

The job will not be submitted (and therefore not restarted) by Control-M.

Corrective Action: Check why the archived sysout was not available for reading. If the CDAM files were manually deleted, the restart cannot be run. If the sysout still exists, contact your INCONTROL administrator.

SUB139S INITIALIZATION OF SUBMITTER FAILED

Explanation: Initialization of Control-M monitor internal submitter task failed.

Control-M monitor shuts down.

Corrective Action: Check the IOA Log and the computer log for the reason of failure.

SUB13AI `task-type task-name` OID=`order-id` SUBMITTER STARTED PROCESSING JOB ON SYSTEM: `system-id`

Explanation: This information message indicates that Control-M has begun the submission process for the indicated task. Message SUB133I will follow and indicates the task was submitted.

Corrective Action: No action is required.

SUB140S INSUFFICIENT MEMORY FOR CONTROL-M MONITOR

Explanation: Insufficient memory for Control-M monitor (during the submission process).

Control-M monitor will shut down.

Corrective Action: Try to increase the REGION of the Control-M monitor.

SUB141E `taskType memName jobName/jobId` DSN `memLib` NOT FOUND

Explanation: The data set described by the memLib parameter is not on the disk.

The job will not be submitted, and the job will finish with NOT SUBMITTED status for reason NOLIB.

Corrective Action: Check the validity of the memLib parameter.

SUB142E `taskType memName jobName/jobId` DSN `memLib` - DYNAMIC ALLOCATION FAILED

Explanation: Dynamic allocation for the data set specified in the memLib parameter failed.

Probable causes are:

Insufficient memory for Control-M monitor.
The DALIB1 DD statement is allocated to the Control-M monitor procedure (it should be reserved for Control-M use).
Other system-related reason.

The job will not be submitted and the job will finish in NOT SUBMITTED status.

Corrective Action: Do one of the following:

Increase Control-M monitor REGION size.
Omit the DALIB1 DD statement from the Control-M monitor procedure.
See the IOA Log, the computer log, and the Control-M monitor sysout for additional messages that will clarify the reason.

If all the above steps fail, call BMC Customer Support for assistance.

SUB143E `taskType memName jobName/jobId orderId` INTERNAL ERROR ON `routineName` MISSING PARAMETER. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the Control-M monitor.

Depending on the severity of the problem, the Control-M monitor will shut down, or at least the job submission will be stopped.

Corrective Action: Have your system programmer call your IOA administrator for assistance. If the Control-M monitor keeps shutting down, hold the problematic job order in the Control-M Active Environment screen (3).

SUB144E `taskType memName jobName/jobId` OID=`orderId` INTERNAL ERROR ON `routineName` ACT BEFORE INIT. INFORM IOA ADMINISTRATOR

Explanation: Internal error in Control-M monitor.

Depending on the severity of the problem, the Control-M monitor will shut down, or at least the job submission will be stopped.

Corrective Action: Have your system programmer call your IOA Administrator for assistance. If the Control-M monitor keeps shutting down, hold the problematic job order in the Control-M Active Environment screen (3).

SUB145E `taskType memName jobName/jobId` OID=`orderId` ERROR IN IOAMEM FUNCTION `func`: RETURN CODE `rc`

Explanation: Internal error in Control-M monitor.

The eight digits that rc represents include a 4-digit reason code and a 4-digit return code. For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

Job submission stops. In some cases, the Control-M monitor will shut down.

Corrective Action: Ask your INCONTROL administrator for assistance. If the Control-M monitor shuts down repeatedly, use the H option of the Control-M Active Environment screen (3) to hold the order that is causing the problem.

If the return code indicates that an abend has occurred, check the Control-M system log for system messages associated with the abend.

SUB146W `taskType memName jobName/jobId` OID=`orderId` TOO MANY DSNAMES FOR CTMLIB

Explanation: Internal Table Overflow in AutoEdit processing.

There is a limit to the number of libraries which may be open simultaneously in the process of submission of a single job. In the processing of AutoEdit variables each time a library is named in a %%INCLIB statement which is not the last statement of the current %%INCMEM, an entry is made in an internal table. This table’s capacity has been exceeded.

The Control-M monitor shuts down with error.

Corrective Action: While the Control-M monitor is shut down, hold the job order causing the problem. Delete it after the Control-M monitor is restarted. The job must be simplified before it can be successfully processed by Control-M.

SUB147S INITIALIZATION OF MAIN LIB FAILED. DDNAME `ddName`

Explanation: The Control-M JCL library initialization failed (the DALIB DD statement).

This message is issued for one of the following reasons:

The Control-M monitor could not be initialized.
The user attempted to order or force a job which cannot be found.
The problem can be due to one of the following:
The DALIB DD statement is missing from the Control-M monitor procedure.
The data set referenced by the DALIB DD statement is not a partitioned data set with record length 80.
Other reasons described in the System log.

System action depends on the following:

If the Control-M monitor indicates a problem with the [main library], the monitor will shut down.
If the message indicates that a job could not be found, the order/force request is ignored.

Corrective Action: Check the computer log and/or the IOA Log file for messages which describe the problem. Correct the problem. If necessary, restart the Control-M monitor.

SUB148E `taskType memName jobName/jobId` OID=`orderId` DSN NOT CATALOGED

Explanation: Data set described by the MEMLIB or OVERLIB parameter is not cataloged.

The job will not be submitted, and it will finish with NOT SUBMITTED status for reason NOLIB.

Corrective Action: Check the validity of the MEMLIB or OVERLIB parameter.

SUB149W `taskType memName jobName/jobId` OID=`orderId` DSN `memLib` IN USE (DISP=OLD)

Explanation: The data set described by the memLib parameter is in use.

Another user is holding the library using the statement DISP=OLD.

Submission of this member will be tried again after a few seconds.

Corrective Action: See if the user who is holding the library can free it.

SUB14AE JOB `memName` OID=`orderId` NOT SUBMITTED, MIGRATED DSN `lib`

Explanation:Highlighted, unrollable message.

The job was not submitted because the library that contains its member migrated.

The job is not submitted and is assigned a NOTOK status for reason NOLIB.

Corrective Action: Restore the library to disk and submit the job again.

SUB150E `taskType memName jobName/jobId` OID=`orderId` UNEXPECTED ERROR ON CTMLIB FUNCTION `func`. NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error in the Control-M monitor.

Depending on the severity of the problem, the Control-M monitor will shut down, or at least the job submission will be stopped.

SUB151E `taskType memName jobName/jobId` DSN `memLib` - NOT A LIBRARY

Explanation: The data set described by the memLib parameter is not a library supported by Control-M.

The job will not be submitted and it will finish with NOT SUBMITTED status for reason NOLIB.

Corrective Action: Check the validity of the memLib parameter.

SUB152E `taskType memName jobName/jobId` DSN `memLib` - RECFM NOT FIXED

Explanation: Record format of the data set described by the memLib parameter is not fixed.

The job will not be submitted and it will finish with NOT SUBMITTED status for reason NOLIB.

Corrective Action: Check the validity of the memLib parameter.

SUB153E `taskType memName jobName/jobId` DSN `dsn` - LRECL GREATER THAN 255

Explanation: Record length of the data set described by the memLib parameter is greater than 255.

The job will not be submitted and it will finish with NO MEMBER status for reason NOMEM.

Corrective Action: Use library with data set record length less than 256, as described by the memLib parameter.

SUB158S SHUT DOWN: INTERNAL ERROR

Explanation: Internal error in Control-M monitor submitter.

Control-M monitor is shut down.

Corrective Action: Look in the Control-M Log (open the SHOW window and specify Y in all message types). If this message is preceded by one of the following messages: SUB153E, SUB152E, SUB151E, then it means that the data set allocated to the DALIB DD statement of the Control-M monitor is not a PDS JCL library. Correct the procedure.

Otherwise, have your system programmer call BMC Customer Support for assistance.

SUB159I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message indicates that the Control-M monitor shut down upon request of the main task.

The Control-M monitor shuts down.

Corrective Action: No action is required.

SUB160I USER EXIT CTMX002 IS NOT ACTIVE

Explanation: This information message indicates that User Exit CTMX002 is not active.

Exit CTMX002 checks each line of the submitted job. However, this exit, which is supplied by Control-M, was not found - which means that the module was probably deleted.

Processing proceeds without checking each line of the submitted job.

Corrective Action: Check whether or not Exit CTMX002 was erroneously deleted from the IOA Load library. Notify your INCONTROL administrator.

SUB161E `taskType memName jobName/jobId` OID=`orderId` SEVERE INTERNAL ERROR WHILE PROCESSING AUTOEDIT INSTRUCTIONS, RC=`rc`. SUBMISSION CANCELLED

Explanation: Severe Control-M internal error during submission of member.

The error occurred in the AutoEdit language interpreter.

Depending on the severity of the error, Control-M monitor will shut down, or at least job submission will be cancelled.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support. You will probably be able to submit the member if you change (or omit) your AutoEdit control statements in the member, but please keep a copy of the original member for problem resolution. If you hold the job order, Control-M monitor will not shut down.

SUB162E `taskType memName jobName/jobId` OID=`orderId` INVALID RETURN CODE FROM EXIT `exitName - rc` PROCESSING CONTINUES

Explanation: Invalid return code from the exitName user exit.

Submission of the member continues.

Corrective Action: Have your system programmer correct the user exit. Check the submitted job very carefully for possible errors.

SUB163E `taskType memName jobName/jobId` OID=`orderId` SUBMISSION CANCELLED DUE TO REQUEST FROM EXIT `exitName`

Explanation: Submission cancelled due to a request from the exitName user exit.

Job submission is terminated by a deliberate JCL error in the JCL stream. The job status will be not submitted reason CANCEL.

Corrective Action: Look for additional messages in the IOA Log. If you do not understand the reason for the cancellation of submission, ask your system programmer.

SUB164I `taskType memName jobName/jobId` OID=`orderId msg`

Explanation: This information message is generated by Control-M submission exit CTMX002.

The message usually explains the reason for cancelling the submission of the job, but it may be only an informational message.

Corrective Action: No action is required.

SUB165E `taskType memName jobName/jobId` OID=`orderId` SUBMISSION CANCELLED - JOB CARD CANNOT BE RESOLVED BY CONTROL-M

Explanation: Invalid format of job statement in member.

Job submission is terminated. The job status will be NOT SUBMITTED reason NOJOB.

Corrective Action: Correct the JCL in the memName member and rerun the job.

SUB166E SUBMITTER FAILURE. CTMLIB ABENDED `abCode` ON FUNCTION `func` OID=`orderId`

Explanation:Highlighted, unrollable message.

An abend has occurred while trying to read a member. The abend code and function can suggest the cause of the problem.

Control-M monitor does not abend. Processing of other jobs continues, but the job submission is terminated.

Corrective Action: Resolve the problem according to the abend code and rerun the job.

SUB167E `taskType memName jobName/jobId` OID=`orderId` SUBMISSION CANCELLED DUE TO REQUEST FROM AUTOEDIT FACILITY

Explanation: Submission cancelled due to a request from Control-M AutoEdit facility due to severe AutoEdit syntax error.

Control-M Log should contain prior messages concerning the type of AutoEdit error.

Job submission is terminated by a deliberate JCL error in the JCL stream. The job status will be NOT SUBMITTED reason CANCEL.

Corrective Action: Correct the AutoEdit statements causing the problem and rerun the job.

SUB168S `taskType memName jobName/jobId` OID=`orderId` CONTROL-M SHUTTING DOWN - COMMUNICATION TO "JES" NOT AVAILABLE

Explanation: Highlighted, unrollable message.

The Control-M monitor cannot communicate with JES, and therefore shuts down.

This can be due to the following:

JES is not working or is in the process of shutting down.
A subsystem of JES stopped working. JES will probably shut down soon with error, or may get stuck.
Some problem with JES operation.
Error in Control-M interface to JES.

The Control-M monitor shuts down as a precaution. If something is wrong with JES, then the results of job submission or initiating of a started task may be unpredictable.

Control-M monitor will shut down.

Corrective Action: If the problem is JES-related, after the JES problem is solved, start the Control-M monitor again.

If you cannot find the cause of the problem, have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support. The sysout of the DADUMP2 DD statement of the Control-M monitor procedure should contain a dump of problem related areas which can help the Control-M support team.

In any case, try to start Control-M monitor again. Production must continue.

SUB169E `taskType memName jobName/jobId` OID=`orderId` SEVERE INTERNAL ERROR WHILE STARTING A STARTED TASK RC=`rc`. TASK WAS NOT STARTED

Explanation: Severe Control-M monitor error while starting a started task.

The problem is probably in the Control-M monitor communication with JES. The rc can be interpreted by the Control-M support team.

Control-M monitor submission task will abend with U0042.

The Control-M monitor will abend on U0006.

Corrective Action: Start the Control-M monitor again. If the problem repeats, hold the started task which causes the problem (it will be in WAIT START state on the Active Environment screen). If the problem continues to appear for every started task, hold all the started tasks that should be started by Control-M. This will allow the jobs to run while someone tries to resolve the problem. Keep the dumps and contact your IOA representative.

SUB170E SEVERE INTERNAL ERROR WHILE RELEASING AN ON SPOOL JOB RC=`rc` OID=`orderId`. JOB NOT RELEASED

Explanation: When the On Spool Facility tried to get the status of the job before releasing it, it received an unknown return code from the subsystem request.

The job is not released.

Corrective Action: Have your INCONTROL administrator prepare the Control-M monitor full output and contact BMC Customer Support.

SUB172E maxNum %%INCLIB STATEMENTS PROCESSED, JOB CANCELED

Explanation: This error message indicates that the maximum number of %%INCLIB statements has been processed, and job submission has been canceled.

Corrective Action: If the current maximum number of %%INCLIB statements is 2048, you can increase the limit to 65535 by applying optional wish I10181. Otherwise, reduce the number of %%INCLIB statements within the JCL.

SUB191E `taskType memName jobName/jobId` OID=`orderId` SYMBOL NOT RESOLVED - `symbol`

Explanation: AutoEdit symbol not resolved.

This error message is issued by the CTMJSP program which is used to analyze AutoEdit statements. The symbol could not be found in the symbols environment. For details, see the Control-M for z/OS User Guide.

The variable jobName/ jobId does not appear in the message when the error occurs before the job statement is processed.

Job submission is terminated with a reason code of CANCL.

Corrective Action: Correct the AutoEdit syntax in the JCL for the job and rerun it.

SUB192E `taskType memName jobName/jobId` OID=`orderId` SYNTAX ERROR. ORIGINAL LINE - `lineText`

Explanation: Job submission is terminated with a reason code of CANCL. This message is generally issued in one of the following cases:

An AutoEdit syntax error was detected on original line lineText during analysis and substitution of an AutoEdit statement.
A reserved Control-M system AutoEdit variable was used invalidly (for example, as the target of an AutoEdit statement or function).

Original line lineText is the original AutoEdit statement before any substitution has taken place.

The variable jobName/jobId does not appear in the message when the error occurs before the job statement is processed.

This message may follow message SUB191E, which describes the error. This message may be followed by message SUB197I, which gives information about the location of the error.

For more information, see the Control-M for z/OS User Guide.

Corrective Action: Correct the AutoEdit syntax in the JCL for the job and rerun it.

If the original line is “SETOLOC%% VARIABLE = val”, insert the line “RESOLVENO” in the original AutoEdit statement above this line.

SUB193E `taskType memName jobName/jobId` OID=`orderId` INTERNAL ERROR. LINE - `line`

Explanation: Internal error while processing AutoEdit statements in the line identified in the message.

This error message is issued by the CTMJSP program which is used to analyze AutoEdit statements.

Job submission is terminated with a reason code of CANCL.

Corrective Action: Have your system programmer call BMC Customer Support for assistance.

SUB194E `taskType memName jobName/jobId` OID=`orderId` INSUFFICIENT STORAGE TO PROCESS AUTOEDIT STATEMENTS. SUBMISSION CANCELLED

Explanation: Insufficient memory to process AutoEdit statements during job submission.

This error message is issued by the CTMJSP program which is used to analyze AutoEdit statements.

Job submission is terminated with a reason code of CANCL.

Corrective Action: Increase the REGION size of the Control-M monitor and rerun the job.

SUB195S BLDL/LOAD OF "CTMMEM" FAILED

Explanation: The CTMMEM module cannot be loaded.

This error message is issued by the CTMJSP program which is used to analyze AutoEdit statements. This could be due to one of the following:

The module does not appear in the load module search list.
There is insufficient memory to load the program.

The Control-M monitor will shut down with an error message.

Corrective Action: Check whether the module is in the IOA Load library. Increase the Control-M monitor REGION size if needed.

SUB196E `taskType memName jobName/jobId` OID=`orderId` ERROR IN MEMBER `memName` LINE `lineNum`

Explanation: Error in AutoEdit symbols the memName member in the lineNum line.

This error message is issued by the CTMJSP program which is used to analyze AutoEdit statements. A member loaded by a %%LIBSYM (or %%GLOBAL) command contains data in invalid format. For details, see the Control-M for z/OS User Guide.

The variable jobName/ jobId does not appear in the message when the error occurs before the job statement is processed.

Job submission is terminated with a reason code of CANCL.

Corrective Action: Correct the contents of the member.

SUB197I `taskType memName jobName/jobId` OID=`orderId` OFFSET `offset` IN SUBSTITUTED LINE - `text`

Explanation: This information message follows message SUB192E or SUB198W, which gives the original text of a line at which an AutoEdit problem was encountered.

The variable jobName/ jobId does not appear in the message when the error occurs before the job statement is processed. This message indicates that the problem occurred at the specified offset in the partially or fully substituted line.

Corrective Action: No action is required.

SUB198W `taskType memName jobName/jobId` OID=`orderId` REDUNDANT DATA ON LINE - `lineNum`

Explanation: Redundant text was detected in the original line, during analysis and substitution of an AutoEdit statement.

The line identified in the message is the original AutoEdit statement before any substitution has taken place. This message may be followed by SUB197I, which gives more details about the redundant text.

The redundant text is ignored and AutoEdit processing continues.

Corrective Action: No action is required.

SUB199W OID=`orderId` SUBMISSION TERMINATED FOR NON FIRST JOB STREAM IN THE JCL MEMBER `memName` LIBRARY `lib`

Explanation: The memName JCL member contains two or more jobs, but the installation set Control-M default specifies that only the first job in a job member is submitted.

Control-M can control only one job for each member. When more than one job resides in a member, Control-M controls only the first job. The default at your installation specifies that submission of all other jobs be cancelled.

An alternative installation default allows for submission of multiple jobs, with only the first job controlled by Control-M.

Only the first job in the member is submitted.

Corrective Action: Separate the member into several members with one job in each member, or contact your INCONTROL administrator to change the installation default to enable submission of multiple jobs in a single member.

SUB19AW UNCLOSED %%IF statement

Explanation: The submitted job contained a %%IF auto-edit statement that was not closed with a %%ENDIF auto-edit statement. A %%ENDIF auto-edit statement was automatically added to the end of the member to close the statement.

Corrective Action: Verify that the %%IF auto-edit statement is complete.

SUB19BW MISSING LABEL REFERENCED BY ACTIVE %%GOTO STATEMENT: < `label`>

Explanation: The “%%GOTO labelx” auto-edit statement is active, but the “%%LABEL labelx” auto-edit statement is not found in the JCL member.

Control-M processes the job as if the “%%LABEL labelx” auto-edit statement is at the end of the JCL member.

Corrective Action: Add the “%%LABEL labelx” auto-edit statement to its correct position in the JCL member.

SUB19DE MISSING A SINGLE QUOTE AT THE [BEGINNING | END] OF THE VARIABLE VALUE

Explanation: This error message indicates that the variable value is missing a single quote before or after the value.

Corrective Action: Add the single quote to the variable value and submit again.

Use the following assignment format:

For %%SETB: %%SETB %%varname='value'
In %%LIBSYM and %%MEMSYM, %%GLOBAL and CACHLST members: %%varname:'value'

SUB1A1W OID=`orderId` JOBCARD TOO LONG. CONTROL-M WILL NOT ADD MSGCLASS/MSGLEVEL/RESTART PARAMETERS

Explanation: The last line of the JOB statement was too long (past column 70), so that Control-M was unable to add more lines to the JOB statement.

Control-M requires correct MSGCLASS and MSGLEVEL parameters in order to analyze the result of the job’s run. If these parameters are invalid or missing, Control-M tries to add default values for them to the JOB statement. Furthermore, Control-M may add a RESTART parameter to the job if needed.

Addition of any of these parameters may require the adding of another JCL line, which in turn requires the adding of a comma (,) to the last existing line. If there is no room at the end of the last existing line to add the comma, the additional line (and therefore, the additional parameters) cannot be added.

Control-M will submit the job as is, without changing any of the mentioned parameters.

Corrective Action: Split the last line of the JOB statement into two lines.

SUB1A2E OID=`orderId` INSUFFICIENT MEMORY TO READ ARCHIVED SYSOUTS

Explanation: The CTMARC internal module failed to read Archived Sysout Data Sets.

The Control-M monitor has attempted to perform a RESTART for an NJE job. As part of this attempt, all archived SYSDATA must be read from the Archived Sysout Data sets and passed as data to the CONTROLR step executed at the remote site. The attempt to read archived SYSDATA has failed due to lack of virtual storage available to the Control-M monitor.

The job submission is cancelled by the Control-M monitor.

Corrective Action: Retry the restart manually. If the problem persists, please report it to your INCONTROL administrator.

SUB1A4E OID=`orderId` SEVERE INTERNAL ERROR WHILE READING ARCHIVED SYSOUTS. LAST RC=`rc`. SUBMISSION CANCELLED

Explanation: Error occurred in the CTMARC internal module CTMARC.

When the Control-M monitor attempts to perform a job restart, it calls the CTMARC internal module to obtain information about the location of the archived SYSDATA for that job. That information must be passed to the CONTROLR step as data during job submission. The error rc indicates the nature of the problem. Possible errors which might occur in the module are:

Return Code	Explanation
12	The name of Archived Sysout Data Set does not follow the Control-M/Restart naming convention for this type of data set.
16	Archived sysout data sets (which are accessed to retrieve archived SYSDATA) belong to another job.

The job submission is cancelled by the Control-M monitor.

Corrective Action: Please contact BMC Customer Support for assistance.

SUB1A5E OID=`orderId` NO RECORDS ABOUT JOB’S PREVIOUS RUN(S). RESTART IMPOSSIBLE

Explanation: An internal error occurred in Control-M.

A job has been rescheduled for restart but the result of the original run of the job is not available. Job restart cannot be performed before the original run has finished execution.

The job submission is cancelled by the Control-M monitor.

Corrective Action: Please contact BMC Customer Support for assistance.

SUB1A6W OID=`orderId` OPEN OF STATISTICS FILE FAILED. RC=`rc` ERROR=`err`

Explanation: This information message is generated if an attempt to open the Control-M Job Statistics file fails.

Possible causes are:

The DASTAT DD statement is missing.
A VSAM open error occurred.

Corrective Action: Look for VSAM messages or other system messages, and correct the JCL for the Control-M monitor procedure.

SUB1A7W OID=`orderId` MISSING JOB STATISTICS. SHOUT WHEN EXECTIME PARAMETER IGNORED

Explanation: This information message is generated if job statistics data is missing from the Job Statistics file.

Possible causes are:

The DASTAT DD statement is missing or there was a VSAM open error (if this message was preceded by the SUB1A6I message).
The Job Statistics file contains no information about the previous executions of the job.

Corrective Action: Use the CTMJSA utility to accumulate statistics data from the IOA Log in order to have most updated Job Statistics file. All the relative SHOUT WHEN EXECTIME messages, which rely on the statistic average exectime will be ignored.

SUB1A8E ACCESS DENIED TO JCL LIBRARY lib

Explanation: The user (specified in the USER field of the Job Scheduling Definition) is not authorized to access the JCL library specified in the Job Scheduling Definition.

The job is not submitted.

Corrective Action: Correct the LIBRARY field in the Job Scheduling Definition, and reorder the job.

SUB1A9E OID=`orderId` SYSOUT OF THE JOB’S PREVIOUS RUN WAS LOST. JOB IS NON RESTARTABLE

Explanation: Internal error in Control-M.

A job has been rescheduled for restart but all Archived Sysout Data Sets were deleted prior to submission of the restarted job.

The job submission is cancelled by the Control-M monitor.

Corrective Action: Try to determine why the Archived Sysout Data Sets were deleted before the job entry was deleted from the Control-M Active Jobs file.

Please refrain from manual deletion of these files.

If the files were not deleted manually, but were deleted by Control-M processing, please notify BMC Customer Support for assistance.

SUB1ABE DELAYED SUBMISSION TIME COULD NOT BE ADDED, JOB WILL BE SUBMITTED IMMEDIATELY

Explanation: The job’s delayed submission time could not be updated when the job became eligible to run. As a result, the delayed submission value will be ignored, and the job will be submitted immediately.

Corrective Action: Contact BMC Support.

SUB1ACI DELAYED SUBMISSION TIME SET TO `HH:MM:SS`

Explanation: The job’s submission time has been set to the specified future date/time, as configured.

Corrective Action: No action is required.

TIM messages

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 TIM300 through TIM3xx

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.

TIM300I CONTROL-M TIMER STARTED

Explanation: This information message indicates that the Control-M monitor internal timer task started. It is routinely issued when the Control-M monitor is started.

Corrective Action: No action is required.

TIM301I SHUT DOWN UPON REQUEST FROM MAIN TASK

Explanation: This information message announces the shutdown of the Control-M monitor.

Shutdown of Control-M timer task upon request from Control-M main task.

Control-M monitor shuts down.

Corrective Action: No action is required.

TIM302I INTERVAL CHANGED FROM `num` 1 TO `num2` SECONDS

Explanation: This information message is generated by a change to the Control-M monitor “sleeping” interval by an F CONTROLM, INTERVAL= xx command.

The variables in this message are:

num1 - the old "sleeping" interval value
num2 - the new "sleeping" interval value

Corrective Action: No action is required.

TMD messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages TMD300 through TMD3xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

TMD300I CONTROL-D TIMER STARTED

Explanation: This information message indicates that the Control-D monitor internal timer task started. It is routinely issued when the Control-D monitor is started.

Corrective Action: No action is required.

TMD301I SHUT DOWN UPON REQUEST FROM MAIN TASK

Explanation: This information message announces the shutdown of the Control-D monitor.

Shutdown of Control-D timer task upon request from Control-D main task.

Control-D monitor shuts down.

Corrective Action: No action is required.

TMD302I INTERVAL CHANGED FROM `nn` TO `nn` SECONDS

Explanation: This information message is generated when the Control-D monitor “sleeping” interval is changed by an F CONTROLD,INTERVAL= xx command.

The variables in this message are:

num1 - the old "sleeping" interval value
num2 - the new "sleeping" interval value

Corrective Action: No action is required.

TMO messages

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

Messages TMO0 through TMO0xx

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

TMO001I {CONTROL-O | CTMCMEM} `monitor` TIMER SUBTASK STARTED. LEVEL `sting`

Explanation: This information message indicates the start of the Control-O TIMER task, which controls the product timer and cleanup processing.

Corrective Action: No action is required.

TMO002I {CONTROL-O | CTMCMEM} TIMER SUBTASK ENDED.

Explanation: This information message indicates the normal termination of the Control-O TIMER task which controls the product timer and cleanup processing.

Corrective Action: No action is required.

TMO004I SVCDUMP WAS CAPTURED SUCCESSFULLY.

Explanation: The Control-O or CMEM monitor successfully captured an SVC dump as a result of an internal process request.

The monitor continues to operate normally.

Corrective Action: Verify that the dump has been successfully written to the system dump files.

TMO005E SVCDUMP WAS FAILED. A PARTIAL DUMP WAS TAKEN BECAUSE THE DUMP DATA SET DID NOT HAVE SUFFICIENT SPACE.

Explanation: The Control-O or CMEM monitor tried to dump the monitor and ECSA. The dump request failed because the dump dataset is too small to contain all the areas that are dumped.

The monitor continues to operate normally.

Corrective Action: Increase the dump files, since they are too small for Control-O or CMEM requirements. Take into account that the ECSA is also dumped by the request.

TMO006E SVCDUMP CAPTURED FAILED RC 8 REASON=`reason` (HEX).

Explanation: The Control-O or CMEM monitor tried to dump the monitor and ECSA storage areas. The dump request failed. The SDUMPX system service returns a return code of 8.

The monitor continues to operate normally.

Corrective Action: Refer to SDUMPX Reason Codes for Return Code 08 in IBM’s MVS Programming Authorized Assembler Services Reference.

TMO007W RELEASING DEAD WSC AT `address` JOBNAME=`jobName` ASID=`number`

Explanation: The Control-O or CMEM monitor found that the WSC block is marked as in use, but it is not in use.

The monitor continues to operate normally. It may issue an SVCDUMP request.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

The SVCDUMP file
The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

TMO008W RELEASING WSC AT `address` JOBNAME=`jobName` ASID=`number`

Explanation: The Control-O or CMEM monitor found that the WSC block has been marked as being in use for a very long time. Normally, the Control-O or CMEM process should hold the WSC block only for a very short time.

The monitor continues to operate normally. It may issue an SVCDUMP request.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

The SVCDUMP file
The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

TMO009I TIMEOUT WSC AT `address` JOBNAME=`jobName` ASID=`number`

The monitor continues to operate normally. The monitor will check the WSC again in subsequent cycles and then decide what action to take.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

The SVCDUMP file
The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

TPM messages

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

Messages TPM100 through TPM1xx

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

TPM160E `mediaName` - INTERNAL ERROR IN VOLSER LIST FOR DSN `dsn`

Explanation: Media mediaName encountered an internal error while trying to access an extent of data set dsn.

The user request is not executed. Depending on internal error severity, one of the following actions occurs:

Media mediaName terminates. The 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.

TPM161S `mediaName` - INTERNAL ERROR ENCOUNTERED - RC=`rc`

Explanation: Media mediaName encountered an internal error.

The user request is not executed. Depending on internal error severity, one of the following actions occurs:

Media mediaName terminates. The 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.

TPM162E `mediaName` - DSN `dsn` IS CATALOGED ON MORE THAN 5 VOLUMES

Explanation: An attempt was made to access an extent of the dsn data set which spans more than five volumes.

The viewing of reports from a data set which migrated on more than five volumes is not supported.

The user request is not executed.

Corrective Action: No action is required.

TPM163E `mediaName` - DSN "`dsn`" IS SECOND FILE ON MULTI-VOLUME SET

Explanation: IOASMON detected a file that was created as a second file on the second volume of a multi-volume set.

An error during the migration process caused a file to be written as the second file on the second volume of a multi-volume set. This might cause a dead-lock while servicing the retrieval request. To avoid the possibility of a deadlock, the retrieval request is rejected.

The retrieval request is rejected.

Corrective Action: Unmigrate the report, re-decollate and migrate the report again.

TRE messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages TRE100 through TRE1xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

TRE150I LOADING OF RECIPIENT TREE STARTED

Explanation: This information message indicates that the loading of the Control-D Recipient Tree started. It is routinely issued when the Recipient Tree is being loaded.

Corrective Action: No action is required.

TRE151S OPEN OF RECIPIENT TREE MEMBER FAILED - DDNAME "DATREE"

Explanation: An attempt to open the Recipient Tree definition member failed.

Possible causes are:

The DATREE DD statement is missing.
The file allocated to the DATREE DD statement is not the Control-D Recipient Tree.
The attempt to open the tree member referenced by the DATREE DD statement failed.

This message can be produced in the following situations:

during initialization of the Control-D monitor or Printers Control monitor
when security checking in the Online User Report List screen
when using KeyStroke Language (KSL) scripts
when issuing Control-D operator command LOADTREE to a Control-D component

Corrective Action: The System Action and User Response are shown in the following table:

When Message Issued	System Action	User Response
During initialization of the Control-D monitor or Printers Control monitor	The Control-D monitor shuts down.	Modify the JCL procedure (CONTROLD/ CTDPRINT) DATREE DD statement to point to the correct library and member, and bring up Control-D.
When security checking in the Online User Report List screen	The user will not be able to enter the User Report List screen.	Modify the CLIST (CTDISPF, CTMISPFD, DMAN, ROSDMAN, ROSTMAND, TMAND) DATREE DD statement to point to the correct library and member, exit from the Control-D Online Facility, and reenter the Online Facility.
When using KeyStroke Language (KSL) scripts	The job will end with errors. KSL reports will not be produced.	Modify the JCL procedure (CTDRKSL/ CTMRKSLD) to point to the correct library and member name, and rerun the job.
When issuing Control-D operator command LOADTREE to a Control-D component	The new Recipient Tree will not be loaded. Control-D (or another component) will continue using the “old” Recipient Tree.	Modify the Recipient Tree using the Online Recipient Tree Definition screen, and reenter the LOADTREE operator command.

TRE152E PARENT `parent` OF RECIPIENT `recipient` IS NOT IN THE TREE OR PARENT LEVEL IS INCORRECT - RECIPIENT IGNORED

Explanation: The recipient entry with the name and level specified in the parent name and parent level fields is not found in the Recipient tree.

This message can be produced in the following situations:

during the initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree.

Corrective Action: Correct the parent name in the Recipient Tree using the Online Recipient Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Recipient Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing the CHECK command to verify the tree	Correct the tree and reissue the command.

TRE153E INVALID LEVEL `lvl` OF RECIPIENT `recip` - RECIPIENT IGNORED

Explanation: An invalid Recipient Tree level has been entered.

The Recipient Tree levels are installation defined (the CTDPARM member). The valid levels are displayed at the top of the Control-D Recipient Tree screen. This message can be produced under in one of the following situations:

during initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
when the Control-D operator command LOADTREE was issued
when the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree.

Corrective Action: Enter a valid Recipient Tree level in the Recipient Tree using the Online Recipient Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Recipient Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing a CHECK command to verify the tree	Correct the tree and reissue the command.

TRE154S INSUFFICIENT MEMORY TO LOAD THE RECIPIENT TREE - LOADING ABORTED

Explanation: Insufficient memory to load the Recipient Tree.

The loading of the Recipient Tree is aborted. This message can be produced in the following situations:

During the initialization of the Control-D monitor and Printers Control monitor.
When security checking in the Online User Report List screen.
The KeyStroke Language.
When the Control-D operator command LOADTREE was issued.

Corrective Action: The System Action and User Response are shown in the following table:

When Message Issued	System Action	User Response
During initialization of the Control-D monitor and Printers Control monitor	The Control-D monitor will shut down.	Increase the REGION parameter of the Control-D monitor and Printers Control monitor - JCL procedures CONTROLD and CTDPRINT.
While security checking in the Online User Report List screen	The user cannot enter the Online Recipient Tree Definition screen.	Log on again using a larger SIZE parameter.
The KeyStroke Language	The job ends with errors. KSL reports are not produced.	Increase the REGION parameter of the job, and rerun.
When the Control-D operator command LOADTREE was issued	The new Recipient Tree is not loaded. Control-D continues using the “old” Recipient Tree.	Increase the REGION parameter of the Control-D monitor and Printers Control monitor - JCL procedures CONTROLD and CTDPRINT. Bring down Control-D, and then up again.

TRE155S THE RECIPIENT TREE IS EMPTY. LOADING ABORTED

Explanation: The Recipient Tree is empty. Loading is aborted.

The Recipient Tree must be defined using the Installation Parameters. This message can be produced in the following situations:

During the initialization of the Control-D monitor and Printers Control monitor.
When security checking in the Online User Report List screen.
The KeyStroke Language.
The Control-D operator command LOADTREE was issued.

The following system actions can occur, depending on the situation:

During initialization of the Control-D monitor and Printers Control monitor: The Control-D monitor shuts down.
When security checking in the Online User Report List screen: The user cannot enter the Online Recipient Tree Definition screen.
The KeyStroke Language: The job ends with errors. KSL reports are not produced.
The Control-D operator command LOADTREE was issued: The new Recipient Tree is not loaded. Control-D continues using the “old” Recipient Tree.

Corrective Action: Delete this Recipient Tree member from the library, then generate a new Recipient Tree using the Online Recipient Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Bring up the Control-D monitor.
When security checking in the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.

TRE157E INVALID LEVEL `lvl` OF PARENT `parent` IN RECIPIENT `recip`

Explanation: The Recipient Tree level entered for the parent of this recipient is invalid.

The valid levels are displayed at the top of the Recipient Tree screen. This message can be produced in the following situations:

during the initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree.

Corrective Action: Correct the level for the parent using the Online Recipient Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Recipient Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Languages	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing a CHECK command to verify the tree	Correct the tree and reissue the command.

TRE158E LEVEL `lvl` OF THE PARENT `parent` IS LOWER THAN THE LEVEL OF RECIPIENT `recip`

Explanation: The level of the parent of the recipient is lower than the level of the recipient being defined.

The level of the parent must be higher than the level of the “child.” (Note that the order can be seen in the Recipient Tree Entry screen).

Corrective Action: Enter a parent name with a different level or give the recipient a lower level.

TRE159E ERROR IN FREEMAIN OF PREVIOUS TREE, LOADING OF NEW TREE CONTINUED

Explanation: The freeing of the memory for the previous Recipient Tree failed.

The Control-D operator command LOADTREE was issued in order to load in a new Recipient Tree. After loading memory for the “new” Recipient Tree, Control-D attempts to free the memory assigned to the “old” Recipient Tree.

The loading of the “new” Recipient Tree will be accepted. However, the memory allocated to the “old” tree will not be freed until Control-D is shut down.

Corrective Action: No action is required.

TRE160I CONTROL-D RECIPIENT TREE LOADED - `num` RECIPIENTS

Explanation: This information message indicates that the Recipient Tree was successfully loaded.

Corrective Action: No action is required.

TRE161E RECIPIENT `recip` ALREADY IN TREE - CURRENT RECIPIENT ENTRY IGNORED

Explanation: The recipient entered (recip) is already in the Recipient Tree. The current recipient entry is ignored.

A recipient name (not synonym) can only appear once in the Recipient Tree. This message can be produced in the following situations:

When entering the Online User Report List screen.
The KeyStroke Language.
The Control-D operator command LOADTREE was issued.
The IOAOMON1 operator command LOADTREE was issued.
When IOAOMON1 is initialized.
When saving an edited tree.
When executing the CHECK command to verify the tree.
During the initialization of the Control-D monitor and Printers Control monitor.

The loading of the Recipient Tree will continue. However, this particular recipient will not become part of the Recipient Tree (the first one will).

Corrective Action: Delete the duplicate recipient using the Online Recipient Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Recipient Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing a CHECK command to verify the tree	Correct the tree and reissue the command.

TRE162E USER ENTRY `entry` NOT REBUILT AFTER AN INTERNAL SORT ERROR

Explanation: The internal sort of the tree elements failed for the user entry identified in the message.

The user entry is disregarded, and processing of the tree is continued.

Corrective Action: Contact BMC Customer Support.

TRE163E MAXIMUM NUMBER OF PC USERS IS EXCEEDED. PC INFO FOR USER `usr` IS IGNORED

Explanation: The number of users authorized for PC file transfer exceeds the maximum number of PC users defined in the PASDPC member in the IOA PARM library.

Maximum number of PC users in PARM library is defined at the time the license is received to use Control-D/WebAccess Server.

All users over maximum will not be able to use file transfer option.

Corrective Action: Set AUTHORIZED TO USE PC to N for some users in screen T, or obtain a new license with a greater number of PC users.

TRE165I TREE CHECK ENDED SUCCESSFULLY. `n` RECIPIENTS

Explanation: This information message request is generated by the CHKTREE command. The recipient tree was checked and no errors were found. The number of recipients in the tree is displayed.

Corrective Action: No action is required.

TRE170I LOADING OF APPROVAL TREE STARTED

Explanation: This information message indicates that the loading of the Control-D Approval Tree started. It is routinely issued when the Approval Tree is being loaded.

Corrective Action: No action is required.

TRE171S OPEN OF APPROVAL TREE MEMBER FAILED - DDNAME "DAAPPR"

Explanation: An attempt to open the Approval Tree definition member failed.

Possible causes are:

The DAAPPR DD statement is missing.
The file allocated to the DAAPPR DD statement is not the Control-D Approval Tree.
The attempt to open the tree member referenced by the DAAPPR DD statement failed.

This message can be produced in the following situations:

during initialization of the Control-D monitor or Printers Control monitor
when issuing Control-D operator command LOADTREE to a Control-D component

Corrective Action: The System Action and User Response are shown in the following table:

When Message Issued	System Action	User Response
During initialization of the Control-D monitor or Printers Control monitor	The Control-D monitor shuts down.	Modify the JCL procedure (CONTROLD/ CTDPRINT) DAAPPR DD statement to point to the correct library and member, and bring up Control-D.
When issuing Control-D operator command LOADTREE to a Control-D component	The new Approval Tree will not be loaded. Control-D (or another component) will continue using the “old” Approval Tree.	Modify the Approval Tree using the Online Approval Tree Definition screen, and reenter the LOADTREE operator command.

TRE172E PARENT `parent` OF APPROVAL `approval` IS NOT IN THE TREE OR PARENT LEVEL IS INCORRECT - APPROVAL IGNORED

Explanation: The approval entry with the name and level specified in the parent name and parent level fields is not found in the Approval tree.

This message can be produced in the following situations:

during the initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Approval tree will continue. However, this particular Approval name will not become part of the Approval Tree.

Corrective Action: Correct the parent name in the Approval Tree using the Online Approval Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Approval Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing the CHECK command to verify the tree	Correct the tree and reissue the command.

TRE173E INVALID LEVEL `lvl` OF Approval - APPROVAL IGNORED

Explanation: An invalid Approval Tree level has been entered.

The Approval Tree levels are installation defined (the CTDPARM member). The valid levels are displayed at the top of the Control-D Approval Tree screen. This message can be produced under in one of the following situations:

during initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
when the Control-D operator command LOADTREE was issued
when the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Approval Tree will continue. However, this particular Approval name will not become part of the Approval Tree.

Corrective Action: Enter a valid Approval Tree level in the Approval Tree using the Online Approval Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitosr and Printers Control monitor	Issue a LOADTREE operator command to load in the new Approval Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing a CHECK command to verify the tree	Correct the tree and reissue the command.

TRE174S INSUFFICIENT MEMORY TO LOAD THE APPROVAL TREE - LOADING ABORTED

Explanation: Insufficient memory to load the Approval Tree.

The loading of the Approval Tree is aborted. This message can be produced in the following situations:

During the initialization of the Control-D monitor and Printers Control monitor.
When security checking in the Online User Report List screen.
The KeyStroke Language.
When the Control-D operator command LOADTREE was issued.

Corrective Action: The System Action and User Response are shown in the following table:

When Message Issued	System Action	User Response
During initialization of the Control-D monitor and Printers Control monitor	The Control-D monitor will shut down.	Increase the REGION parameter of the Control-D monitor and Printers Control monitor - JCL procedures CONTROLD and CTDPRINT.
While security checking in the Online User Report List screen	The user cannot enter the Online Approval Tree Definition screen.	Log on again using a larger SIZE parameter.
The KeyStroke Language	The job ends with errors. KSL reports are not produced.	Increase the REGION parameter of the job, and rerun.
When the Control-D operator command LOADTREE was issued	The new Approval Tree is not loaded. Control-D continues using the “old” Approval Tree.	Increase the REGION parameter of the Control-D monitor and Printers Control monitor - JCL procedures CONTROLD and CTDPRINT. Bring down Control-D, and then up again.

TRE175S THE APPROVAL TREE IS EMPTY. LOADING ABORTED

Explanation: The Approval Tree is empty. Loading is aborted.

The Approval Tree must be defined using the Installation Parameters. This message can be produced in the following situations:

During the initialization of the Control-D monitor and Printers Control monitor.
When security checking in the Online User Report List screen.
The KeyStroke Language.
The Control-D operator command LOADTREE was issued.

The following system actions can occur, depending on the situation:

During initialization of the Control-D monitor and Printers Control monitor: The Control-D monitor shuts down.
When security checking in the Online User Report List screen: The user cannot enter the Online Approval Tree Definition screen.
The KeyStroke Language: The job ends with errors. KSL reports are not produced.
The Control-D operator command LOADTREE was issued: The new Approval Tree is not loaded. Control-D continues using the “old” Approval Tree.

Corrective Action: Delete this Approval Tree member from the library, then generate a new Approval Tree using the Online Approval Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Bring up the Control-D monitor.
When security checking in the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.

TRE177E INVALID LEVEL `lvl` OF PARENT `parent` IN APPROVAL `approval`

Explanation: The Approval Tree level entered for the parent of this Approval name is invalid.

The valid levels are displayed at the top of the Approval Tree screen. This message can be produced in the following situations:

during the initialization of the Control-D monitor and Printers Control monitor
when entering the Online User Report List screen
the KeyStroke Language
the Control-D operator command LOADTREE was issued
the IOAOMON1 operator command LOADTREE was issued
when IOAOMON1 is initialized
when saving an edited tree
when executing the CHECK command to verify the tree

The loading of the Approval Tree will continue. However, this particular Approval name will not become part of the Approval Tree.

Corrective Action: Correct the level for the parent using the Online Approval Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Approval Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing a CHECK command to verify the tree	Correct the tree and reissue the command.

TRE178E LEVEL `lvl` OF THE PARENT `parent` IS LOWER THAN THE LEVEL OF APPROVAL `approval`

Explanation: The level of the parent of the Approval name is lower than the level of the Approval name being defined.

The level of the parent must be higher than the level of the “child.” (Note that the order can be seen in the Approval Tree Entry screen).

Corrective Action: Enter a parent name with a different level or give the Approval name a lower level.

TRE180I CONTROL-D APPROVAL TREE LOADED - `num` APPROVALS

Explanation: This information message indicates that the Approval Tree was successfully loaded.

Corrective Action: No action is required.

TRE181E APPROVAL NAME `approval` ALREADY IN TREE - CURRENT APPROVAL NAME ENTRY IGNORED

Explanation: The Approval name entered is already in the Approval Tree. The current Approval name entry is ignored.

An Approval name can only appear once in the Approval Tree. This message can be produced in the following situations:

When entering the Online User Report List screen.
The KeyStroke Language.
The Control-D operator command LOADTREE was issued.
The IOAOMON1 operator command LOADTREE was issued.
When IOAOMON1 is initialized.
When saving an edited tree.
When executing the CHECK command to verify the tree.
During the initialization of the Control-D monitor and Printers Control monitor.

The loading of the Approval Tree will continue. However, this particular Approval name will not become part of the Approval Tree (the first one will).

Corrective Action: Delete the duplicate Approval name using the Online Approval Tree Definition screen. Depending on the situation, do as shown in the following table:

When Message Issued	User Response
During initialization of the Control-D monitor and Printers Control monitor	Issue a LOADTREE operator command to load in the new Approval Tree.
When entering the Online User Report List screen	Exit from the Control-D Online Facility, and reenter the Online Facility.
The KeyStroke Language	Rerun the job.
When the Control-D operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When the IOAOMON1 operator command LOADTREE was issued	Reenter the LOADTREE operator command.
When IOAOMON1 is initialized	Issue a LOADTREE operator command for IOAOMON1.
When saving an edited tree	Correct the tree and resave.
When executing a CHECK command to verify the tree	Correct the tree and reissue the command.

TRE185I APPROVAL TREE CHECK ENDED SUCCESSFULLY. `n` APPROVALS

Explanation: This information message request is generated by the CHKTREE command. The Approval tree was checked and no errors were found. The number of Approval names in the tree is displayed.

Corrective Action: No action is required.

TST messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages TSTA00 through TSTAxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

TSTA80E INVALID PARM LIST OR NO PARM LIST

Explanation: An invalid parameter was passed to the IOALOC program. The IOALOC program accepts either ALLOC or FREE as input parameters.

The IOALOC program stops executing.

Corrective Action: Supply the correct input parameter.

Messages TSTF00 through TSTFxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

TSTF30E INTERNAL CONSOLE ERROR. FUNCTION `func`. RETURN CODES `rc1`, `rc2`. REASON CODE `rsn`. USING THE INTERNAL CONSOLE TERMINATES

Explanation: An error occurred when using the extended MCS console.

Control-D terminates the extended MCS console and starts using a standard method for preventing the mixing of chunks during deferred printing.

Corrective Action: Keep a system log of the problem, and a job log of the Control-D printer monitor. It is recommended to stop, then restart, the Control-D monitor to prevent a possible mixing chunks problem.

TSTF31I THE INTERNAL OPERATOR CONSOLE IS ACTIVATED

Explanation: This information message is generated when Control-D activates an extended MCS console to prevent the mixing of chunks during deferred printing.

When APPLY is set to YES for optional wish WD2624, Control-D uses an extended MCS console to prevent the mixing of chunks during deferred printing.

Corrective Action: No action is required.

TSTF32E NO RESPONSE OF INTERNAL CONSOLE. USING THE CONSOLE TERMINATES

Explanation: There is no response from the extended MCS console used by Control-D to prevent the mixing of chunks during deferred printing.

Control-D stops using the extended MCS console and starts using a standard method for preventing the mixing of chunks during deferred printing.

Corrective Action: Keep a system log of the problem, and a job log of the Control-D printer monitor. It is recommended to stop, then restart, Control-D monitor to prevent a possible mixing chunks problem.

TSTFB0S PARAMETER `parm` NOT RECOGNIZED

Explanation: The parameter specified for the IOATEST utility is invalid.

The IOATEST utility terminates with a condition code of 08.

Corrective Action: Correct the syntax of the parameters to IOATEST.

TSTFB1S PARAMETER SHOULD BE NUMERIC (`parm`)

Explanation: The value of a parameter that should be numeric is nonnumeric.

The IOATEST utility terminates with a condition code of 08.

Corrective Action: Make sure the value of the parameter is numeric.

TSTFB2S NUMERIC PARAMETER OUT OF RANGE (`parm`)

Explanation: Numeric parameter is not within the defined range.

The utility terminates with a condition code of 08.

Corrective Action: Make sure the value of the parameter is within the defined range.

TSTFB3S ONLY UP TO TEN MINOR LINES ARE ALLOWED FOR A MULTI-LINE MESSAGE

Explanation: More than ten minor lines were specified for a multi-line message; 10 is the maximum allowed.

The IOATEST utility terminates with a condition code of 08.

Corrective Action: Make sure that no more than 10 minor lines are specified.

TSTFB4W (`parm`) PARAMETER LONGER THAN ALLOWED. TRUNCATED TO LEFTMOST 4 CHARACTERS

Explanation: The value specified for the parm parameter exceeded 4 characters.

The parameter value is truncated to the first four (leftmost) characters. Processing continues.

Corrective Action: Specify a valid value for the parm parameter.

UAT messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages UAT900 through UAT9xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

UAT9B1S RELEASE OF ATF FILE NOT SUPPORTED BY THIS RELEASE OF CONTROL-D

Explanation: The release defined in the Active Transfer file is not the same as the release defined in the Control-D Load library.

Control-D checks that the release number defined in the Active Transfer file is the same release number that is defined in the Control-D Load library. An error occurs when trying to allocate an Active Transfer file that belongs to a different Control-D release, for example, a test or production release.

Requested function is not performed.

Corrective Action: Backup the Active Transfer file and reformat it. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 6, Format the A.T.F File.

UAT9B2S OPEN OF CONTROL-D ATF FILE FAILED

Explanation: An attempt by Control-D to open the Active Transfer file failed. The DAATF DD statement for the Active Transfer file is missing in the logon or Print monitor procedure.

Requested function is not performed.

Corrective Action: Check the DAATF DD statement in the Control-D and logon procedures.

UAT9B3S CONTROL-D ATF FILE IS FULL

Explanation: An overflow was detected in the Active Transfer file. The Active Transfer file is full and requires enlargement or compression.

Requested function is not performed.

Corrective Action: Compress or enlarge the Active Transfer file using the CTDCATF utility. For more details, see the INCONTROL for z/OS Utilities Guide.

UAT9B7S FILE ALLOCATED TO DDNAME "DAATF" IS NOT YOUR CONTROL-D ATF

Explanation: The QNAME defined in the Active Transfer file is not the same as the QNAME defined in CTDPARM. Either a file from another Control-D installation was accessed, or there was an error in the current installation.

Requested function is not performed.

Corrective Action: Check CTDPARM. If the QNAME was changed after installation procedures were performed, specify the original QNAME and rerun CTDPARM. If two different Control-D installations are running concurrently, then make sure that the files do not mix between the two different monitors.

UAT9B8S FILE ALLOCATED TO DDNAME "DAATF" IS NOT A CONTROL-D ATF

Explanation: The Active Transfer file does not have a valid identification. The Active Transfer file must contain the characters ATF in the first block (offset 18).

Requested function is not performed.

Corrective Action: Backup the Active Transfer file and reformat it. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 6, Format the A.T.F File.

UAT9B9S CONTROL-D ATF FILE IS FORMATTING/ CTDBAT PROBABLY ABENDED

Explanation: A compression or formatting of the Active Transfer file was started, but did not end successfully. The Active Transfer file contains an indicator that the format or compression processing was incomplete.

Requested function is not performed.

Corrective Action: Backup the Active Transfer file and reformat it. You can do this using ICE, as follows:

In the IOA Installation Menu, select Customization.
Select the environment to customize.
In the Customization screen, set Product ID to CTD and select Product Customization.
Select Major Step 6, Customize Control-D Dataset Parameters.
Select Minor Step 6, Format the A.T.F File.

UBK messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages UBK900 through UBK9xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

UBK9C0I CTDUPBKP UTILITY STARTED

Explanation: This information message indicates that the CTDUPBKP utility has started.

Corrective Action: No action is required.

UBK9C1I CTDUPBKP UTILITY COMPLETED SUCCESSFULLY

Explanation: This information message indicates that the CTDUPBKP utility has completed without errors.

Corrective Action: No action is required.

UBK9C2S CTDUPBKP UTILITY ENDED WITH ERRORS

Explanation: This information message indicates that the CTDUPBKP utility has ended with errors.

Corrective Action: Check all the messages issued by the CTDUPBKP utility and proceed accordingly.

UBK9C3I FILE=ACT WAS SPECIFIED. ACTIVE USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to ACT in the input parameters of the CTDUPBKP utility, and as a result the Active User file is processed.

Corrective Action: No action is required.

UBK9C4I FILE=HST WAS SPECIFIED. HISTORY USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to HST in the input parameters of the CTDUPBKP utility and, as a result, the History User file is processed.

Corrective Action: No action is required.

UBK9C5I FILE=MIG WAS SPECIFIED. MIGRATION USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to MIG in the input parameters of the CTDUPBKP utility and, as a result, the Migration User file is processed.

Corrective Action: No action is required.

UBK9C6E NO FILE PARAMETER WAS SPECIFIED

Explanation: The FILE parameter was not specified in the input parameters of the CTDUPBKP utility.

The FILE parameter is mandatory.

The CTDUPBKP utility terminates

Corrective Action: Specify the FILE parameter and rerun the utility.

UBK9C7E NO $SYSDATA RECORDS FOUND IN THE {ACTIVE | HISTORY | MIGRATION} USER FILE

Explanation: The CTDUPBKP utility did not find any $SYSDATA records in the specified user file to update.

The CTDUPBKP utility terminates.

Corrective Action: Check the input FILE parameter of the utility for the correct user file, and rerun the utility.

UBK9C8E SELECT CARD WAS NOT SPECIFIED

Explanation: A SELECT statement was omitted from the input parameters of the CTDUPBKP utility.

The CTDUPBKP utility terminates.

Corrective Action: Add a SELECT statement to the CTDUPBKP input statements of the CTDUPBKP utility, and rerun the utility. For more information, see the INCONTROL for z/OS Utilities Guide..

UBK9C9I input_parm WAS SPECIFIED

Explanation: This information message displays the input parameter that the user specified for the CTDUPBKP utility.

Corrective Action: No action is required.

UBK9CAI NO VOLSER WAS FOUND FOR THE {ACTIVE | PERMANENT | HISTORY} USER FILE

Explanation: This information message indicates that a detailed report ordered by the user was not produced because the $SYSDATA record of the identified user file was not found.

Corrective Action: No action is required.

UBK9CBI `input_control_stmt`

Explanation: This information message displays the input control statement that the user specified for the CTDUPBKP utility.

If the input control statement is in error, this message is followed by message UBK9CCE.

Corrective Action: No action is required.

UBK9CCE ERROR IN CONTROL STATEMENT

Explanation: An error was found in the input control statement specified by the user for the CTDUPBKP utility.

The input control statement is displayed in message UBK9CBI which precedes this message.

The CTDUPBKP utility terminates.

Corrective Action: For a description of the input parameters, see the CTDUPBKP utility in the INCONTROL for z/OS Utilities Guide.. Correct the input control statement accordingly and rerun the utility.

UBK9CDW THERE IS NO CONTROL RECORD FOR BKPMIS `backupMissionName`

Explanation: The CTDUPBKP utility could not find the Backup Control record for the backup mission of the current $SYSDATA record.

When FILE is set to HST in the input parameters of the CTDUPBKP utility, the utility attempts to read the backup control record for the backup mission of the current $SYSDATA record. In this case, the backup control record could not be found in the History file.

The CTDUPBKP utility continues with processes that do not require the backup control record.

Corrective Action: To create a backup control record, in the input parameters of the CTDUPBKP utility specify the backup mission name in the BKPMIS parameter, and the number of backup generations to retain in the GENER parameter. Rerun the CTDUPBKP utility.

For more information, see the CTDUPBKP utility in the INCONTROL for z/OS Utilities Guide..

UBK9CEE RETPD CANNOT BE CHANGED

Explanation: The RETPD parameter was specified as an input parameter for the CTDUPBKP utility but the generation number found in the Backup Control record was not 0.

When activating the CTDUPBKP utility, the user specified the RETPD parameter without setting GENER to NONE. The backup mission in question was previously run using the NUMBER OF DAYS TO KEEP method. Once a mission has been run using NUMBER OF DAYS TO KEEP method, it cannot be run using the RETPD method.

The CTDUPBKP utility continues with other processes.

Corrective Action: Either change the method in the parameters to NUMBER OF DAYS TO KEEP then rerun the utility, or define a new backup mission defined with the RETPD parameter.

UBK9CFE INVALID RETURN CODE FROM SORT. RC=`rc`

Explanation: The SORT utility called by the CTDUPBKP utility ended with errors.

The CTDUPBKP utility terminates.

Corrective Action: Refer to the section on return codes in the SORT utility documentation in the INCONTROL for z/OS Utilities Guide.. Correct the cause accordingly and rerun the CTDUPBKP utility.

UBK9CGW THE NEW RETENTION PERIOD (`numDaysNew`) DIFFERS FROM THE VALUE (`numDaysOld`) IN THE MIGRATION MISSION `missionName`

Explanation: The new retention period that you set through the CTDUPBKP utility is compared with the current value in the corresponding migration mission. This warning message alerts you that the newly specified value differs from the value in the corresponding migration mission.

Corrective Action: Ensure that the new retention period matches your needs or adjust it as necessary.

UBK9CHW THE MIGRATION MISSION `missionName` IS NOT FOUND IN THE USER FILE

Explanation: The new retention period that you set through the CTDUPBKP utility could not be compared with the current value in the corresponding migration mission, because the corresponding migration mission was not found in the user file.

Corrective Action: None.

UBK9F0I CONTROL RECORD FOR BKPMIS `backupMissionName` HAS BEEN CREATED

Explanation: This information message indicates that a backup control record was recreated for the backup mission identified in the message.

A backup control record is recreated when the FILE parameter was set to HST for the backup mission, and when the original backup control record is missing.

Corrective Action: No action is required.

UBK9F1I CTDUPBKP IS RUNNING IN SIMULATE MODE:

Explanation: This information message indicates that the CTDUPBKP utility is running in simulation mode. The report listing the selected records and specified updates is produced, but no updates are actually performed.

Corrective Action: Analyze the report. If all requested updates are correct, run the utility in production mode (with parameter SIMULATE=NO).

UBK9F2I MIGMIS missionName PRIMARY/SECONDARY VOLSER volser IS CHANGED TO SCRATCH.

Explanation: This information message indicates that the volume serial number for the specified migration mission is cleaned by the CTDUPBKP utility. The next migration mission run will request a scratch tape volume for migration.

The variables in this message are:

missionName - migration mission name for which the action is performed.
volser - the old volume serial number which is changed to scratch.

Corrective Action: No action is required.

UBK9F3E NO MIGMIS PARAMETER WAS SPECIFIED.

Explanation: This error message is issued when the SCRATCHVOL or SCRATCHSECVOL parameter is specified, but no MIGMIS selection parameter was previously specified.

The CTDUPBKP utility terminates.

Corrective Action: Specify the MIGMIS selection parameter with the migration mission name or with the value ALL if you want to perform the action for all migration missions.

UBV messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages UBV900 through UBV9xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

UBV9C0I STARTING TRANSLATION OF BACKUP VOLSERS IN SYSDATA RECORDS

Explanation: This information message indicates that the CTDUBV utility has started translating volume serial numbers found in the User Report List files.

Volume serial numbers in the History User Report List file and, optionally, in the Active User Report List file, are translated.

Corrective Action: No action is required.

UBV9C1I TRANSLATION OF BACKUP VOLSERS IN SYSDATA RECORDS COMPLETED SUCCESSFULLY

Explanation: This information message indicates that the CTDUBV utility has finished translating volume serial numbers found in the User Report List files.

Volume serial numbers in the History User Report List file and, optionally, in the Active User Report List file, were translated.

The utility has finished processing the backup volume serial numbers.

Corrective Action: No action is required.

UBV9C2S TRANSLATION OF BACKUP VOLSERS IN SYSDATA RECORDS ENDED WITH ERRORS

Explanation: The CTDUBV utility ended with errors.

This message follows a message indicating the nature of the problem.

Corrective Action: Refer to the prior message for the reason the CTDUBV utility ended with errors.

UBV9C3I ACTUSR=NO WAS SPECIFIED, ACTUSR FILE BYPASSED

Explanation: This information message indicates that the ACTUSR parameter was set to NO in the CTDUBV utility.

Volume serial numbers in the History User Report List file are translated. Volume serial numbers in the Active User Report List file are be translated.

The utility begins processing backup volume serial numbers in only the History User Report List file.

Corrective Action: No action is required.

UBV9C4I ACTUSR=YES WAS SPECIFIED, ACTUSR FILE WILL BE PROCESSED

Explanation: This information message indicates that the ACTUSR parameter was set to YES in the CTDUBV utility.

Volume serial numbers in both the History User Report List file and the Active User Report List file are translated.

The utility begins processing the backup volume serial numbers in the History User Report List file and the Active User Report List file.

Corrective Action: No action is required.

UBV9C5E VOLSER TRANSLATION FILE DAUBVLST IS EMPTY

Explanation: No volume serial number translation data was provided by the DAUBVLST DD statement in the JCL for the CTDUBV utility.

DAUBVLST contains or refers to a file which contains a list of input volsers and the output volsers to which they should be translated. This file is empty.

The utility is terminated.

Corrective Action: Supply the missing Volume Translation Statements.

UBV9C6E DAUBVLST DD STATEMENT MISSING

Explanation: The DAUBVLST DD statement was not found in the JCL for the CTDUBV utility.

DAUBVLST contains or refers to a file which contains a list of input volsers and the output volsers to which they should be translated.

The utility is terminated.

Corrective Action: Check the presence and spelling of the DAUBVLST DD statement.

UBV9C7E MEMBER NOT FOUND - `memName`

Explanation: The DAUBVLST DD statement points to a member that is not in the library.

The member referred to by DAUBVLST DD DSN=LIB(member) was not found.

Corrective Action: Check the member name.

UBV9C8E NO $SYSDATA RECORDS FOUND IN THE `fileName` FILE

Explanation: The Active User Report List file or the History User Report List file is empty.

The CTDUBV utility finished without performing any updates.

Corrective Action: Verify the references to the Active and History User Report List files in the JCL.

UBV9C9I parm WAS SPECIFIED

Explanation: This information message indicates that the parm input parameter was specified in the DAUBVIN DD statement.

Corrective Action: No action is required.

UBV9CAI NO `detail/unmatch` VOLUMES WERE FOUND FOR THE `actusr/hstusr` FILE

Explanation: This information message indicates that the Active or History User Report List file contained no volumes relevant to the DETAIL report option, or that the Volume Translation Statements referenced by the DAUBVLST DD statement contained no volumes relevant to the UNMATCH report.

One of the following occurred:

For the DETAIL report option: The report was not produced because no volser specified by means of the Volume Translation Statements matched a volser in the indicated User Report List file.
For the UNMATCH report option: The report was not produced because every volser specified by means of the Volume Translation Statements matched a volser in the indicated User Report List file.

The utility finishes without producing the requested report.

Corrective Action: If the DETAIL report was not produced, verify that the Volume Translation Statements were coded correctly and contain the correct volume serial numbers to be translated.

If the UNMATCH report was not produced, no action is required because all volumes specified in the Volume Translation Statements were found in the indicated User Report List file and translated.

UBV9CCE COLUMNS 7-9 AND 16 OF THE `stmt_type` CONTROL STATEMENTS MUST BE BLANK

Explanation: There is an error in the format of the DAUBVLST Volume Translation Statements.

Volume Translation Statements must contain the old volume name in columns 1-6, the new volume name in columns 10-15, and blanks in columns 7-9 and 16.

The CTDUBV utility is terminated.

Corrective Action: Find and correct the Volume Translation Statements which are causing the error.

UBV9CFE INVALID RETURN CODE FROM SORT, RC=`rc`

Explanation: The system sort routine failed.

The utility is terminated.

Corrective Action: Determine the cause of the sort error, correct it, and rerun the utility.

UDR messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages UDRA00 through UDRAxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

UDRA80E USERDAILY `userdaily-name` NOT PROCESSED -- DATABASE ACCESS ERROR `error-code`

Explanation: This message indicates an error occurred during execution of the CTMEMUDL procedure. Data related to userdaily-name could not be retrieved from the database.

The CTMEMUDL procedure stops processing.

Corrective Action: Note the error code (error-code) and contact BMC Customer Support.

UDRA81E USERDAILY `userdaily-name` NOT PROCESSED -- CMEM/CTO ENVIRONMENT NOT FOUND

Explanation: This error message indicates the database interface program was not available during the processing of the CTMEMUDL procedure. This prevented the retrieval of data related to userdaily-name from the userdaily database.

The CTMEMUDL procedure stops processing.

Corrective Action: Activate CMEM or Control-O and then rerun the CTMEMUDL procedure.

UDRA82I USERDAILY `userdaily-name` PROCESSED SUCCESSFULLY

Explanation: This information message indicates the CTMEMUDL procedure successfully generated ORDER statements for tables contained in userdaily-name as specified in the userdaily database.

Corrective Action: No action is required.

UDRA83E USERDAILY `userdaily-name` PROCESSED -- FUNCTION: `functionName` ERROR: `error-code`

Explanation: This message indicates an error (error-code) occurred while executing the functionName function during processing of the CMTEMUDL procedure.

The CTMEMUDL procedure stops processing.

Corrective Action: Note the function name and error code, and then contact BMC Customer Support.

UDRA84E INVALID EMDAILY PARAMETER ON EXEC STATEMENT

Explanation: This error message indicates that an unrecognized value was specified for the EMDAILY parameter when the CTMEMUDL procedure was invoked.

The CTMEMUDL procedure stops processing.

Corrective Action: Specify a valid userdaily name for the EMDAILY parameter. The maximum size of this parameter is 10 characters. For more information on managing User Daily Jobs from Control-M/Enterprise Manager, see the INCONTROL for z/OS Administrator Guide.

UDRA85E USERDAILY `userdaily-name` NOT FOUND IN DATABASE

Explanation: This error message indicates the userdaily name (userdaily-name) does not exist in the userdaily database. The userdaily name (userdaily-name) was specified for the EMDAILY parameter when the CTMEMUDL procedure was invoked.

The CTMEMUDL procedure stops processing.

Corrective Action: Execute the CTMEMUDL procedure with the EMDAILY parameter set to '*,LIST' to obtain a list of all userdaily jobs in the userdaily database.

UDRA86I CTMUDR STARTED

Explanation: This informational message indicates that the initial program invoked by the CTMEMUDL procedure has begun processing.

Corrective Action: No action is required.

UDRA87I CTMUDR ENDED

Explanation: This information message indicates the normal termination of the initial program invoked by the CTMEMUDL procedure.

Corrective Action: No action is required.

UDRA88I INPUT REQUEST: `request`

Explanation: This information message shows the value (request) of the EMDAILY parameter used when invoking the CTMEMUDL procedure.

Corrective Action: No action is required.

UDRA89I TABLE=tableName LIB=libName DAILY=dailyName CONVERTED

Explanation: This information message notifies you that conversion of User Daily data for a table was successful. This message is issued for each table that is successfully migrated to the UDLINDEX member when you invoke the CTMEMUDL procedure with EMDAILY='$$CONVERT'.

Corrective Action: No action is required.

UDRA8AI CONVERSION PROCESS ENDED SUCCESSFULLY

Explanation: This information message notifies you that the conversion of User Daily data for all tables was successful. This message is issued after you invoke the CTMEMUDL procedure with EMDAILY='$$CONVERT'.

Corrective Action: No action is required.

UDRA8BE CONVERSION PROCESS ENDED WITH ERROR

Explanation: Conversion of User Daily data by the CTMEMUDL procedure was not performed successfully for all tables.

Corrective Action: Troubleshoot the problem based on the other issued messages, and try again.

UDRA8CE ENQ OF MEMBER "UDLINDEX" FAILED

Explanation: The UDLINDEX member is locked by another user. Check-in cannot be performed for the table that you associated with a User Daily.

Corrective Action: Check who is locking the UDLINDEX member and release it. Then try again to check in the table.

ULD messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages ULDU00 through ULDUxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

ULDU80I LOADING OF RECORDS INTO USER FILE STARTED

Explanation: This information message indicates that the CTDULD utility has started normally.

The CTDULD utility copies records from a sequential file to the current User Report List.

Corrective Action: No action is required.

ULDU81I LOADING OF RECORDS INTO USER FILE ENDED OK

Explanation: This information message indicates that the CTDULD utility has ended.

The CTDULD utility copies records from a sequential file to the current User Report List.

Corrective Action: No action is required.

ULDU82W DUPLICATE RECORD FOR `userName jobName` IGNORED

Explanation: There is already a record identified as userName jobName in the current User Report List file. The current record with that identity is ignored.

Corrective Action: No action is required.

ULDU83I `num1` RECORDS READ FROM INPUT FILE, `num2` RECORDS ADDED TO USER FILE

Explanation: This information message indicates that the CTDULD utility has read num1 records from the input file and added num2 records to the User Report List file.

Corrective Action: No action is required.

ULDU84I `num` DUPLICATE RECORDS REJECTED

Explanation: While the CTDULD utility was copying records from a sequential file to the current User Report List file, duplicate records were found. This information message displays the total number of records rejected as duplicates.

Corrective Action: No action is required.

ULDU85I `num` RECORDS REPLACED

Explanation: While the CTDULD utility was copying records from a sequential file to the current User Report List file, records were replaced. This information message displays the total number of records replaced.

Corrective Action: No action is required.

ULDU86S INCORRECT REPLACE PARAMETER, SHOULD BE "Y" OR "N"

Explanation: The user tried to run the CCTDULD utility with the REPLACE parameter set to an invalid value. Valid values for the CTDULD utility REPLACE parameter are Y and N.

The CTDULD utility terminates.

Corrective Action: Set the REPLACE parameter to Y or N and rerun the utility.

ULDU87E LOADING OF RECORDS INTO USER FILE ENDED WITH ERROR

Explanation: The CTDULD Control-D utility ended with an error.

The utility stops executing.

Corrective Action: Examine the job sysout for other error messages, and take appropriate corrective action, then rerun the utility.

ULDU88S OPEN OF DDNAME `ddName` FAILED

Explanation: The ddName DD statement failed to open.

Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement does not exist.

The CTDULD utility stops executing with a condition code of 8 or 12.

Corrective Action: Correct the JCL of the CTDULD utility and rerun the utility.

ULDU89S INCORRECT DBFILE PARAMETER, SHOULD BE ACT, PRM, HST OR MIG

Explanation: The user tried to submit the CTDULD utility with an invalid DBFILE parameter value. The available DBFILE parameter values are ACT, PRM, HST, and MIG.

The utility stops with RC=8.

Corrective Action: Correct the DBFILE parameter in the JCL and resubmit the job.

UMG messages

This group includes messages for the Control-V product.

Messages UMGM00 through UMGMxx

This group includes messages for the Control-V product.

UMGM01I CONTROL-V UNMIGRATE STARTED

Explanation: This information message indicates that the CTVUNMIG Control-V utility started.

CTVUNMIG returns migrated files to DASD.

Corrective Action: No action is required.

UMGM02I CONTROL-V UNMIGRATE ENDED O.K.

Explanation: This information message indicates that the CTVUNMIG Control-V utility ended normally.

Corrective Action: No action is required.

UMGM03S CONTROL-V UNMIGRATE ENDED WITH ERRORS

Explanation: The CTVUNMIG Control-V utility ended with errors.

CTVUNMIG terminates.

Corrective Action: Check the job log or the IOA log for the other messages generated by this error. Correct the problem, and rerun the CTVUNMIG utility.

UMGM04E LOADING OF CONTROL-{D | V} INSTALLATION PARAMETERS FAILED

Explanation: Load of the CTDPARM or CTVPARM module failed.

Loading of the Control-D or Control-V Installation Parameters failed. Possible causes are:

The IOA Load library is not in the load modules search list.
There is insufficient memory to load the IOA Installation Parameters.
A specified load module does not exist in the Load library.

The CTVUNMIG utility continues without sending messages to the IOA log.

Corrective Action: To produce messages to the IOA log, try one of the following:

If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
If the loading failed because of lack of memory, increase the region size.

Rerun CTVUNMIG.

UMGM05S OPEN OF IOA LOG FILE FAILED

Explanation: The IOA Log file was unable to open 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.

The CTVUNMIG utility continues without sending messages to the IOA log.

Corrective Action: To produce messages to the Job log:

Check the Job log for additional messages associated with this error.
Correct the JCL for the job
Rerun CTVUNMIG.

UMGM06E INVALID PARAMETER:- `parm`

Explanation: The user specified an invalid parameter for the CTVUNMIG utility.

The utility stops executing with an error.

Corrective Action: Correct the parm parameter and rerun the utility.

UMGM07E MISSING PARAMETERS

Explanation: The user omitted mandatory parameters from the input to the CTVUNMIG utility.

CTVUNMIG stops executing with an error.

Corrective Action: Specify the required parameters and rerun the utility.

UMGM08S UNABLE TO LOAD MODULE `modName`

Explanation: Control-V was unable to load the modName module.

Possible causes are:

The IOA Load library is not in the load modules search list.
Insufficient storage was available to load the module.
The modName module does not exist in the IOA Load library.

In this message, modName is the name of the unloadable module.

System action depends on the cause:

If modName is the IOASPRM module, the CTVUNMIG utility continues without IOA parameters.
If modName is the LSMCALL module, the utility stops executing with an error.

Corrective Action: No action is required.

If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
If the loading failed due to lack of memory, increase the REGION size.
Rerun CTVMIG.

UMGM09S OPEN OF PARAMETERS FILE FAILED. DDNAME SYSIN

Explanation: CTVMIG was unable to open the SYSIN DD statement.

This problem could be due to either of the following:

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

The utility stops executing with a condition code of 08.

Corrective Action: Correct the CTVUNMIG JCL, and rerun the job.

UMGM10S OPEN OF DDNAME=`ddName` DSNAME=`dsn` FAILED

Explanation: The user specified a DD name that could not be opened.

The utility stops executing with a condition code of 16.

Corrective Action: Check the system log for messages generated in response to this failure. If you are unable to solve the problem, report the contents of the messages to BMC Customer Support.

UMGM11I DDNAME=`ddName` DSNAME=`dsn` DYNAMIC ALLOCATION FAILED

Explanation: This information message identifies the data set name of an unallocated DD name.

This message follows dynamic allocation error message CTD922E.

The variables in this message are:

ddName - the unallocated DD name
dsn - the name of the data set referenced by ddName

Corrective Action: No action is required.

UMGM12I FILE DSNAME=`dsn` UNMIGRATION ENDED

Explanation: This information message indicates that the specified file was successfully unmigrated.

In this message, dsn is the last extent of a CDAM file that was unmigrated. The unmigrated file can be found on DASD.

Corrective Action: No action is required.

UMGM13E MIGRATED FILE EOD REACHED

Explanation: This information message indicates that the size of the migrated file did not correspond to the information in the header of that file.

The job stops executing with a condition code of 08.

Corrective Action: Contact BMC Customer Support and send the complete log of the job.

UMGM15E INPUT CARD WITH ORIGINAL INDEX FILE NAME IS MISSING

Explanation: A migrated Index file name is specified as a parameter to the CTVUMG utility but the card with the original Index file name and its parameters is missing.

If the message is issued during the restore migrated job run, it means that there are problems with the automatically created restore job. These problems are usually the result of manually editing the job.

The utility stops.

Corrective Action: To correct this problem do one of the following actions:

If the message is issued during the restore migrated job run, resubmit the restore migrated mission to create a new restore job.
If the message is issued by the CTVUNMIG utility because the migrated Index file name was manually specified as input parameter, use the restore migrated mission instead of the CTVUNMIG utility to restore Index files together with CDAM files.

UMGM1AS MISMATCH BETWEEN DISK TYPE `hdtype` AND REQUESTED TYPE `rtype (hrtype)`

Explanation: The user specified the wrong disk type in the parameter for the CTVUNMIG utility.

There was a mismatch between the disk type hdtype of the original CDAM file and the disk type that is associated with the rtype unit name.

The variables in this message are:

hdtype - the disk type of the original CDAM
rtype - the type of the unit requested by the user
hrtype - the device type associated with rtype

CTVUNMIG stops executing with a condition code of 08.

Corrective Action: Specify the correct disk type in the PARM field and delete the DS name from the disk (as specified in message UNGM1BI) and rerun the job.

UMGM1BI PLEASE DELETE ALLOCATED FILE `dsn`

Explanation: This information message follows error message UMGM1AS and indicates the DS name to be deleted from the disk.

Corrective Action: Delete the specified file.

UPD messages

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 UPDJ00 through UPDJxx

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.

UPDJ01E UPD INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the specified type occurred during processing of the UPD subtask.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ02E OVERRUN OF THE UPDATE MESSAGES QUEUE. TRANSMISSION TOO SLOW OR NOT ENOUGH MEMORY

Explanation: The storage available for database update messages is full.

New database update messages have overwritten old messages that have not yet been sent. This may be due to a lack of memory or may happen when a large number (usually several thousand) of update messages have been accumulated without being sent, due to slow transmission of the messages.

Slow transmission may be due to one of the following:

Communications bottleneck, such as inadequate communication bandwidth
Mainframe bottleneck, such as high paging of the Control-M Application Server
Workstation bottleneck, such as CPU overload

The Control-M Application Server shuts down.

Corrective Action: If message xxxJ07E (for example, UPDJ07E) precedes this message, implement the User Action from that message. Otherwise, determine where the bottleneck is and resolve it.

UPDJ03E ADD INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the type type occurred during processing of the CTWADD subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ04E DEL INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the type type occurred during processing of the CTWDEL subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ05E READ INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the type type occurred during processing of the CTWREAD subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ06E LOCK OF UPD CHAIN FAILED. STD=`std` FUNC=`func`

Explanation: Locking of the update messages chain has failed.

Access to the update messages chain is serialized by a locking mechanism. Subtask number std in function func attempted to lock the chain several times but was unsuccessful.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

UPDJ07E GETMAIN FOR UPD MESSAGE FAILED. OLDEST MESSAGE(S) WILL BE DELETED

Explanation: The storage available for database update messages is full.

New database update messages have overwritten old messages that have not yet been sent. This happens when a large number (usually several thousand) of update messages have been accumulated without being sent, due to slow transmission of the messages.

Slow transmission may be due to one of the following:

Communications bottleneck, such as inadequate communication bandwidth
Mainframe bottleneck, such as high paging of the Control-M Application Server
Workstation bottleneck, such as CPU overload

Storage space is made available for these messages by deleting the oldest message not yet sent. The Control-M Application Server continues processing. As long as there is a lack of storage space, old messages not yet sent will continue to be deleted to make room for new messages.

Corrective Action: Increase the storage space available by increasing the REGION size of the Control-M Application Server. If slow transmission is a problem, determine where the bottleneck is and resolve it.

UPDJ08E MAXIMUM MESSAGES IN UPD CHAIN REACHED. OLDEST MESSAGE WILL BE DELETED

Explanation: The storage available for database update messages is full.

Slow transmission may be due to one of the following:

Communications bottleneck, such as inadequate communication bandwidth
Mainframe bottleneck, such as high paging of the Control-M Application Server
Workstation bottleneck, such as CPU overload

Corrective Action: Determine where the bottleneck is and resolve it.

UPDJ50I CTWUPD STARTED

Explanation: This information message indicates that the Control-M Application Server started the CTWUPD subtask.

Corrective Action: No action is required.

UPDJ51I LOGICAL CONNECTION IS SUSPENDED WHILE THE ACTIVE JOBS FILE IS BEING FORMATTED

Explanation: This information message indicates that the logical connection between the Control-M Application Server and the Workstation Gateway is temporarily suspended, because the Active Jobs file is currently being formatted.

The workstation database is not up-to-date, and no requests issued by the Enterprise Controlstation Control Application will be handled, until the format of the Active Jobs file is completed.

Corrective Action: No action is required.

UPDJ52I LOGICAL CONNECTION RESUMED

Explanation: This information message indicates that the logical connection between the Control-M Application Server and the Workstation Gateway has been resumed.

The workstation database may now request synchronization, and other requests issued by the Enterprise Controlstation Control Application will now be handled.

Corrective Action: No action is required.

UPDJ53I LOGICAL CONNECTION SUSPENDED DUE TO STOPLINK MODIFY COMMAND

Explanation: This information message indicates that the Control-M Application Server received a STOPLINK modify command.

The STOPLINK modify command causes disconnection until a STARTLINK modify command is received.

The Control-M Application Server stops transferring updates and disconnects from the Enterprise gateway.

Corrective Action: Enter a STARTLINK modify command.

UPDJ58E DATABASE UPDATES SENT TO THE WORKSTATION GATEWAY HAVE NOT BEEN CONFIRMED IN TIME

Explanation: The Control-M Application Server sent database updates to the Enterprise Controlstation Workstation Gateway, but did not receive confirmation for them in time.

This error message is issued by the Control-M Application Server program and is due to one of the following:

The Workstation Gateway has stopped responding, due to an error condition in the software or hardware.
Responses are delayed because of poor performance.

Corrective Action: Check if the workstation is hanging and if there are any error messages at the workstation which indicate the cause of the problem. If the workstation is not hanging, there must be some performance bottleneck in the system. Try to determine whether this bottleneck is at the workstation side, in the communication media, or at the mainframe.

UPDJ59E CONFIRMATION SEQUENCE NUMBER ERROR. EXPECTED=`exp_num` RECEIVED=`rcv_num`

Explanation: The Control-M Application Server has received an out of sequence confirmation of a database update.

This error message is issued by the Control-M Application Server. The Mainframe Gateway expects to receive confirmations for database updates in increasing order, but a confirmation with a sequence number of rcv_num has been received, when a confirmation with a sequence number of at least exp_num was expected.

The Control-M Application Server continues executing.

Corrective Action: Contact BMC Customer Support.

UPDJ60E DATA BASE UPDATE TYPE `msgType` HAS BEEN REJECTED BY THE WORKSTATION GATEWAY

Explanation: The Enterprise Controlstation gateway rejected a message of the msgType type from the Control-M Application Server.

This message is issued each time a database update message is rejected by the Enterprise Controlstation gateway.

Possible values for msgType are:

msgType	Meaning
A	Update of full Active Jobs file record.
B	Short update of an Active Jobs file record.
N	New job that was added to the Active Jobs file.
O	Update of full Active Jobs file record.
X	Update of only the fixed part of an active jobs.
C	Condition update.
R	Control resource update.
Q	Quantitative resource update.
T	Alert (Shout message) to workstation.

The gateway continues processing. Rejected database updates are written to the file referenced by the DASNAP DD statement.

Corrective Action: Look for error messages on the workstation side and correct the problem accordingly. Review the rejected database updates in the file referenced by DASNAP.

UTI messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages UTI300 through UTI3xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

UTI330I COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY STARTED

Explanation: This information message indicates the normal start of the CTDAMUTI utility.

Corrective Action: No action is required.

UTI331I COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY ENDED OK

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

Corrective Action: No action is required.

UTI332S COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY ENDED WITH ERRORS

Explanation: The CTDAMUTI Compressed Dataset Access Method utility ended with errors.

This is a general message when the CTDAMUTI utility ends with errors. The job sysout should contain prior messages detailing the reasons.

Corrective Action: No action is required.

UTI333E INVALID CDAM MAINTENANCE UTILITY FUNCTION: `func`

Explanation: An invalid function was given to the CTDAMUTI Control-D utility.

For more information, refer to the section on the CTDAMUTI CDAM Maintenance Utility in the Control-D and Control-V User Guide.

The CTDAMUTI utility terminates with a return code of 08.

Corrective Action: Correct the function, and rerun the CTDAMUTI utility.

UTI334W NO CDAM FILES FOUND FOR THE SPECIFIED SELECTION CRITERIA

Explanation: No CDAM data sets were found that match the data set identification parameters given to the CTDAMUTI utility.

The CTDAMUTI CDAM Maintenance Utility attempts to locate CDAM data sets based on the data set identification parameters given to it. For more information, see the Control-D and Control-V User Guide.

One of the following problems is present:

An error was made by the user in the data set identification parameter.
Someone deleted the required CDAM data sets.

The CTDAMUTI utility will terminate with a return code of 04.

Corrective Action:

Do one of the following:
- Correct the data set identification parameter.
- Restore the requested CDAM data sets.
Rerun the utility.

UTI335S OPEN OF PARAMETERS FILE FAILED. DDNAME "SYSIN"

Explanation: The open of the SYSIN DD statement failed.

For more information, see the section on the CTDAMUTI CDAM Maintenance Utility in the Control-D and Control-V User Guide.

Possible causes are:

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

The CTDAMUTI utility terminates with a return code of 12.

Corrective Action: Correct the CTDAMUTI JCL and rerun the utility.

UTI336I CDAM DATASET dsn IS BEING COPIED

Explanation: This information message from the CTDAMUTI utility indicates that CDAM data set dsn was copied successfully.

The CTDAMUTI utility terminates with a return code of 0.

Corrective Action: No action is required.

UTI337I CDAM DATASET `dsn` DELETED

Explanation: This information message from the CTDAMUTI utility indicates that CDAM data set dsn was deleted successfully.

The CTDAMUTI utility terminates with a return code of 0.

Corrective Action: No action is required.

UTI338W CDAM DATASET `dsn` IS NOT A SYSOUT (CANNOT BE PRINTED)

Explanation: The dsn CDAM data set is not a sysout file, meaning, a SYSOUT parameter was not specified when this CDAM file was created.

This warning message is issued by the CTDAMUTI utility.

The sysout class is set to *, and the dsn CDAM data set is printed.

Corrective Action: No action is required.

UTI339S OPEN OF OUTPUT (SPOOL PRINT) FILE FAILED

Explanation: Internal error in the CTDAMUTI utility.

The dynamic allocation of a sysout print file by the CTDAMUTI utility failed.

The CTDAMUTI utility terminates with a return code of 12.

Corrective Action: Have your system programmer call your IOA representative for assistance.

UTI33AS NO SELECTION PARAMETERS ARE SPECIFIED

Explanation: No CDAM selection parameters were specified in the input of the CTDAMUTI utility.

At least one CDAM selection parameter must be specified in the input of the CTDAMUTI utility.

The CTDAMUTI utility ends with an error.

Corrective Action: Rerun the CTDAMUTI utility specifying CDAM selection parameters.

UXD messages

This group includes messages for the Control-M/Analyzer product.

Messages UXDX00 through UXDXxx

This group includes messages for the Control-M/Analyzer product.

UXDX01E CTDX005 IS CALLED FOR AN INVALID FUNCTION `function`. REQUEST REJECTED.

Explanation: :Sample Exit Program CTDX005 was called for the function unintended function.

The request is ignored.

Corrective Action: Notify your INCONTROL administrator.

UXDX02E CONTROL CHARACTER TRANSLATION ERROR

Explanation: An error occurred when sample Exit Program CTDX005 attempted to transfer ASA control characters to machine control characters, or vice versa.

Translation of the current record is terminated.

Corrective Action: Notify your INCONTROL administrator.

UXDX03E ABEND `abCode` OCCURED IN CONTROL-D EXIT 005

Explanation: Abend abCode occurred during the execution of sample Exit Program CTDX005.

The current request is terminated. The Exit program returns with a return code of 12.

Corrective Action: Notify your INCONTROL administrator.

UXDX04E ABEND `abCode` OCCURED IN CONTROL-D EXIT 003

Explanation: Abend abCode occurred during the execution of sample Exit Program CTDX003.

The current request is terminated. The Exit program returns with a return code of 12.

Corrective Action: Notify your INCONTROL administrator.

UXDX05E PRINT FILE `ddName` CANNOT BE OPENED. REPORTS WILL BE SENT TO A SPOOL.

Explanation: Sample Exit Program CTDX005 was unable to open the ddName print file.

The print mission’s output is rerouted to a spool instead of a dataset.

Corrective Action: Notify your INCONTROL administrator.

UXDX06E FAILED TO ALLOCATE EXISTING PRINT FILE `dsName` RC=`rc` RSN=`rsn`

Explanation: Sample Exit Program CTDX005 failed to use the existing dsName dataset for its print file.

The variables in this message are:

dsName - the dataset to be used for the print file
rc - the return code from the failed dynamic allocation request
rsn - the reason code from the failed dynamic allocation request

The Exit program tries to create a new dataset for its print file.

Corrective Action: Notify your INCONTROL administrator.

UXDX07E PRINT FILE ALLOCATION ERROR: DSNAME=`dsName` RC=`rc` RSN=`rsn`

Explanation: Sample Exit Program CTDX005 failed to allocate the new dsName dataset for its print file.

The variables in this message are:

dsName - the dataset to be used for the print file
rc - the return code from the failed dynamic allocation request
rsn - the reason code from the failed dynamic allocation request

The print mission’s output is rerouted to a spool instead of a dataset, as described in message UXDX05E.

Corrective Action: Notify your INCONTROL administrator.

UXDX08I PRINT FILE `ddNamedsName` ASSIGNED TO MISSION `misName`

Explanation: This information message indicates that the dsName dataset was allocated for the print mission’s misName print file with ddName.

Corrective Action: Notify your INCONTROL administrator.

UXDX09W FAILED TO UNALLOCATE PRINT FILE `ddName` RC=`rc` RSN=`rsn`

Explanation: Sample Exit Program CTDX005 failed to unallocate the ddName print file.

The variables in this message are:

ddName - the DD name to be used for the print file
rc - the return code from the failed dynamic allocation request
rsn - the reason code from the failed dynamic allocation request

The program continues with a new print file.

Corrective Action: Notify your INCONTROL administrator.

UXDX0AW CONTROL-D APAPARM PROCESSING WILL BE IGNORED.

Explanation: The delivered sample Exit Program CTDAPA displays this message when it fails to get the directory of the APAPARM library. The detailed description of the error is presented by the preceding messages.

APAPARM processing is not carried out.

Corrective Action: Notify your INCONTROL administrator.

UXDX0BE CONTROL-D APAPARM PROCESSING IS TERMINATED.

Explanation: The delivered sample Exit Program CTDAPA displays this message when it fails to read the member of the APAPARM library related to the report being processed. The detailed description of the error is presented by the preceding messages.

APAPARM processing is terminated for the report.

Corrective Action: Notify your INCONTROL administrator.

UXDX0CW TOO LONG AFP COMMAND `command` IN MEMBER `memName`, IT IS IGNORED

Explanation: The delivered sample Exit Program CTDAPA displays this message when it encounters an AFP command that is too long in the memName member of the APAPARM library. The command in the message displays the header of the problematic AFP command in the memName member.

The referred AFP command is ignored during report printing.

Corrective Action: Notify your INCONTROL administrator.

UXDX0DW CONTROL-D NLP PROCESSING WILL BE IGNORED.

Explanation: The delivered sample Exit Program CTDNLP displays this message when it fails to get the directory of the OUTPARMS library. The detailed description of the error is presented by the preceding messages.

NLP processing is not carried out.

Corrective Action: Notify your INCONTROL administrator.

UXDX0EE CONTROL-D NLP PROCESSING TERMINATED.

Explanation: The delivered sample Exit Program CTDNLP displays this message when it fails to read the member of the OUTPARMS library related to the report being processed, or when that member contains invalid data. The detailed description of the error is presented by the preceding messages.

NLP processing is terminated for the report.

Corrective Action: Notify your INCONTROL administrator.

UXDX0FE INVALID NLP COMMAND `command` ... IN MEMBER `memName`

Explanation: The delivered sample Exit Program CTDNLP displays this message when it encounters invalid data in the memName member of the OUTPARMS library. The command in the message displays the header of the problematic data line in the memName member.

See message UXDX0EE.

Corrective Action: Notify your INCONTROL administrator.

UXDX0GW NLP REPORT `reportName` SPECIFICATION NOT FOUND IN MEMBER `memName`

Explanation: The delivered sample Exit Program CTDNLP displays this message when it does not find an NLP specification of the reportName report in the memName member of the OUTPARMS library.

NLP processing is not carried out for the report.

Corrective Action: Notify your INCONTROL administrator.

UXDX0HW CONTROL-D TP1 PROCESSING WILL BE IGNORED.

Explanation: The delivered sample Exit Program CTDTP1 displays this message when it fails to get the directory of the TP1PARM library. The detailed description of the error is presented by the preceding messages.

TP1 processing is not carried out for the report.

Corrective Action: Notify your INCONTROL administrator.

UXDX0IW TP1 REPORT `reportName` SPECIFICATION NOT FOUND IN MEMBER `memName`

Explanation: The delivered sample Exit Program CTDTP1 displays this message when it does not find a TP1 specification of the reportName report in the memName member of the TP1PARM library.

TP1 processing is not carried out for the report.

Corrective Action: Notify your INCONTROL administrator.

UXDX0JE CONTROL-D TP1 PROCESSING TERMINATED.

Explanation: The delivered sample Exit Program CTDTP1 displays this message when it fails to read the member of the TP1PARM library related to the report being processed. The detailed description of the error is presented by the preceding messages.

TP1 processing is terminated for the report.

Corrective Action: Notify your INCONTROL administrator.

UXDX0KW CONTROL-D OUTPARMS PROCESSING WILL BE IGNORED.

Explanation: The delivered sample Exit Program CTDOUT displays this message when it fails to get the directory of the OUTPARMS library. The detailed description of the error is presented by the preceding messages.

OUTPARMS processing is not carried out.

Corrective Action: Notify your INCONTROL administrator.

UXDX0LE CONTROL-D OUTPARMS PROCESSING TERMINATED.

Explanation: The delivered sample Exit Program CTDOUT displays this message when it fails to read the member of the OUTPARMS library related to the report being processed. The detailed description of the error is presented by the preceding messages.

OUTPARMS processing is not carried out for the report.

Corrective Action: Notify your INCONTROL administrator.

UXDX0ME CONTROL-D BANNERS PROCESSING TERMINATED.

Explanation: Either the CTDX003 or CTDX014 delivered sample Exit Programs displays this message when it fails to get the directory of the BANNERS library or when the allocated memory is not sufficient to process banners. The detailed description of the error is presented by the preceding messages.

Banners processing is not carried out.

Corrective Action: Notify your INCONTROL administrator.

UXDX0NE PROGRAM CTDINX FAILED ON FUNCTION `func` WITH RC=`rc`

Explanation: The delivered sample Exit Program CTDX003 displays this message when it fails to print the mission bundle index or the user bundle index.

The variables in this message refer to program CTDINX, which is responsible for building those indexes:

func - the type of the program call
rc - the return code of the program

Printing of the bundle indexes is terminated.

Corrective Action: Notify your INCONTROL administrator.

UXDX0PE PROGRAM CTDINX FAILED ON FUNCTION `func` RC=`rc` FDBK=`feedback`

Explanation: The delivered sample Exit Program CTDX003 displays this message when it fails to initiate printing of a bundle index.

The variables in this message refer to program CTDINX, which is responsible for building those indexes:

func - the type of the program call
rc - the return code of the program
feedback - the feedback code from the SYSOUT open or (un)allocation, in case of error

Printing of the bundle indexes is not carried out.

Corrective Action: Notify your INCONTROL administrator.

UXDX0QE INSUFFICIENT MEMORY. MISSION = `mis_name`, BUFFER SIZE = `bufferln`, GETMAIN ERROR, RC= `rc`

Explanation: There is insufficient memory to obtain a buffer for BANNER during printing.

The variables in this message are:

mis_name – print mission name
buferln – required buffer size
rc – return code

This Printing Mission will not print any reports.

The UXDX0QE message is followed by message UXDX0ME.

Corrective Action: Perform the following actions:

Increase the REGION size of the Control-D monitor.
Decrease the value of optional wish WD2618 - Limit number of print missions per print monitor. Default value is 16.
Bring Control-D down, then bring it up.
Rerun the Printing Mission.

VPL messages

This group includes messages for the Control-O product.

Messages VPL400 through VPL4xx

This group includes messages for the Control-O product.

VPL440I READ/WRITE GLOBAL VARIABLES STARTED

Explanation: This information message indicates that the CTOVPL program, which is responsible for loading and writing global variables, has begun read/write to the Control-O global pools.

Corrective Action: No action is required.

VPL441S INVALID PARAMETERS

Explanation: The CTOVPL program received an incorrect parameter list while executing a LOADGLOBAL/ WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

VPL442S ERROR OPENING DAGLBLST

Explanation: The CTOVPL program was unable to open the Global Pool List during execution of a LOADGLOBAL/ WRITEGLOBAL command.

The Global Pool List is defined by the DAGLBLST DD statement in the procedure of the Control-O monitor.

The LOADGLOBAL/WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the DD statement and related data set specifications in the Control-O monitor procedure.

VPL443S POOL `poolid` - GETMAIN ERROR

Explanation: The user issued a LOADGLOBAL command with the poolid Variable Global pool. However, the variables in this pool could not be loaded.

There is insufficient storage in ECSA for loading Global variables from the specified Global variable pool.

Command LOADGLOBAL is ignored.

Corrective Action: Increase the size of ECSA storage.

VPL444S POOL `poolid` - ERROR LOADING GLOBAL VARIABLES

Explanation: Control-O could not load variables from the poolid Global variable pool.

This message is preceded by messages describing the cause of the error.

Command LOADGLOBAL is ignored.

Corrective Action: See the accompanying messages for details about the cause of the error and possible solutions.

VPL445S POOL `poolid` - ERROR WRITING GLOBAL VARIABLES

Explanation: Control-O could not write variables to the poolid Global pool.

This message is preceded by messages describing the cause of the error.

Command WRITEGLOBAL is ignored.

Corrective Action: See the accompanying messages for details about the cause of the error and possible solutions.

VPL446S POOL `poolid` - NOT FOUND IN MEMORY

Explanation: The user specified a LOADGLOBAL/WRITEGLOBAL command, but Control-O could not locate the specified pool.

Control-O could not locate the specified pool while executing a LOADGLOBAL/WRITEGLOBAL command and could not locate the control block for the specified pool name. This usually happens when either the specified pool name is not defined in the Global Pool List member (DAGLBLST) or the specified member was never loaded.

The LOADGLOBAL/ WRITEGLOBAL command is ignored.

Corrective Action: Do the following:

Define the pool in the DAGLBLST member.
Load the pool by means of the LOADGLOBAL command.

VPL447S FREEMAIN INTERNAL ERROR

Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL/ WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

VPL448S ERROR FREEING AUTO-EDIT INTERNAL BLOCKS

Explanation: The CTOVPL program was unable to free internal control blocks while executing a LOADGLOBAL/WRITEGLOBAL command.

This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

VPL449S ERROR FREEING GLOBAL POOL INTERNAL BLOCKS

Explanation: Control-O could not free internal control blocks of a Global variable pool.

Control-O could not free internal control blocks while executing a LOADGLOBAL/WRITEGLOBAL command. This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

VPL44AS ERROR RELEASING COUPLING FACILITY RESOURCES

Explanation: Old data was not successfully deleted from the Coupling facility.

When newly loaded variables became effective after a LOAGLOBAL operation for an XAE (SYSPLEX-wide AutoEdit) database, Control-O or CMEM failed to delete the old copy of the AutoEdit databases from the Coupling facility.

Old data from the Coupling facility structure is not deleted.

As a result, unnecessary data may accumulate in the space allocated for the Coupling facility structure until the space is exhausted.

Corrective Action: Shut down all Control-O or CMEM monitors as soon as possible and restart them, one at a time.

In addition, send the sysout files for your monitor to BMC Customer Support for analysis.

VPL44BE ERROR SWITCHING COUPLING FACILITY INFORMATION

Explanation: During an attempt to switch to the new version of XAE database variables that were being loaded, an error occurred.

XAE variables are loaded in three steps. They are loaded to ECSA, copied to the Coupling facility and then marked effective in the Coupling facility. This message indicates a failure during the third step.

During the implicit LOADGLOBAL operation at startup, Control-O initialization fails. During ongoing operations, only the LOADGLOBAL operation fails.

Corrective Action: Send all the Control-O sysout files and the contents of the DAGLBLST library member to BMC Customer Support for analysis.

VPL44CE `request` (X’`code`’) FOR STRUCTURE `structureName` FAILED. REASON: `rsn`

Explanation: A request to the XAE structure failed. The message details the request name and code, and the reason for the failure.

Additional information is written to DATRACE.

Corrective Action: Check that all XAE structures are allocated and that Control-O or CMEM did not lose a connection to them. If a connection was lost, restart Control-O or CMEM. Otherwise, contact BMC Customer Support for assistance.

VPL450S POOL `poolid` IS NOT SPECIFIED IN DAGLBLST

Explanation: Control-O could not locate the poolid pool in the DAGLBLST Global Variable Pool List member.

This message is normally issued in response to a failure of a LOADGLOBAL/ WRITEGLOBAL command in the DAGLBLST Global Pool List member.

The LOADGLOBAL/WRITEGLOBAL command is ignored.

Corrective Action: Do the following:

Define the pool in the DAGLBLST Global Pool List member.
Load the pool by means of command LOADGLOBAL.

VPL451S INVALID CARD IN DAGLBLST

Explanation: The CTOVPL program detected an invalid statement in the Global Pool List.

The Global Pool List is defined in the DAGLBLST DD statement in the Control-O monitor procedure.

The LOADGLOBAL/ WRITEGLOBAL command is ignored.

Corrective Action: Check and correct the Global Pool List member.

VPL452S POOL `poolid` IS PROTECTED. IT CANNOT BE UPDATED

Explanation: Control-O cannot execute a WRITEGLOBAL command for the poolid Global Variable pool.

The poolid pool name is defined in the DAGLBLST Global Variable Pool List member as protected or temporary.

The WRITEGLOBAL command is ignored.

Corrective Action: Check the definition of the pool in the DAGLBLST member and correct the definition if necessary.

VPL453S INTERNAL ERROR HANDLING PNX BLOCKS

Explanation: This message indicates an internal error.

Corrective Action: Contact BMC Customer Support.

VPL454S POOL `poolid` - AUTOEDIT ERROR, RC=`rc`,REASON=`rsn`

Explanation: Control-O detected an invalid AutoEdit expression in the poolid Global Variable pool at startup or while executing command LOADGLOBAL.

The poolid Global variable specified in the AutoEdit expression was not loaded. The error was caused for one of the following reasons:

A mistake was made when the POOL member was manually edited.
There was an internal error.

Depending on poolid type, the pool is stored in one of two locations: the Global Variables Library or a Control-O AutoEdit Variable database.

The AutoEdit statement is ignored. Command LOADGLOBAL continues with the next line in the DAGLBLST member.

Corrective Action: Do the following:

Refer to the table in the description of message WTO283E in this document for an explanation of the return code and reason code included in this message.
Check the source of the AutoEdit expression.
Correct the error and reissue command LOADGLOBAL.
If the problem is due to an internal error, contact BMC Customer Support.

VPL455I POOL `poolid` HAS BEEN LOADED TYPE= `pool_type` ROWS=`loaded_variables/ max_variables_allowed`

Explanation: This information message indicates that the Global Variable pool poolid was successfully loaded. If pool_type starts with DB, S1 or S2 the numbers in ROWS= are the loaded value and the maximum variables allowed. In other cases the values will be 0.

Corrective Action: No action is required.

VPL456I POOL `poolid` HAS BEEN WRITTEN

Explanation: This information message indicates that the Global Variable pool poolid was successfully written.

Corrective Action: No action is required.

VPL457W DATABASE `database` NOT FOUND IN DATABASES FILE

Explanation: During Control-O or CMEM initialization, Control-O or CMEM failed to load the Global AutoEdit Variable database because the database does not exist in the Global AutoEdit Variable Database file.

The member pointed to by the DD name DAGLBLST contains, among other things, a list that specifies the Control-O Global AutoEdit Variable database and the IOA Global AutoEdit Variable database. The required database that appears in the list does not exist in the Global AutoEdit Variable Database file.

Control-O or CMEM initialization continues.

Corrective Action: Notify the INCONTROL administrator

VPL458S POOL `poolid` - ERRORS WHILE READING POOL

Explanation: Control-O could not read the poolid Global variable pool during execution of command LOADGLOBAL.

The poolid pool is not loaded.

Corrective Action: Verify that the Global pool is in the Global AutoEdit library and that the library is not corrupted.

VPL459I READ/WRITE GLOBAL VARIABLES ENDED

Explanation: This information message indicates that the CTOVPL program successfully completed execution of command LOADGLOBAL/WRITEGLOBAL.

Corrective Action: No action is required.

VPL45AW WARNING! `poolName` CONVERTED FROM `Stype` TO `DBtype`

Explanation: There is a conflict between inconsistent IOAPLEX and DAGLBLST settings, as follows:

In IOAPLEX, the ENABXES parameter or ENABXAE parameter is set to N.
In DAGLBLST, the XAE database is specified as S1 type and S2 type, where type is the one of the following database types:
- TEMP
- PROT
- INPUT
- INOUT

Control-O loads the database as a standard, or non-XAE, database. Database loading continues.

Corrective Action: Check whether, and how, the reduced capability affects any applications that use the downgraded XAE pool.

VPL45BE --- MEMBER TYPE ERROR ---

Explanation: Control-O or CMEM monitor encounter an invalid POOL TYPE in control record in the DAGLOBAL list file.

Corrective Action: No action is required.

VPL45CE --- KEYWORD NOT RECOGNIZED ---

Explanation: Control-O or CMEM monitor encounter an invalid keyword in a record in the DAGLOBAL list file.

Corrective Action: No action is required.

VPL45DE --- ALL BLANKS - ERROR ---

Explanation: Control-O or CMEM monitor the control record in the DAGLOBAL list file is all blank.

Corrective Action: No action is required.

VPL45EE --- NO BLANKS - ERROR ---

Explanation: Control-O or CMEM monitor encounter an empty control record format in the DAGLOBAL list file.

Corrective Action: No action is required.

VPL45FE --- LESS THAN ZERO ---

Explanation: Control-O or CMEM monitor encounter an invalid control record value in the DAGLOBAL list file.

Corrective Action: No action is required.

VPL45GE --- INVALID CARD FORMAT ---

Explanation: Control-O or CMEM monitor encounter an invalid control record format in the DAGLOBAL list file.

Corrective Action: No action is required.

VPL45HE RECORD=`record`

Explanation: Control-O or CMEM monitor encounter an error in the DAGLOBAL list file the previous error messages.

The record has been rejected.

Corrective Action: Correct the record and LOADGLOBAL or WRITEGLOBAL as necessary.

VPL45IE MAXIMUM NUMBER OF ROWS `max-num-rows` EXCEEDED WHILE LOADING POOL `pool-name.` LOAD STOPPED.

Explanation: During LOADGLOBAL of AutoEdit POOL pool-name, excessive rows were encountered beyond the maximum number of defined rows max-num-rows in screen IV.

The loading stops.

Corrective Action: If the unloaded AutoEdit variable is required, increase the maximum number of rows for the pool using the screen IV and re-issue the LOADGLOBAL command.

VPL45JI XAE TYPE 2 POOL `pool-name` HAS NOT BEEN LOADED BECAUSE ANOTHER LPAR HAS ALREADY LOADED IT.

Explanation: During initial loading of AutoEdit POOLs, loading of the POOL pool-name, has been skipped because the POOL has already been loaded by Control-O/CMEM on another LPAR.

Corrective Action: No action is required.

VRF messages

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

Messages VRFJ00 through VRFJxx

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

VRFJ00E `ddName` - REAL NUMBER OF BLOCKS DIFFERENT THAN DEFINED

Explanation: The number of blocks in the file, indicated by the ddName DD statement, does not match the CNDREC# parameter defined in the IOAPARM member. The IOACCND verification program terminates with a return code of 04.

Corrective Action: Correct the number of blocks specified in the CNDREC# parameter table, or increase the file size so that it contains at least as many blocks as specified in the table.

VRFJ01E `ddName` - NUMBER OF BLOCKS ALLOCATED GREATER THAN DEFINED

Explanation: The actual size of the file pointed to by the ddName DD statement was greater than the size defined in the parameter table by a factor of more than one track.

The size of the file is defined in IOAPARM, CTMPARM or CTDPARM, depending on the product in which the file is used.

The verification program terminates with a return code of 04.

Corrective Action: Correct the number of blocks specified in the parameter table, or change the file size, so that they correspond more closely.

VRFJ02E `ddName` - NOW BEING FORMATTED - TRY AGAIN LATER

Explanation: File utilization data cannot be obtained because the Active Jobs file pointed to by the ddName DD statement is currently being formatted.

Processing of the Active Jobs file terminates with a return code of 08.

Corrective Action: Try running the IOAVERFY utility later.

VRFJ03E `ddName` - PARM QNAME `qName1` DIFFERENT THAN IN FILE `qName2`

Explanation: QNAME qName1 defined in CTMPARM differs from QNAME qName2 specified in the file pointed to by the ddName DD statement.

In a correctly installed system, the qnames of the files must be identical to the QNAME specified in CTMPARM.

Processing of the current command terminates with a return code of 8.

Corrective Action: Reformat the file pointed to by the ddName DD statement using the proper installation procedures.

VRFJ04E `ddName` - RECORD LENGTH FOR VERSION `versn` SHOULD BE `len`

Explanation: An incorrect record length was specified for the file pointed to by the ddName DD statement. The record length should be the length len specified in the message for the version of the product versn indicated in the message.

Processing of the current command terminates with a return code of 08.

Corrective Action: Delete and redefine the file with the proper record length.

VRFJ05E `ddName` - INVALID VERSION - `versn`

Explanation: The IOA version found in the file pointed to by the ddName DD statement was not recognized.

Processing of the current command terminates with a return code of 08.

Corrective Action: Reformat the file and rerun the IOAVERFY utility. If the problem persists, notify BMC Customer Support.

VRFJ06E `ddName` - DSORG `org` - SHOULD BE DIRECT ACCESS OR SEQUENTIAL

Explanation: The file pointed to by the ddName DD statement is defined with data set organization org. It should be defined as DA (Direct Access) or sequential.

Processing of the current command terminates with a return code of 08.

Corrective Action: Define the file according to the specifications contained in the IOA Installation Guide.

VRFJ07E `ddName` - RECFM `recFormat` - SHOULD BE FIXED

Explanation: The file pointed to by the ddName DD statement has the record format recFormat. It should be defined as F (Fixed).

Processing of the current command terminates with a return code of 08.

Corrective Action: Define the file according to the specifications contained in the IOA Installation Guide.

VRFJ08E `ddName` - DEVTYP `device_type` - MUST BE 3340/3350/3375/3380/3390/9345

Explanation: The file pointed to by the ddName DD statement has an invalid device type (device_type).

Valid device types, as indicated in the message, are 3340, 3350, 3375, 3380, 3390 and 9345.

Processing of the current command terminates with a return code of 08.

Corrective Action: Define a valid device type for the file.

VRFJ0AE `ddName` - REAL NUMBER OF BLOCKS DIFFERENT THAN DEFINED

Explanation: The number of real blocks in the file, indicated by the ddname DD statement, does not match the CNDREC# parameter defined in the IOAPARM member. The IOACCND verification program terminates with a return code of 04.

Corrective Action: Correct the number of blocks specified in the CNDREC# parameter table, or increase the file size so that it contains at least as many blocks as specified in the table.

VRFJ0BE ERROR WITH INIT / PROCESS

Explanation: An internal error occurred during the INIT or PROCESS stage of the IOAVERFY run.

Corrective Action: Try running IOAVERFY again. If the problem persists, contact BMC Customer Support.

VRFJ0CE THE LOAD OF ALT INDEX FAILED

Explanation: The alternative index file cannot be read by the IOAVERFY utility.

Corrective Action: Check that the alternative index file exists. If necessary, contact BMC Support.

VRFJ0DI ALTERNATIVE INDEX OF ACT AND {HST|MIG|MGn} ARE SAME

Explanation: IOAVERFY found that the alternative index of the active file is identical to that of the specified file:

HST – History User Report List file
MIG – Migrated User Report List file (Control-V only)
MG1-MG9 – MUF partition of Migrated User file (Control-V only)

Corrective Action: No action required.

VRFJ0DE ALTERNATIVE INDEX OF ACT AND {HST|MIG|MGn} ARE DIFFERENT

Explanation: IOAVERFY found that the alternative index of the active file differs from that of the specified file:

HST – History User Report List file
MIG – Migrated User Report List file (Control-V only)
MG1-MG9 – MUF partition of Migrated User file (Control-V only)

Corrective Action: Compare the differing files and resolve the differences.

VRFJ0EI THERE IS NO MIG PARTITION

Explanation: No MIG partitions found, the IOAVERFY utility will not run.

Corrective Action: No action required.

VRFJ0FE THE MIGPART IS NOT ACCESSIBLE

Explanation: The IOAVERFY utility could not access the MIG partition. The IOAVERFY utility will not run.

Corrective Action: Try again later. If the problem persists, contact BMC Customer Support.

VRFJ0HI PARTITION RECORD OF MIG USER FILE

Explanation: Title of the Migration Partition report within the DAVRFOUT DDcard. Generated by the IOAVERFY utility.

Corrective Action: No action required.

VRFJ0IE `routine` FINISHED NOT O.K

Explanation: IOAVERFY detected a routine that finished NOT OK.

Corrective Action: No action required.

VRFJ0JI COMPARING THE FIRST 100 LINES ONLY

Explanation: IOAVERFY will now begin comparison of the Active Alternative Index list with the ALTERNATIVE INDEX list of the other user files. Due to the length of the files, only the first 100 lines will be included in the comparison.

Corrective Action: No action required.

VRFJ0KI `routine` ENDED COMPLETELY

Explanation: IOAVERFY found that this routine ended without errors.

Corrective Action: No action required.

VRFJ0LE `routine` ENDED WITH ERROR

Explanation: IOAVERFY found that this routine ended with errors.

Corrective Action: Use this information to troubleshoot the routine.

VRFJ12E `ddName` IS A MULTI VOLUME DATASET. VOL=`volser`

Explanation: The file pointed to by the ddName DD statement is defined on more than one volume. Volume volser indicates the first volume.

Processing of the current command terminates with a return code of 08.

Corrective Action: Make sure that the file is defined on one volume only.

VRFJ13E `ddName` - `volser` - VOLUME NOT MOUNTED

Explanation: Volume volser, which contains the file pointed to by the ddName DD statement is not available.

Processing of the current command terminates with a return code of 16.

Corrective Action: Make sure that the volume volser is online, and rerun the IOAVERFY utility.

VRFJ14E `ddName` - DSCB NOT FOUND ON VOLUME `volser`

Explanation: No format-1 DSCB was found on volume volser for the file pointed to by the ddName DD statement.

The file pointed to by the ddName DD statement is not defined on volume volser.

Processing of the current command terminates with a return code of 16.

Corrective Action: Make sure that the correct volume is referenced in the JCL of the ddName DD statement, or that the file is correctly cataloged.

VRFJ15E `ddName` - I/O ERROR ON VTOC OF VOLUME `volser`

Explanation: An error has occurred when accessing the VTOC of volume volser.

Processing of the current command terminates with a return code of 16.

Corrective Action: Contact BMC Customer Support.

VRFJ16E `ddName` - BLOCK SIZE IS LARGER THAN TRACK SIZE

Explanation: The block size of the file pointed to by the ddName DD statement is larger than the size of a track on the disk on which the file resides.

Processing of the current command terminates with a return code of 08.

Corrective Action: Define the block size of the file to be no greater than one track.

VRFJ17E `ddName` IS AN EMPTY DATASET

Explanation: The file pointed to by the ddName DD statement does not contain any records.

Processing of the current command terminates with a return code of 16.

Corrective Action: Format the file (using the appropriate formatting step in the ICE CUSTOMIZE process), and rerun the IOAVERFY utility.

VRFJ18E COMMAND NOT SUPPORTED IN FUJITSU (MSP) SYSTEM

Explanation: The specified command cannot be used to obtain system information under Fujitsu.

Processing of the current command terminates with a return code of 08.

Corrective Action: No action is required.

VRFJ19E SUBSYSTEM `subsys` NOT FOUND

Explanation: A LIST SUBSYSTEM command was specified for a subsystem (subsys) which is not defined.

The LIST SUBSYSTEM command lists the control blocks for the specified subsystem. If the subsystem name is omitted, the default is taken from IOAPARM.

Processing of the current command terminates with a return code of 08.

Corrective Action: Specify the LIST SUBSYSTEM command either with a correct subsystem name or without a subsystem name.

VRFJ20I SUBSYSTEM `subsys` IS NOT ACTIVE

Explanation: This information message is generated when the IOAVERFY utility determines (using the LIST SUBSYSTEM command) that subsystem subsys is not active.

Processing of the current command terminates with a return code of 04.

Corrective Action: No action is required.

VRFJ21I SUBSYSTEM BELONGS TO ANOTHER ENVIRONMENT

Explanation: This information message is generated if the IOA environment in the subsystem control blocks does not match the environment the IOAVERFY utility belongs to.

This message is accompanied by messages VRFJ22I and VRFJ23I, which provide additional information about the mismatched environments.

Blocks SSCT and SSVT are printed, and the command terminates.

Corrective Action: Provide BMC Customer Support with the information presented in messages VRFJ22I and VRFJ23I.

VRFJ22I SUBSYSTEM `subsys` ENVIRONMENT: `env`

Explanation: This information message displays the environment (env) found in the control blocks of the subsys subsystem.

This messages accompanies message VRFJ21I, which indicates an environment mismatch between the subsystem and the IOAVERFY utility.

Corrective Action: No action is required.

VRFJ23I VERIFICATION PROGRAM ENVIRONMENT: `env`

Explanation: This information message displays the environment (env) of the IOAVERFY utility.

This message accompanies message VRFJ21I, which indicates an environment mismatch between the subsystem and the IOAVERFY utility.

Corrective Action: No action is required.

VRFJ24E SSVT SCAN ERROR - FUNCTION TERMINATED

Explanation: The IOAVERFY utility detected an internal error while scanning the subsystem control blocks.

Processing of the current command terminates with a return code of 16.

Corrective Action: Notify BMC Customer Support.

VRFJ28S NUMBER OF ALLOCATED RECORDS ON THE AJF IS NOT EQUAL TO MI0SIZE

Explanation: The value of the CKPSIZE parameter in CTMPARM is not equal to the value in the MI0SIZE field of Active Jobs File (AJF) record0 (the first record in the AFJ).

DSECT CTMMI0 describes AJF record0.

The number of records in the AJF (the value in the MI0SIZE field) must equal the number specified by CKPSIZE in CTMPARM.

Processing of the current statement stops and a return code of 16 is issued.

Corrective Action: Make sure that the ALCIOVFY library member in PARM points to the correct AJF.

VRFJ29E JOB(`XXXXXX`) IN TABLE(`YYYYYY`) DOESN'T POINT BACK TO ITS PARENT

Explanation: A table (identified by RBA YYYYYY) contains a job (identified by RBA XXXXXX), but the job does not include a reference to the table.

Corrective Action: Run the utility again with the CORRECT parameter.

VRFJ2AE TABLE(`YYYYYY`) DOESN'T POINT TO A JOB(`XXXXXX`) BELONGING TO IT

Explanation: A job (identified by RBA XXXXXX) includes a reference to a table (identified by RBA YYYYYY), but the table does not contain the job.

Corrective Action: Run the utility again with the CORRECT parameter.

VRFJ2BE ORPHAN JOB(XXXXXX) POINTS TO A NON-TABLE ENTITY(YYYYYY)

Explanation: A job (identified by RBA XXXXXX) includes a reference to a non-table entity (identified by RBA YYYYYY), but the job is not contained in any table.

Corrective Action: Run the utility again with the CORRECT parameter.

VRFJ2CW OID IN DIAGNOSE CMD IGNORED SINCE JOB IS PART OF SMART TABLE. FULL AJF IS PROCESSED.

Explanation: During the execution of the IOA IOAVERFY utility in which the following request was issued:

DIAGNOSE AJF FORMAT OID=oid

the utility determined that the job associated with order-ID oid was ordered as part of (contained in) a SMART table. Since the utility supports the OID parameter for stand-alone jobs only, but not for jobs that are part of SMART tables, the DIAGNOSE FORMAT request is performed for the entire AJF. The utility continues processing the entire AJF.

Corrective Action: No action is required.

VRFJ30S THE SNC RECORD SNCCND# VALUE DOESN’T MATCH IOAPARM CNDREC# PARAMETER

Explanation: The value of the CNDREC# parameter in IOAPARM, which specifies a number of records, does not match the number of records specified in the SNC record.

A number of records is set during installation to determine file sizes. CNDREC# specifies the number of records in the IOA Conditions file. This value must equal the number of records that SNCCND# specifies in the SNC record.

The system stops processing the current statement and issues a return code of 16.

Corrective Action: Make sure that the ALCIOVFY library member in IOAPARM points to the correct SNC file.

VRFJ31E TWO CONSECUTIVE "VER" INPUT STATEMENTS ARE NOT ALLOWED

Explanation: Two VER statements occur in succession.

One REP statement must follow each VER statement.

Only the second VER statement is processed.

Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.

VRFJ32E A "REP" INPUT STATEMENT IS PRESENT BEFORE THE CURRENT "VER"

Explanation: A REP statement precedes a VER statement.

Each REP statement must follow a VER statement.

Only the VER statement is processed. The REP statement is ignored.

Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.

VRFJ33E TWO CONSECUTIVE "REP" INPUT STATEMENTS ARE NOT ALLOWED

Explanation: Two REP statements occur in succession.

One VER statement must precede each REP statement.

Only the second REP statement is processed. The first REP statement is ignored.

Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.

VRFJ34E A "REP" INPUT STATEMENT IS PRESENT, BUT NO PREVIOUS "VER"

Explanation: There is no VER statement before the current REP statement.

One VER statement must precede each REP statement.

The REP statement is ignored.

Corrective Action: Correct the VER and REP statements, and rerun the IOAVERFY utility.

VRFJ35I THE RECORD WAS MODIFIED SUCCESSFULLY

Explanation: This information message indicates that the Control-M Active Jobs file, the Control-M History file, the IOA Conditions file, or the Control-M Resources file, was updated by a set of VER and REP statements.

Corrective Action: No action is required.

VRFJ36S CANNOT BALANCE QUANTITATIVE RESOURCE `quantResource` ADJUST IT MANUALLY

Explanation: The VERIFY utility found that the number of units of this resource currently in use exceeds the maximum defined for it.

Corrective Action: Use the ADD, CHANGE and/or DELETE options on screen 4 to manually balance the resource file.

VRFJ37I NO ERRORS FOUND IN `fileName` FILE (`verifyType` VERIFICATION)

Explanation: This information message indicates that the DIAGNOSE command of the IOAVERFY utility did not find any errors in the specified file.

In this message, verifyType is one of the following:

STANDARD - no errors were found using the standard DIAGNOSE command (without the FORMAT subparameter).
ENHANCED - no errors were found using the enhanced verification method (FORMAT (and OID) subparameters).

Corrective Action: No action is required.

VRFJ38E A "VER" STATEMENT MUST BE PRECEDED BY "ZAP FILE `fileId` "

Explanation: When a file is to be modified by means of the VER and REP statements using the IOAVERFY utility, the file to be modified must be identified in a ZAP statement that must precede the VER and REP statements.

The ZAP statement must be in the format

ZAP FILEfileId

where fileId is one of the following:

AJF - the Control-M Active Jobs file
HST - the Control-M History Jobs file
CND - the IOA Conditions file
RES - the Control-M Resources file

Corrective Action: No action is required.

VRFJ40I VERIFY ENQ STARTED ON THE `system-id` SYSTEM FOR THE `qname` QNAME

Explanation: This informational message indicates that the IOAVERFY utility was invoked with the VERIFY ENQ parameter on the system-id system to verify the locking mechanism for the qname QNAME.

Corrective Action: No action is required.

VRFJ41E VERIFY ENQ FAILED. `ERROR TYPE type REASON CODES= xx xx xx`

Explanation: An error occurred when executing the IOAVERFY utility with the VERIFY ENQ parameter. The utility terminated with return code 12. The error type and reason codes displayed in the message indicate the type of error.

Corrective Action: Keep the IOAVERFY job log of the failed run and contact BMC Customer Support.

VRFJ42I VERIFY ENQ FINISHED ON THE `system-id` SYSTEM FOR THE `qname` QNAME

Explanation: This informational message indicates that the IOAVERFY utility, invoked with the VERIFY ENQ parameter, finished verifying the locking mechanism for the qname QNAME on the system-id system.

Corrective Action: Verify that the list produced by the IOAVERFY utility (beginning with the VRFJ44I title message and continuing with the VRFJ45I informational messages) includes all the systems where the instances of IOAVERFY (with the VERIFY ENQ parameter) were simultaneously invoked. Any system that is not included has a problem with the ENQ related definition. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.

VRFJ43I VERIFY ENQ: START CONTROL-M ENQ TEST? L(IST), Q(UIT)

Explanation: This informational message indicates that the IOAVERFY utility, with the VERIFY ENQ parameter, is ready to start checking the locking mechanism.

Corrective Action: Do one of the following:

To start checking the locking mechanism
Simultaneously, start instances of the IOAVERFY utility (using the same specification of the VERIFY ENQ parameter) on all the systems having access to the IOA and Control-M files.
Enter L.
To stop the checking process, terminate the utility by entering Q.

VRFJ44I ------ LIST OF SYSTEMS SHARING THE ENQ RESOURCES --------------

Explanation: This title message precedes the VRFJ45I informational messages that display the systems that correctly share the ENQ resources.

Corrective Action: No action is required.

VRFJ45I `system-id`

Explanation: This informational message contains the name of a system (detected by the IOAVERFY utility with the VERIFY ENQ parameter) that correctly shares the ENQ resources. The list of VRFJ45I messages is preceded with the VRFJ44I title message.

Corrective Action: Verify that the list produced by the IOAVERFY utility includes all the systems where the instances of IOAVERFY (with the VERIFY ENQ parameter) were simultaneously invoked. Any system that is not included has a problem with the ENQ related definition. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.

VRFJ46E RESOURCES WITH THE `qname` QNAME ARE EXCLUDED FROM GLOBAL SERIALIZATION

Explanation: The IOAVERFY utility (with the VERIFY ENQ parameter) detected that ENQ requests (with the QNAME specified in the utility parameters) are excluded from cross-system serialization. If the z/OS Global Resource Serialization is being used, this occurs when RNLDEF RNL(EXCL) is defined for qname in the GRS resource name list. The utility terminates with a return code of 8.

Corrective Action: If the z/OS Global Resource Serialization is used, remove the RNLDEF RNL(EXCL) definition for qname. If another cross-system serialization facility is used, ensure that the ENQ requests for qname are correctly handled by the facility. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.

VRFJ47E GLOBAL RESOURCE SERIALIZATION NOT ACTIVE ON THE `system` SYSTEM

Explanation: The IOAVERFY utility (with the VERIFY ENQ parameter) detected that the global resource serialization is not active on the system where the utility ran. The utility terminates with a return code of 8.

Corrective Action: If the IOA and Control-M files are accessed from several systems (in a multi-system environment), the global resource serialization facility must be activated to provide serialized file access and update, while preventing file corruption. For further information about the QNAME and SHRQNAM parameters, see the chapter about IOA in the INCONTROL for z/OS Installation Guide.

WKJ messages

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 WKJ400 through WKJ4xx

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.

WKJ437E INVALID DATE `date` SPECIFIED FOR `action`

Explanation: While processing a CMEM or Control-O request for action FORCEJOB, ADDCOND, or DELCOND, the Control-M monitor encountered an invalid date.

The date was either not a valid date or was not in the format specified by the DATETYP parameter in the IOAPARM.

This message is followed by the WKJA59E message or the WKJC39E message which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Make sure that the date format corresponds to the DATETYP parameter in IOAPARM.

WKJ438E INTERNAL ERROR ON THE COMMUNICATION FILE. A SNAP IS PRODUCED

Explanation: Control-M has detected mismatches in the communications file while processing SHOUT to Log records from Control-O.

Corrective Action: There are two possible causes for this problem. The corrective action depends on the cause of the problem.

Problem Cause	Corrective Action
The number of subsystem-to-monitor file (S2M) records is not the same in the CTMPARM member and in the FORMSUB2 job, the file allocation and format job.	Compare the CTMCPU statements in CTMPARM with the FORMSUB2 job that was run for each system. If the problem persists, save the snap (dump), prepare the Control-M monitor full output, and contact BMC Customer Support.
The value of the SMODE parameter in CMMPARM or CTOPARM is not F.	Ensure that the SMODE parameter in CMMPARM or CTOOPARM is set to F.

The affected records are not written to the IOA Log. A snap dump is written to the DADUMP DD statement.

WKJ439E MISSING JOB `jobName` IN TABLE `tableName` IN `lib`

Explanation: The jobName job was not found in the tableName table.

A FORCEJOB request for the jobName job in the tableName table failed.

This message is followed by message WKJA59E, which contains more details about the error.

No additional action will be taken for the failed job order.

Corrective Action: Check that the job exists in the indicated scheduling table. For further actions, see message WKJA59E FORCEJOB FAILED FOR JOB jobName IN TABLE tableName FROM dsn

WKJ43AI FORCEJOB `jobname` TABLE tablename TRIGGERED BY `eventType` `jobname/jobid`

Explanation: An informational message issued to the IOA LOG when the Control-M monitor executes a DO FORCEJOB request. The DO FORCEJOB request may be triggered by a CMEM/Control-O rule or by another Control-M job.

The message contains information about the rule or job that triggered the DO FORCEJOB request, with the following details:

jobname – Name of the forced job
tablename - Name of the forced scheduling table or the table of the forced job
eventType – Triggering event, one of the following:
- JSTART – Job started
- JEND – Job ended
- MSG – Control-O/CMEM event
jobname/jobid – Name and/or ID of the triggering job

Corrective Action: No action is required.

WKJ43EW JOB `jobName` (OID=`orderId`) HUNG IN SUBMISSION

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job has been hung in submission status for several seconds.

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Consider manually forcing the job identified in the DO FORCEJOB command.

WKJ43FI TRIGGER JOB `jobName` (`jobId`) NOT FORCED

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job is one of the following:

a cyclic job found on the Active Jobs file
hung in submission status
currently being handled by one of the local sysplex monitors

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Do the following:

Check to see if JES is hung. If it is, find out why, and address that problem.
Consider how to act in relation to
the jobName job, that is, the job that is hung
the job identified in the DO FORCEJOB command

WKJ440I CONTROL-M MONITOR IS READY TO RECEIVE CMEM REQUESTS

Explanation: This information message indicates that the CMEM facility in the Control-M monitor was successfully initialized and the Control-M monitor is ready to accept requests from Control-O or from CMEM subsystem functions.

Corrective Action: No action is required.

WKJ441E CONTROL-M MONITOR CMEM FACILITY IS DEACTIVATED AS A RESULT OF A FAILURE

Explanation:Highlighted, unrollable message.

A severe error has occurred while processing requests from one of the following:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB

Information about the error which caused the deactivation of the On Spool Jobs Facility was previously displayed on the operator console.

Control-M monitor stops processing requests from:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB.

Other parts of Control-M monitor will not be affected.

Corrective Action: Look for previous error messages. Correct the error, shut down the Control-M monitor and start it again.

WKJ442E ERROR WHILE LOADING CTMJOB\CTMMEM FOR CMEM PROCESSING

Explanation:Highlighted, unrollable message.

The CTMJOB or CTMMEM module could not be loaded by the Control-M monitor.

Load for the CTMJOB or CTMMEM module failed for one of the following reasons:

Insufficient storage.
The module or modules could not be found in the libraries specified in the STEPLIB DD statement or in the Linklist.

Control-M monitor will not process requests from:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB

Corrective Action: Correct the error, shut down the Control-M monitor and start it again.

WKJ443E OPEN ERROR OCCURRED DURING CMEM PROCESSING, DSN=`dsn`

Explanation: The Control-M monitor has encountered an open error while processing CMEM or Control-O requests.

An open error occurred on one of the Control-M communication data sets. Possible causes are:

An incorrect communication file was defined.
A security product failed the open request.

Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Do the following:

Check that CTMPARM points to the correct communication file.
Check the communication file dsn, and make sure that it is properly defined, formatted and cataloged.
Make sure that no restrictions are imposed by MVS, a security package, and so on.
Correct the error, shut down the Control-M monitor and start it again.

WKJ444E I/O ERROR OCCURRED DURING CMEM PROCESSING, DSN=`dsn`

Explanation: The Control-M monitor has encountered an I/O error while processing CMEM/Control-O requests.

An I/O error occurred on one of the Control-M communication data sets.

Control-M monitor stops processing CMEM/Control-O requests.

Corrective Action: Do the following:

Check the communication file dsn, and make sure that it is properly defined and formatted.
Check that CTMPARM points to the correct communication file. If the file and CTMPARM appear correct: a. Check the MVS LOGREC file for a physical disk error. b. Reallocate and reformat the communication file dsn. After correcting the error, stop the Control-M monitor and start it again.

WKJ445E DYNAMIC ALLOCATION ERROR, RC=`rc`, REASON CODE=`rsn`, DSN=`dsn`

Explanation: The Control-M monitor has encountered a dynamic allocation error while processing CMEM or Control-O requests.

A dynamic allocation error occurred on one of the Control-M communication data sets. Possible reasons for this failure include:

The communication file dsn is not cataloged on the correct disk.
The communication file dsn is cataloged in a catalog which cannot be accessed by the Control-M monitor.
The wrong communication file name, or no communication file name, was specified in IOACPRM.
The MVS allocation exit failed the allocation request.
A security product failed the allocation.

For information regarding the return code rc and the reason code rsn, see the IBM manual MVS Programming: Authorized Assembler Services Guide. Reallocate and format or re-catalog the file if necessary.

The Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Check the definitions in IOACPRM and correct as necessary. After the error is corrected, stop the Control-M monitor and start it again.

WKJ446W SYSPLEX TABLE MISSING - SYSTEM LOGGER INTERFACE DISABLED

Explanation: Control-M attempted to read the Sysplex Table and failed.

Control-M could not find the Sysplex Table or encountered errors while reading the Sysplex Table. This could be due to one of the following:

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

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

Corrective Action: Check why the Sysplex Table is not in the load library or has an invalid format. Correct the problem and recycle Control-M.

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

Explanation: A System Logger request failed.

One of the following System Logger requests failed:

Request	Explanation
DEFCFS, IXGINVNT	(define coupling facility structure)
DEFLGS, IXGINVNT	(define log stream)
CONLGS, IXGCONN	(connect to log stream)
WRITEL, IXGWRITE	(write a log stream log block)
BRWSEL, IXGBRWSE	(browse a log stream log block)
DELETL, IXGDELET	(delete a log stream log block)
DISLGS, IXGCONN	(disconnect from log stream)
DELLGS, IXGINVNT	(delete log stream)
DELCFS, IXGINVNT	(delete coupling facility structure)

R15 is provided by Control-M and is one of the following:

R15	Explanation
08	Minor System Logger request error
12	Intermediate System Logger request error
16	Major System Logger request error
20	Permanent System Logger request error
24	Internal Control-M error
28	Operating system does not support System Logger interface
32	Internal Control-M error

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

Corrective Action: When a System Logger error occurs, check the system log or the console that displays error messages for the IXGLOG System Logger address space for further details. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

WKJ448E CMEM LOST `num` TRANSACTIONS FROM THE CPU WITH SMFID=`smfid`

Explanation: Control-M was down, or stopped processing CMEM or Control-O requests.

During the time the Control-M monitor was inactive (due to a problem or daily maintenance), the CMEM subsystem functions or Control-O wrote to the Communication files more records than size allowed. Therefore the oldest CMEM or Control-O requests were overwritten and lost.

No additional action is performed.

Corrective Action: To prevent this situation from recurring, do one of the following:

Make sure that the Control-M monitor will not remain inactive for a long time.
Increase the size of the Communication files.

WKJ449E MISSING TABLE `tableName` IN `lib`

Explanation: Table tableName was not found in the library lib, or the table was empty.

A FORCEJOB request for a scheduling table or a specific job failed.

This message is followed by message WKJA59E, which contains more details about the error.

This message may also be issued in the following situations:

the library in which the member resides is being compressed
the disk volume on which the library resides on is being reorganized or defragmented

These actions should be avoided during job ordering periods.

No additional action will be taken for the failed job or table order.

Corrective Action: Check that the table exists in the indicated library. Refer to message WKJA59E for further actions.

WKJ44AI SYSTEM LOGGER INTERFACE ACTIVATED

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

Corrective Action: No action is required.

WKJ44BE SYSTEM LOGGER NOT SUPPORTED ON THIS OPERATING SYSTEM

Explanation: Control-M cannot utilize the System Logger interface on the host operating system.

The host operating system does not support the System Logger interface.

The CMEM facility is deactivated.

Corrective Action: Change the parameters in the appropriate IOA PARM library members to use the Subsystem-to-Monitor (S2M) communication files to implement communication between CMEM or Control-O and Control-M.

WKJ44CI ATTEMPTING TO RECONNECT TO MVS SYSTEM LOGGER

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

Control-M tries several times to reconnect to the MVS System Logger.

Corrective Action: No action is required.

WKJ44DE ATTEMPT TO RECONNECT TO MVS SYSTEM LOGGER FAILED

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

Corrective Action: No action is required.

WKJ44EE MVS SYSTEM LOGGER ERROR - CMEM FEATURE DISABLED

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

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

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

WKJ44FI TRIGGER JOB `jobName` (`jobId`) FOUND ON AJF. JOB NOT FORCED

Explanation: This information message refers to a Control-O or CMEM ON JOBARRIV or ON JOBEND rule with a DO FORCEJOB command. The job used to trigger this DO FORCEJOB was found on the Active Jobs file.

Control-M does not order and submit the DO FORCEJOB.

Corrective Action: No action is required.

WKJ44GA REPLY "ABORT", "CONTINUE", OR "RETRY"

Explanation: After displaying a CMEM-related error message, Control-M disables communication between CMEM or the Control-O monitor and Control-M. Control-M then displays message CTM44GA giving the user the choice of how to continue.

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

Corrective Action: Enter one of the following responses:

ABORT - terminate the Control-M monitor
CONTINUE - disable communication between CMEM or the Control-O monitor and Control-M, but allow the Control-M monitor to continue processing
RETRY - retry the failed dynamic allocation request

Messages WKJA00 through WKJAxx

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.

WKJA56E MEMBER `memName` READ ERROR RC=`rc` IN `dsn`

Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered an error while reading table memName in data set dsn.

This message is followed by additional messages which identify the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: For a description of return code rc, see the DOCIMEM member in the IOA DOC library.

WKJA57E MEMBER `memName` IS EMPTY IN `dsn`

Explanation: While processing CMEM or Control-O request, the Control-M monitor encountered an empty table memName in data set dsn.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Make sure that table memName contains valid scheduling information.

WKJA58E ABEND `abCode` WHILE PROCESSING `dsn`

Explanation: While processing a CMEM/Control-O request for data set dsn, the Control-M monitor encountered an abend condition abCode.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: Record the abend code, prepare the Control-M monitor full output, and contact BMC Customer Support.

WKJA59E FORCEJOB FAILED FOR JOB `jobName` IN TABLE `tableName` FROM `dsn`

Explanation: An error occurred while processing a FORCEJOB request for the jobName job, or, in the case where jobName is blank, for the complete scheduling table tableName.

The source of the request may be:

a Control-O request for a DO FORCEJOB.
a Control-M request for a DO FORCEJOB.
a CMEM FORCEJOB action.

This message is preceded by another message, which gives more details of the cause of the error.

Control-M may try again to execute the job or table, depending on the values set for the FORCE#RT and FORCE#WI installation parameters. For more information, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: Correct the error as detailed in the preceding message. If scheduling is still required for the job or table for which the error occurred, then the job or table should be ordered manually. If the specification in the original request was incorrect, correct it and reload, if necessary. Reload the CMEM table or reorder the Control-O rule.

WKJA5AE ANOTHER MONITOR ALREADY READING FROM LOG STREAM STR=`structureName` L/S=`logStreamName`

Explanation: This error message is issued when an attempt is made to read an MVS System Logger log stream which is currently being read by another Control-M monitor.

To avoid a loop of FORCEJOB jobs, the same MVS System Logger log stream should not be read simultaneously by more than one Control-M monitor. Should a second Control-M monitor attempt to read the same log stream, this error message is issued.

The CMEM facility is deactivated for this Control-M monitor.

Corrective Action: If and when the other Control-M monitor terminates, this monitor can be restarted. Make sure only one Control-M monitor is reading the same MVS System Logger log stream simultaneously.

WKJA5BE FREEMAIN (`storage_add /len`) FAILED AT POINT `ref_point`

Explanation: A Control-M component attempted to free a block of working storage, but failed to do so.

The variables in this message are:

storage_add - the working storage address
len - the length of the working storage
ref_point - the reference point in the Control-M component

No additional action is performed.

Corrective Action: If this is a recurring problem, prepare the Control-M monitor full output and contact BMC Customer Support. If ignored, this may cause severe insufficient storage problems.

WKJA5CI CONTROL-M WILL RETRY PERFORMING THE FORCEJOB REQUEST FOR JOB `jobName` TABLE `tableName` IN `dsn`

Explanation: Control-M failed to execute a DO FORCEJOB request because a scheduling table was in use.

The source of the DO FORCEJOB request may be any of the following:

a Control-O request for a DO FORCEJOB
a Control-M request for a DO FORCEJOB
a CMEM DO FORCEJOB action

Control-M queues the DO FORCEJOB request, and may try again to execute it, depending on the values set for the FORCE#RT and FORCE#WI installation parameters.

For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

WKJA5DI FORCEJOB SUCCEEDED AFTER RETRIES FOR JOB `jobName` IN TABLE `tableName` FROM `dsn`

Explanation: After failing to execute a DO FORCEJOB request because a scheduling table was in use, Control-M retried the request and succeeded in executing it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.

The source of the DO FORCEJOB request was one of the following:

a Control-O request for a DO FORCEJOB
a Control-M request for a DO FORCEJOB
a CMEM DO FORCEJOB action

Corrective Action: No action is required.

WKJA5EI CONTROL-M WILL RETRY PROCESSING DATASET TRIGGER: `trigger_dsn`

Explanation: During the processing of a CONNECT DIRECT request, no successfully triggered events were processed, and a data set-in-use condition occurred.

The probable source of the CONNECT DIRECT request is the IOADCC utility.

Control-M queues the DO FORCEJOB request, and will try again to execute it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.

For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

WKJA5FE SCHEDULE LIBRARY `schedLib` IS MIGRATED

Explanation: A DO FORCEJOB command was issued for a table in the schedLib scheduling library, which has been migrated. An attempt was made to RECALL the library. An additional message follows describing whether the RECALL action was successful or not.

Corrective Action: Look for the following messages, which inform about the success of the RECALL action.

WKJA5GE RECALL OF LIBRARY `schedLib` FAILED RC `rc` REASON `rsn`

Explanation: A DO FORCEJOB command was issued for a table in the schedLib scheduling library, but the action could not be completed because the library, which was migrated, could not be recalled.

Corrective Action: Do the following:

Ensure that the RECLRQST parameter is set (in the CTMPARM member of the IOA PARM library).
Check the rc and rsn codes in the section about the IOAMEM assembler macro in the INCONTROL for z/OS Administrator Guide, and take the appropriate action.

WKJA5HI SCHEDULE LIBRARY `schedLib` HAS BEEN RECALLED

Explanation: This information message indicates that a DO FORCEJOB command was issued for a table in the schedLib scheduling library. To complete this action, the library, which was migrated, has been RECALLed.

Corrective Action: No action is required.

WKJA5IE CONTROL-M WILL NO LONGER RETRY THE REQUEST

Explanation: When a schedule table is not available because the data set is in use by another address space, Control-M retries the request several times based on the FORCE#RT parameter in CTMPARM. When this number of retries is exhausted and Control-M no longer retries the request, this message is displayed.

Control-M no longer retries the request.

Corrective Action: Determine why the data set is in use and retry the request manually. Messages CTMC53E and CTMA59E give details about the job name, table name, and schedule library name.

WKJA5JE POST ERROR NOTIFICATION STAGE `stage` FAILED

Explanation: A DO FORCEJOB action triggered by this job failed. An attempt to specify the post-error indication in the job image failed.

Corrective Action: Do the following:

Locate the failed DO FORCEJOB command and manually order the job.
Notify BMC Customer Support about the error. The stage specified in the message is required for BMC error analysis.

Messages WKJC00 through WKJCxx

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.

WKJC39E `action` FAILED FOR `cond`

Explanation: An error occurred while processing a request to add or delete the condition.

The source of the request may be:

a Control-O request for a DO COND
a CMEM ADDCOND or DELCOND action

This message is preceded by another message, which gives more details of the cause of the error.

No additional action will be taken for the failed add or delete condition request.

Corrective Action: Correct the error as detailed in the preceding message. If addition or deletion of the condition is still required, it should be added or deleted manually. If the specification in the original request was incorrect, correct it and reload if necessary. Reload the CMEM table or recorder the Control-O rule.

WKJC50E INSUFFICIENT STORAGE FOR CMEM PROCESSING

Explanation:Highlighted, unrollable message.

Insufficient storage for CMEM processing initialization in the Control-M monitor.

The Control-M monitor stops processing CMEM/Control-O requests.

Corrective Action: Increase the REGION size specified for the Control-M monitor.

WKJC50W Control-M MONITOR CMEM FACILITY IS NOT INSTALLED

Explanation: Control-M has determined that the CMEM facility is not installed.

Communication between CMEM or the Control-O monitor and Control-M is not established, but the Control-M monitor continues processing.

Corrective Action: No action is required.

WKJC51E INSUFFICIENT STORAGE FOR TABLE `tableName` FROM `lib`

Explanation: Insufficient storage for loading table tableName into storage.

This message is followed by message WKJA59E, which contains more details about the error.

Job order fails. No additional action taken.

Corrective Action: Increase the REGION size specified for the Control-M monitor; or define a smaller table if possible, for example, if only one job is ordered from the table. For further actions, see message WKJA59E.

WKJC52E DATASET IS NOT A LIBRARY, DSN=`dsn`

Explanation: While processing a CMEM/Control-O request, the Control-M monitor encountered a data set dsn which is not a partitioned data set.

This message is followed by message WKJA59E or WKJC39E which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Specify the name of a partitioned data set containing one or more valid scheduling tables.

WKJC53E DATASET IN USE, DSN=`dsn`

Explanation: While processing a CMEM/Control-O request, the Control-M monitor encountered a data set dsn which is currently used by another job.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: Determine which job has allocated the data set with disposition OLD and resolve the conflict.

WKJC54E DATASET IS NOT CATALOGED, DSN=`dsn`

Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is not cataloged.

This message is followed by additional messages which identify the failed action.

No additional action will be taken for the failed job/table order.

Corrective Action: Make sure that the SCHLIB library specified in the CMEM table entry refers to a cataloged data set.

WKJC55E DYNAMIC ALLOCATION ERROR, DSN=`dsn`

Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a dynamic allocation error.

This message is followed by message WKJA59E which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Record the problem, prepare the Control-M monitor full output, and contact BMC Customer Support.

WKJC56E M2S FILE IS FOR QNAME `qName`. IT DOES NOT MATCH IOA QNAME `qName` DSN=`dsn`

Explanation: Control-M could not allocate the monitor to the Monitor to Subsystem (M2S) file of another IOA environment.

During initialization the Control-M monitor compares the QNAME in the IOA environment with the QNAME in the M2S file. They should match.

Message CTM441E is issued.

Corrective Action: Check the IOACPRM member and do one of the following:

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

WKJC57E S2M FILE IS FOR SMFID `smfid` QNAME `qName`. IT DOES NOT MATCH IOA QNAME `qName` DSN=`dsn`

Explanation: The Control-M monitor could not allocate the subsystem to the Subsystem to Monitor (S2M) file of another IOA environment.

During initialization the Control-M monitor compares the qname in the IOA environment with the qname in the S2M file. They should match.

Message CTM441E is issued.

Corrective Action: Check the CTMPARM member and do one of the following:

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

WKJC58I M2S FILE FOR IOA QNAME `qName`. DSN=`dsn`

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

qName is defined in the M2S file with the data set name dsn.

Corrective Action: No action is required.

WKJC59I S2M FILE FOR SMFID `smfid` QNAME `qName` DSN=`dsn`

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

qName is defined in the S2M file with the data set name dsn.

Corrective Action: No action is required.

WKJC5AE SMFID `smfid` NOT FOUND IN M2S DSN=`dsn`

Explanation: The SMFID is not in the Monitor-to-Subsystem (M2S) file.

During initialization the Control-M monitor checks that every SMFID required for CMEM functions is defined in the M2S file.

Message Control-M issues the CTM441E message and CMEM functions becomes inactive.

Corrective Action: Add the missing SMFID to the M2S file, and restart the Control-M monitor.

For more information on adding the SMFID to the M2S file, see the section on reformatting communication files for only one SMFID in the INCONTROL for z/OS Installation Guide.

WKJC5BE INVALID BLOCK SIZE FOR FILE TYPE `type`

Explanation: The record length of the communication file between Control-M and CMEM was incorrect. The record size for the file was defined incorrectly. As a result, no records are written to the file.

The file type is either M2S or S2M:

For an M2S file, the correct record length is 1000 decimal.
For an S2M file, the correct record length is 80 decimal.

Job processing continues, but CMEM processing is ignored.

Corrective Action: Reformat the file with the correct record size.

WLI messages

This group includes messages for the Control-M for z/OS product, for the CTMWLI utility and the Modify INDEX commands.

Messages WLI000 through WLI0xx

This group includes messages for the CTMWLI utility of the Control-M for z/OS product.

WLI000I CTMWLI STARTED

Explanation: This information message indicates the normal start of the CTMWLI utility.

Corrective Action: No action is required.

WLI001I CTMWLI ENDED OK

Explanation: This information message indicates the normal end of the CTMWLI utility.

Corrective Action: No action is required.

WLI002W CTMWLI ENDED WITH WARNING

Explanation: The CTMWLI utility ended with a warning.

Corrective Action: Review the output for more information.

WLI003E CTMWLI ENDED WITH ERROR

Explanation: The CTMWLI utility ended with an error.

Corrective Action: Review the output for more information.

WLI004E CTMWLI ERROR ALLOCATING STORAGE

Explanation: This error message indicates that there is not enough storage space for the job.

Corrective Action: Increase the storage size and resubmit the job.

WLI005I CTMWLI PARM IS: `parameters`

Explanation: This information message displays the input parameters.

Corrective Action: No action is required.

WLI006W CTMWLI `command` COMMAND, NO PARAMETERS CHECK

Explanation: This warning message indicates that the command does not use parameters, but parameters were specified.

Corrective Action: No action is required. The parameters will be ignored.

WLI007E CTMWLI INVALID PARAMETERS `parameter`

Explanation: This error message indicates that an invalid parameter was used in the job.

Corrective Action: Fix the parameters and resubmit the job.

WLI008E CTMWLI DUPLICATE PARAMETER `parameter`

Explanation: This error indicates that a duplicate parameter was detected in the job.

Corrective Action: Fix the parameters and resubmit the job.

WLI009E CTMWLI MISSING PARAMETER `parameter`

Explanation: This error indicates that a required parameter was missing in the job.

Corrective Action: Fix the parameters and resubmit the job.

WLI00AW CTMWLI MISSING PARAMETER `parameter`. USE DEFAULT `default-value`

Explanation: This warning message indicates that an optional parameter is missing in the job. The utility will use the default value.

Corrective Action: No action is required.

WLI00BE CTMWLI MISSING PROGRAM PARM

Explanation: This error message indicates that no parameter was specified in the PARM statement of the CTMWLI utility.

Corrective Action: Add the missing parameters and resubmit the job.

WLI00CE CTMWLI MISSING COMMAND

Explanation: This error message indicates that no command was specified for the CTMWLI utility.

Corrective Action: Add the missing command and resubmit the job.

WLI00FI CTMWLI `command` STARTED

Explanation: This information message notifies you that the specified command was started by the CTMWLI utility.

Corrective Action: No action is required.

WLI01AE CTMWLI `ddname` DD IS MISSING

Explanation: This error message indicates that a DD statement is missing in the job for the CTMWLI utility.

Corrective Action: Add the missing DD statement and resubmit the job.

WLI01BE CTMWLI INVALID `ddname` FILE, `reason`

Explanation: This error message indicates that a DD statement points to an invalid file and provides the reason.

Corrective Action: Fix the file and resubmit the job.

WLI01CE CTMWLI `ddname` FILE TOO SMALL

Explanation: This error message indicates that the output file is too small.

Corrective Action: Increase the output file size and resubmit the job.

WLI01DE CTMWLI ERROR OPENING FILE `ddname`

Explanation: An error occurred while opening the file.

Corrective Action: Review the output for more information.

WLI01EE CTMWLI ERROR CLOSING FILE `ddname`

Explanation: An error occurred while closing the file.

Corrective Action: Review the output for more information.

WLI01FE CTMWLI I/O ERROR IN FILE `ddname`

Explanation: An error occurred while reading or writing to the file.

Corrective Action: Review the output for more information.

WLI01GE CTMWLI ERROR IN FILE `ddname`

Explanation: An error occurred while processing one of the files.

Corrective Action: Review the output for more information.

WLI025I CTMWLI {INIT|COPY} OPTLIND#=`Load-Index_count` HIST=`history_entries` RMF=`rmf_entries` CALC=`calculated_entries` FFU=`ffu_entries`

Explanation: This information message indicates the input or output values for the INIT or COPY command, with the number of entries of each kind.

Corrective Action: No action is required.

WLI026I CTMWLI INIT FOUND `count` LOAD-INDEXES

Explanation: This information message indicates the number of Load-Indexes for an INIT command.

Corrective Action: No action is required.

WLI027I CTMWLI INIT NO LOAD-INDEXES FOUND

Explanation: No Load-Indexes were found for an INIT command.

Corrective Action: No action is required, but no data will be included in the output file.

WLI029E CTMWLI ERROR WHILE OBTAINING LOAD-INDEX INFORMATION, `command`

Explanation: An error occurred while trying to obtain Load-Index information for the specified Load-Index command.

Corrective Action: Review the output for more information.

WLI02BW CTMWLI INPUT FILE DOES NOT CONTAIN ANY DATA TO COPY

Explanation: The input file for a COPY command was empty.

Corrective Action: No action is required, but no data will be copied to the output file.

WLI02CI CTMWLI {INPUT|OUTPUT} OPTLIND#=`Load-Index_count` HIST=`history_entries` RMF=`rmf_entries` CALC=`calculated_entries` FFU=`ffu_entries`

Explanation: This message indicates the size specifications of the input or output file of a COPY action, with the number of entries of each kind.

Corrective Action: No action is required.

WLI02DI CTMWLI INPUT FILE CONTAINS `Load-Index_count` LOAD-INDEXES, `rmf_entries` RMF, `calculated_entries` CALC RECORDS

Explanation: This message indicates the input values for a COPY command, with the number of entries of each kind used.

Corrective Action: No action is required.

WLI02EE CTMWLI OUTPUT {STATUS|RMF} IS TOO SMALL

Explanation: The output for status or RMF records is too small for a COPY action. Action aborted.

Corrective Action: Increase the required value and resubmit the job.

WLI02FW CTMWLI `type` DATA MIGHT BE TRUNCATED

Explanation: The specified type of output records for a COPY action is smaller than the input records. The records might be truncated.

Corrective Action: Increase the required value and resubmit the job.

WLI031I LOAD-INDEX `Load-Index_name` WAS SET TO LEVEL `level`

Explanation: The SET action was performed successfully by CTMAPI on the specified external Load-Index.

Corrective Action: No action is required.

WLI032I LOAD-INDEX `Load-Index_name` WAS OVERRIDDEN TO `level`

Explanation: The OVERRIDE action was performed successfully by CTMAPI on the specified Load-Index.

Corrective Action: No action is required.

WLI033I LOAD-INDEX `Load-Index_name` WAS RELEASED TO `level`

Explanation: The RELEASE action was performed successfully by CTMAPI on the specified Load-Index. The override was released.

Corrective Action: No action is required.

WLI034W LOAD-INDEX `Load-Index_name` NOT OVERRIDDEN, SKIPPED

Explanation: The Load-Index that you tried to release does not currently have an override applied. The RELEASE action was not performed.

Corrective Action: If relevant, fix the command input and rerun the command.

WLI035W LOAD-INDEX `Load-Index_name` NOT EXTERNAL, SKIPPED

Explanation: A SET command was run by CTMAPI against a Load-Index that is not external. The Load-Index is skipped.

Corrective Action: If relevant, fix the command input and rerun the command.

WLI036E LOAD-INDEX API FAILED, RC: `rc` REASON: `rsn`

Explanation: An internal error occurred in CTMAPI.

The following return codes are possible:

Return Code	Meaning
0	Load-Index API ended successfully.
4	Load-Index API ended with warning.
8	Load-Index API ended with error.
12	Load-Index API ended with fatal error.

Corrective Action: The following table provides troubleshooting guidelines for various possible reason codes. For any other reason code, contact BMC Support.

Reason Code	Issue	Corrective Action
24	Cannot allocate the WLI file.	Check if the WLI file exists.
28	The Workload Policy does not exist in the WLI file.	Fix the Workload Policy name and try again.
32	Insufficient storage space; could not allocate memory.	Add more storage space.
36	Failed to open the WLI file.	Contact BMC Support.
48	Failed to close the WLI file.	Contact BMC Support.
60	Failed to read the WLI file.	Contact BMC Support.
64	Failed to write the WLI file.	Contact BMC Support.
96	WLI file has invalid format.	Check the WLI file and try again.
100	WLI file header is invalid.	Check the WLI file and try again.

WLI037W LOAD-INDEX CALCULATION INACTIVE

Explanation: The Control-M monitor is inactive and calculations cannot be made for Load-Indexes.

Corrective Action: Check the activation status of the Control-M monitor.

WLI038W LOAD-INDEX NOT FOUND.

Explanation: No Load-Indexes were found that fit the criteria specified in the command.

Corrective Action: Adjust the selection criteria and rerun the command.

WLI03AW DATASET DAWLI IS NOT ALLOCATED.

Explanation: Could not apply definitions, Load-Index repository not allocated.

Corrective Action: Check the WLI file and, if needed, use the CTMWLI utility to allocate or format it.

WLI03BI ACTION PERFORMED SUCCESSFULLY, `n` LOAD-INDEXES MODIFIED

Explanation: The modify command completed successfully. The message includes the number of Load-Indexes that were modified by CTMAPI.

Corrective Action: No action is required.

WLI03CI LOAD-INDEXES NOT FOUND

Explanation: No defined Load-Indexes were found by CTMAPI.

Corrective Action: Define Load-Indexes.

WLI03DI LOAD-INDEXES WERE SUCCESSFULLY APPLIED

Explanation: The definitions of Load-Indexes were applied successfully.

Corrective Action: No action is required.

WLI03FI NO HISTORY RECORDS FOUND FOR LOAD-INDEX: Load-Index_name

Explanation: No History records were found for the specified Load-Index. This might happen, for example, if the Load-Index is new.

Corrective Action: No action is required.

WLI03GI `Load-Index_name` SET TO `level` ENDED, LEVEL IS OVERRIDDEN

Explanation: The SET command, for setting the Load-Index to the specified new level, ended successfully. However, the Load-Index is currently overridden. The change to this new level will take effect only after the Load-Index is released.

Corrective Action: No action is required.

WLI03NI INCLUDE MUST BE DEFINED.

Explanation: The Load-Index must include at least one LPAR.

Corrective Action: Fix the Load-Index definitions to include at least one LPAR.

WLI03XE YOU ARE NOT AUTHORIZED TO USE THIS OPTION

Explanation: You are not authorized to use the Load-Index command. Command ignored.

Corrective Action: If you think that you should be authorized to perform this action, contact your INCONTROL administrator.

Messages WLIA00 through WLIAxx

This group includes messages for the CTMWLI utility of the Control-M for z/OS product.

WLIA01I LOAD-INDEX `Load-Index_name` SET TO `level`

Explanation: The specified Load-Index was successfully set to the specified new level.

Corrective Action: No action is required.

WLIA02W LOAD-INDEX `Load-Index_name` REMAINS AT OVERRIDDEN VALUE `current_level`, WILL BE SET TO `new_level` WHEN RELEASED

Explanation: The specified Load-Index was set to a new level. However, the Load-Index is currently overridden and the current level will continue to be used until the Load-Index is released.

Corrective Action: No action is required.

WLIA05I LOAD-INDEX `Load-Index_name` WAS INTERNALLY SET TO `level`

Explanation: The specified Load-Index was set to a new level using an internal command.

Corrective Action: No action is required.

WLIA06W LOAD-INDEX `Load-Index_name` REMAINS AT OVERRIDDEN VALUE `current_level`, WILL BE INTERNALLY SET TO `new_level` WHEN RELEASED

Explanation: The specified Load-Index was set to a new level using an internal command. However, the Load-Index is currently overridden and the current level will continue to be used until the Load-Index is released.

Corrective Action: No action is required.

WLIA09I LOAD-INDEX `Load-Index_name` WAS OVERRIDDEN, LEVEL SET TO `level`

Explanation: The specified Load-Index was overridden and was set to the specified level.

Corrective Action: No action is required.

WLIA0AI LOAD-INDEX `Load-Index_name` WAS RELEASED, LEVEL SET TO `level`

Explanation: The specified Load-Index was released and was set to the specified level.

Corrective Action: No action is required.

Messages WLIC00 through WLICxx

This group includes messages for the Control-M for z/OS product, for the Modify INDEX commands.

WLIC00I ENDED OK, `number` LOAD-INDEXES [LISTED|MODIFIED]

Explanation: This information message indicates the normal end of the modify command. The message includes the number of Load-Indexes that were included in the list (for the LIST command) or modified (for all other commands).

Corrective Action: No action is required.

WLIC01W ENDED WITH WARNING, `number` LOAD-INDEXES [LISTED|MODIFIED]

Explanation: This warning message indicates that the modify command ended with warning. The message includes the number of Load-Indexes that were included in the list (for the LIST command) or modified (for all other commands).

Corrective Action: Check the command output for more information.

WLIC02E ENDED WITH ERROR, `number` LOAD-INDEXES [LISTED|MODIFIED]

Explanation: This error message indicates that the modify command ended with error. The message includes the number of Load-Indexes that were included in the list (for the LIST command) or modified (for all other commands).

Corrective Action: Check the command output for more information.

WLIC03W ENDED WITH WARNING, NO LOAD-INDEXES FOUND

Explanation: No Load-Indexes were found that fit the criteria specified in the command.

Corrective Action: Adjust the selection criteria and rerun the command.

WLIC04E INTERNAL ERROR - LOADING LOAD-INDEX API

Explanation: An internal error occurred.

Corrective Action: Contact BMC Support.

WLIC05E INVALID INPUT, CANNOT EXECUTE THE COMMAND

Explanation: The command contained invalid input and was ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC06E UNKNOWN COMMAND `command`

Explanation: Invalid command entered. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC07E DUPLICATE COMMANDS

Explanation: A duplicate command was entered. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC09E UNKNOWN PARAMETER `parameter`

Explanation: Invalid parameter entered. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC0AE DUPLICATE PARAMETER `parameter`

Explanation: A duplicate parameter was entered. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC0BE INVALID PARAMETER VALUE `parameter`

Explanation: Invalid parameter value entered. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC0DE NO COMMAND ENTERED

Explanation: No LOAD-INDEX command entered. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC0EE MISSING MANDATORY PARAMETER

Explanation: The command was missing a mandatory parameter. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC0FE PARAMETER NOT ALLOWED

Explanation: Invalid parameter entered in the command. Command ignored.

Corrective Action: Fix the command input and rerun the command.

WLIC0VE ERROR INITIALIZING COMMANDS HANDLER

Explanation: Initializing of command handler failed. The Optimization feature is disabled.

Corrective Action: Review the monitor output and fix the issue.

WLIC0WW LOAD-INDEX OPTIMIZATION IS DISABLED, COMMAND IGNORED

Explanation: A Modify command was issued, but the Optimization feature is disabled and the command is ignored.

Corrective Action: Reissue the command when Optimization is active once again.

WLIC10I NAME=`Load-Index_name` TYPE=`type` LEVEL=`level` OVERRIDDEN=[Y|N]

Explanation: Basic information provided for the listed Load-Index.

Corrective Action: No action is required.

WLIC12I NAME=`Load-Index_name` TYPE=`type` DESC=`description`

Explanation: First line of detailed information provided for the listed Load-Index.

Corrective Action: No action is required.

WLIC13I LEVEL=`level` OVERRIDDEN=[Y|N] SET AT=`timestamp` BY=`initiator` NOTE=`note`

Explanation: Second line of detailed information provided for the listed Load-Index.

Corrective Action: No action is required.

WLIC14I ---------------------------------------------

Explanation: Third line of detailed information provided for the listed Load-Index (a separation line).

Corrective Action: No action is required.

WLIC15I `Load-Index_nameaction` TO `level` ENDED SUCCESSFULLY

Explanation: The action performed by the command completed successfully. The specified new level was applied to the Load-Index.

Corrective Action: No action is required.

WLIC16W `Load-Index_nameaction` TO `level` ENDED WITH WARNINGS

Explanation: The action performed by the command ended with warnings. The specified new level was applied to the Load-Index.

Corrective Action: Check the command output for more information.

WLIC17E `Load-Index_nameaction` ENDED WITH ERRORS

Explanation: The action that the command attempted to perform on the Load-Index ended with errors.

Corrective Action: Check the command output for more information.

WLIC1AW `Load-Index_name` NOT EXTERNAL, SKIPPED

Explanation: A SET command was run against a Load-Index that is not external. The Load-Index is skipped.

Corrective Action: Fix the command input and rerun the command, as necessary.

WLIC1BI `Load-Index_name` SET TO `level` ENDED, LEVEL IS OVERRIDDEN

Corrective Action: No action is required.

WLIC1DW `Load-Index_name` NOT OVERRIDDEN, SKIPPED

Explanation: A Release command was issued but the Load-Index is not overridden. The command is ignored.

Corrective Action: No action is required.

Messages WLIL00 through WLILxx

This group includes messages for the Control-M for z/OS product, for the Modify INDEX commands.

WLIL40E USE WHY(?) OPTION FOR ACTION TYPE SET

Explanation: The WHY command is available only for a Set action on a Load-Index.

Corrective Action: No action is required.

WLIL50E CALCULATION NOT AVAILABLE FOR EXTERNAL LOAD-INDEXES

Explanation: No calculation information is available for the selected Load-Index, because it is an external Load-Index.

Corrective Action: No action is required.

WLIL51E NO DATA AVAILABLE FOR SELECTED LOAD-INDEX

Explanation: No calculation information is available for the selected Load-Index, because no LPAR was included in the calculations.

Corrective Action: No action is required.

WLIL52S LOAD-INDEX (WLI) FILE IS FULL. LOAD-INDEX NOT ADDED.

Explanation: The Load-Index repository is full. New Load-Indexes cannot be added.

Corrective Action: Enlarge the WLI file and try again to add the Load-Index.

WLIL53E CALCULATION NOT AVAILABLE FOR MAINVIEW ALARM LOAD-INDEXES

Explanation: No calculation information is available for the selected Load-Index, because it is an MVA (MainView Alarm) Load-Index.

Corrective Action: No action is required.

WLM messages

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 WLMW00 through WLMWxx

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.

WLMW00E INVALID PARAMETER PASSED TO CTMWLM; WLM SRVCLASS REQUEST ABORTED

Explanation: CTMWLM, the Control-M workload management service class processing module, received an incomplete or incorrect parameter list.

The specific service class request is aborted.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

WLMW01E IOAMEM GETMEM ERROR. RETURN=`rc` REASON=`rsn`

Explanation: CTMWLM, the Control-M workload management service class processing module, was unable to read the WLMSCTBL table in the CTM PARM library.

The specific service class request is aborted.

Corrective Action: Note the values of rc and rsn, prepare the Control-M monitor full output, and contact BMC Customer Support.

WLMW02E GETMAIN FOR INTERNAL TABLE FAILED. LEN=`len` R15=`r15`

Explanation: CTMWLM, the Control-M workload management service class processing module, was unable to acquire enough storage to build the internal table which represents the WLMSCTBL table in the CTM PARM library.

The specific service class request is aborted.

Corrective Action: Note the values of len and r15, prepare the Control-M monitor full output, and contact BMC Customer Support.

WLMW03E FREEMAIN OF OLD INTERNAL TABLE FAILED. LEN=`len` PTR=`ptr`

Explanation: CTMWLM, the Control-M workload management service class processing module, was unable to free previously-acquired storage.

Corrective Action: Note the values of len and ptr, prepare the Control-M monitor full output, and contact BMC Customer Support.

WLMW04I WLM SRVCLASS TABLE {LOADED | RELOADED} SUCCESSFULLY WITH `num` ENTRIES

Explanation: CTMWLM, the Control-M workload management service class processing module, successfully loaded or reloaded the WLMSCTBL table from the CTM PARM library.

Corrective Action: No action is required.

WLMW05W INTERNAL WLM SRVCLASS TABLE HAS NO VALID ENTRIES

Explanation: CTMWLM, the Control-M workload management service class processing module, successfully loaded or reloaded the WLMSCTBL table from the CTM PARM library but found no valid entries.

All subsequent service class requests are effectively ignored.

Corrective Action: Correct or add entries to the WLMSCTBL table in the CTM PARM library.

WLMW06E ENTRY `rec` PARSING ERROR: `jobNameapplNamefromTime toTime`

Explanation: CTMWLM, the Control-M workload management service class processing module, detected a parsing error in this entry in the WLMSCTBL table in the CTM PARM library.

The variables in this message are:

rec - the record number
jobName - the name of the job in the WLMSCTBL table entry
applName - the name of the application in the WLMSCTBL table entry
fromTime - the start time of the range
toTime - the end time of the range

The table entry is ignored.

Corrective Action: Correct the entry in the WLMSCTBL table in the CTM PARM library.

WLMW07I {COMMAND | MACRO} ISSUED TO RESET JOB TO SRVCLASS `servClass`

Explanation: CTMWLM, the Control-M workload management service class processing module, attempted to reset the service class of the job to servClass.

Corrective Action: No action is required.

WLMW08E IWMRESET MACRO ERROR. SRVCLASS=`servClass` RETURN=`rc` REASON=`rsn`

Explanation: CTMWLM, the Control-M workload management service class processing module, attempted to reset the service class of the job to servClass but failed.

The specific service class request is unsuccessful.

Corrective Action: For information about the return and reason codes, see the explanation of IWMRESET in the IBM manual MVS Programming: Workload Management Services.

WLMW0DW UNABLE TO BUILD SYSNAMES TRANSLATION TABLE

Explanation: CTMWLM, the Control-M workload management service class processing module, was unable to create the SYSNAME translation table. This table is required when Control-M needs to issue a modify command to reset a job’s Service Class and the JES2 member name or JES3 main name are different from the MVS system name (SYSNAME).

Corrective Action: Turn on trace level 28, prepare the Control-M monitor full output, and contact BMC Customer Support.

WTO messages

This group includes messages for the Control-O product.

Messages WTO200 through WTO2xx

This group includes messages for the Control-O product.

WTO280E ERROR EXECUTING DO `stmt_type`

Explanation: An error occurred while executing the indicated type of DO statement.

The DO action fails.

Corrective Action: Correct the DO statement in the rule.

WTO282I `text` (`usr`)

Explanation: This information message indicates that a user message was activated by the SHOUT Facility. user is the user ID of the job order requesting the SHOUT statement.

Corrective Action: No action is required.

WTO283E AUTOEDIT FAILED, RC=`rc`, REASON=`rsn`. PROCESSING OF THIS RULE IS ABORTED

Explanation: An AutoEdit symbol within a DO statement in a Control-O rule definition could not be resolved.

DO statements within a rule definition are processed sequentially. If AutoEdit resolution of a symbol with a DO statement fails, the DO statement, and any subsequent DO statements within the rule definition, are cancelled. This default processing can be overridden by using the %%RESOLVE NO control statement in a previous DO SET statement. The statement will be resolved as far as possible before performing the DO statements.

The DO action in which the AutoEdit resolution failed, and any subsequent DO actions, are cancelled.

Corrective Action: Check the return code (rc) and reason code (rsn) in the following tables to determine the reason for the failure. Correct the symbol in the rule definition, and reorder the table. If the return code or reason code is not listed, the error is an internal error, and you should notify BMC Customer Support.

Return Code ( rc )	Reason Code ( rsn )	Explanation
s	GETMAIN or FREEMAIN error
	1 through 6	GETMAIN failure If you receive this error after the rule executes in wait mode, use the %%$LOCALPOOLSIZE system variable to try and solve the problem. For a list of events that cause a rule to enter wait mode, see the description of the WAITPR# parameter.
	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.
	100	ISGENQ returned a non-zero return code.
	980	Internal error - global pool or database not found
	982	Internal error - global pool or database not found
	983	$GLOBAL 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.
	100	Timeout error. %%$DBROW = %%$DBSETVAR was used to set an IOAVAR variable but the action could not be serialized for 2 minutes.
	107	No global anchor was passed. Program error.
	108	Field not defined in database.
	109	Requested row is out of range or database has reached its maximum row count.
	110	Unable to lock the Global Variables pool.
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.

WTO284E AUTOEDIT FAILED FOR TEXT: `text`

Explanation: During rule processing, Control-O failed to resolve an AutoEdit variable, either because of a syntax error or because the AutoEdit variable was not found.

This message is usually followed by message WTO283E, which explains the reason for the error.

The rule is aborted.

Corrective Action: Check message WTO283E to determine why the AutoEdit variable did not resolve, and correct the problem accordingly.

WTO285W RULE `rule` REACHED THRESHOLD `num` SUSPENDED, TABLE `table` LIB `library`

Explanation: The rule identified in the message was suspended because it reached the rule threshold limit.

The rule threshold limit determines the maximum number of times a rule may be triggered. This limit is defined in one of the following ways:

in the THRSHOLD parameter in the CONTROL section of the CTOPARM member in the IOA PARM library
in the THRSHOLD field of the rule

The rule is suspended.

Corrective Action: Determine why the rule reached the limit, and if there is a problem correct it. Adjust the threshold limit value, if necessary, or use the Rule Status screen to release the rule from its SUSPEND state.

WTO287E DO WAIT INVALID IN COMMAND RESPONSE MODE

Explanation: A DO WAIT statement was encountered while in Command-Response mode. A DO WAIT statement is invalid when a rule is executing a DO COMMAND in the Command-Response mode.

The rule is aborted or ignored.

Corrective Action: Correct the rule so that it does not encounter a DO WAIT statement when in Command-Response mode.

WTO288E MAXIMUM NUMBER OF ‘DO’ STATEMENTS EXCEEDED

Explanation: A rule executed more than 10,000 DO statements. This message is followed by another message containing the name of the problematic rule.

In order to avoid an infinite loop, only a limited number of DO statements can be executed. The default setting for this limit is 10,000. You can override this default by setting %%DOLIMIT to a higher value.

The rule is aborted.

Corrective Action: Either correct the rule to perform less than 10,000 DO statements, or set %%DOLIMIT to a higher value.

WTO289E GLOBAL DATE IS NOT SUPPORTED FOR ADD CONDITION REQUESTS

Explanation: The dateref field in the DO COND statement contains wildcard symbols ($$$$ or ****).

The rule is aborted or ignored.

Corrective Action: Specify a distinct date in the dateref field.

WTO28AE MAXIMUM NUMBER OF NESTED RULES EXCEEDED

Explanation: The maximum number of nested rules executed in response to a DO RULE statement has been exceeded. Rules can be nested up to 20 deep.

The rule at the twenty-first level is aborted or ignored

Corrective Action: Correct the logic so that there are no more than 20 nesting levels for rules.

WTO28BE INVOKED RULE NOT FOUND

Explanation: The rule invoked using a DO RULE statement was not found in the specified, or default, table.

The rule is aborted or ignored

Corrective Action: Correct the DO RULE statement to contain a rule defined in the specified or default table, or define the rule in the specified table.

WTO28CW RULE IS IN "WAIT ACTIVATION" STATUS. "DO RULE" IS IGNORED

Explanation: A rule invoked another rule by using the DO RULE statement did not satisfy the Runtime Scheduling criteria.

Processing continues. The invoked rule is ignored.

Corrective Action: If this is not intentional, correct the invoked rule definition so that it satisfies the Runtime Scheduling criteria.

WTO28DE RULE=`rulename` ABORTED. TABLE=`tableName` LIBRARY=`dsn`

Explanation: A rule aborted because of an error. This message is preceded by another message that describes the cause of the error.

The rule is aborted at the point of error.

Corrective Action: Correct the error according to the preceding message.

WTO28EW RULE=`rulename` IGNORED. TABLE=`tableName` LIBRARY=`dsn`

Explanation: This warning message indicates that a problem occurred when processing a rule. This message is preceded by another message that describes the problem.

The rule is ignored. Processing continues.

Corrective Action: Correct the problem according to the preceding message.

WTO28FE {CTOCON | CONVCON} R15 `rc`

Explanation: A nonzero return code was received from a called program or routine. During execution, detection of a nonzero return code caused this message to be issued.

Execution of the rule terminates

Corrective Action: Send a screen print of the rule and the a trace of its execution to BMC Customer Support.

WTO28IE ERROR EXECUTING DO DOM - INVALID MESSAGE ID NUMBER SUPPLIED

Explanation: A DO DOM statement contains an invalid value for a message identification number (DOM ID). See the Control-O User Guide for a description of valid AutoEdit system variables that can be used to specify the desired message ID number.

The rule is aborted.

Corrective Action: Correct the DO DOM statement by specifying a valid message ID number (DOM ID).

WTO2A1E NO FREE WAIT ELEMENT AVAILABLE

Explanation: A rule that was required to wait could not, because no Wait element was available for it. A rule requires a Wait element to wait. In this case, the maximum number of Wait elements defined in the WAITPR# parameter of CTOPARM was already being used.

The rule is aborted.

Corrective Action: Adjust the WAITPR# and NUMCONS parameters in CTOPARM according to the instructions in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

WTO2A2E WAIT ELEMENT IS TOO SMALL

Explanation: A rule that was required to wait could not, because the Wait element was too small. A waiting rule stores its data in a Wait element. In this case, the Wait element is not large enough to store the rule data.

Rule is aborted.

Corrective Action: Either split the rule into two rules, or use less AUTOEDIT variables in it. When splitting the rule, do not define the second rule as an ON RULE, because it will use the same Wait element as the first rule.

XAM messages

This group includes messages for the Control-O product.

Messages XAM500 through XAM5xx

This group includes messages for the Control-O product.

XAM561E REQUESTED FUNCTION NOT SUPPORTED

Explanation: The requested function is not in the list of supported XAM functions.

The XAM interface returns a return code of 08 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Check the syntax and spelling of the requested function. If necessary, contact your INCONTROL administrator.

XAM562E INTERNAL RESOURCES EXHAUSTED

Explanation: The space in an internal table is exhausted. The XAM interface keeps an internal table of all XAM activities in the address space. The table can contain a maximum 256 concurrent TCBs requesting XAM services. There is no address space for a new XAM user.

Some TSO, REXX, or CLISTs running in the address space probably did not execute the TERM(inate) function, which releases the acquired XAM resources.

The XAM interface returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Determine why there is insufficient space, and correct the problem accordingly.

XAM563E IOA SUBSYSTEM `subsys` INACTIVE. INTERFACE CANNOT BE USED

Explanation: A request has been received through the XAM interface that needs the Control-O monitor, but Control-O is not active.

The requested activity is aborted.

Corrective Action: Check why Control-O is not active. Once the Control-O monitor is active again, re-issue the request.

XAM564E CTO ENVIRONMENT NOT PROPERLY INITIALIZED

Explanation: The XAM interface did not find the control blocks belonging to the calling routine. Every requester of XAM services uses a set of control blocks to provide the necessary AutoEdit Environment. The XAM interface did not find the blocks belonging to this requester.

The XAM interface returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Execute the INIT function of XAM under the current requester.

XAM565E SETOLOC/SETOGLB ERROR CODE = `rc` REASON = `rsn`, TEXT=`text`

Explanation: XAM is unable to execute the AutoEdit request. XAM detected an error while trying to resolve or set an AutoEdit expression.

The XAM interface returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Ensure that the AutoEdit expression in the SETOLOC, SETOGLB or RESOLVE functions is correctly written.

The following table shows possible values for the error code (rc) and reason code (rsn), with the explanation of each:

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

XAM566E IOA SUBSYSTEM `subsys` NOT RESPONDING TO REQUESTS

Explanation: The IOA subsystem subsys did not terminate rule execution within the expected time frame. The XAM requester waits up to two minutes for a DORULE request to terminate the rule. If no such request is received within two minutes, this message is displayed.

The XAM interface returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Review the rule execution results for errors and rectify as appropriate.

XAM567E IOA SUBSYSTEM `subsys` INACTIVE

Explanation: The requested service cannot be provided because the IOA subsystem subsys is not up.

The XAM interface returns a return code of 16 to the calling routine. The final system action depends on the calling environment.

Corrective Action: Start the Control-O monitor.

XAM568E IOA SUBSYSTEM `subsys` DETECTED AN ERROR

Explanation: An internal error was detected by the IOA subsystem subsys during the execution of a XAM DORULE request.

The XAM interface returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Do the following:

Collect information about the functions requested by the XAM interface.
Determine whether or not the Control-O monitor is properly running for ongoing automation which is not related to XAM.
Contact BMC Customer Support.

XAM569E IOA SUBSYSTEM `subsys` RETURNED AN INVALID RETURN CODE

Explanation: Due to an internal error, an invalid return code was returned by the subsystem subsys during the execution of a XAM DORULE request.

The XAM interface returns a return code of 16 to the calling routine. The final System Action depends on the calling environment.

Corrective Action: Do the following:

Collect information about the functions requested by the XAM interface.
Determine whether or not the Control-O monitor is properly running for ongoing automation which is not related to XAM.
Contact BMC Customer Support.

XAM56AW SOME LOCAL VARIABLES NOT COPIED FROM XAM TO RULE, REASON=`rsn`

Explanation: A request was made to execute a Control-O rule by means of the DORULE function of the XAM interface. However, by the time the request was made, the XAM program that was executing had created an excessive number of local AutoEdit variables. The XAM service cannot share all these local AutoEdit variables with the Control-O rule, so some are discarded before the rule is given control.

In this message, rsn is an internal reason code used by BMC Customer Support.

The DORULE function continues, and control is given to the rule, but some local AutoEdit variables that cannot be copied to the rule environment are discarded. These discarded local AutoEdit variables are not available to the executed rule, nor are they available to the original XAM program once execution of the rule is complete.

Corrective Action: Use less local AutoEdit variables in the XAM program. You may be able to achieve this by using global, rather than local, AutoEdit variables.

If the problem persists, contact BMC Customer Support.

XAM56BW SOME LOCAL VARIABLES NOT COPIED BACK FROM RULE TO XAM, REASON=`rsn`

Explanation: A request was made to execute a Control-O rule by means of the DORULE function of the XAM interface. However, by the time the rule finished executing, an excessive number of local AutoEdit variables had been created. The XAM service cannot share all these local AutoEdit variables with the original environment (the calling XAM program), so some are discarded before returning from the rule.

In this message, rsn is an internal reason code used by BMC Customer Support.

Execution of the DORULE request is completed, and control returns to the calling XAM program. However, some of the local AutoEdit variables that cannot be copied to the environment of the calling program are discarded. These discarded local AutoEdit variables are then no longer available to the original XAM program.

Corrective Action: Use less local AutoEdit variables in the XAM program and in the Control-O rule that you were executing. You may be able to achieve this by using global, rather than local, AutoEdit variables.

If the problem persists, contact BMC Customer Support.

XAM56EW CONTROL-O MONITOR IS NOT ACTIVE. IOA SUBSYSTEM `subsystem_name`

Explanation: XAM discovered that Control-O monitor is not active.

The XAM function failed.

Corrective Action: Validate that Control-O monitor is active in the system that the XAM is executing. If Control-O monitor is not active, request the operator to start it and then perform the XAM function again.

XAM56FW CONTROL-O MONITOR INTERFACE ERROR RC=`##`. IOA `subsystem_name`

Explanation: This is an internal error that might be created when the XAM interface returns a return code greater than 4. In most cases it occurs when the XAM function is performed when Control-O monitor did not complete its startup or it started its shutdown.

The XAM function failed.

XCF messages

This group includes messages for the Control-O product.

Messages XCF200 through XCF2xx

This group includes messages for the Control-O product.

XCF2B2I XCF QUERY ERROR RC=`rc` REASON=`rsn`

Explanation: This information message indicates that an error was detected while Control-O was querying XCF.

Control-O issued macro IXCQUERY. The macro returned return code rc and reason code rsn.

Corrective Action: Review the macro return code and reason code. If necessary, correct the problem and restart Control-O.

XMM messages

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

Messages XMM600 through XMM6xx

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

XMM645I MONITOR USER PGM APPLID TERMINAL START LASTUSED ST

Explanation: After an operator DISPLAY command to one of the Online monitors, this header message for message XMM646I is issued.

Corrective Action: No action is required.

XMM646I `monName user pgm applId terminal start lastUsed st`

Explanation: After an operator DISPLAY command to one of the Online monitors, this message is displayed for each active user.

The variables in this message are:

monName - the name of the monitor started task
user - the user name (ID)
pgm - the program name
applId - the application ID
terminal - VTAM terminal ID
start - user sign-on time
lastUsed - time stamp of last user entry
st - Valid values are:
- W (Waiting for user data)
- A (Active user is waiting for response)

Corrective Action: No action is required.

XMM647E `monName` - LOAD OF `pgm` FAILED. SIGNON OF USER `usr` FAILED

Explanation: Load for a module requested during user sign-on to the Online facility failed. The user main program as specified by Online monitor sign-on exit or by default (CTMXMAN, CTMXMAND, CTDXMAN, or CTDXMANU) cannot be found in the Online monitor STEPLIB libraries.

Sign-on to the specified IOA Online monitor is terminated.

Corrective Action: Contact your INCONTROL administrator to find out why the program is missing. If the problem is not resolved, call BMC Customer Support.

XMM648S `monName` - ONLINE MONITOR ENDED WITH ERROR

Explanation:Highlighted, unrollable message.

A severe error has occurred. IOA Online monitor shutting down.

Detailed information on this error is available in the messages which were previously displayed on the operator console.

The specified IOA Online monitor is shutting down.

Corrective Action: Check the system log for additional messages.

XMM649E `monName` - INVALID MODIFY PARAMETERS. VALID PARAMETERS ARE:

Explanation: An invalid parameter was passed to the specified IOA Online monitor by an operator modify command (F). A list of valid modify parameters will appear on the operator console following this message.

The modify command is rejected.

Corrective Action: Enter a correct modify parameter.

Messages XMM700 through XMM7xx

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

XMM770I INVALID TRACE LEVEL WAS SPECIFIED: `xxxxxxxxxxxxxxx`

Explanation: This information message is issued when the trace is turned on for the IOA online monitor and the trace level is invalid.

When the command F IOA- monName, TRACE= nnn,ON or OFF is used to turn the trace ON or OFF, and the trace level is invalid, this message is issued. The trace level may be set to any value from 1 through 256.

The system ignores the command and continues processing.

Corrective Action: Reset the trace level to a valid value and try again.

XMM775I `monName` - `validModifyParm`

Explanation: This information message follows message CTM649E, which is issued when a MODIFY parameter is invalid.

Corrective Action: No action is required.

XMM776I `monName` - SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message indicates that the specified Online monitor is shutting down based on an operator’s request.

Corrective Action: No action is required.

XMM777I `monName` - ONLINE MONITOR INITIALIZATION STARTED

Explanation: This information message indicates that the specified Online monitor was started and is currently building the required internal environment.

Corrective Action: No action is required.

XMM778I `monName` - ONLINE MONITOR INITIALIZATION COMPLETED

Explanation: This information message indicates that the specified Online monitor is ready to serve the user’s sign-on request.

Corrective Action: No action is required.

XMM779E `monName` - ONLINE MONITOR INITIALIZATION FAILED RC `rc` IN STEP `step#`

Explanation: The specified Online monitor initialization has encountered an internal error in the step# step and has returned the return code rc.

The following step numbers and return codes can appear in the message:

Step No. (step#)	Explanation
0001	Subsystem initialization error.
	Return Code (rc)	Description
	04	IOA component already active.
	08	Subsystem name not supplied.
	12	Subsystem executor not found.
	16	Insufficient storage.
	20	Subsystem already active for a different IOA release.
	24	IOAOMON already active for a different IOA release.
	28	Invalid parameters passed to the initialization routine.
	32	Internal error.
0002	ECBLIST could not be obtained in CSA/ECSA
0003	Cross-memory environment establishment error AXSET).
0004	Cross-memory environment establishment error (LXRES).
0005	(ETCRE).
0006	(ETCON).
0007	IOAOMON could not be made non-swappable.
0009	There is only one return code for this step:
	Return Code (rc)	Description
	08	IOAOMON could not find its own ASCB.

The specified online monitor will shut down.

Corrective Action: Act according to the step number and return code as follows:

Step Code	Return Code (rc)	Action
0001
	08	Verify that the subsystem name is defined.
	12	Verify that the subsystem name is defined.
	16	Try again.
	20	Verify that the subsystem is used solely by the current IOA version of IOAOMON.
	24	Verify that the subsystem is used solely by the current IOA version of IOAOMON.
	28	Forward problem to IOA representative.
	32	Forward problem to IOA representative.
0002		Try again.
0003 through 0009		Forward problem to your IOA representative.

XMM77AI USER `userId` WAS CANCELED DUE TO TIMEOUT

Explanation: This information message indicates that the communication session with the specified user was terminated because no data was transmitted during a period of time which exceeded the time-out interval.

This message is generated by CTMXSND which communicates with the OMON cross-memory monitor.

Corrective Action: No action is required.

XMM780I `monName` - NO USER IS SIGNED ON TO THIS ONLINE MONITOR

Explanation: This information message is displayed when the operator inquires about active users in the specified Online monitor but there are none.

Corrective Action: No action is required.

XMM781E `monName` - INSUFFICIENT STORAGE FOR USER `usr`. SIGN-ON FAILED

Explanation: Insufficient virtual storage in the Online monitor address space.

User sign-on request is terminated.

Corrective Action: Increase the REGION size of the Online monitor. If the problem persists, reduce the number of users allowed to sign on to the Online monitor by lowering the value of the MAXSESS parameter of the specific monitor in IOAXPRM. For more details, see the advice on installing the IOA Online monitor in the INCONTROL for z/OS Installation Guide.

XMM782E `monName` - INSUFFICIENT STORAGE FOR INITIALIZATION.

Explanation:Highlighted, unrollable message.

Insufficient memory for the online monitor.

The specified online monitor shuts down.

Corrective Action: No action is required.

XMM784E `monName` - AN ONLINE MONITOR WITH THE SAME STC NAME IS ALREADY ACTIVE

Explanation: The operator entered a START command in order to activate monitor. Control-D and Control-M online monitors may work simultaneously provided that each monitor uses a unique name.

The newly started online monitor terminates.

Corrective Action: If an additional online monitor is needed, define another JCL procedure with a different name to support it.

XMM785I EXISTING USERS (IF ANY) ARE NOT USING A TREE

Explanation: This information message is generated if a DISPLAY TREES inquiry is made, but no users are using a Control-D Recipient Tree.

Corrective Action: No action is required.

XMM786I `monName` - NEW TREE LOADED. NEW USERS WILL BE SIGNED ON TO THE NEW TREE

Explanation: This information message indicates that the operator has modified the Online monitor with the LOADTREE command.

A new tree was loaded from the data set (member) allocated to the DATREE DD statement. The new tree will be in effect for all users who sign on from this point in time.

Corrective Action: No action is required.

XMM787W `monName` - MAXIMUM NUMBER OF TREES LOADED. A TREE MUST BE FREED IN ORDER TO LOAD A NEW ONE

Explanation: The operator entered a LOADTREE command but there are already five trees in storage. Only five tree copies can be loaded.

Corrective Action: Wait and retry. A tree is freed when the last user working with an old tree leaves the user screen, or is cancelled.

XMM788I `monName` - THE FOLLOWING USERS ARE SIGNED ON TO TREE NUMBER `num`

Explanation: This information message is the result of a DISPLAY TREES inquiry to one of the online monitors. It acts as a header for message CTM789I. The message is displayed for each Recipient Tree that is loaded in the online monitor.

Corrective Action: No action is required.

XMM789I `monName` - `userId` ...

Explanation: This information message displays the result of a DISPLAY TREES inquiry to one of the online monitors. It is displayed for each group of six users.

The variables in this message are:

monName - The name of the online monitor started task.
userId - User ID that is using the Recipient Tree.

Corrective Action: No action is required.

XMM78AE `ioaomon stc name` INITIALIZATION OF THE LIBRARY `ddName` FAILED

Explanation: The IOA online monitor could not process the library referenced by the ddName DD statement. The error occurred when the IOA online monitor address space attempted to initialize processing for the library or a member within the library.

The IOA online monitor terminates with a return code of 8.

Corrective Action: Check for the presence of the ddName DD statement, the library referenced by it and/or the member name in the ALC allocation member and in the JCL for the monitor. Add the missing entry or correct the entry in error. Restart the IOA online monitor.

XMM78BE `ioaomon stc name` MEMBER PRMXMM WITH COMMON COMMANDS AND PFKEYS IS NOT FOUND

Explanation: The IOA online monitor did not find the PRMXMM member in the IOA PARMCMD library. The library referenced by the DACMDCU DD statement under the IOA online monitor does not contain the PRMXMM member, which internally defines common COMMANDS and PFKEYS.

The IOA online monitor terminates with a return code of 8.

Corrective Action: Insure that the DACMDCU DD statement correctly refers to the IOA PARMCMD library. Ensure that the PRMXMM member exists in the library. If the problem persists, contact BMC Customer Support.

XMM78CI `ioaomon stc name` MEMBER `memName` WITH COMMANDS OR PFKEYS IS NOT FOUND

Explanation: This information message indicates that the IOA online monitor did not find the COMMAND or PFKEYS member in the IOA PARMCMD library. The libraries referenced by the DACMDCU and DAPFCMD DD statement under the IOA online monitor do not contain the COMMAND or PFKEYS member associated with the currently displayed screen.

The IOA online monitor continues execution. Problems may occur when attempting to execute commands entered on the user’s screen.

Corrective Action: Ensure that the DACMDCU and DAPFCMD DD statement correctly refer to the IOA PARMCMD library. Ensure that all necessary COMMAND and PFKEYS members exist in the library. If the problem persists, contact BMC Customer Support.

XMM78DE `jobName` JOBNAME NOT DEFINED IN IOAXPRM

Explanation: When starting up, the IOA Online monitor jobName was not found in IOAXPRM (either explicitly, or by mask).

The IOA Online monitor terminates.

Corrective Action: Use a valid job name, or make the necessary changes to IOAXPRM, and restart the monitor.

XMM78EE `jobName` WRONG LEVEL OF IOAXPRM

Explanation: The eye-catcher of the IOAXPRM member was not found in storage.

The probable cause is that the eye-catcher was overwritten by another module.

The startup of the IOA monitor stops.

Corrective Action: Contact your INCONTROL administrator. If no solution can be found for the problem, contact BMC Customer Support.

XMM793I `monName` - ONLINE MONITOR SHUTTING DOWN

Explanation:Highlighted, unrollable message.

This information message is generated when the specified Online monitor is shutting down.

Corrective Action: No action is required.

XMM794I `monName` - USER `user` NOT FOUND

Explanation: This information message indicates that an inquiry in the format DISPLAY USER= user was entered with a user name which is not active in the specified Online monitor.

Corrective Action: No action is required.

XMM795I `monName` - USER `usr` CANCELLED

Explanation: This information message indicates that the specified Online user was cancelled upon operator’s request. User session will be terminated.

Corrective Action: No action is required.

XRB messages

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

Messages XRBH00 through XRBHxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

XRBH01I CREATION OF PRINT CONTROL RECORDS STARTED

Explanation: This information message indicates that the CTDBLXRP utility has begun processing.

The CTDBLXRP utility rebuilds Print Control Records in the Active User Report List file.

Corrective Action: No action is required.

XRBH02I CREATION OF PRINT CONTROL RECORDS ENDED OK

Explanation: This information message indicates that the CTDBLXRP utility has successfully completed execution.

The CTDBLXRP utility rebuilds Print Control Records in the Active User Report List file.

The CTDBLXRP utility terminates with a condition code of 0.

Corrective Action: No action is required.

XRBH03S CREATION OF PRINT CONTROL RECORDS ENDED WITH ERRORS

Explanation: The CTDBLXRP utility, which rebuilds Print Control Records in the Active User Report List file, encountered a critical error during execution.

The utility terminates with a condition code of 8 or higher.

Corrective Action: Check the IOA Log file and system log for previous messages associated with the error. Correct the problem and re-execute the utility.

XRBH04I WAITING FOR ANOTHER CTDDELRP OR CTDBLXRP OR RESTORE JOB TO TERMINATE

Explanation: This information message indicates that the CTDBLXRP utility, which rebuilds Print Control Records in the Active User Report List file, detected another job that requires CTDBLXRP to wait before resuming processing.

To insure data integrity, the CTDBLXRP utility will not run concurrently with another CTDBLXRP, CTDDELRP or Restore Mission job.

The CTDBLXRP utility waits until the contending job terminates and then resumes processing.

Corrective Action: No action is required.

XRBH05I WAITING FOR ANOTHER TASK TO FINISH

Explanation: This information message indicates that the CTDBLXRP utility, which rebuilds Print Control Records in the Active User Report List file, detected another currently executing task that requires CTDBLXRP to wait before resuming processing.

To insure data integrity, the CTDBLXRP utility will not run concurrently while a Print Plan file is being built by a subtask in the Control-D monitor address space.

The CTDBLXRP utility waits until the contending task terminates and then resumes processing.

Corrective Action: No action is required.

XRBH06I LAST WAIT IS COMPLETE

Explanation: This information message indicates that the CTDBLXRP utility, which rebuilds Print Control Records in the Active User Report List file, has resuming processing after waiting for another job or task to complete.

This message follows messages XRBH04I and/or XRBH05I.

Corrective Action: No action is required.

XRBH07E "FE" PRINT SUPPORT ERROR. RETURN CODE `rc` FUNCTION `func`

Explanation: While performing function func, the CTDBLXRP utility, which rebuilds Print Control Records in the Active User Report List file, encountered an error and produced the return code rc.

The error associated with each return code is identified below.

Return Code	Explanation
008	Memory shortage.
012	Memory shortage.
016	Invalid function.
020	Database I/O error.
024	Open error.

Corrective Action: Check the IOA Log file and system log for additional messages associated with the error. Determine the cause of the error. Correct the problem and re-execute the utility. If the problem persists, contact BMC Customer Support.

XRBH08W ORPHAN INP RECORD. PRINT MISSION: `prtmis`, REPORT KEY: `rep_key`

Explanation: This warning message indicates that the CTDBLXRP utility encountered an orphan INP record. The INP record points to the User record with the ID rep_key, which is missing from the User file. The orphan INP record is deleted from the User file. The pointer to this record is not included in the record created by the utility print control. The utility continues to work.

Corrective Action: No action is required.

XRBH09E INVALID PARAMETER: FILE= `val`

Explanation: The val value of the FILE parameter specified in the EXEC statement for the utility CTDBLXRP is not valid. The valid values are ACT or MIG. The utility stops.

Corrective Action: Correct the invalid parameter value in the JCL and rerun the job.

XRBH0AI SCANNING OF `file` USER FILE STARTED

Explanation: This information message indicates that the CTDBLXRP utility started to scan the file Control-D User file. The following values are available for file:

ACT - Active User file
MIG - Main Migrated User file partition
MIGn - Migrated User file partition n, where n can be from 1 to 9

Corrective Action: No action is required.

N–Z

NRC Messages

Messages NRC900 through NRC9xx

NRC930I NOTE AND RULER CONVERSION STARTED.

NRC931I WD1164 IS SET TO status

NRC932I NOTE AND RULER CONVERSION ENDED

NRC933E NOTE AND RULER CONVERSION ENDED WITH ERROR

NRC934I record_type RECORDS: n

NRC935S SORT ERROR RC=rc

NRC936S OPEN FILE ddname ERROR

NRC937S INSUFFICIENT STORAGE

NSC Messages

Messages NSC300 through NSC3xx

NSC391I NIGHT SCHEDULE REPORT STARTED

NSC392S MAXIMUM NUMBER OF INCLUDE PARAMETERS EXCEEDED

NSC393I NIGHT SCHEDULE REPORT ENDED

NTP Messages

Messages NTP0 through NTP0xx

NTP001E SECURITY VIOLATION. YOU ARE NOT AUTHORIZED TO EDIT THE NOTE

NTP002E PLEASE FILL IN A VALID OPTION - "Y" OR "N"

NTP003E NOTE PAD FILE IS IN USE, TRY AGAIN LATER

OGR messages

Messages OGR0 through OGR0xx

OGR004E NO MATCHING RECORDS FOUND IN THE LOG FILE

Messages OGR300 through OGR3xx

OGR391I OVERNIGHT EXECUTION REPORT STARTED

OGR393I OVERNIGHT EXECUTION REPORT ENDED

OGR394S MAXIMUM NUMBER OF INTERVALS EXCEEDED

OPL messages

Messages OPL300 through OPL3xx

OPL341S OPERLOG NOT AVAILABLE UNDER MVS/ESA 5.2

OPL342S ERROR OPENING OPERLOG FILE

OPL346S ABEND abCode INTERCEPTED WHILE PROCESSING THE OPERLOG

OPL347S ERROR RETURN CODE FROM A SYSTEM LOGGER REQUEST rc

OPL348S OPERLOG IS EMPTY

OPL349S OPERLOG END OF FILE IS REACHED

OSM messages

Messages OSM100 through OSM1xx

OSM150E mediaName - DYNAMIC ALLOCATION ERROR FOR DDNAME=SORTIN RC= rc, REASON CODE= rsn

OSM151E mediaName - SORT OF OSS EXTRACT DATABASE FILE FAILED. RC=rc

OSM152E mediaName - VOLSER volser NOT FOUND IN OSS EXTRACT DATABASE FILE

OSM153E mediaName - PLATTER platterId NOT FOUND FOR VOLSER volser

OSM154E mediaName - INTERNAL ERROR RC= rc

PAS messages

Messages PAS0 through PAS0xx

PAS046S BLDL/LOAD FAILED FOR THE MODULE modName

Messages PASF00 through PASFxx

PASF90I THE PASSWORD OF CONTROL- x IS AUTHORIZED

PASF90S OPEN OF DDCARD ddName FAILED

PASF91S PASSWORD MEMBER TOO LARGE (DD ddName)

PASF91W Control- x IS NOT INSTALLED !

PASF92S SYNTAX ERROR IN PASSWORD MEMBER (DD ddName)

PASF93S VALUE ERROR IN PASSWORD MEMBER (DD ddName)

PASF94S PASSWORD INVALID, PLEASE RECHECK PASSWORD MEMBER (DD ddName)

PASF95S PASSWORD FOR CONTROL- x IS ABOUT TO EXPIRE IN n DAYS

PASF96S PASSWORD FOR CONTROL- x HAS EXPIRED

PASF97S INTERNAL ERROR OCCURRED ON DD ddName, PLEASE NOTIFY THE IOA ADMINISTRATOR

PASF98S OBLIGATORY FIELD MISSING FROM PASSWORD MEMBER (DD ddName)

PASF9AS PASSWORD FOR CONTROL-x NOT DEFINED IN MEMBER (DD ddName)

PASF9BS AUTHORIZATION PERIOD HAS NOT STARTED YET (DD ddName)

PASF9CS CPUID/MODEL NOT FOUND IN AUTHORIZED CPU LIST (DD xxxxxxxx)

PASF9DS CARD = text

PASF9ES PASSWORD DDCARD ddName POINTS TO A NON EXISTING MEMBER (ABEND S013-18)

PASF9FS PASSWORD FOR CONTROL- x EXPIRED, TEMPORARY AUTHORIZATION GRANTED

PDA messages

Messages PDA400 through PDA4xx

PDA482S OPEN OF USER DATE CONTROL RECORD FAILED. DDNAME "DACHK"

PDA483S OPEN OF IOA LOG FILE FAILED

PDA484I POST DAILY CHECKPOINT WRITTEN

PLN messages

Messages PLN0 through PLN0xx

PLN020I THE MEMBER memName IS NOT SCHEDULED ACCORDING TO DATE-CRITERIA, AND WILL BE EXCLUDED

PLN021E ACCESS OR ANALYZING OF CALENDAR calName FOR MEMNAME memName FAILED

PMM messages

Messages PMM300 through PMM3xx

PMM350I PRINTING MISSIONS MANAGER STARTED

PMM351S INCORRECT NUMBER OF EXPECTED SUBTASKS

PMM352S GETMAIN ERROR FOR PRINTING MISSIONS MANAGER INTERNAL WORK VECTOR

PMM354S INTERNAL ERROR - CS FAILED IN ADD OF PRINT MISSIONS MANAGER VECTOR

PMM355S INTERNAL ERROR - CS FAILED IN MOVE OF PRINT MISSIONS MANAGER VECTOR

NRC931I WD1164 IS SET TO `status`

NRC934I `record_type` RECORDS: `n`

NRC935S SORT ERROR RC=`rc`

NRC936S OPEN FILE `ddname` ERROR

OPL346S ABEND `abCode` INTERCEPTED WHILE PROCESSING THE OPERLOG

OPL347S ERROR RETURN CODE FROM A SYSTEM LOGGER REQUEST `rc`

OSM150E `mediaName` - DYNAMIC ALLOCATION ERROR FOR DDNAME=SORTIN RC= `rc`, REASON CODE= `rsn`

OSM151E `mediaName` - SORT OF OSS EXTRACT DATABASE FILE FAILED. RC=`rc`

OSM152E `mediaName` - VOLSER `volser` NOT FOUND IN OSS EXTRACT DATABASE FILE

OSM153E `mediaName` - PLATTER `platterId` NOT FOUND FOR VOLSER `volser`

OSM154E `mediaName` - INTERNAL ERROR RC= `rc`

PAS046S BLDL/LOAD FAILED FOR THE MODULE `modName`

PASF90I THE PASSWORD OF CONTROL- `x` IS AUTHORIZED

PASF90S OPEN OF DDCARD `ddName` FAILED

PASF91S PASSWORD MEMBER TOO LARGE (DD `ddName`)

PASF91W Control- `x` IS NOT INSTALLED !

PASF92S SYNTAX ERROR IN PASSWORD MEMBER (DD `ddName`)

PASF93S VALUE ERROR IN PASSWORD MEMBER (DD `ddName`)

PASF94S PASSWORD INVALID, PLEASE RECHECK PASSWORD MEMBER (DD `ddName`)

PASF95S PASSWORD FOR CONTROL- `x` IS ABOUT TO EXPIRE IN `n` DAYS

PASF96S PASSWORD FOR CONTROL- `x` HAS EXPIRED

PASF97S INTERNAL ERROR OCCURRED ON DD `ddName`, PLEASE NOTIFY THE IOA ADMINISTRATOR

PASF98S OBLIGATORY FIELD MISSING FROM PASSWORD MEMBER (DD `ddName`)

PASF9AS PASSWORD FOR CONTROL-`x` NOT DEFINED IN MEMBER (DD `ddName`)

PASF9BS AUTHORIZATION PERIOD HAS NOT STARTED YET (DD `ddName`)

PASF9CS CPUID/MODEL NOT FOUND IN AUTHORIZED CPU LIST (DD `xxxxxxxx`)

PASF9DS CARD = `text`

PASF9ES PASSWORD DDCARD `ddName` POINTS TO A NON EXISTING MEMBER (ABEND S013-18)

PASF9FS PASSWORD FOR CONTROL- `x` EXPIRED, TEMPORARY AUTHORIZATION GRANTED

PLN020I THE MEMBER `memName` IS NOT SCHEDULED ACCORDING TO DATE-CRITERIA, AND WILL BE EXCLUDED

PLN021E ACCESS OR ANALYZING OF CALENDAR `calName` FOR MEMNAME `memName` FAILED

PMS406E RECIPIENT `recipName` IGNORED. RECIPIENT NOT FOUND IN THE TREE

PMS408E PRINTING PLAN FILE ALLOCATION ERROR. RC= `rc`, ERROR= `errCode`

PMS422I START COMMAND HAS BEEN ISSUED FOR PROCEDURE `procName`, COM `number`

PMS42BE ERROR READING SKELETON. CTMMEM RC= `rc`

PMS42CE MESSAGE=MEMBER `memName` IS NOT FOUND IN THE SKELETON LIBRARY

PMS42EI PRINT JOB `name` / `jobId` HAS BEEN SUBMITTED

PMS433S ALLOC OF `dd_stmt` FAILED ON `rsn`

PMS434S FREE OF `dd_stmt` FAILED ON `rsn`

PMS435S SORT OF BUNDLE FAILED. RC= `rc`

PMS439I ONLY (`number`) FREE ENTRIES ARE LEFT ON THE COMMUNICATION FILE - PLEASE INCREASE ITS SIZE