On Mon, 4 Apr 2022 14:16:55 -0700, Charles Mills wrote:
>If you want them both to be the same, why not just set them both the same?
>
>Serious question.
>
No. That fails for human error, indolence, and bias ("We don't need
no steenkin UNIX -- we got along fine without it in 1968!") That
provoked the OP's perplexity.
Rather, there should be a single point of control in PARMLIB, perhaps
HMC, in which a value could be entered in the format described in
UNIX System Services Command Reference, Appendix I. TZ environment
variable. This implies the current offset and schedule of Daylight
Saving changes. Control block entries such as CVTLDTO can be
derived from this, preferably automatically. Existing control block
entries do not provide sufficient information to calculate the TZ
environment variable such as for:
Australia/Canberra: "AEST-10AEDT,M10.1.0,M4.1.0/3"
America/Denver: "MST7MDT,M3.2.0,M11.1.0"
That system setting should govern the behavior of processes ini
which TZ is unset, rather than the current default of UTC.
>On Apr 4, 2022, at 11:40:05, Peter wrote:
>>
>> I see OMVS and MVS have their own time and date settings.
>>
>> Isn't their a way to have a common configuration settings for date and
>> time for MVS and OMVS ?
>>
>RFE.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
