On Mon, Nov 3, 2014 at 6:25 AM, Elardus Engelbrecht < [email protected]> wrote:
> Kirk Wolf wrote: > > >>Wouldn't it be great if you didn't have to configure default system > environment variables like TZ for each and every job? > > It would be great, but if your system is using LE, then whatever the > default is setup in LE (CEE parmlib member or CEE option module depending > on LE library used), is used, unles you set up your own TZ for EACH > application. [1] > This is what I have done. I am "lucky" in that my company is little and does not span time zones. But it does make me wonder what a multinational company would do for a default TZ which is not GMT. TZ of the "home office", or of the physical location of the data center, or the CEO's wife's favorite second cousin? <grin/> > > >>Headline: Provide option for dubbed processes to inherit environment > from init process > > Question: add another requirement - that dubbed proc can either accept > inheretance or not. If not, use its own defaults if not setup (own TZ). > > I'm not understanding this. If the inheritance were done, the application could still have its own defaults set. Perhaps via LE parameters in the PARM=. Hum, and if a dubbed process "inherits" its environment variables, and is in an LE run unit, does it inherit from "init" or from the ENVAR parameter, if any, set via the PARM? I.e. who takes precedence when an LE run unit is dubbed. I vote for LE. And, other that in code, how are the application specific environment variables set? Via the SYSENV DD statement? Of course, if a request is made from IBM, that is _their_ design decision. I've often been told that IBM prefers to be told what you want the end results to be, not how you want them accomplished. > > Paul Gilmartin wrote: > > >Many years ago, I submitted a PMR to the effect that when TZ is unset the > time zone should default not to UTC but to system time, as on many other > UNIX systems. It was rejected on the ground that such behavior would be > incompatible with AIX. > > Good PMR, but why, oh why was it ultimately rejected? Whoever rejected > that PMR are either bored or too lazy. > > > >Where's /etc/localtime when you need it? > > I also don't see or missed it after searching my z toys. Do you need to > create it manually? But *will* it be used at all? > No it won't be used, that's what Gil was getting at. Personally, I don't see the need. IMO, all z/OS systems should have the hardware TOD clock set to GMT/UTC (yes, I know they are not exactly the same thing). I don't really see the plus of /etc/localtime vs. just setting the z/OS TIMEZONE offset. They are both "global" to the z/OS image. I would hope that the UNIX default would be the same as the z/OS batch default. But that's just my personal take on it. > > Groete / Greetings > Elardus Engelbrecht > > [1] - I had to show my SMTP (actually CSSMTP) team how to setup a member > containing TZ=GMT-2 statement. They could do it on other LPARs where needed. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- The temperature of the aqueous content of an unremittingly ogled culinary vessel will not achieve 100 degrees on the Celsius scale. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
