Diagnosis
A periodic job was terminated because it could not schedule a new datein its factory calendar. The calendar is assigned to the job duringscheduling.
Possible causes of the problem:
RESET N1
The calendar does not contain any days (workdays) that allow the job tobe executed. The calendar is probably not correctly defined.
Example: The calendar does not contain any workdays (it only consistsof non-workdays).
This might then be the cause if the job was scheduled with the options'on workdays only' and 'omit job'.
A periodic job, which is scheduled for a particular workday in themonth (e.g. 3rd workday), cannot find a date in the current calendar.This is another case in which the calendar is probably not correctlydefined.
Example: The calendar ends with the end of the current year, and theperiodic job is next due to start in the next year.
The factory calendar could not be found or could not be loaded. Checkwhether the calendar is defined.
If the calendar does exist, you should check whether the calendarbuffer is large enough or whether there are other storage spaceproblems.
For more information on the calendar buffer, refer to the documentationfor profile parameters zcsa/calendar_ids andzcsa/calendar_area in the profile maintenance function and inthe Customizing system (Customizing IMG, Basis section).
IF DEVICE='SCREEN'
Parameter documentation
ENDIF

System Response
The scheduler flags this job as terminated. No job step in this job wasexecuted.
The job chain to which this job belongs is also terminated. Automaticscheduling of this job is not continued.
This message, along with other messages, are entered in the log of thisjob in order to point out this problem. Additional messages shouldindicate why scheduling failed.
Previous runs of this job are not affected by this termination, but thejob cannot be scheduled periodically until the problem with thecalendar has been eliminated.
For consistency reasons, the system also displays a date and time forthis job in the job log. These are values for the scheduling period andnot the execution time. It is the time when the system determined thatthe new job cannot run.
Caution:

• The time is almost identical to the date of the last periodic job in
the chain to be correctly processed.

• It is possible that this predecessor is not yet finished but is still
active.

Procedure
Check whether the calendar (calendar ID) still exists, whether itsvalues are correct and whether the start restriction for your job iscorrectly set.
Perhaps your calendar is simply too short.
When you have solved the problem with the calendar (or eliminated thecause, if different), you must reschedule the periodic job so that itcan be automatically scheduled again after your period entries. Thebackground processing system cannot recommence periodic scheduling onits own.
To reschedule the job, select menu options Tools ->Administration -> Jobs -> Job overview. Displaythe job in the overview and then select Job -> Scheduling-> Repeat.