On Tue, 28 Oct 2025 15:15:10 -0500, Paul Gilmartin <[email protected]> wrote:
>There are more than two timezones that z/OS supports/ What is the 3rd timezone supported by z/OS (not CPU & CLOCK00)? LOCALTIME() is a LE (C, Cobol, ...). It is not supported by z/OS. When run from task providing ENV variables, a variable which is meaningless to CICS, IMS, TSO, batch, ...). >Enter 6:00am in struct tm; call mktime; subtract 4*60*60 seconds; call >localtime. >But this is best done in UTC because 0200 occurs twice next month. Your point was IANA handled the time change. This is logic needed to handle time change for this situation. The programmer is implementing time change and IANA is a small part of this logic. >The problem exists; z/OS deals poorly with it. ROTFLOL, Google's Youtube video list from your subscriptions in time sequence but if you pay close attention, you will see one or two out of time sequence but most people never notice which I find irritating. Linux deals poorly with it. >This is best done using UTC, not local. Again, IANA did not make this decision. You are saying it's up to the programmer to handle the time change. >??? z/OS can be excused for doing it poorly because users could do >it better with considerable redundant effort. What makes you think Linux is better? It's simply different. In z/OS, we analyze problems using CLOCKxx timezone without changing the timezone. In Linux, if time is important for debugging, I need to change TZ so that all references to localtime are consistent. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
