Lucas Rosalen wrote: >Mike is right. >At 2:01 you've "added" 3600s (to make it 3:01), so JES2 tried to catch up as >the interval had already been more than satisfied.
Indeed and this is documented, <quote> If, at 1:15 a.m., the clock is set ahead two hours, making the current time 3:15 a.m., the command will be issued immediately, at 3:15 a.m., and will be issued again at the next interval (two hours beyond 3:15 a.m.), which is 5:15 a.m. <end quote> But does not 100% describe the OP's problem. I'm also puzzled by this. I believe we all missed something obvious. What we're doing is, we let the automation software issues several $T commands (with T= and I= keywords) on the hour (whatever) or about 5 minutes after hour and then we let JES2 go on. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
