Messages CTM500 through CTM5xx

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.

CTM501I CTMJOB STARTED

Explanation: This information message indicates that the CTMJOB program has started.

The CTMJOB program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM502S OPEN OF SCHEDULE DATA FAILED. DDNAME "DAJOB"

Explanation: Open of scheduling tables data set failed (the DAJOB DD statement).

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure, and could be due to one of the following:

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

The CTMJOB program will end with errors.

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

CTM502E CONVCON INVALID RC=rc REASON =rsn CONSOLE ID=consId CONSOLE NAME=consName

Explanation: A command was issued to a console specified by CONSOLE ID= consId or CONSOLE NAME= consName, and the CONVCON service return code is not 0. When a command is issued to a console, the CONVCON service is called to verify the console. The return code from the CONVCON service that validates the console response is rc.

The command may be rejected depending on the CONVCON action.

Corrective Action: To determine the reason for the error, see the Authorized Assembler Services Guide. Correct the error, and reissue the command.

CTM503S OPEN OF USER DATE CONTROL-RECORD FAILED - DDNAME "DACHK"

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement). Issued by the CTMJOB program which is usually activated by the New Day procedure.

Possible causes are:

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

The CTMJOB program will end with errors.

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

CTM504S USER DATE CONTROL-RECORD IS EMPTY

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

The CTMJOB program will end with errors.

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

CTM505S PREVIOUS RUN OF CTMJOB DID NOT FINISH OK

Explanation: A previous run of the CTMJOB program did not finish OK. This program is usually activated as part of the New Day procedure.

Date-2 and date-3 (or date-4 and date-5) of the Date Control Record are not equal. Possible causes are:

• The previous run of the CTMJOB program did not finish OK.
• Someone has modified the contents of the User Date Control Record (the DACHK DD statement).

For more information, see the Control-M chapter in the INCONTROL for z/OS Administrator Guide.

The CTMJOB program ends with errors.

Corrective Action: Change date-3 (or date-5), positions 25-30 (or positions 50-55) in the Date Control Record (the DACHK DD statement) to the values of date-2 (or date-4).

To rerun the same Daily, correct all the dates to the value of the day before. Be careful not to order the same job twice during a rerun on the same day. BMC recommends that you delete the ordered jobs from the Active Jobs file and then run the Daily again.

If the previous abend happened after many jobs had been ordered, BMC recommends requesting the remaining jobs manually by means of CLIST CTMJOBRQ.

CTM506S SCHEDULING FAILED FOR MEMBER memName

Explanation: Scheduling failed for the memName member. This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

The IOA Log or the job output should contain an additional message concerning the reason for failure.

The job order of member is not placed in the Active Jobs file. Depending on the severity of the problem, the New Day procedure will either continue to the next job order or terminate with the condition code 08.

Corrective Action: Check the IOA Log or the job’s output for the reason.

CTM507S LAST MONTHLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATE

Explanation: Invalid last monthly Scheduling Date.

The last monthly Scheduling Date (positions 18-23) in the User Date Control Record is greater than the current original Scheduling Date (positions 1-6). Possible causes are:

• The previous run of the CTMJOB program did not finish OK.
• Someone has modified the contents of the User Date Control Record (DD statement DACHK).

For more details, see the INCONTROL for z/OS Administrator Guide.

The CTMJOB program will end with errors.

Corrective Action: Correct the User Date Control Record (the DACHK DD statement).

CTM508S LAST MONTHLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK IT

Explanation: The last monthly scheduling date is more than 28 days ago.

Possible causes are:

• The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to “yesterday.”
• Someone has modified the contents of the General Date Control Record incorrectly.

For more details, see the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the User Date Control Record (the DACHK DD statement).

CTM509S INVALID YEAR IN ORIGINAL SCHEDULING DATE OF USER DATE CONTROL-RECORD

Explanation: Invalid year in the original scheduling date of the User Date Control record. This year is not yet supported by Control-M.

The CTMJOB program will end with errors.

Corrective Action: Please correct the year field (the DACHK DD statement).

CTM510S SEVERE ERROR IN THE SCHEDULING DATA - NOTIFY THE IOA ADMINISTRATOR

Explanation: Severe error in the scheduling data.

This message is produced when the scheduling tables (described by the DAJOB DD statement) contain erroneous data. This can be due to the following:

• The contents of the table were incorrectly modified using an editor or program, and the format of the table is invalid.
• Internal error in Control-M.

'The program terminates with a condition code of 08.

Corrective Action: Try to restore the table to its original state. If you cannot, prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support.

If it is a batch Daily using a permanent Date Control Record, correct the contents of the record before running the Daily again. If issued during a User Daily or New Day procedure, see message CTM505S for further details.

CTM513I SCHEDULE FAILED FOR num CONTROL-D CATEGORIES

Explanation: This information message indicates that num Control-D decollating missions categories were not found in the library allocated to the DAREPMIS DD statement.

The Control-M New Day procedure continues processing.

Corrective Action: Look at the IOA Log for the failed categories and associated reasons for failure.

CTM514S INSUFFICIENT STORAGE FOR THE JOB

Explanation: Insufficient storage for processing the job order.

The program terminates with a condition code of 08.

Corrective Action: Increase the REGION size of the task which issued the request.

CTM515S ERROR IN SCHEDULING DATA - TOO MANY CARDS FOR ONE JOB

Explanation: Too many statements for one job. Scheduling data used to describe the job order are too large to be processed by Control-M.

The job order will not be placed on the Active Jobs file. The New Day procedure will terminate with a condition code of 08.

Corrective Action: Check the contents of the job order, using the Online Scheduling Facility, and remove unnecessary scheduling data. Prepare the Control-M monitor full output and contact BMC Customer Support.

CTM516S ERROR IN SCHEDULING DATA - FIRST CARD SHOULD START WITH "D"

Explanation: Invalid scheduling data in the first data set described by the DAJOB DD statement. The first statement of valid scheduling table should start with D.

Possible causes are

