Messages JOB500 through JOB5xx

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.

JOB501I CTMJOB STARTED JOB=username/jobID TYPE=jobType

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.

JOB502S 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 record length is not 80.

The CTMJOB program will end with errors.

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

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

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

JOB505S 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 will end 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. We recommend 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, we recommend requesting the remaining jobs manually using CLIST CTMJOBRQ.

JOB506S 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 the memName member is not placed in the Active Jobs file. Depending on the severity of the problem, the New Day procedure will continue to the next job order or terminate with the condition code 08.

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

JOB507S 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 (the DACHK DD statement).

For more details refer to 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).

JOB508S 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 refer to 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).

JOB50BS ERROR READING SCHEDULE DATA. DDNAME DAJOB. ERROR TYPE IS error_type

Explanation: You invoked a Daily job (either System or User) that has a concatenation of Control-M Definition Tables in DAJOB input DD statements. When accessing one of the DD statements in this concatenation, a problem occurred — either an ABEND (error type ABEND) or an Input/Output error (error type IO ERROR). This message is usually followed with z/OS system messages that contain additional information about the ABEND or Input/Output error.

The Daily job terminates with an error. Jobs from the tables in the DAJOB DD statements prior to the problematic one are processed. All remaining DAJOB DD statements are not processed.

Corrective Action: Analyze the ABEND or Input/Output error data, perform the required corrections, and try to rerun the Daily job to order the remaining jobs. If an Enhanced Checkpoint Date Record is used, the Daily job will automatically start from the point where it stopped in the previous run. If an Enhanced Checkpoint Date Record is not used, then before the Daily job rerun, the tables that have already been processed (that is, DD statements prior to the problematic one in the DAJOB concatenation) should be temporary commented or removed from the Daily job JCL.

JOB50CE Additional_Input/Output_error_data

Explanation: This message contains additional information about an Input/Output error, in SYNADAF data format. It follows the JOB50BS message when the error type is IO ERROR. See the description of message JOB50BS.

Corrective Action: See message JOB50BS.

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

Explanation: Severe error in the scheduling data.

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

• The contents of a 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 JOB505S for further details.

JOB511I OID=orderId ODATE odate TASK=owner / systemId / jobName PLACED ON AJF

Explanation: This information message indicates that the job order was placed successfully in the Active Jobs file (AJF).

The task is now in the Active Jobs file in Wait Schedule state.

The following variable TASK fields are displayed:

• owner - the security user ID under which the ordering job that issued the JOB511I message was run
• systemId - the system ID of the ordering job
• jobName - the job name of the ordering job

Corrective Action: No action is required.

JOB512W LIBRARY lib SHOULD BE COMPRESSED

Explanation: The library specified in the PDS parameter contains fewer free tracks than the number specified in the MINIMUM parameter.

The PDS and MINIMUM parameters are used for automatically compressing a library. If the MINIMUM condition is satisfied, then the CTMJOB program will issue this message and the job order will be placed in the Active Jobs file.

For more details, refer to the Control-M chapter of the Control-M for z/OS User Guide.

The job order will be placed in the Active Jobs file.

Corrective Action: No action is required.

JOB513I SCHEDULE FAILED FOR number CONTROL-D CATEGORIES

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

The Control-M New Day procedure continued processing.

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

JOB514S INSUFFICIENT STORAGE FOR THE JOB

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

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

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

Explanation: There is invalid scheduling data in the first data set described by the DAJOB DD statement.

The first statement of a valid scheduling table should start with D. This could be due to one of the following:

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

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

JOB518S INVALID YEAR IN USER DATE CONTROL RECORD

Explanation: There is an 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).

JOB519S 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 formats are:

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

JOB520S OPEN OF IOA LOG FILE FAILED

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

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

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

The New Day procedure ends with errors.

Corrective Action: Do the following:

1. Look for additional messages that will help identify the problem.
2. Correct the JCL or the CLIST.
3. Rerun the job.

JOB522S 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). This error message is issued by the CTMJOB program which is usually activated as part of the New Day procedure.

Valid formats are:

• ddmmyy
• mmddyy

The message may be due to one of the following:

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

JOB523S 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 error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

