With Tom's permission, I'm forwarding a private reply to the list because it
contains some good tests he ran.
More to follow...
Patrick
> -----Original Message-----
> From: Emerson, Tom # El Monte [SMTP:[log in to unmask]]
> Sent: Thursday, October 26, 2000 8:36 pm
> To: 'Patrick Santucci'
> Subject: RE: [HP3000-L] How to fix Time Zone error?
>
> > -----Original Message-----
> > From: Patrick Santucci [mailto:[log in to unmask]]
> >
> > I know that. What I need to know is, do I do a SETCLOCK
> > TIME=xx:xx;NOW and
> > then do SETCLOCK TIMEZONE=W5:00 and then SETCLOCK;CANCEL?
> > Won't that mess me
> > up? Or is there a better way/proper order so I *don't* mess
> > things up??
> >
>
> Fortunately (?) you are only 5 hours off the mark -- I'm on the west coast
> so I'm 7/8 hours off instead...
>
> is your shop 24x7? I seem to recall your "concern" was whether or not it
> would mess up "month end" processing. I expect it won't [very much]
> because
> there is at least a 2-day buffer between "the change" and "the end of the
> month" [unless you have jobs that kick off at midnight 1 or 2 days before
> the actual "end" of the month]
>
> changing the timezone is a 5-hour difference, so don't change it prior to
> 7pm [or wait until after 5am -- it's the end of the day so I don't want to
> think too hard ;) ] and the "day" shouldn't change. In other words, if
> you
> have a job that kicks off "at midnight", changing the clock after 5am
> won't
> cause the job to "run twice" when it shouldn't. (or would that be "not run
> at all, when it should run once...?")
>
> >>>>insert homer simpson 'DOH!' here<<<<
>
> I've just bought a used HP for my very own use -- it's sitting in the
> corner
> here, and I REALLY don't have anything "running" on it, production or
> otherwise -- here's a transcript of a few commands, this might give some
> insight:
>
> [note in particular the change from W8:0 to w0:0 initially showed a
> correction, but one second later the "correction" was gone...]
>
> :showclock
>
> SYSTEM TIME: THU, OCT 26, 2000, 5:25:14 PM
> CURRENT TIME CORRECTION: 0 SECONDS
> TIME ZONE: 8 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :setclock timezone=w0:0;now
> The NOW or GRADUAL option requires both DATE and TIME. (CIERR 11705)
> :showclock
>
> SYSTEM TIME: THU, OCT 26, 2000, 5:25:34 PM
> CURRENT TIME CORRECTION: 0 SECONDS
> TIME ZONE: 8 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :setclock timezone=w0:0
>
> SYSTEM TIME: THU, OCT 26, 2000, 5:25:42 PM
> CURRENT TIME CORRECTION: 28800 SECONDS
> TIME ZONE: 0 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :showclock
>
> SYSTEM TIME: FRI, OCT 27, 2000, 1:25:49 AM
> CURRENT TIME CORRECTION: 0 SECONDS
> TIME ZONE: 0 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :setclock cancel
> Both DATE and TIME parameters must be supplied. (CIERR 11703)
> :setclock;cancel
>
> CORRECTION OF 0 SECONDS HAS BEEN CANCELLED.
>
> :showclock
>
> SYSTEM TIME: FRI, OCT 27, 2000, 1:26:14 AM
> CURRENT TIME CORRECTION: 0 SECONDS
> TIME ZONE: 0 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :setclock timezone=w5:0
>
> SYSTEM TIME: FRI, OCT 27, 2000, 1:26:37 AM
> CURRENT TIME CORRECTION: -17999 SECONDS
> TIME ZONE: 5 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :showclock
>
> SYSTEM TIME: FRI, OCT 27, 2000, 1:26:38 AM
> CURRENT TIME CORRECTION: -17997 SECONDS
> TIME ZONE: 5 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :setclock;cancel
>
> CORRECTION OF -17990 SECONDS HAS BEEN CANCELLED.
>
> :showclock
>
> SYSTEM TIME: FRI, OCT 27, 2000, 1:26:43 AM
> CURRENT TIME CORRECTION: 0 SECONDS
> TIME ZONE: 5 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :setclock date=10/26/2000;time=8:27:00pm;now
> :showclock
>
> SYSTEM TIME: THU, OCT 26, 2000, 8:27:02 AM
> CURRENT TIME CORRECTION: 0 SECONDS
> TIME ZONE: 5 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :setclock date=10/26/2000;time=20:27:30;now
> :showclock
>
> SYSTEM TIME: THU, OCT 26, 2000, 8:27:32 PM
> CURRENT TIME CORRECTION: 0 SECONDS
> TIME ZONE: 5 HOURS 0 MINUTES WESTERN HEMISPHERE
>
> :
>
>
> [now of course I have to "reset" it back to reality, but I was planning on
> a
> reload anyway ;) ]
>
>
> I think if you lower the limit so that jobs cannot log on [and suspend any
> "job schedulers" you might have], then issue the timezone change, cancel
> the
> timezone change, then do a "setclock date/time;now" to get the clock back
> to
> the "real" local time, you shouldn't have any "problems" with jobs
> streaming
> when the should (or shouldn't)
|