• The data set described by the DAJOB DD statement is not a scheduling table.
• The scheduling data has been manually modified incorrectly.

The CTMJOB program ends with errors.

Corrective Action: Check contents of the data set described by the DAJOB DD statement and if the problem is not solved, check to find the person who may have manually changed the scheduling data.

CTM517S SCHEDULING DATA NOT AVAILABLE

Explanation: The DD statement pointing to the job scheduling tables is empty or missing.

The program ends with errors.

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

CTM518S INVALID YEAR IN USER DATE CONTROL-RECORD

Explanation: Invalid year in the User Date Control record used by the New Day procedure. This year is not supported by the release of Control-M you are using.

The CTMJOB program ends with errors.

Corrective Action: Please correct the year field (the DACHK DD statement).

CTM519S INVALID PREVIOUS WEEKLY SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 43-48)

Explanation: Invalid previous weekly Scheduling Date in the User Date Control record (positions 43-48). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

This date (date-4 of User Date Control record) might not be equal to date-5 (positions 50-55) or in invalid format. Valid format is ddmmyy or mmddyy.

Possible causes are:

• The previous run of the CTMJOB program did not finish OK.
• Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM522S INVALID ORIGINAL SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 1-6)

Explanation: Invalid original scheduling date in the User Date Control Record (positions 1-6). Valid format is ddmmyy or mmddyy.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Possible causes are:

• The previous run of the CTMJOB program did not finish OK.
• Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM523S INVALID PREVIOUS MONTHLY SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 18-23)

Explanation: Invalid previous monthly scheduling date in the User Date Control Record (positions 18-23). This date (date-2 of User Date Control Record) should be equal to date-3 (positions 24-29) or in valid format. The valid format is ddmmyy or mmddyy.

This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

Possible causes are:

• The previous run of the CTMJOB program did not finish OK.
• Someone has incorrectly modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

The CTMJOB program will end with errors.

Corrective Action: Correct your Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM524S CTMJOB ENDED WITH ERRORS

Explanation: The CTMJOB program ended with errors.

The IOA Log usually contains prior messages concerning the errors.

The CTMJOB program finishes executing with a condition code of 08.

Corrective Action: Do the following:

• Check the IOA Log for errors.
• If CTMJOB is being executed from within the New Day procedure or from a User Daily, correct the Date Control Record (date-3 and date-5) manually, if necessary, to allow the next run of the Daily.

For more details, see the INCONTROL for z/OS Utilities Guide.

CTM525I CTMJOB ENDED

Explanation: This information message is a normal message issued when the CTMJOB program terminates. CTMJOB is activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM528I MEMBER memName ID=orderId ODATE odate PLACED ON ACTIVE JOBS FILE-descr

Explanation: This information message is issued when a job order is placed on the Active Jobs file. The task is now on the Active Jobs file in WAIT SCHEDULE state.

Corrective Action: No action is required.

CTM529S LAST WEEKLY SCHEDULING DATE GREATER THAN THE CURRENT ORIGINAL SCHEDULING DATE

Explanation: The last weekly scheduling date in the Date Control Record is greater than the current original scheduling date.

This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure. Date-4 (positions 43-48) should not be greater than date-1 (positions 1-6) in the Date Control Record.

Possible causes are:

• The previous run of the CTMJOB program did not finish OK.
• Someone modified the contents of the User Date Control Record (the DACHK DD statement).

For more details, see the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the User Date Control Record (the DACHK DD statement) and rerun the New Day procedure.

CTM530S LAST WEEKLY SCHEDULING DATE WAS MORE THAN 28 DAYS AGO, CHECK IT

Explanation: The last weekly scheduling date is more than 28 days ago.

Possible causes are:

• The User New Day procedure has not been used for more than 28 days. Correct the dates in the record to yesterday.
• Someone has modified the contents of the General Date Control Record incorrectly.

For more details, see the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the Date Control Record (the DACHK DD statement) and rerun.

CTM531W MEMBER memName ODATE odate - SCHEDULING CANCELLED BY USER EXIT

Explanation: Scheduling cancelled by the CTMX001 user exit; the member did not pass user checking. The CTMX001 user exit is activated for each job order before it is placed on the Active Jobs file. The exit can direct the New Day procedure not to place the job order on the Active Jobs file, in which case this message is issued.

The job order is not placed on the Active Jobs file.

Corrective Action: Look for additional messages in the IOA Log clarifying the reason for the cancel (usually security). If you cannot find a reason, consult your system programmer.

CTM532S OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED. DDNAME "DACKPT"

Explanation: Open of Control-M Active Jobs file failed.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure, and is due to one of the following:

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

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the job/CLIST and rerun it.

CTM533S CONTROL-M ACTIVE JOBS FILE IS FULL. NOTIFY THE IOA ADMINISTRATOR

Explanation: Highlighted, unrollable message.

Control-M Active Jobs file is full. There is no more space for new job orders.

The job order is not placed in the Active Jobs file.

Corrective Action: Consult your system programmer immediately. You may need to increase the size of the Active Jobs file.

CTM534S SEVERE ERROR ON CONTROL-M ACTIVE JOBS FILE. NOTIFY THE IOA ADMINISTRATOR

Explanation: Severe error on Control-M Active Jobs file.

This could be due to one of the following:

• An I/O error occurred.
• The file allocated to the DACKPT DD statement is not the Control-M Active Jobs file.
• The Active Jobs file has been corrupted.

The CTMJOB Control-M program, which is activated as part of the New Day procedure, ends with errors.

Corrective Action: Prepare the Control-M monitor full output and have your system programmer contact BMC Customer Support. Check whether the file has been updated from two computers without global ENQ control, or maybe by an unauthorized program.

CTM535S CONTROL-M ACTIVE JOBS FILE IS BEING FORMATTED. TRY AGAIN LATER

Explanation: Control-M Active Jobs file is currently being formatted. This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. The General New Day procedure is currently running and is formatting the file.

Corrective Action: Try again later.

