And it's kind of late to mention this, but if your 3000 uses POSIX or C
routines, it might be worth throwing in /bin/date with your showclock, both
before and after the time change. This is especially useful if you bother
doing so just before 2AM, so as to capture the change from standard time to
DST. It also serves to show that this time is not affected by setclock.

I remember running into minor anomalies with our third-party scheduler,
which could be explained by demonstrating that it used C time routines, and
that these were not the same value as what showclock returns. The POSIX
clock, which I believe can be referred to as the software clock,
self-adjusts, although it does it the other way around on MPE, calculating
universal time from clock time, and takes into account time zone and DST.

Chances are, no one else will care. But I would rather have this audit trail
than not.

Greg Stigers, MCSA
this space for rent

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *