Hi Guys,
To set up interval there is a from parameter (similar to re run from) for cyclic jobs. It can have 3 values - STRT, END and TRGT.
Can anyone explain what is use of TRGT? How is it different from START parameter. Both seems to be same.
Interval for cyclic jobs
-
philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
When the value of Rerun From is Start, the time until the next job run is counted from the moment that the current job run begins.
When the value of Rerun From is End, the time until the next job run is counted from the moment that the current job run is complete.
When the value of Rerun From is Target, the interval is measured from the scheduling time of the current job run.
from start and from target a not exactly the same as the scheduling time and the start of a run is not exactly the same, but look both to be very close.
regards
Philmalmaison
When the value of Rerun From is End, the time until the next job run is counted from the moment that the current job run is complete.
When the value of Rerun From is Target, the interval is measured from the scheduling time of the current job run.
from start and from target a not exactly the same as the scheduling time and the start of a run is not exactly the same, but look both to be very close.
regards
Philmalmaison
Thanks a lot
Thanks a lot for the clarification.
-
nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00
Shashwat ,
Actually, “from start” counts the start time of the previous run while “from target” count an exact number of cycles, from a “TIMEFROM” boundary.
Lets consider a job having the following parms:
TIMEFROM 0715
Cyclic Y
Interval 15M
If you order you job at 0700 or any time before 0715, there will be no difference, since the first run will be at 0715, and the subsequent run 15 minutes later, which is 0730 and so on.
If you order your job any time after 0715, let’s say 1138, then:
The first run will be at 0738, and:
- if the start type is “Start”, then the next run will be at 1138+15 minutes, which is 1153, then 1208 etc...
- If the start type is “Target”, then the next cycle will be at the “from time”, which is 0715, plus an exact number of cycles of 15 minutes, which results in 1145, then 1200 etc..
Of course, if you don’t specify a from time, the “from target” has no basis for calculations, and the behaviour will be the very same as “from start”
Cheers
Actually, “from start” counts the start time of the previous run while “from target” count an exact number of cycles, from a “TIMEFROM” boundary.
Lets consider a job having the following parms:
TIMEFROM 0715
Cyclic Y
Interval 15M
If you order you job at 0700 or any time before 0715, there will be no difference, since the first run will be at 0715, and the subsequent run 15 minutes later, which is 0730 and so on.
If you order your job any time after 0715, let’s say 1138, then:
The first run will be at 0738, and:
- if the start type is “Start”, then the next run will be at 1138+15 minutes, which is 1153, then 1208 etc...
- If the start type is “Target”, then the next cycle will be at the “from time”, which is 0715, plus an exact number of cycles of 15 minutes, which results in 1145, then 1200 etc..
Of course, if you don’t specify a from time, the “from target” has no basis for calculations, and the behaviour will be the very same as “from start”
Cheers