CTM536S SEVERE ERROR IN SCHEDULING DATA CARDS

Explanation: A severe error was found in the scheduling data statements. This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Scheduling fails for the job order. The CTMJOB program terminates with a condition code of 08.

Corrective Action: Look for additional messages concerning the error, correct the error and rerun.

CTM537S NO MORE INTERNAL WORK AREA. SEE MESSAGES AND CODES FOR REQUIRED ACTION

Explanation: Internal work areas of the New Day procedure have been exhausted. The job order contains more data than can be handled by the current release of Control-M.

The New Day procedure will terminate with a condition code of 08.

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

CTM538S LOADING OF CONTROL-M/ANALYZER INSTALLATION PARAMETERS FAILED

Explanation: Loading of Control-M/Analyzer Installation Parameters, which are in the CTBPARM member in the IOA PARM library, failed.

Possible causes are:

• There is insufficient memory to load the IOA Installation Parameters.
• The CTBPARM member does not exist in the IOA PARM library.
• The IOA PARM library was updated while you were working and the position of the CTBPARM member has changed.

The requested function is terminated.

Corrective Action: Look in the system log for additional related messages. Try one of the following:

• If loading failed because of lack of memory: increase the REGION size for batch missions; for TSO, try to log on again using a larger SIZE parameter.
• If you are using many IOA screens concurrently, try to exit a few using the END command. This releases memory used by the screens.
• If the PARM library has been modified and you are working under TSO, try to log on again. If you are working under ROSCOE, you may have to shut down ROSCOE and bring it up again.

CTM53AS AJF IS ALMOST FULL AND REACHED THE 'STOP ORDER' THRESHOLD. JOB IS NOT ORDERED.

Explanation: When the amount of used space in the AJF increases and reaches the percentage threshold specified in the STOPORDR CTMPARM parameter, Control-M stops ordering jobs.

Control-M stops ordering jobs but all other functions (for example, job submission and post-processing) continue normally.

Corrective Action: The user must compress the AJF.

CTM53BE JOB CAN NOT BE ADDED BECAUSE THE MOST RECENT GROUP ON THE AJF IS DELETED

Explanation: An attempt was made to use the DYNAMIC INSERT JOB INTO GROUP option "R" (recent) to add a job to a deleted group.

Corrective Action: No action is required.

CTM53CW CONTROL-M AJF/HST WAS NOT INDEXED, NOTIFY THE IOA ADMINISTRATOR

Explanation: Control-M was unable to index the Active Jobs file or History file because there is not enough space for additional text index records. See Optional Wish M11262.

Corrective Action: Consult your system programmer. You might need to apply Optional Wish M11262.

CTM53DE CONTROL-M AJF CAN NOT BE INDEXED, USE CTMCAJF TO COMPRESS IT

Explanation: Control-M monitor was unable to index an entry in the Active Jobs file because there is no more space for new text index records.

Corrective Action: Consult your system programmer immediately. Run CTMCAJF to compress the AJF and see Optional Wish M11262.

CTM540E ERROR IN CARDS. REASON=rsn, CODE=field

Explanation: A severe error was found in the scheduling data statements. This message is issued by Control-M (the CTMINP program) when it encounters an invalid value in a data statement.

The variables in this message are:

• rsn - a reason code that describes the probable cause of the error
• field - the field in which the error was found

Possible values of rsn and field, with explanations, are shown in the following tables.

Job order scheduling will fail. The User Daily will terminate with a condition code of 08.

Corrective Action: Use the values of rsn and field to locate the problem in the job definition. Correct the problem and run the User Daily again.

CTM540W LOAD OF SECURITY MODULE modName FAILED. SECURITY CHECKING WILL BE BYPASSED

Explanation: Loading of the modName IOA security module failed. Possible causes are:

• The installation is not using the specified user security module, and has erased the default IOA-supplied module.
• The IOA Load library is not in the load modules search lists of the job (STEPLIB + Linklist).
• There is insufficient memory.
• Another system oriented reason which can be found in the syslog.

As a result, no security checking is performed. For more details, see the sections on Security Interface Modules appropriate security guides.

Corrective Action: Notify the INCONTROL administrator. This is a potentially serious situation. Someone may be attempting to violate security.

CTM543E ID=id TASK=taskName OID=orderId - NOT FORCED OK, JOB IS ALREADY {DELETED | CHANGED | TERMINATED}

Explanation: A request was made to force the taskName task specified in the message. By the time the monitor accepted the request, the job was running, was being changed, or had already been deleted, so the request could not be performed. This message is written to the IOA Log file only.

The user request is ignored.

Corrective Action: If the entry was DELETED, it cannot be forced. If not, wait until the job ends, and if it ends NOTOK, try to force it again.

CTM544E UNABLE TO FORCE OK A CYCLIC JOB

Explanation: The user issued line command O (Force OK) for a cyclic job. Cyclic jobs cannot be Forced OK.

The user request is ignored.

Corrective Action: No action is required.

CTM545E I/O ERROR ON "AJF". CONTROL-M SWITCHES TO DUAL "AJF"

Explanation: An I/O error occurred while the Control-M monitor accessed the Active Job File (AJF). Control-M starts using the Dual AJF (CTM ALTCKP data set) instead of the primary AJF.

The Control-M monitor continues running using the Dual AJF.

Corrective Action: To use the Dual AJF in the Control-M Active Environment screen (Screen 3), reallocate the DACKP DD statement in the online environment so that it specifies the Dual AJF instead of the primary AJF.

To return to using the primary AJF, perform the following steps:

1. Fix the problem that caused the I/O error.
2. Reallocate the AJF file if necessary.
3. Stop the Control-M monitor.
4. Copy the Dual AJF to primary AJF, using the CTMCAJF or IEBGENER utility.
5. Restart the Control-M monitor.

CTM546S "CTMPARM" USED TO FORMAT THE "AJF" DIFFERS FROM YOUR "CTMPARM"

Explanation: The CTMPARM member used by the job that formatted the Active Jobs file (AJF) differs from the online user CTMPARM member. This can occur for a variety of reasons, including the following:

