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.


-----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.


"Bradley V. Stone" <bvstone@xxxxxxxxxxxx> 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 -

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].