On Tue, 10 Mar 2015 21:53:46 +0000, Pommier, Rex wrote: >I don't know if I would infer that JES2 resyncs to the top of the hour. I >would infer that JES2 simply restarted its 3600 second timer at the point of >time the time changed. I would guess that if, for example, at 5:35 PM you >changed the time to 5:36 PM, your hourly automatic command would start >faithfully executing every hour at 36 minutes after the hour. > I would more plausibly infer that at 01:45 it queued an event to be dispatched at or after 02:45 local time. Suddenly, at 03:00 the greater-or-equal condition became true and the event was dispatched.
>-----Original Message----- >From: J O Skip Robinson >Sent: Tuesday, March 10, 2015 3:51 PM > >I'm 90% sure of the answer but would like confirmation. We have a JES2 >automatic command that's executes once an hour (T=3600) with no specific start >time. Before the Sunday Daylight Saving Time switch, this command was >executing at 45 minutes past the hour. Immediately after the time switch, it >began executing at 1 minute past the hour. We had no IPLs or JES2 restarts. > >Can I infer that upon detecting a local time change, JES2 resyncs automatic >commands to the top of the hour? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
