On 2014-07-10, at 08:34, Ed Jaffe wrote: > On 7/9/2014 11:04 PM, Jim Mulder wrote: >> Upon closer inspection, >> the code dealing with CVTLSO and CVTLDTO is on a path used only >> for TIME with LINKAGE=SYSTEM. STCKCONV does not do anything >> with CVTLDTO and CVTLSO, or attempt any kind of leap second >> or time zone adjustment. > > THANK GOD!! You scared me with your previous post! > > We call STCKCONV in *many* places assuming it is a straight conversion with > no time zone adjustments made. > > Whew! :) > "Assuming", because it's not documented, and you (probably) haven't the access to the source code that Jim has.
Does your code run on systems with CVTLSO<>0? Does the (now) 25 second offset from STCKCONV time to cause problems? Our site chose to disable leap seconds because of vendor inconsistencies. And when we had leap seconds enabled, I reported a disagreement between times reported in IEBCOPY SYSPRINT and the job log. IBM fixed it by APAR. -- gil
