RE: IBM i timestamps -- MIDRANGE-L

Subject: RE: IBM i timestamps
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Wed, 17 Jul 2019 18:36:21 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

It looks like ISO 8601 includes time zone info (2019-07-17T18:32:47+0000) and the value that the Db2 CURRENT_TIMESTAMP function gives doesn't (2019-07-17 13:33:55.291065).

-----Original Message-----
From: Jay Vaughn [mailto:jeffersonvaughn@xxxxxxxxx]
Sent: Wednesday, July 17, 2019 12:13 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: IBM i timestamps

test your IBM i knowledge question of the day...

are the timestamps on the iSeries ISO 8601 compliant?
Can they be configured to be compliant?

Brought to you by...
Jay

As an Amazon Associate we earn from qualifying purchases.

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.