The software in question is "reporting" z/OS security-related events so the one time zone in which the box itself is located (or where its sysprogs think of it as being located) is appropriate and sufficient.
Yeah, the fact that z/OS has two completely different "systems" for specifying the local time zone is annoying, but not my problem to solve today. Customers are not really limited to two time zones, are they? You could in theory run 5 instances of my program with five different TZ settings, right? I hate local time. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Friday, September 06, 2013 7:18 AM To: [email protected] Subject: Re: Where environment variables set for batch POSIX programs? On Fri, 6 Sep 2013 07:05:56 -0700, Charles Mills wrote: > >My question is what do I tell the customers that ask "how come you >don't get the time right without us telling you what to do with a parm >or DD? Our MVS programs know what the local time is. What's wrong with >your program?" I want to be able to say "you need to set TZ in >_________ as described in _____________." > Yes, but do your customers' programs know what time it is in Pacific/Apia, e.g. Many enterprises nowadays span multiple time zones; restricting customers to two is pretty harsh. Cite: http://en.wikipedia.org/wiki/Conway%27s_law (Or did I overlook some imputed rhetoric?) Simply, if either the POSIX time or the OS/360 time is set in PARMLIB, but not both, the system should infer the one missing from the one supplied. If both are supplied but incosistent, it should issue an informative message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
