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



Kevin,

Using your SQL statement as a base, I believe this should return the proper
UTC offset every time:
WITH ts
AS (
SELECT CHAR(CURRENT TIMESTAMP) AS iso_Zdate_col
FROM sysibm.sysdummy1
)
SELECT LEFT(iso_Zdate_col, 10)
CONCAT 'T' CONCAT REPLACE(SUBSTR(iso_Zdate_col, 12, 8), ':', '.')
CONCAT (CASE WHEN CURRENT timezone < 0 THEN '-' ELSE '+' END)
CONCAT SUBSTR(DIGITS(CURRENT TIMEZONE), 1, 2) CONCAT ':' CONCAT
SUBSTR(DIGITS(CURRENT TIMEZONE), 3, 2)
FROM ts ;

It could be rewritten as a SQL function but, of course, as you correctly
state, the real solution would be for IBM to provide us a proper ISO 8601
timestamp.

Regards,



Luis Rodriguez


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