Eric,
You remember quite rightly :)
If you are on a current release (V5R3 or later) you can indeed see job attributes such as time offset, time zone, and datetime. The "gotcha" right now though is, for current releases, the job time zone will always equal the system time zone. So while there are externals in support of each job being in its own time zone, there is currently no way to actually turn it on.
When V5R3 was installed on a system, the licensed internal code switched from tracking time from a local base to a UTC base and then converting time to local when providing it to existing interfaces (the MI for example) in order to maintain compatibility with existing applications (including i5/OS). With V6R1 it is my understanding that selected parts of the operating system are now using UTC internally and mapping UTC times to local job times within their commands, APIs, panels, etc. But the lack of an interface to set a given job to a time zone different from the system time zone continues (and so you can't really "see" these V6R1 changes even though they are there).
So it certainly appears that the intent is there. But today, as I mentioned, "There is no IBM provided support for running jobs, in the same LPAR, that are using different time zones from the perspective of RPG or DDS opcodes."
Bruce Vining
http://www.brucevining.com/
"DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> wrote:
Bruce,
I seem to recall that IBM had stated intent to add something like JOBUTCOFF (Job UTC Offset). Is that not the case?
I remember discussions about this, regarding the OS having to store date/time values as UTC offset 0 (GMT), and translating to the job's utc offset for presentation to the user.... Sounded like a lot of work...
Maybe I'm not remembering this right.
Thanks,
Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Bruce Vining
Sent: Wednesday, September 10, 2008 6:27 PM
To: Midrange Systems Technical Discussion
Subject: Re: Way to change job date/time?
There is no IBM provided support for running jobs, in the same LPAR, that are using different time zones from the perspective of RPG or DDS opcodes. It is possible through the use of locales for jobs to seem to be in different time zones, but this requires application use of the locale and still does not influence time as seen in RPG or DDS opcodes.
In the past I have seen some applications that accomplished this type of feat by way of running only at low levels of system security, by running in system state, and/or by replacing specific IBM provided programs. Sounds like at least one provider ran into the new V6R1 integrity changes.
Bruce
"Bradley V. Stone" wrote:
I have a client who used software that they could change the date/time on a
job (mainly for timezones). IT was something they could run and for the job
only it would affect opcodes like TIME, etc, for RPG and DDS.
For V6R1 this application is no longer availabe. We have found one
alternantive, but they say it's too expensive.
Any idea on how this is done? Couldnt find much in the IBM online docs. MI
instructions perhaps?
Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com
midrange.com