• The user is migrating from one release to another.
• The user is enlarging the AJF using a STEPLIB different from the one used by the online users.
• The QNAME specified in the CTMPARM member does not match the QNAME specified in Record 0 of the AJF.

The Active Environment screen is not updated.

Corrective Action: Exit from the Control-M Online facility and reenter. If the problem recurs, contact your system programmer. Your logon procedure may point to an old CTMPARM member.

CTM547E I/O ERROR ON DUAL "AJF". USAGE OF DUAL "AJF" TERMINATED

Explanation: An I/O error occurred while the Control-M monitor accessed the Dual Active Job File (AJF) (CTM ALTCKP data set).

The Control-M monitor continues running without using the Dual AJF (CTM ALTCKP data set). No mirror AJF is supported; if errors occur in the primary AJF, no valid Active Jobs file will be available.

Corrective Action: Correct the problems that cause the I/O error. Reallocate the Dual AJF file, if needed. Stop and restart the Control-M monitor.

CTM548E SEVERE ERROR IN CALENDAR calName OR YEAR NOT FOUND IN CALENDAR

Explanation: Severe error in the calName IOA calendar. Either the year is not defined in the calendar, or the calendar has been incorrectly modified.

The job order is not issued. Processing of other job orders continues.

Corrective Action: Check the contents of the job order and the calendar.

CTM549E NO AVAILABLE "AJF" EXISTS. Control-M MONITOR SHUTS DOWN

Explanation: Control-M could not access a valid Active Jobs file (AJF) due to one of the following situations:

• An I/O error occurred when the Control-M monitor accessed the Active Job File while no Dual AJF was available.
• An I/O error occurred while the Control-M monitor accessed the Dual AJF, which was being used instead of the primary AJF because of a previous I/O error in the primary AJF.

The Control-M monitor shuts down.

Corrective Action: Do the following:

1. Correct the problem that caused the I/O error.
2. Reallocate the AJF files, if needed.
3. Restart the Control-M monitor.

CTM54DE MAXIMUM 50 INSTREAM JCL ENTRIES ALLOWED

Explanation: More than 50 lines of Instream JCL were specified in the job scheduling definition.

Corrective Action: Reduce the number of Instream JCL lines to 50 or fewer.

CTM54EE DAYS MUST BE BLANK, OR 000 TO 120

Explanation: This message is produced when specifying a value greater than 120 in the FROM TIME + DAYS, UNTIL TIME + DAYS, or the DUE OUT TIME + DAYS job definition parameters.

The cursor remains positioned on the invalid value.

Corrective Action: Correct the + DAYS parameter as required.

CTM54FE FOR JOB ENDED NOTOK, VALUE MUST BE BLANK OR K (KEEP THE RESOURCE)

Explanation: For the CONTROL job definition parameter, the onFail subparameter was specified with an invalid value.

Corrective Action: Specify a valid value of blank or K (keep the resource).

CTM54GE FOR JOB ENDED OK, VALUE MUST BE BLANK OR D (DISCARD THE RESOURCE)

Explanation: For the RESOURCE job definition parameter, the onOK subparameter was specified with an invalid value.

Corrective Action: Specify a valid value of blank or D (discard the resource).

CTM54LE TO DAYS CAN NOT BE SMALLER THAN FROM DAYS

Explanation: This message is produced when the + DAYS value in the FROM TIME is greater than the + DAYS value in the UNTIL TIME job definition parameter.

The cursor remains positioned on the invalid value.

Corrective Action: Correct the + DAYS parameter as required.

CTM54ME INTERNAL ERROR IN CONTROL-M. ERROR CODE = rsn

Explanation: The AJF Space Reuse Facility has encountered an internal error.

The possible values of rsn are explained in the following table:

The AJF Space Reuse Facility is disabled.

Corrective Action: Do the following:

• Contact BMC Customer Support.
• To reactivate the AJF Space Reuse Facility, format or compress the AJF and recycle the Control-M monitor.

CTM54NS "CTMPARM" USED TO FORMAT THE "HST" DIFFERS FROM YOUR "CTMPARM"

Explanation: The CTMPARM member used by the job that formatted the HST differs from the online user CTMPARM member. This can occur for a variety of reasons, including the following:

• The user is migrating from one release to another.
• The user is enlarging the HST using a STEPLIB different from the one used by the online users.
• The QNAME specified in the CTMPARM member does not match the QNAME specified in Record 0 of the HST.

The History Environment screen is not updated.

Corrective Action: Exit from the Control-M Online facility and reenter. If the problem recurs, contact your system programmer. Your logon procedure may point to an old CTMPARM member.

CTM551E INVALID SCROLL AMOUNT

Explanation: Invalid scroll amount specified. The scrolling amount should be PAGE, HALF, CRSR, or MAX. For details, see the chapter that describes online facilities in the user guide for the active INCONTROL product.

Corrective Action: Correct the scroll amount field.

CTM552E INVALID DATE

Explanation: Invalid date specified. Valid date format is usually ddmmyy or mmddyy. In some screens, the date format is ddmm or mmdd.

In some cases, the date value may be valid but its value relative to another date is invalid, for example, when a FROM DATE is later than the TO DATE in the date prompt screen of the P (PLAN) option in Screen 2.

Corrective Action: Correct the DATE field or the DATE parameter as appropriate.

CTM552S GETMAIN FAILED IN CTMRSG GROUP PROCESSING

Explanation: The CTMRSG program could not allocate storage.

Group processing is terminated.

Corrective Action: Increase the region size.

CTM553E "UNTIL DATE" IS BEFORE "FROM DATE"

Explanation: UNTIL DATE is before FROM DATE.

Corrective Action: Correct either UNTIL DATE or FROM DATE.

CTM554E READ ERROR ON IOA LOG

Explanation: I/O error while reading the IOA Log file. Possible causes are:

