×
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.
On 04-Aug-2016 17:19 -0500, Vernon Hamberg wrote:
<<SNIP>> There are usually workarounds - I did a quick Google […]
that had this hit from 10 years ago:
http://www.itjungle.com/fhg/fhg052406-story02.html
There is a sample there of an SQL function that can use an API
the system has had for at least 10 years.
Re the article positing "companies with locations in multiple time
zones that connect to a central iSeries, time stamp presentation can be
a problem": I would expect a much simpler approach [long since
available] might be to similarly ensure the stored TIMESTAMP
"information [is] in a single base time zone such as Coordinated
Universal Time (UTC)", and then the local presentation is as simple as
ensuring the subtraction of the CURRENT TIMEZONE from the zero-offset
value; though possibly still dependent on the each server-wide time zone
rather than specific to a user\job?
Select (StoredAsUTC_TS - current timezone)
From table_with_stored_TS_values
As an Amazon Associate we earn from qualifying purchases.
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.