This date (date-2 of User Date Control Record) should be equal to date-3 (positions 24-29) or in valid format.

Valid formats are:

• ddmmyy
• mmddyy

The message may be due to one of the following:

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

JOB524S CTMJOB ENDED WITH ERRORS

Explanation: The CTMJOB program ended with errors. It is activated as part of the New Day procedure.

The IOA Log should contain prior messages concerning the errors.

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

Corrective Action: Check the IOA Log for the errors. If necessary, correct the Date Control Record (date-3 and date-5) manually to allow the next run of the New Day procedure. If you cannot find any prior error messages in the IOA log or job log, ensure that the Control-M Job Scheduling library is not being compressed simultaneously with any job ordering.

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

JOB525I CTMJOB ENDED JOB=username/jobID TYPE=jobType

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.

JOB526S **** ERROR IN SCHEDULING DATA FORMAT ****

Explanation: The scheduling table has been corrupted. Scheduling data do not conform to Control-M valid format.

This message is followed by a number of JOB527 messages which describe all the statements that belong to the damaged job order. The asterisk (*) appears in the line under the erroneous data.

The CTMJOB will terminate with a condition code of 08.

Corrective Action: If you cannot restore the table to its original state, have your system programmer call BMC Customer Support for assistance.

If it is a batch Daily using a permanent Date Control Record, correct the contents of the record before running the Daily again. For considerations, please see message JOB505S.

JOB527S CARD = stmt

Explanation: The scheduling table has been corrupted.

This message follows message JOB526, and displays each statement in the damaged job order in the scheduling table. An asterisk (*) appears in the line under a damaged statement.

The CTMJOB program ends with errors.

Corrective Action: If you cannot restore the table to its original state, have your system programmer call 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. For considerations, please see message JOB505S.

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

Explanation: This information message is a standard message indicating that a job order has been 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.

JOB529S 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. The message may be due to one of the following:

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

JOB530S 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, refer to 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.

JOB531W MEMBER memName ODATE odate - SCHEDULING CANCELLED BY USER EXIT

Explanation: Scheduling cancelled by user exit CTMX001; the memName member did not pass user checking.

User exit CTMX001 is activated for each job order before it is placed on the Active Jobs file. The exit can specify to 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 will not be placed on the Active Jobs file.

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

JOB532S 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 or CLIST and rerun it.

JOB534S SEVERE ERROR ON CONTROL-M ACTIVE JOBS FILE

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

This could be due to one of the following:

• An I/O error, or 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 will end 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.

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

JOB536S SEVERE ERROR IN SCHEDULING DATA CARDS

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

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

JOB538E taskType memName OID=orderId ODATE odate SCHEDULING FAILED

Explanation: Scheduling failed. 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 output of the job should contain prior message concerning the reason for failure.

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

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

JOB539W taskType memName ODATE odate SCHEDULING CANCELLED BY USER EXIT userExit

Explanation: An unauthorized user attempted to send a job to the AJF.

The job order will not be placed on the Active Jobs file.

Corrective Action: Do the following:

1. Check your authorization.
2. The next step depends on how the job is being ordered, as follows:
   • If the job is being ordered online, log off and log on again.
   • If the job is being ordered by the Control-M monitor, restart the monitor.
   • If the job is being ordered by the New Day procedure, rerun the New Day procedure.
3. Look in the IOA Log for additional messages that clarify the reason for the job being cancelled. If there is no such message, check the userExit user exit.

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

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

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

JOB541I JOB PLACED ON ACTIVE JOBS FILE AT RBA: rba

Explanation: This information message indicates that a job has been successfully placed in the Active Jobs file, and displays the job’s rba.

Corrective Action: No action is required.

JOB54AE RESOLVED CONDITION NAME '%%COND_VAR' IS TOO LONG,ORDER FAILED.

Explanation: This error message indicates that the job order failed because the AutoEdit condition variable contains more than 40 characters.

Corrective Action: Ensure that the AutoEdit condition variable contains 40 characters or less.

JOB54BE RESOLVED CONDITION NAME '%%COND_VAR' CONTAINS BLANKS,ORDER FAILED.

Explanation: This error message indicates that the job order failed because the AutoEdit condition variable contains spaces.

