Sorry. I now remember this is a topic we covered before and a change was made so the )LOAD ignored ⎕TZ. That works.
The thing that brought the problem up is because a garbage/unused ⎕TZ, although not loaded, is saved. This creates problems with source code control systems because ⎕TZ may keep changing artificially when two developers are working on the same code but in different time zones. Bottom line - ⎕TZ should not be saved. Thanks. Blake On Wed, Sep 9, 2015 at 9:10 PM, Blake McBride <[email protected]> wrote: > Greetings, > > ⎕TZ should not be saved with SAVE or DUMP. I should be able to count on > ⎕TZ containing the locally applicable time zone - not the one the developer > had! If, for some reason the developer wants to change ⎕TZ, it should be > done explicitly in a function. A global value should never be saved. > > Blake > >
