|
What Al Mac said was right. If you don't have to support too many time zones you might consider LPAR but that opens up a host of support issues. But, I'd keep hammering on IBM with Design Change Requests, or DCR's, to get them to fix this. I was hoping for this kind of support in V5R4. There is already a bunch of underlying support built in. Like RTVJOBA has CL var for DATFMT CL var for DATSEP CL var for TIMSEP CL var for DATE CL var for CYMDDATE CL var for DATETIME CL var for TIMZON CL var for TIMZONABBR CL var for TIMZONFULL CL var for TIMOFFSET So they don't have much further to go. They are getting close to flipping the switch. Frankly I think they are so close (and this is pure speculation!) why not just ptf it out? What's left? CHGJOBD? SBMJOB? CHGUSRPRF? CHGDEVDSP? Make the api's etc that retrieve system time respect the values in RTVJOBA? Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.