Actually 'resetting at the moment of time change' is probably a better characterization. STP changes the time offset at the top of the hour, so timer intervals would reset to that. BTW I should have said that the auto command has I=3600, not T=.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pommier, Rex Sent: Tuesday, March 10, 2015 2:54 PM To: [email protected] Subject: Re: Time change effect on JES2 AUTO commands 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. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of J O Skip Robinson Sent: Tuesday, March 10, 2015 3:51 PM To: [email protected] Subject: Time change effect on JES2 AUTO commands 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? . . . J.O.Skip Robinson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
