Re: Changing the system clock this weekend...

["Jim Franz" <franz400@xxxxxxxxxxxx>]

The Time Adjustment seems a good solution for my sites. Don't have any
need to synch with other systems, and it's not an option to bring the 
machine down
(it's taking and processing orders).
However - I'm not planning to sign on at 1:59am to point & click a navigator 
function.
Why can't Rochester figure it out their job scheduler works great to run 
stuff overnight.
We need a  #%*#  command to call.
So I will do what I've done every year - chgsysval qhour.
jim franz



> Kenneth--
> Your wish has been granted!
> > http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzati/rzatitimeadj.htm
> > It's supposed to gradually adjust and have no duplicate times.  Read
> > the above.
> > > It says (in part):
> > > If you need to adjust the system time by two or fewer hours, use
> > > the time adjustment function to change the system time.
> > > A time adjustment is preferred over manually changing the time of
> > > day system value because it incrementally speeds up or slows down
> > > the rate at which time moves forward rather than making one single,
> > > instantaneous change in time. A large jump in time, either forward
> > > or backward, can cause unpredictable errors if jobs are
> > > concurrently accessing system time.
> > >
> > > If your system time is off more than 2 hours and you do not need to
> > > change the system time immediately, you can use multiple time
> > > adjustments to reach the desired time value. For example, if your
> > > system time is off 3 hours, you can make a 2-hour time adjustment
> > > and a 1-hour adjustment to make a total adjustment of 3 hours.
>
> I haven't used it...  and I'm curious to see how well it works!
>
> --Paul E Musselman
> PaulMmn@xxxxxxxxxxxxxxxxxxxx