What would be the problem with varying the TZ variable by user (udc logon) so that each user logs on
in the time zone they are in, so that the current date and time are automatically adjusted, depending
on who is running the program?  If you have a separate batch user, you could still vary the batch user
or TZ variable based on who initiated the job pretty simply.

"Simpkins, Terry" wrote:

> I have read with great interest the numerous posts recently about the various utilities
> to adjust the system time for YR2000 testing.  But I have a different need for such a tool.
>
> We run a single HP3000 production machine that provides computing resource (MANMAN) for
> numerous manufacturing locations (8 and growing) around the world.  These plants are
> (naturally) in various time zones.  Each plant would like to see their transactions posted
> (and reported) in the local time, instead of Eastern Standard/Daylight Time.
>
> While I suspect that more than one of them will perform the required "localization" in
> the application, I am concerned about the impact on "system functions" such as file creation
> date/time, etc.  (Stan, down boy ;-)
> Has anyone else conducted a thorough examination of these issues?
> I am worried that having the "file modified" date reflect local time, our backups (and recoveries)
> could become much more complicated (unnecessarily).  Likewise, the issues on IMAGE
> logging and "rollback" recovery concern me.
>
> We are just started to give this issue some serious consideration, and I thought I would see if
> I can leverage someone's prior efforts.
>
> *******************************
> Terry W. Simpkins
> Director ISIT
> Lucas Control Systems
> [log in to unmask]
> *******************************