• The file allocated to the DALOG DD statement is not the IOA Log.
• The file allocated to the DALOG DD statement is the IOA Log, but it is of a different version.
• A read disk I/O error occurred.

Corrective Action: Check the TSO log of the job for additional messages. If necessary, correct the JCL for the job or the allocations for the CLIST.

CTM555S OID=orderId INSUFFICIENT STORAGE. INCREASE THE REGION SIZE

Explanation: There was insufficient memory to perform a task.

The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.

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

CTM556I TOP OF DATA REACHED

Explanation: This information message indicates that a FIND PREV command did not find another string from the current position to the top of the scrolled data.

Corrective Action: No action is required.

CTM557I BOTTOM OF DATA REACHED

Explanation: This information message indicates that a FIND command did not find another string from the current position to the bottom of the scrolled data.

Corrective Action: No action is required.

CTM558E INTERNAL ERROR - INVALID PARAMETER TO CTMSROL

Explanation: Internal error in IOA scroll routine.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

CTM559I STRING NOT FOUND

Explanation: The string specified in the FIND command is not found in the list at all in the first search from the current position, or the prefix specified in a LOCATE command is not found in the list.

Corrective Action: No action is required.

CTM55AI INVALID SCROLL AMOUNT HAS BEEN ENTERED, CHANGED TO THE PREVIOUS VALUE

Explanation: An invalid value has been entered in the SCROLL field.

Valid values are:

• PAGE - to scroll a full page
• HALF - to scroll a half page
• CRSR - to scroll by cursor position
• MAX - to scroll the maximum amount available

The scroll amount is changed to the last valid value.

Corrective Action: No action is required.

CTM560I PLEASE SPECIFY A VALID FIND STRING

Explanation: A FIND or LOCATE command was specified without a string. The string cannot contain blanks.

Corrective Action: No action is required.

CTM561E INTERNAL ERROR - INVALID RETURN CODE FROM CTMSROL

Explanation: Internal error in IOA scroll routine.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

CTM562E ADD OPTION INVALID FOR NEGATIVE CONDITIONS

Explanation: In screen 3.? (Scheduling Analysis), the A (Add) option is not valid for negative (inverted) conditions. Negative conditions may only be deleted.

Corrective Action: Correct the option and try again.

CTM563E DELETE OPTION ONLY VALID FOR NEGATIVE CONDITIONS

Explanation: In screen 3.? (Scheduling Analysis), the D (Delete) option is only valid for negative (inverted) conditions. Use the A (Add) option for regular conditions.

Corrective Action: Correct the option and try again.

CTM564E READ ERROR ON IOA CONDITIONS FILE

Explanation: Internal error reading the IOA Conditions file.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

CTM566E INVALID OPTION

Explanation: Invalid option specified in the field.

Corrective Action: Correct the option and try again.

CTM567E USER NOT AUTHORIZED

Explanation: The function requested is not authorized for the user. The message is issued by the IOA security mechanism.

Corrective Action: Check with your system security administrator.

CTM567I COND cond ODATE odate {ADDED | DELETED | FOUND} BY USER userId / jobName (jobId)

Explanation: This information message indicates that the ADD, DELETE, or CHECK option completed successfully and the cond condition with the odate original scheduling date was added to or deleted from, or found in the IOA Conditions file.

In this message, odate is the date on which the message is issued. If the ADD, DELETE, or CHECK option is run by the IOACND utility in batch mode, the user ID (userId), job name (jobName), and job ID (jobId) of the batch file are also displayed.

Corrective Action: No action is required.

CTM568E MISSING PARAMETER OF ADD REQUEST

Explanation: The ADD command was supplied without an additional parameter. At least one parameter is expected after the ADD command. The valid parameters are COND, LCOND, CONDITION, CONTROL, or RESOURCE.

Corrective Action: Supply the correct command parameter.

CTM569E INVALID TYPE IN ADD REQUEST

Explanation: Invalid ADD type supplied. At least one parameter is expected after the ADD command. The valid parameters are COND, LCOND, CONDITION, CONTROL, or RESOURCE.

Corrective Action: Specify the requested ADD type.

CTM571E PFK UNDEFINED

Explanation: You have pressed an undefined PFkey.

Corrective Action: Type the SHPF command and press Enter to see the PFkey assignments in the current screen.

CTM572E AMBIGUOUS COMMAND

Explanation: There is more than one command starting with the specified abbreviation. The abbreviated command is too short to identify a specific command. When the cursor is positioned in the COMMAND field, command abbreviations are represented on the Help line by the highlighted letter or letters.

Corrective Action: Specify the correct abbreviation.

CTM573E INVALID DATA ON PFK MEMBER OR COMMAND MEMBER

Explanation: An error occurred in an IOA command or PFK member. The IOA Online facility is controlled by command members and PFKs members. The members are located in the IOA PARM library. Possible causes are:

• The data set allocated to DD statements DACMDLIB, DAPFLIB is not the IOA PARM library.
• Somebody erroneously modified the IOA command (PFK) members of this screen.
• An internal IOA error. This is not likely.

The current screen is locked. No command can be entered.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA online interface, the computer operator will have to cancel the TSO session. To resolve the problem do the following:

1. Correct the allocations of the IOA Allocation Parameter on the IOA PARM library.
2. Ask for help from your INCONTROL administrator, who probably knows what was modified in the command member and how to restore the old copy. For more information, see the INCONTROL for z/OS Installation Guide.
3. Try again. If the problem continues, contact BMC Customer Support.

CTM574E UNRECOGNIZED COMMAND

Explanation: The command that appears in the command window is not a valid command under this screen.

Corrective Action: Type the correct command syntax and press Enter.

CTM575E INVALID PARAMETERS - SCREEN DOES NOT EXIST

Explanation: Internal error in Control-M or Control-D screen or commands management routines. Possible causes are:

• The IOA command member of the screen was incorrectly modified. The reserved areas in the command line description were altered.
• Internal IOA error.

The current screen is locked. No command can be entered.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not escape the IOA Online interface, the computer operator must cancel the TSO session. To resolve the problem, do the following:

