Yes you should be concerned with the value of TZ, it just so happens
     that since you are on the east coast, that is what it is defaulting
     to, so you haven't seen a problem.  If you were on the west coast,
     then all your report times would be wrong.

     I was running a bi-coastal speedware shop, and we had the program set
     the TZ variable at startup depending on the user ID (we did session
     names to indicate location).

     So you should set up a system UDC that does SETVAR TZ,"EST5EDT" and
     you should be set.

     Shawn



______________________________ Reply Separator _________________________________
Subject: SPRINGING FORWARD
Author:  [log in to unmask] at Internet-Mail
Date:    4/7/98 8:27 AM


All this discussion concerning the setting and changing of the system
clocks has started me thinking and that in itself is scary.  Here in Maryland,
USA we just sprang the clocks forward 1 hour to Eastern Daylight Time.

The only process we did was to run the utility SETCLOCK with the parm
of TIMEZONE=W4:00   The system clock moved immediately and the clock which
is read by Speedware also is correct.  AND when I run the program
SHOWCLKS.PUBXL.TELESUP all looks good with GMT and MPE System Time and the
offset.  But, the current value of Time Zone(TZ) variable is NOT ASSIGNED

Am I missing something, why should we concern ourselves with the TZ value?
I do believe this has never been assigned and things seem fine.