Corrective Action: Ensure that the AutoEdit condition variable does not contain any spaces.

JOB547W TABLE TblName IS NOT A SMART TABLE. RBC STATEMENT IGNORED

Explanation: The SELECT or IGNORE RBC statement refers to a job which is not part of a SMART Table.

SELECT and IGNORE RBCs always follow an ORDER statement for a SMART Table. They are meaningless for a job which is not part of a SMART Table.

The SELECT or IGNORE RBC statement is ignored. The job is ordered.

Corrective Action: No response needed.

JOB548E OID=orderId SEVERE ERROR IN CALENDAR calName OR YEAR NOT FOUND IN CALENDAR

Explanation: Severe error in the calName IOA calendar, or the year not found in the 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.

JOB549W CONTROL-M/RESTART NOT AVAILABLE. IFRERUN ACTION IGNORED FOR MEMBER memName

Explanation: The scheduling table contains the IFRERUN definition, but Control-M was unable to act on this definition.

The probable cause is that CTR is set to N in IOAPARM, the IOA installation parameters member.

The scheduling table is ordered without the IFRERUN definition.

Corrective Action: Ensure that CTR is set to Y in IOAPARM.

JOB550W CONTROL-M/RESTART NOT AVAILABLE. SET ACTION IGNORED FOR MEMBER memName

Explanation: The scheduling table contains the SET definition, but Control-M was unable to act on this definition.

The probable cause is that CTR is set to N in IOAPARM, the IOA installation parameters member.

The scheduling table is ordered without the SET definition.

Corrective Action: Ensure that CTR is set to Y in IOAPARM.

JOB551S LOAD OF CTMPARM FAILED IN CTMRSG GROUP PROCESSING

Explanation: During group order processing the Control-M configuration parameters could not be accessed.

The program aborts the order processing.

Corrective Action: Contact your INCONTROL administrator who should verify that the CTMPARM member exists in the installation library.

JOB552S GETMAIN FAILED IN CTMRSG GROUP PROCESSING

Explanation: The CTMRSG program could not allocate storage.

Group processing is terminated.

Corrective Action: Increase the region size.

JOB553S AJF (CKP) FILE OPEN FAILED IN CTMRSG GROUP PROCESSING

Explanation: During Group Order processing, the CTMRSG program was unable to open the Active Jobs File (AJF).

Group Order processing terminates.

Corrective Action: Correct the AJF file problem, and order the group again.

JOB554I INPUT CONDITION REMOVED: CONDITION=cond, MEMBER=memName, GROUP=grp

Explanation: This information message is issued during group order processing, when Control-M determined that in a certain group, an output condition of a member that was not scheduled, is an input condition for a member that was scheduled.

The input condition is removed as a prerequisite for job execution.

Corrective Action: No action is required.

JOB555I MEMBER memName SCHEDULING FORCED BY USER EXIT

Explanation: This information message indicates that the memName member was ordered due to a user exit decision.

This message is only issued when user exit CTMX001 is called before normal Control-M scheduling logic has been performed, or when CTMX001 overrides a Control-M scheduling decision not to order the job. This message can appear only after optional installation feature WM2603 has been enabled.

Corrective Action: No action is required.

JOB556W MEMBER memName- INVALID RETURN CODE FROM USER EXIT IGNORED. PRESUMED TO BE 0

Explanation: User exit CTMX001 returned an invalid return code.

Control-M continues as if the user exit had not been called.

Corrective Action: Contact your INCONTROL administrator to correct user exit CTMX001.

JOB557W OID=orderId SCHEDULING FORCED BY USER EXIT

Explanation: A member was ordered as a result of a user exit decision. This message is issued when user exit CTMX001 is called before normal Control-M scheduling logic has been performed, or when CTMX001 overrides a Control-M scheduling decision not to order the job. This message can appear only after optional installation feature WM2603 has been enabled.

Corrective Action: No action is required.

JOB558W OID=orderId ILLEGAL RETURN CODE FROM USER EXIT IGNORED

Explanation: User exit CTMX001 returned an invalid return code.

Control-M continues as if the user exit had not been called.

Corrective Action: Contact your INCONTROL administrator to correct user exit CTMX001.