BLSUXTOD does not know the context of the TOD clock value you are passing, and does not attempt to account for time zones or leap seconds. When you use BLSUXTOD, you are expected to any adjustments of interest to you before calling BLSUXTOD.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY > So this is the first time I really care for leap seconds. I need a > conversion from TOD clock value to readable format in REXX. Found > the BLSUXTOD service. Works nice. so far so good. > > > The PoP has a table of TOD clock values taking care of the 26 leap > seconds inserted so far. The last one was inserted on June 30, 2015 > after 23:59:59. So there is a valid time stamp 23:59:60 on June > 30st, just before July 1st, 00:00:00. > > > If I take the value for July 1st, 2015 from the PoP table and > subtract the equivalent of one second I understand this is the TOD > value for June 30 23:59:60. Am I mixing up things? > > > If all is correct so far, I think BLSUXTOD is in error. It does not > take care of the leap seconds. For the above value, it returns July > 1st, 2015 00:00:25 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
