Previous Topic

Next Topic

Book Contents

Book Index

Messages JOBD00 through JOBDxx

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.

JOBD65E JOB jobName OID=orderId ODATE odate BYPASSED DUE TO MISSING PREV/NEXT DATES - descr

Explanation: The job was not scheduled by Control-M because the requested previous or next original scheduling date (ODAT), could not be calculated.

The job to be scheduled contains IN and/or OUT conditions with ODAT PREV or ODAT NEXT. However these dates could not be calculated by Control-M, possibly because the calendar for the previous or next year is missing.

The job is not scheduled. Processing continues with the next job.

Corrective Action: Correct the situation and then reschedule the job manually.

JOBD66E MEMBER memName ODATE odate BYPASSED DUE TO MISSING PREV/NEXT DATES - descr

Explanation: The member was not scheduled by Control-M because the requested previous or next original scheduling date (ODAT) could not be calculated.

The member to be scheduled contains IN and/or OUT conditions with ODAT PREV or ODAT NEXT. However, these dates could not be calculated by Control-M, possibly because the calendar for the previous or next year is missing.

The member is not scheduled. Processing continues with the next member.

Corrective Action: Correct the situation and then reschedule member manually.

JOBD67S ORDERING CHECKPOINT RECORD IS INVALID FOR THIS DAILY

Explanation: The Ordering Checkpoint Record contains recovery information which is invalid for this Daily run.

The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains data specifying recovery for the CTMJOB program, but these data are incorrect for the jobs that were ordered in this run of CTMJOB.

The CTMJOB program ends with errors.

Corrective Action: Either run CTMJOB with the same data (ordered jobs) as were in the last (abending) run, or blank out the values of the keywords in the Ordering Checkpoint Record, and run CTMJOB without recovery.

JOBD68S STRUCTURE OF ORDERING CHECKPOINT RECORD IS INVALID

Explanation: The Ordering Checkpoint Record contains invalid keywords, or valid keywords in invalid offsets. The Ordering Checkpoint Record, which is in the same member as the User Date Control Record, contains keywords in an unexpected structure.

The CTMJOB program ends with errors.

Corrective Action: Either correct the Ordering Checkpoint Record, or delete the Ordering Checkpoint Record, and run CTMJOB without recovery.

JOBD69I NO JOBS WERE SCHEDULED DURING SCHEDULING REQUEST

Explanation: This information message indicates that no jobs matched the ordering criteria during a scheduling request. This message is issued after the scheduling request has been processed, and no jobs were ordered.

Corrective Action: If you think a job should have been ordered in this scheduling request, check and correct the scheduling parameters as required, and rerun the scheduling request.

JOBD6AI RETRO SCHEDULING BYPASSED FOR JOBS WITHIN GROUP

Explanation: This information message indicates that Y was specified in the RETRO field in a group entity or in one of the group jobs. RETRO processing is not supported in GROUPS. Setting RETRO to Y in a group can cause jobs to be scheduled on inappropriate ODATES.

The RETRO field is ignored in group processing.

Corrective Action: Set the RETRO field to N and retry.

JOBD6BI NUMBER OF JOBS ORDERED - jobsnum

Explanation: This information message indicates the number of jobs ordered by the present invocation of CTMJOB.

Corrective Action: No action is required.

JOBD90E RECOVERY RECORD INCOMPATIBLE WITH DATE RECORD

Explanation: The Date Control Record indicates that recovery is not necessary, but the recovery record, that is, the second record of the Date Control Record member used for Enhanced Daily Checkpointing, indicates that recovery is needed.

This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure. In the Date Control Record, date-2 (columns 18-23) is equal to date-3 (columns 25-30) and date-4 (columns 43-48) is equal to date-5 (columns 50-55). However, the recovery record contains non-blank values for the recovery parameters.

For more details, please refer to the description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.

The program terminates with a condition code of 08.

Corrective Action: If recovery is required, set date-3 to the day before date-2, and date-5 to the day before date-4. If recovery is not required, replace the values in the recovery record with blanks.

JOBD91E INVALID PREVIOUS MONTHLY SCHEDULING DATE IN USER DATE CONTROL RECORD (POSITIONS 25-30)

Explanation: Invalid previous monthly scheduling date in the User Daily Date Control Record date-3 (columns 25-30). This error message is issued by the CTMJOB program, which is usually activated as part of the New Day procedure.

Valid formats for the date are:

Possible causes are:

For more details please refer to description of the Date Control Record in the INCONTROL for z/OS Administrator Guide.

The program terminates with a condition code of 08.

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

Parent Topic

JOB messages