I'm of the thought you are overthinking it. The steps you have look good to
me. Since timestamps on the system are kept in a way that changing the
timezone should not affect the system clock it occurs to me the wait is a
bit of overkill but it works.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Smith, Mike
Sent: Tuesday, March 03, 2015 4:02 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Chagne the timezone
A number of years ago we moved out LPARs to the parent companies systems
but essentially left everything about the system the same, including the
time zone. It is currently running in Eastern but we're switching to
Central. Looking at the system, I have QTIMZON set to -05:00 Eastern
Standard Time EST and the QUTOFFSET set to -05:00 as well. My plan to
implement this change is as follows:
ENDSBS *ALL to restricted state
Change QTIMEZON system value from QN500EST3 to QN0600CST3, which will change
QUTOFFSET.
Immediately do a PWRDWNSYS with Restart *NO Wait a bit more than an hour and
then have Operations IPL the partition.
Why the wait? I want to limit the chance of getting any application fall
out from having, say a file keyed on Date/Time cause a problem. Also, could
get wonky looking at the logs if this are co-mingled.
Anyone do this and see something I'm not thinking of? No something ya do
every day but it sounds fairly straight forward. I realize my system has
the auto adjust for day light savings time that is essentially doing the
same thing but that's system processed instead of a systems programmer in
the wee hours of the morning, hitting an unexpected command.
Perhaps I'm over thinking this. :)
Michael Smith
Systems Manager - iSeries Support, SAP Basis Administration and Technical
Support (D.R., Open Systems Storage and Mainframe Storage) CTS - Corporate
Technical Services
E : Michael_Smith@xxxxxxxxxxxxxx<mailto:Michael_Smith@xxxxxxxxxxxxxx>
Business Hours : M - F : 8:00 - 4:30 EST
________________________________
Confidentiality: This transmission, including any attachments, is solely for
the use of the intended recipient(s). This transmission may contain
information that is confidential or otherwise protected from disclosure. The
use or disclosure of the information contained in this transmission,
including any attachments, for any purpose other than that intended by its
transmittal is strictly prohibited. Unauthorized interception of this email
is a violation of federal criminal law. If you are not an intended recipient
of this transmission, please immediately destroy all copies received and
notify the sender.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
