RE: Daylight Saving Time

> When DST starts local system time will change from 2:00 AM to 
> 3:00 AM, and when ending from 2:00 AM to 1:00 AM.  This will 
> take place independent of whether or not you are using an 
> external time server, and will conform to your local 
> definitions of time.

I understood all that.  I was looking for something that speeded it up to
move ahead an hour, or slowed it down for an hour catch-up instead of a jump
in one fell swoop.  There is a lot of discussion in the Infocenter (yes I
found it!) regarding changing the time and it's effect on scheduled jobs and
other time-dependant operations.
 
> Time adjustment is not used as that would cause the minute 
> after 2:00 AM to be "something" between 2:00AM and 3:00AM.  
> This time value (for example purposes 2:01AM) does not exist 
> (per your legislative authorities).

OK, I never thought of the time 'not existing' for legal reasons.  But what
about the other direction in the fall?  Does the time 1:30am legally occur
twice?  
 
> It is because of these types of headaches that the system 
> internally tracks time with UTC (rather than local time) 
> starting with V5R3.  UTC does not have the concept of DST.  
> Time simply moves forward, and the system then converts the 
> internal UTC times to the appropriate local times based on 
> the time zone in effect.  To avoid time shifts the use of a 
> standard such as UTC is the way to go.  Local times are just 
> too easily changed by government decisions.

Does that mean UTC is what goes into QHST?  Does that mean if I view QHST,
then change my time zone or offset, then view QHST again, the times will be
different?

And how does the Advanced Job Scheduler know not to run that 1:30am
scheduled job a 2nd time?  Or does it run again?  (No, I don't have any
between 1am and 3am, but inquiring minds want to know.)

Thanks.