(Have I ever mentioned how I hate switching from bottom posting to top posting in the same thread. :-) )
I'm sure it would work just dandy, although I've never tried it. But what would you, a z/OS sysprog rather do: Change the image profile on the HMC twice a year, or change a parmlib member? Remember, the sysplex timer doesn't change times, just the offset gets changed automatically twice a year. I don't think the HMC setting is an offset of the offset. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ On Mon, 23 Jan 2012 12:54:24 -0800, Skip Robinson <[email protected]> wrote: >I have NO experience with this, but in the Image profile there in an >option to use 'Logical partition time offset' in lieu of 'Standard time of >day'. Would that help in managing multiple time zones? > >. >. >JO.Skip Robinson >SCE Infrastructure Technology Services >Electric Dragon Team Paddler >SHARE MVS Program Co-Manager >626-302-7535 Office >323-715-0595 Mobile >[email protected] > > > >From: Mark Zelden <[email protected]> >To: [email protected] >Date: 01/23/2012 12:07 PM >Subject: Re: Set Clock Command >Sent by: IBM Mainframe Discussion List <[email protected]> > > > >On Mon, 23 Jan 2012 13:00:30 -0600, Paul Gilmartin <[email protected]> >wrote: > >>On Mon, 23 Jan 2012 11:52:11 -0600, Mark Zelden wrote: >>> >>>Unfortunately the sysplex timer only support 1 offset. >>> >>Does that mean you must choose between GMT and LOCAL? Ugh. >>Even if it supported two offsets, that's not enough. But the >>Sysplex Timer (AKA ETR? AKA STP?) should support only GMT. >>The rest should be done with software. z/OS UNIX is far better >>than legacy z/OS in this area, while yet far inferior to other >>UNIX-like systems. (Ubuntu Linux provides several hundred.) >> > >The timer is set to GMT and operates from that. But it also (optionally) >can have an offset. The offset is set to pacific in our case. I don't >know if *you* consider that hardware or software, but I consider >it "hardware". For the LPARs not running pacific time, it means >taking the offset from software and changing CLOCKxx parmlib >members twice a year and either IPLing or using "SET TIMEZONE". > >Prior to the existence of "SET TIMEZONE" (z/OS 1.7 and above) >we either used RO *ALL,SET CLOCK = with getting the local >time as close as we could to the GMT time or we used the >SETHOUR program from CBT file 639 which did it for you >and could get the local time set to the same second as the >GMT time. It also updated the CLOCKxx member in parmlib. > >Regards, > >Mark >-- >Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS >mailto:[email protected] >Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html >Systems Programming expert at http://expertanswercenter.techtarget.com/ > >Mark > > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