1. Restore the original command member. For more information, see the INCONTROL for z/OS Installation Guide.
2. Try again. If the problem continues, contact BMC Customer Support.

CTM576E INVALID COMMAND

Explanation: The command in the command window is not valid for this screen.

Corrective Action: Type the correct command syntax and press Enter.

CTM577E UNABLE TO ACCESS PFK MEMBER

Explanation: The IOA Online facility failed to access the PFK member of this screen. The IOA Online facility is controlled by command members and PFKs members. The members are located in the IOA PARM library. Possible causes are:

• The data set allocated to the DAPF DD statement is not the IOA PARM library.
• Someone erroneously modified the IOA PFK member or members of this screen.
• The PFK member of this screen is not in the library described by the DAPFLIB DD statement. It may have been renamed during local adaptation.
• The REGION size is exhausted, during an open command.
• Internal IOA error.

You will be locked in the current screen without the ability to enter any command.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA online interface, the computer operator will have to cancel the TSO session. To resolve the problem, do the following:

1. Correct the allocations of the IOA Allocation Parameter on the IOA PARM library.
2. Have your INCONTROL administrator look at the PFK member to undo what was modified, or restore the old copy. For more information, see the INCONTROL for z/OS Installation Guide.
3. Restore the member from the original IOA PARM library.
4. Increase the size of your TSO logon procedure. If you work with ISPF and IOA on the same terminal concurrently, we recommend a 2-3MB region size.
5. Try again. If the problem continues, contact BMC Customer Support.

CTM578E UNABLE TO INITIALIZE COMMANDS ENVIRONMENT

Explanation: The IOA Online facility failed to access the command member of this screen. The IOA Online facility is controlled by command members and PFKs members. The members are located in the IOA PARM library. Possible causes are:

• The data set allocated to the DACMD DD statement is not the IOA PARM library.
• Someone has erroneously modified the IOA command member of this screen.
• The command member of this screen does not exist in the library described by the DACMD DD statement. It may have been renamed during local adaptation.
• The REGION size has been exhausted (during an open command).
• Internal IOA error.

The current screen is locked. No command can be entered.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA online interface, the computer operator will have to cancel the TSO session. To resolve the problem, do the following:

1. Correct the allocations of the IOA Allocation Parameter on the IOA PARM library.
2. Check that the product parameters in IOAPARM match the products which are installed.
3. Ask your INCONTROL administrator, who probably knows what was modified, to restore the old copy. For more information, see the INCONTROL for z/OS Installation Guide.
4. Restore the member from the original IOA PARM library.
5. Increase the size of your TSO log on procedure. If you are working with ISPF and IOA on the same terminal concurrently, we recommend 2-3MB region size.
6. Try again. If the problem continues, contact BMC Customer Support.

CTM579E INVALID PARAMETERS TO COMMAND ANALYZER

Explanation: Internal IOA Online facility error.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA Online interface, your computer operator will have to cancel the TSO session.

Try again. If the problem continues, contact BMC Customer Support.

CTM57AE CONTROL-M IS ACTIVE IN COMPATIBILITY MODE, OPTION NOT ALLOWED

Explanation: The Control-M compatibility mode in the IOAPARM is 2 (MODECTM=3). This option is new and requires that Control-M be set to no compatibility mode (MODECTM=3)

The option is disabled.

Corrective Action: No action is required.

CTM580E INVALID RETURN CODE FROM COMMAND ANALYZER

Explanation: Internal IOA Online facility error.

Corrective Action: Press PA1 or RESET at least 20 times. If this does not abort the IOA Online interface, the computer operator will have to cancel the TSO session.

Try again. If the problem continues, contact BMC Customer Support.

CTM581S OPEN OF IOA SYNCHRONIZATION FILE FAILED. DDNAME "DASINC"

Explanation: Open of IOA Conditions Synchronization file failed (DD statement DASINC). Possible causes are:

• The DASINC DD statement is missing.
• The file allocated to the DASINC DD statement is not the IOA Synchronization file.
• The file allocated to the DASINC DD statement Synchronization file, but it is of a different version or of a different Control-M monitor.

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

CTM582S INVALID REQUEST PASSED TO CTMURS ROUTINE

Explanation: The CTMURS IOA internal utility received an invalid request. For example, the CHANGE command was used for an undefined resource.

The requested function is not performed.

Corrective Action: Contact your system programmer. If necessary, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM583S INTERNAL ERROR - INVALID RESOURCE TYPE (CTMURS). NOTIFY THE IOA ADMINISTRATOR

Explanation: Internal error. Invalid resource type passed to the CTMURS IOA internal utility.

The function requested is not performed.

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

CTM584E COND cond ODATE odate DOES NOT EXIST

Explanation: The condition marked for deletion (option D) was already deleted from the IOA Conditions file, while you were working on the screen by another IOA user or IOA monitor.

This message may also be issued when:

