Frank, Thanks for correcting a previous poster on the fact that whole hour offsets are not required.
However could you state at what release of zOS that the GMT operand of the SET command was removed? It still exists as of OS/390 2.10. Check your "Systems Commands" manual for your whatever release you feel no longer supports such. Don Stubbs -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@;VM.MARIST.EDU]On Behalf Of Br|chmann Sent: Thursday, October 24, 2002 7:48 AM To: [EMAIL PROTECTED] Subject: Re: time change The ,GMT operand has gone, but if you have ETRMODE NO, you can use the T CLOCK= command to set the local time. The values for minutes and seconds can be 0-59, so no problems for India here :-) If you have ETRMODE and ETRZONE YES, you can use the sysplex timer timezone offset, to change the local time on all members using it, in one go. Maybe your subsystems and applications will get confused by this, but CICS and DB2 should be OK. Regards Frank. John Summerfield wrote : >On Wed, 23 Oct 2002 23:48, you wrote: >> Prior releases of MVS, VSE, VM, and so on did require a reboot >> to change the clock. They also tended to use local time on the > >I coulda sworn... > >Back in the days when I was a VS1 sysprog, one could enter the command >t clock=... >and then was asked to press (or otherwise manipulate) a button/switch to allow >the change to the hardware clock. > > >I also recall that "[,GMT]" was listed as a valid operand.
