Setting the TIMEZONE in CLOCKxx will alter the time displayed on console messages, but not as you desire. The TIMEZONE offset is added (or subtracted) from the SYSTEM (HW) clock to produce the displayed time (I won't go in to all of the minutiae here). In neither case will the console messages ever display with the PST suffix.
I am somewhat less familiar with the UNIX SYSTEM SERVICES TZ environment variable, but the basic principle is the same. The TZ offset specified is added or subtracted to the HW clock. USS TZ offsets handle DST processing automatically. Given your current offset and the fact that you do (apparently) do not actually want to change the time displayed you will need to reset the HW clock *AND* specify the appropriate TZ offset. HTH, -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Donnelly, John P Sent: Wednesday, February 24, 2010 5:39 PM To: [email protected] Subject: TIMEZONE Specification We have TIMEZONE W.00.00.00 specified in our CLOCKxx PARMLIB members. System displays date/time as: 28 JAN 2010 11:10:44 +0000 We wish this display to be: 28 JAN 2010 11:10:44 PST Will setting the TIMEZONE parameter as: TIMEZONE W.08.00.00 Produce the desired result? May we introduce singularly by LPAR without causing date/timestamp problems in a shared disk farm? Timestamps are a very great concern hereabouts... ---------------------------------------------------------------------- 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: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