• You are not using an enqueue management product or have not specified a QNAME to the enqueue product. An enqueue product synchronizes requests to the IOA Conditions file.
• You enlarged the IOA Conditions file incorrectly. For example, you did not use the IOACCND utility or you failed to update the IOAPARM that indicates that the file was enlarged (CNDREC#).

Corrective Action: Correct the condition that caused the error.

CTM585E AT LEAST ONE OF "CONTROL", "RESOURCE" OR "CONDITION" MUST BE "Y"

Explanation: None of the CONTROL, RESOURCE, or CONDITION options has been marked as Y.

Corrective Action: Mark at least one of the retrieval options as Y.

CTM586S OPEN OF IOA CONDITIONS FILE FAILED. DDNAME "DACNDSF"

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

• The DACNDF DD statement is missing.
• The file allocated to the DACNDF DD statement is not an IOA Conditions file.
• The file allocated to the DACNDF DD statement is the IOA Conditions file, but it is of a different version or of a different IOA Installation.

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

CTM587I COND cond ODATE odate ALREADY EXISTS

Explanation: A condition added using the ADD command already exists in the file.

The addition request is ignored.

Corrective Action: No action is required.

CTM589E CONDITIONS FILE IN USE. PLEASE TRY AGAIN LATER

Explanation: Another user is currently updating the file. The file is momentarily in use by another user or by one of the IOA monitors.

The command requested is not performed.

Corrective Action: Try again.

CTM590E PLEASE SPECIFY CONDITION/RESOURCE NAME

Explanation: Missing condition or resource name in ADD command window.

Corrective Action: Specify the missing condition or resource name.

CTM591I PLEASE USE THE "ADD" COMMAND

Explanation: An A line command has been specified for a condition or resource name. Only an ADD primary command can be used to add a condition or resource.

Corrective Action: Use the ADD command in the commands window.

CTM592E ONLY ONE OPTION AT A TIME

Explanation: More than one option has been specified. Only one option is allowed for each Enter.

Corrective Action: Select only one option.

CTM593E INVALID OPTION. SPECIFY EITHER "Y" OR "N"

Explanation: Invalid retrieval criteria option. The valid options are either Y for Yes, or N for No.

Corrective Action: Select Y or N.

CTM594E ONLY TRAILING BLANKS ALLOWED

Explanation: The condition or resource name contains embedded blanks. A condition or resource name cannot contain embedded blanks.

Corrective Action: Correct the condition or resource name.

CTM595E UNEXPECTED RETURN CODE FROM CTMURS. SEE MESSAGES AND CODES

Explanation: Internal error. Invalid return code from the CTMURS IOA internal utility.

The function requested is not performed.

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

CTM596E ADD OF COND cond ODATE odate FAILED. FILE IS FULL

Explanation: Highlighted, unrollable message.

The Conditions file is full.

The condition is not added to the file.

Corrective Action: Try to manually delete conditions from the specified day of the odate, but in other months. If you need all the conditions in the file, ask your system programmer to increase the capacity of the IOA Conditions file. Also, run the IOACLCND utility periodically to erase unnecessary conditions from the Conditions file and prevent the problem.

CTM597E INVALID CONTROL-TYPE. USE "E" - EXCLUSIVE OR "S" - SHARED

Explanation: Invalid control type specified in the ADD Control-command window. A control type should be E for exclusive or S for shared.

Corrective Action: Correct the control type field.

CTM598I CONTROL-RESOURCE resourceName ALREADY EXISTS

Explanation: A control resource being added by means of the ADD command already exists in the file.

The addition request is ignored.

Corrective Action: No action is required.

CTM599E ADD OF CONTROL-RESOURCE resourceName FAILED. FILE IS FULL

Explanation: Highlighted, unrollable message.

The Control-M Resources file is full.

The control resource is not added to the file.

Corrective Action: Consult your system programmer about the possibility of increasing the capacity of Control-M Resources file. It is not clear to us why a user would want to add a control resource. Call BMC Customer Support for advice.

CTM5A1E OPEN OF CONTROL-M STATISTICS FILE FAILED. RC=VSAM_return_code ERROR=VSAM_reason_code

Explanation: Error when trying to open the Control-M Statistics File for updating the Jobs Counting data. If the Control-M Statistics File was already successfully opened previously, then the error is considered as recoverable and Control-M tries to later update the Jobs Counting data. However, if it was the first attempt to open the Control-M Statistics File, then the error is considered as unrecoverable and Jobs Counting Facility is terminated (message CTM5A3E issued).

Corrective Action: If the message is issued frequently or the message CTM5A3E is also issued (Jobs Counting Facility is terminated) then contact IOA Technical support.

CTM5A2E ERROR IN operation JOB ACCOUNTING RECORD. RC=VSAM_return_code ERROR=VSAM_reason_code

Explanation: Error when trying to process the Jobs Counting Record (in the Control-M Statistics File) for accessing/updating the Jobs Counting data. The Jobs Counting Facility is terminated, the message CTM5A3E is issued.

Corrective Action: Contact IOA Technical support.

CTM5A3E JOB ACCOUNTING FACILITY TERMINATED

Explanation: The Jobs Counting Facility is terminated as the result of an error in accessing the Control-M Statistics File or the Jobs Counting Record in that file. It is preceded by the CTM5A1E or CTM5A2E message.

Corrective Action: Contact IOA Technical support.

CTM5A4W JOB ACCOUNTING RECORD NOT FOUND

Explanation: The message is issued by the Jobs Counting Report Utility when it detects that the Jobs Counting Record (which would contain the Jobs Counting Data) does not exist in the Control-M Statistics File. Usually it means that the Jobs Counting Facility was not activated or it was terminated and the corresponding error messages (CTM5A1E / CTM5A2E / CTM5A3E) will be issued by Control-M Monitor.

Corrective Action: Check the job log of Control-M Monitor and contact IOA Technical support.

CTM5A5W JOB ACCOUNTING RECORD IS EMPTY

Explanation: The message is issued by the Jobs Counting Report Utility when it detects that the Jobs Counting Record (which would contain the Jobs Counting Data) is empty. Usually it means that the Jobs Counting Facility was not activated or it was terminated and the corresponding error messages (CTM5A1E / CTM5A2E / CTM5A3E) will be issued by Control-M Monitor.

Corrective Action: Check the job log of Control-M Monitor and contact IOA Technical support.

CTM5B1I RECOVERY PROCEDURE INVOKED TO PREVENT DUPLICATE JOB PROCESSING

Explanation: During the start of Control-M monitor, it was detected that the previous monitor execution terminated abnormally and there are jobs whose processing might cause duplicate submissions or DO FORCEJOB execution. The Recovery Mode processing is invoked. It will scan the IOA LOG, extract information regarding the jobs whose statuses are ambiguous and set their statuses appropriately. In a CTMPLEX environment, this message can be issued not only during the start of Control-M monitor, but it can also be issued by the Global monitor if it detects a Coupling Facility failure or the abnormal termination of any Local monitor. The message can be also issued by a Local monitor when it switches to Global as a result of an abnormal termination of the previous Global.

For a general description about the Control-M Recovery Facility, see the Recovery Tools sub-section in Chapter 3, Control-M, in the INCONTROL for z/OS Administrator Guide. For more information about the installation parameters, RECENA and RECLEVEL, which control the Recovery Mode processing, see Chapter 2, Customizing Control-M, in the INCONTROL for z/OS Installation Guide: Customizing.

Corrective Action: Check the following messages issued by the Recovery Mode processing. Some messages indicate customer analysis and manual intervention might be required.

CTM5B2I JOB member_name / Order_ID PUT IN SUBMITTED STATUS BY RECOVERY PROCEDURE

Explanation: The Control-M Recovery processing analyzed the job in WAIT SUBMISSION status to prevent duplicate job submission. As a result of the analysis of the IOA LOG, the procedure detected that the job has already been submitted (before the Control-M abnormal termination) and extracted its JOBNAME and JOBID from the IOA LOG. The job is automatically put into SUBMITTED status so that Control-M can continue tracking and performing the regular Post Processing when the job finishes.

For a general description about the Control-M Recovery Facility, see the Recovery Tools sub-section in Chapter 3, Control-M, in the INCONTROL for z/OS Administrator Guide. For more information about the installation parameters, RECENA and RECLEVEL, which control the Recovery Mode processing, see Chapter 2, Customizing Control-M, in the INCONTROL for z/OS Installation Guide: Customizing.

Corrective Action: No user action required.

CTM5B3W JOB member_name / Order_ID PUT IN HOLD BY RECOVERY PROCEDURE TO PREVENT DUPLICATE action

Explanation: Control-M Recovery processing placed the job into HOLD status because it detected the possibility of duplicate submission or DO FORCEJOB execution and the analysis of the IOA LOG did not determine the job status at the moment of the Control-M abnormal termination. 'action' can either be 'SUBMISSION' or 'FORCEJOB'.

For a general description about the Control-M Recovery Facility, see the Recovery Tools sub-section in Chapter 3, Control-M, in the INCONTROL for z/OS Administrator Guide. For more information about the installation parameters, RECENA and RECLEVEL, which control the Recovery Mode processing, see Chapter 2, Customizing Control-M, in the INCONTROL for z/OS Installation Guide: Customizing.

Corrective Action: Check the actual status of the indicated job. If the job was not submitted or no DO FORCEJOB executed before the Control-M abnormal termination, then FREE the job so that Control-M can submit the job or execute its DO FORCEJOB.

If the job was already submitted or at least some of its DO FORCEJOB were already executed before the Control-M abnormal termination, more detailed analysis and manual actions are required. Check the results of the job execution (for the job put into HOLD to prevent duplicate submission) or check the DO FORCEJOB executed (for the job put into HOLD to prevent duplicate DO FORCEJOB). The customer might then have to manually make up the Post Processing actions according to the jobs execution results (for example, adding OUT CONDITIONS). In some situations the Force OK request might be applicable here.

CTM5B4W number JOBS PUT IN HOLD STATUS BY RECOVERY PROCEDURE TO PREVENT DUPLICATE ACTIONS

Explanation: Control-M Recovery processing placed number jobs into HOLD status because it detected the possibility of their duplicate submission or DO FORCEJOB execution and the analysis of the IOA LOG did not determine the job statuses at the moment of the Control-M abnormal termination. The CTM5B3W messages, which were issued before CTM5B4W, indicate the jobs put into HOLD statuses.

For a general description about the Control-M Recovery Facility, see the Recovery Tools sub-section in Chapter 3, Control-M, in the INCONTROL for z/OS Administrator Guide. For more information about the installation parameters, RECENA and RECLEVEL, which control the Recovery Mode processing, see Chapter 2, Customizing Control-M, in the INCONTROL for z/OS Installation Guide: Customizing.

Corrective Action: Analyze the previous CTM5B3W messages and handle the jobs listed by these messages as explained in the User Action part for CTM5B3W.

CTM5B6E ERROR IN LOG FILE DURING RECOVERY PROCEDURE

Explanation: During the Control-M recovery procedure, Control-M recovery could not open the IOA log file and extract the needed information.

Corrective Action: Check the IOA Log file and fix the issue.

CTM5C5I JOB job_member_name IS RECYCLED WITH CYCLIC SMART TABLE Table_Name RECYCLE

Explanation: The job belongs to a Cyclic SMART Table. When the Cyclic SMART Table is recycled for possible re-execution, all of its jobs (excluding ones in HELD or DELETED statuses) are recycled.

Corrective Action: No action is required.

CTM5C6I PERFORMING CONDITION ADJUSTMENT TO ALLOW CYCLIC SMART TABLE Table_Name RECYCLE

Explanation: The recycling processing of Cyclic SMART Tables includes the Internal Smart Table Conditions cleanup, which guarantees the correct order of execution of the SMART Table jobs. This message is followed by the SEL250I message, which contains the name of the Conditions deleted.

Corrective Action: No action is required.

CTM5C7I TABLE IS MARKED TO BE COMPLETED BY JOB jobName (orderId)

Explanation: This message is issued to the Smart Table’s log, indicating that it was completed by the job’s ‘End Table’ Post Processing parameter.

Corrective Action: No action is required.

CTM5C8I END-TABLE PERFORMED. TABLE tableName (orderId) IS MARKED TO BE COMPLETED

Explanation: This message is issued to the log of the job that marked the specified Smart Table as ‘To be Completed’ as a result of processing the job’s ‘End Table’ parameter.

Corrective Action: No action is required.

CTM5CAI TABLE TableName (OrderId) IS MARKED TO BE COMPLETED BY AJF COMPRESS

Explanation: Control-M New Day processing or AJF Compress forced Smart Table completion because the MAXWAIT of all its jobs (and the Smart Table itself) had expired. For additional information, see the description of Control-M Installation parameter FRMAXWT in the INCONTROL for z/OS Installation Guide: Customizing.

Corrective Action: No action is required.