8.3.4 Release timing
A jobnet definition is switched at the specified release time, irrespective of the schedule rules for the release-target jobnet. The release time is specified as an absolute time in 24-hour schedule. As a result, if the release-target jobnet runs in 48-hour schedule, for example, you must specify the release time after considering conversion to 48-hour schedule.
Note that the definition of a generation that started before the release time will not be switched if the release time has passed during execution.
- Organization of this subsection
(1) Release timing when using a 48-hour schedule
If the scheduler service uses a 48-hour schedule, the jobnet definition is released at the release time in absolute-time format. The following figure shows an example of release in the 48-hour schedule.
|
This example assumes that the jobnet is executed every day at 26:00 (48-hour schedule).
The execution schedule for 26:00 on March 31 in 48-hour schedule equals 2:00 on April 1 in absolute time, which is earlier than the release time of 00:00 on April 2. As a result, the jobnet is executed with the definition that has the release ID AJS_AUTO. The execution schedule for 26:00 on April 1 in 48-hour schedule equals 2:00 on April 2 in absolute time, which is later than the release time of 00:00 on April 2. As a result, the jobnet is executed with the definition that has the release ID 001.
Therefore, if you want to use the definition that has the release ID AJS_AUTO to execute a jobnet scheduled for execution at 26:00 on April 1, you need to set a release time of 2:01 or later on April 2.
(2) Release timing when a base time is set
If a base time (other than 00:00) is set, the jobnet definition is also released at the release time in absolute time. The following figure shows an example of release when a base time is set.
|
This example assumes that the base time is 9:00 and that the jobnet is executed every day at the relative time of 15:00.
The execution schedule of 15:00 on March 31 is a relative time in relation to the base time of 9:00. This execution schedule is 00:00 on April 1 in absolute time, which is earlier than the release time of 00:00 on April 2. As a result, the jobnet is executed with the definition that has the release ID AJS_AUTO. Similarly, the execution schedule of 15:00 on April 1 equals 00:00 on April 2 in absolute time, which is the same time as the release time of 00:00 on April 2. As a result, the jobnet is executed with the definition that has the release ID 001.
Therefore, if you want to use the definition that has the release ID AJS_AUTO to execute a jobnet scheduled for execution at 15:00 on April 1, you need to set the release time to 00:01 or later on April 2.
(3) Release timing when a jobnet is executed more than once a day
If the schedule rules are set so that a jobnet is executed more once a day, the jobnet definition is released at a release time in absolute time. The following figure shows an example of release when the schedule rules are set for executing the jobnet more than once a day.
|
This example assumes that the jobnet is executed every day at 0:00 and 26:00.
For the execution schedules up to 9:00 on April 1, which is earlier than the release time of 00:00 on April 2, the jobnet is executed with the definition that has the release ID AJS_AUTO. The execution schedule of 26:00 on April 1 equals 2:00 on April 2 in absolute time, which is later than the release time of 00:00 on April 2. As a result, the jobnet is executed with the definition that has the release ID 001.
However, if you want to execute a jobnet with the definition that has the release ID AJS_AUTO at 26:00 on April 1, but with the definition that has the release ID 001 on April 2 or later, you will need to set the release time in the range from 2:01 to 8:59 on April 2.
(4) Release timing when a substitute schedule for a closed day job is set
The following describes release when Execute on next open day or Execute on previous open day is set for Substitute schedule of closed day job.
(a) Release timing when "Execute on next open day" is set
If Execute on next open day is set for Substitute schedule of closed day job, the jobnet definition is released at the release time in absolute time. The following figure shows an example of release when Execute on next open day is set.
|
This example assumes that April 1 is a closed day and that April 2 is an open day.
Because April 1 is a closed day, the execution schedule for 16:00 on April 1 is shifted to 16:00 on April 2. Because 16:00 on April 2 is later than the release time of 00:00 on April 2, the jobnet is executed with the definition that has the release ID 001.
Therefore, if you want to use the definition that has the release ID AJS_AUTO to execute a jobnet at 16:00 on April 2, which is the execution schedule after shifting, you need to set the release time to 16:01 or later on April 2.
(b) Release timing when "Execute on previous open day" is set
If Execute on previous open day is set for Substitute schedule of closed day job, the jobnet definition is released at the release time in absolute time. The following figure shows an example of release when Execute on previous open day is set.
|
This example assumes that April 1 is an open day and that April 2 is a closed day.
Because April 2 is a closed day, the execution schedule for 16:00 on April 2 is shifted to 16:00 on April 1. Because 16:00 on April 1 is earlier than the release time of 00:00 on April 2, the jobnet is executed with the definition that has the release ID AJS_AUTO.
Therefore, if you want to use the definition that has the release ID 001 to execute a jobnet at 16:00 on April 1, which is the execution schedule after shifting, you need to set a release time that is earlier than 16:00 on April 1.
(5) Release timing when a start condition is set
If a start condition is set, the jobnet definition is released at the release time in absolute time. The following figure shows an example of release when a start condition is set.
|
In this example, the release time falls between two monitoring periods. In this case, the jobnet definition is switched at the release time.
However, if monitoring is still in progress at the release time as shown in the following figure, the jobnet definition is not switched.
|
As shown above, if monitoring has not stopped when the release time arrives, the release-target jobnet is executed with the definition that has the release ID AJS_AUTO. The definition that has the release ID 001 will be executed after the next monitoring period starts. Therefore, if you want to use the definition that has the release ID 001 for execution of the jobnet being executed at the release time, you need to kill the monitoring.
(6) Release timing when a schedule rule differs before and after release
If a schedule rule differs before and after release, the jobnet definition and schedule rule are released at the release time in absolute time. The following figure shows an example of release when the schedule rule is different before and after release.
|
This example assumes that a jobnet executed every day at 00:00 is to be executed every day at 15:00 after the release time arrives. Because 00:00 on April 1 is later than the release time of 00:00 on April 2, the jobnet is executed at 00:00 on April 1 according to the schedule rule in effect for release ID AJS_AUTO. At the release time of 00:00 on April 2, the definition that has the release ID 001 is released, and starting that day, the job is executed at 15:00 instead of 0:00.
However, if you want to use the schedule rule in effect for release ID AJS_AUTO to execute a jobnet on April 2 by setting a scheduled start time of 00:00 on April 2, you will need to specify the release time in the range from 15:01 on April 2 to 15:00 on April 3.
If you specify the release time in the range from 00:01 to 15:00 on April 2, the jobnet is executed twice on that day. This occurs because the jobnet is executed with the definition that has the release ID AJS_AUTO at 00:00 on April 2, and then with the definition that has the release ID 001 at 15:00 the same day.
(7) Release timing when a time zone is specified
The release time depends on the time zone setting used for release entry. Therefore, if this time zone is different from the time zone specified when the release-target jobnet was registered for execution, the jobnet definition is released at the release time of the time zone used for release entry. The following figure shows an example of different time zone settings.
|
In this example, the GMT (Greenwich Mean Time) time zone setting is used for registering execution, and the JST-9 (Japan Standard Time) time zone setting is used when the jobnet-definition release was registered.
Because the release time uses the time zone specified when the jobnet-definition release was registered, the release time is 00:00 on April 2 (JST-9). The execution schedule of 15:00 on March 31 (GMT) equals 00:00 on April 1 (JST-9), which is earlier than the release time of 00:00 on April 2 (JST-9). As a result, the jobnet is executed with the definition that has the release ID AJS_AUTO. The execution schedule for 15:00 on April 1 (GMT) equals 00:00 on April 2 (JST-9), which is the same time as the release time. As a result, the jobnet is executed with the definition that has the release ID 001.
Note that if a time zone for which daylight saving time applies was specified when the release-target jobnet was registered for execution, the jobnet definition is released at the release time specified in the time zone setting for release entry.
(8) Release timing when an exclusive schedule is specified
If an exclusive schedule is specified, the jobnet definition and the exclusive schedule are switched at the release time in absolute time. The following figure shows an example of an exclusive schedule that differs before and after release.
|
In this example, jobnet B is specified for exclusion in the exclusive schedule with release ID AJS_AUTO, and jobnet C is specified for exclusion in the exclusive schedule with release ID 001. In this case, jobnet A excludes jobnet B until 23:59 on April 1, and excludes jobnet C from 00:00 on April 2. We recommend that you do not change the exclusive schedule specification because switching of exclusive schedules might cause operational difficulties.