AFAIK there is no reason to shut down at the time change. The only exception would be if your applications use local time (eg. Time stamps in data files) that could cause grief. We keep a few of our production CICS AORs down for this reason but leave our test & UAT regions up to hopefully catch an error that will prove we need to shut down the application. Of course not catching an error in test does not prove there can't be one in production. Various products (CICS, Omegamon) have commands to refresh local time.
Ken Porowski -----Original Message----- Hale, Bob We shutdown TMON-DB2, TMON-CICS and RMF down for an hour. At 2:00 we set the time back to 1:00 and keep running. We do issue the RESET command in the running CICS regions. We do not stop anything else we just keep running. We also change the TIMEZONE so when we did do the next IPL the clock will be correct. We did do an IPL on 11/9/2008 but not because of the time change. Bob -----Original Message----- Kelman, Tom We do the same thing. If anyone knows how to make the change without sitting idle for an hour we'd like to know that also. Tom Kelman Enterprise Capacity Planner Commerce Bank of Kansas City (816) 760-7632 > -----Original Message----- Ted Kempf > > How are you folks handling your "fall back" EST time change ? We set > CLOCK00 with TIMEZONE W.05.00.00, shutdown the system for an hour, then > IPL and life continues. What are your experiences with SET TIMEZONE ? > Trying > to find a better way than sitting idle for an hour !! > > Ted ---------------------------------------------------------------------- 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
