On Mon, 10 Sep 2012 09:03:28 -0700, Charles Mills wrote: >Is there a technique, statement or utility that will cause a program or >jobstep to "see" a different timezone? I recall you could do this in VSE. I >looked at the CBT tape and did not find anything. Is there a programming >technique that would work? The politics are such that writing code is a more >acceptable solution than a vendor product. > UNIX System Services?
>and subsequent steps in the job -- but not other programs in the LPAR -- >"see" the timezone as PDT, UTC-9. > >Was there some sort of technique to do this developed during the Y2K >excitement? > Likely very specialized. >What do shops do that have LPARs that serve users in multiple time zones -- >some one-off homegrown solution that works (only) for them? > z/OS is far behind the industry norm in this area. (Well, if one discounts Windows.) But several years ago I submitted a PMR that IBM's C preprocessor ignored the TZ environment variable when evaluating the built-in __DATE__ and __TIME__ macros. WAD. But a customer with more clout than I must have renewed the issue. Some time subsequently I found it was working correctly. Simply, TZ should be a variable settable with such as the JCL SET statement, and that setting should apply to invocation of the TIME macro in subsequent job steps, but not to other jobs in the LPAR. Programs that access fields in the CVT directly deserve little support. >What do shops do that have LPARs that serve users in multiple time zones -- >some one-off homegrown solution that works (only) for them? > Suffer? Consider this one more factor in evaluating the recommendations of the airline magazines to move to vendors that offer better support? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
