That would mean every user should "see" their jobs like an exclusive
partition around timestamps. Suppose: I am in the American Continent. I
have users from, say, in Kazakhstan. The time difference is meaningful.
Suppose I need to conduct an audit on work done by them. Is the IBMi going
to know, i.e., today in the American continent is 31st of December at 3pm
(anywhere) and what time do you think they would need to know about DB
updates? They will surely be on New Year! Way ahead of time!

I believe that, unless there is an agreement on time zone differences, no
way to do it.
This, to me, sounds like NASA's worries about what JWST is doing.

JS


El mar, 11 nov 2025 a las 18:44, x y (<xy6581@xxxxxxxxx>) escribió:

My customers have facilities across multiple time zones. I define every
remote device (i.e., no QPADEVxxxx) and include a location code, which
could then be tied to a time zone. DDS's *DATE and *TIME are system
values, so you'll have to add code to your green-screen programs to
reference the device's location if you want the local date and time on your
display. All my timestamps are system time.

It's very surprising IBM ignored time zones for such a long time--SQL
forced it. It's still a surprise that IBM hasn't added time zone/time
offset support into the LOCALE option. It's a fool's errand to think IBM
would do anything to DDS at this time. Like it or not, HTML is way smarter
than DDS.

Before I'd go down the path of changing display files and programs to show
local dates and times, I'd look at converting the app to a browser-based
solution.

On Tue, Nov 11, 2025 at 5:50 AM Shane Reeves via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Just wondering if there a system way to define a different timezone for a
particular user ID or group, in order to track/display the user's local
time for activities rather than system's local time. Or is this
something
I'd have to develop 'manually'?

Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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