× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Tom Jedrzejewicz wrote:

Actually, as this discussion went on in various forms over the last few
weeks, I started to wonder why the "local" time  is used at all.  I would
think that every system should keep a standard time (i.e.Zulu
time<http://en.wikipedia.org/wiki/Coordinated_Universal_Time>)
and present it in local time.

I would think this would be particularly useful for messaging systems, such
as MQ.

Since at least V5R3, the RJNE0200 format for the QjoRetrieveJournalEntries API has returned the 'unformatted' timestamp of journal entries. I haven't looked for earlier usage since the QTIMZON/QUTCOFFSET issues were really clarified also at V5R3.

This can be converted to *UTC or just about any "local" variation desired. IMO, it is _the_ value to use as far as time-sensitive journal entries are concerned.

I suspect that IBM makes use of it at points. You can bet that it's the only timestamp I'll be putting much effort into for journal entries for the foreseeable future.

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.