Changing the system clock this weekend...

I know that if we don't do anything on our V5R3 system, the system clock will 
automatically be moved back an hour this coming Sunday morning...

Does anyone share my concern that doing this on an "active system" will result 
in Job Accounting, Security and Application journal integrity issues?

For example, our job accounting journal we will most likely show jobs ending 
before they started... Application journals could have issues with commitment 
boundaries and recovery issues related to inconsistencies in the time stamp on 
journal entries. Security events logged to the security journal will overlap 
for an hour. 

How do you get around these issues without quiescing your system or powering it 
off for an hour and manually changing the clock when nothing is active?

I can't seem to find anyone at IBM who cares about this issue. They did say not 
to have any time sensitive processes running at 2am on Sunday though. On a 7/24 
system using journaling, isn't everything "time sensitive"? 

We also have our system configured to verify the system date using SNTP and 
I've been told that the SNTP server we point to will move the clock back 
automatically too... 

Does anyone on this list share my concern about this issue or am I just blowing 
this all out of proportion? 

I'd really like to know your opinion on this matter....

Thanx

Kenneth

****************************************
Kenneth E. Graap
IBM Certified Specialist 
iSeries Multiple System Administrator
NW Natural (Gas Services)
keg@xxxxxxxxxxxxx
Phone: 503-226-4211 x5537
FAX:    503-721-2518
****************************************