We only do that on time change weekend. At 02:00 local time Sunday. And we don't normally have any jobs running at that time. But it is not our intention to not run jobs then. We just generally don't.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Dazzo, Matt > Sent: Monday, January 23, 2012 9:55 AM > To: [email protected] > Subject: Re: Set Clock Command > > I am curious in other shops that use the 'T TIMEZONE' command > if they stop batch work before issuing the command. > > Thanks Matt > > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Staller, Allan > Sent: Monday, November 21, 2011 3:29 PM > To: [email protected] > Subject: Re: Set Clock Command > > You got it. The XCF couple dataset uses the stamp from the GMT clock. > Instead of SET CLOCK= twice a year, you would issue SET > TIMEZONE twice a > year . > > Check the fine manuals for details on SET TIMEZONE. The TIMEZONE value > should also be set in CLOCKxx. > > Since resetting the hardware clock will require a Power On > Reset, there > is no additional impact. > > Of course, you can eliminate the HW clock/Power On Reset by > fudging the > TIMEZONE values. > > NOTE: The XCF couple dataset cannot handle the back time change. It > "remembers" the last time it was used and will fail the IPL if the > timestamps are not in ascending sequence. I would allocate a > new set of > XCF couple datasets and IPL with those (or wait 5 hours for the IPL). > After IPL, you can dynamically migrate back to the original files if > desired. > > HTH, > > > <snip> > I have been looking at the set clock command in hopes of maybe > eliminating the IPL. From reading the good old book I think I > have to do > the following. Anything else I am missing or should be aware of? How > does the DASD XCF dataset handle the time change when going back 1 hr? > Thanks Matt > > 1.Set the SE clock to GMT > 2. Change the TIMEZONE to -5 for EST > </snip> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
