I can contribute one factoid to this discussion. We use IBM's TWS for job scheduling. Because of the scheduling's extreme sensitivity to time stamps and because of a negative incident we had a few years back, we've been accustomed to bouncing TWS shortly after the 'fallback' time change. This time we rode it out and watched for any scheduling anomalies. We found none. Meanwhile no application area has reported problems with duplicate time stamps interfering with their production. (Is that a second factoid?) So running with true UTC and current OS and middleware, fallback time change should no longer be a global concern.
. . . 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 jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Giliad Wilf Sent: Friday, November 06, 2015 3:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: RE-IPL for the Daylight to Standard time conversion? Much to my regret I've seen the discussion on topic "RE-IPL for the Daylight to Standard time conversion?" too late, and was unable to read all posts on the issue, so bear with me if it turns out that someone else has already mentioned an excellent publication I'm mentioning now: SG24-2070 - S/390 Time Management and IBM 9037 Sysplex Timer, at http://www.redbooks.ibm.com/redbooks/pdfs/sg242070.pdf Chapter 9, "Offset Change Impacts to Subsystems", is worth reading (and so is Chapter 8). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
