|
I've always been too scared to change to/from DST unless the system is quiesced. I guess I should count my blessings. We do a full save every Sunday @ 6:00am. I just have the operator bring the system to a restricted state and change the time before launching the backup. Fortunately, we don't have anything that critical as far as timestamps go. Changing it manually at 6:00am works just fine.
barsa@xxxxxxxxxxxxxxxxxxx 10/26/2006 10:03:50 AM >>>
When you "fall back" the system must essentially be quicessed. There were some issues with MQ and SAP in '04. Unknown if they were resolved. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Graap, Kenneth" <keg@xxxxxxxxxxxx m> To Sent by: "Midrange" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc youngren@xxxxxxxxxx Subject 10/26/2006 12:22 Changing the system clock this PM weekend... Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 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 ****************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
