Our time changes don't occur right at 02:00.   Unfortunately, we have
some applications that do not tolerate the time change well, so we
typically shut them down.  We no longer IPL in the spring, and just do
the SET TIMEZONE command.   However in the fall we still do IPL.

I'd love to get away from that, but alas, no one in the app world seems
to have the time to want to find out.

_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
[email protected]
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Skip Robinson
Sent: Monday, January 23, 2012 12:15 PM
To: [email protected]
Subject: Re: Set Clock Command

I'm curious. We have not done 'SET CLOCK' for 15 years since we acquired

sysplex timers and now have STP. Time changes are automatic/programmed.
Is 
the reason for using manual processes strictly financial? 

.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[email protected]



From:   "Jousma, David" <[email protected]>
To:     [email protected]
Date:   01/23/2012 08:22 AM
Subject:        Re: Set Clock Command
Sent by:        IBM Mainframe Discussion List <[email protected]>



We do.  Mostly out of application cautiousness.   Much like still IPLing
to go backwards in time in the fall.

_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
[email protected]
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Dazzo, Matt
Sent: Monday, January 23, 2012 10: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

This e-mail transmission contains information that is confidential and
may 
be privileged.   It is intended only for the addressee(s) named above.
If 
you receive this e-mail in error, please do not read, copy or
disseminate 
it in any manner. If you are not the intended recipient, any disclosure,

copying, distribution or use of the contents of this information is 
prohibited. Please reply to the message immediately by informing the 
sender that the message was misdirected. After replying, please erase it

from your computer system. Your assistance in correcting this error is 
appreciated.

----------------------------------------------------------------------
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

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to