Mark, In his post Rich is referring to a problem that has been fixed. Many VSE users have a tendency to continue to warn others about a problem that affected them one at one time and they keep on giving the warning long after the problem has been fixed.
On Sunday I entered the command "SET TIMEZONE=CST" on VM. The VM clock backed up 1 hour. I then did a normal shut down CICS on VSE entered the command "TIME ZONE=VM" and brought CICS up with a warm start. The time on the VSE log shows that the CICS job start time was 56 minutes before the job end time. No problem because the time zone had changed so CICS knew that its warm start data was ok. Did I need to shut CICS down and bring it back up? Probably not, but I did it to make sure that no transaction was active when the clock changed. Stephen Frazier Oklahoma Department of Corrections -----Original Message----- From: [EMAIL PROTECTED] [mailto:owner-linux-390@;VM.MARIST.EDU]On Behalf Of Mark Perry Sent: Tuesday, October 29, 2002 2:27 PM To: Linux on 390 Port Subject: RE: time change Hi Rich, not being either a VSE or a CICS type of person, I was surprised about your comment "CICS journalling and warm start data tends to get a little ornery about the clock going backward" - is there no way to make CICS use GMT/UTC rather than local time for such important things as journaling? Ciao Mark -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@;VM.MARIST.EDU]On Behalf Of Rich Smrcina Sent: 29 October 2002 17:28 To: [EMAIL PROTECTED] Subject: Re: time change VSE will set the clock at IPL time. It can either do that from VM's clock and zone setting or it can use it's equivalent of timezones and boundaries if it is running native or in an LPAR. It doesn't make much sense to use VSE zones and boundaries if running under VM, unless VSE needs a different zone setting than VM. It is not necessary to IPL the system in order to change the time, though. The VSE AR command "TIME ZONE=VM" will fetch the zone and offset from VM and apply them to a running system. All of the caveats about running jobs apply here. CICS journalling and warm start data tends to get a little ornery about the clock going backwards, so CICS will need to either come down and wait an hour or get cold started. Scheduling software (like FAQS/PCS) will need to be cycled along with anything else that is timestamp sensitive. DB2 doesn't seem to care, but watch out for other database software. On Tuesday 29 October 2002 10:14 am, you wrote: > It is my understanding that VSE only checks the TIME parameters at IPL > time. > > Bob Lee, VSE Systems Programmer | Voice: 909-594-5611 > Mt. San Antonio College | Fax: 909-598-6995 > 1100 N. Grand Ave., Walnut CA 91789 | Internet: [EMAIL PROTECTED] > > > > > Hi Rich, > > I just want to bounce this off of you. The time didn't change on the VSE > systems as I thought it would. I did a SET TIMEZONE CST on VM and that > worked right but VSE didn't pickup the time change, so I reipled the VSE > guests. > > I think I know the answer but need your confirmation, I should have did a > SET TIMEZONE=VM from the VSE console to have VSE pickup the NEW time, > right? > I didn't think I needed to do that since I applied the fix from Axel. If I > need to enter that command at VSE, then I will change my procedure that I > gave the operators to include the additional command. Again thanks. > > > Dennie -- Rich Smrcina Sytek Services, Inc. Milwaukee, WI [EMAIL PROTECTED] [EMAIL PROTECTED] Catch the WAVV! Stay for Requirements and the Free for All! Update your S/390 skills in 4 days for a very reasonable price. WAVV 2003 in Winston-Salem, NC. April 25-29, 2003 For details see http://www.wavv.org
