2.7.1 Troubleshooting problems related to the registration of jobs and jobnets for execution
If an error occurs during registration for execution, the following schedule rules might be specified for the root jobnet. Do not specify these schedule rules.
-
A past date is specified as a start date, and no processing cycle is set in the schedule rule.
-
An invalid date (for example, 2/30) is specified as a start date in the schedule rule.
-
A closed day is specified as a start date in the schedule rule, but no closed day is specified in the calendar definition to be used.
-
A closed day is specified as a start date in the schedule rule, but Do not execute is specified as the substitute schedule method for closed day jobs.
-
Do not execute is specified as the substitute schedule method for closed day jobs in the schedule rule, but closed days are specified in all the calendar definitions to be used.
-
The same schedule rule as that for a jobnet specified in the exclusive schedule is set. (All planned executions must be in the exclusive schedule.)
-
A definition that disables calculation of the same execution date from the schedule rule number that corresponds to a schedule rule number of an upper level jobnet is created.
-
If an invalid unit, such as one that does not exist, is specified in a job group or exclusive schedule that references the calendar, the status of the jobnet becomes shutdown status.
-
For a schedule that is planned to be executed soon, the schedule is changed dynamically according to the status and time so that the planned execution might not be carried out as scheduled.
If any of the above schedules is set in a nested jobnet, the jobnet is handled as Not sched. to exec., and execution does not occur until the status is temporarily changed.