You'll need a program to cause the delay (written in-house or obtained elsewhere) that preferably won't consume any CPU cycles. Personally, I use a Unix step (BPXBATCH) and invoke the Unix "sleep" command, or I use one of a few in-house written utilities.
We should not schdule in the Schduler,needs to run manually
It is a Production Job
Sorry, but this makes no sense. There is neither business nor technical reason to do this manually when the system is supported by scheduling software.
Why does someone believe there needs to be a delay between runs? Why do there need to be multile runs?
None of my clients allow jobs to "wait for a while" then continue. These systems run many thousands of batch jobs a day and leaving batch initiators "idle" (i.e. asleep) tying up system resources is no longer acceptable.
If you clearly explain what is needed (rather than how someone has chosen to meet the need) you will probably get more useful suggestoins. _________________ Have a good one
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum