On Wed, 10 Jul 2013 20:29:53 +0000, Staller, Allan wrote: >Afaik, there is no such facility for z/OS(z/OS). For (z/OS(OMVS) the TZ >environment variable will handle DST offsets automatically. However, this >variable needs to be set in several places. > I'll disagree with the "automatically" part. You must tell it what to do. And, in general, you can't.
For example, on a Solaris system, I created two files with the commands: user@Solaris:470$ history 461 touch -t 200603221200 Touched-in-2006 462 touch -t 200703221200 Touched-in-2007 where: user@Solaris::474$ echo $TZ US/Mountain Now an extended directory shows me: user@Solaris:469$ ls -alE total 38 Date Time zone drwxr-sr-x 2 user 513 4 2013-07-10 15:02:59.226383291 -0600 . drwxr-sr-x 57 user 513 355 2013-07-10 14:51:00.523492633 -0600 .. -rw-r--r-- 1 user 513 0 2006-03-22 12:00:00.000000000 -0700 Touched-in-2006 -rw-r--r-- 1 user 513 0 2007-03-22 12:00:00.000000000 -0600 Touched-in-2007 Solaris knows that the US/Mountain offset was 7 hours on March 22, 2006, and 6 hours on March 22, 2007. z/OS doesn't know, and there's no way to tell it; there's no value that gives correct results for both 2006 and 2007. (z/OS has no similar option for an extended directory listing. I think they're too embarassed to publicize such flaws.) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
