RE: Is there a name for date format used by DB2?

I also thought it was Scaliger.  Seem to recall some posts by Bruce Vining about it.

Here's a really old reference I found on IBM's site.  Note the 2nd paragraph.
Date

A date is a three-part value (year, month, and day) designating a point in time under the Gregorian calendar, which is assumed to have been in effect from the year 1 A.D. The range of the year part is 0001 to 9999. The date formats *JUL, *MDY, *DMY, and *YMD can only represent dates in the range 1940 through 2039. The range of the month part is 1 to 12. The range of the day part is 1 to x, where x is 28, 29, 30, or 31, depending on the month and year.

The internal representation of a date is a string of 4 bytes that contains an integer. The integer (called the Scaliger number) represents the date.

The length of a DATE column as described in the SQLDA is 6, 8, or 10 bytes, depending on which format is used. These are the appropriate lengths for character-string representations for the value.


Roger Harman
COMMON Certified Application Developer – ILE RPG on IBM i on Power
OCEAN User Group
<http://www.ocean400.org>






----------------------------------------

Subject: Re: Is there a name for date format used by DB2?
To: midrange-l@xxxxxxxxxxxx
From: vhamberg@xxxxxxxxxxxxxxx
Date: Fri, 16 Oct 2015 17:28:43 -0500

Dates, times, and timestamps are stored the same way whether table/file
created DDS source or by a CREATE TABLE. The underlying objects and data
types are the same. That is what object-based system is all about.

The internal length of a date is 4 bytes - it's probably a serial number
representing a number of days from some starting point - someone it is a
Lillian date - I'm not sure, but it might be - that's after some day in
1400 something, as I recall.

A time is 3 bytes long internally

A timestamp (7.1 and before) is 10 bytes long - that is a date (4) a
time(3) and microseconds (3 more). In 7.2 we can have up to 12 "micro"
digits, so maybe the length is increased - I'm on 7.1 and can't see that.

I did a hex(tdate) and hex(ttime) and hex(ttimestamp) and the results
are 8 long for dates - that's 4 bytes - time is 6 long and looks like
hours-minutes-seconds stored in nybbles - 10:15:35 would be x'101535' -
I don't know that for certain, just surmising some stuff. Timestamp is
20 hex digits, the last 6 would be the microseconds stored in nybbles
again, perhaps. So here is the result of displaying both the values and
the hex contents of a date field, a time field, and a timestamp field

HEX ( TDATE ) TDATE HEX ( TTIME ) TTIME HEX ( TTMSTMP )
TTMSTMP
00257EDA 10/10/15 111213 11:12:13 00257EDA111213123456
2015-10-10-11.12.13.123456

Note the TDATE value is displayed in the job's DATFMT - presentation is
managed at application level - storage is always the same.

Actually I think the date number is the number of days since January 1,
4713 BCE - this was established by a certain Scaliger, as a date when
several calendars coincided. We've had a discussion in these lists about
what is what in regard to Julian and other calendar naming - I won't get
into what I don't remember.

If I take the number of days above (x'257EDA', decimal 2,457,306 and
divide by 365.25 and subtract 4713 from that number, I get 2014.7

And __remember___ - it doesn't matter how the table was created - all
date/time values are stored the same in the underlying physical storage.

HTH
Vern

On 10/16/2015 4:29 PM, Matt Olson wrote:

I'm assuming your talking about database column dates.

As far as I know DB2 stores the date in ISO format if the file is described with DDL (SQL).

If it is described using DDS all bets are off as you could define the date format at creation, so there is no real standard there, could be *USA, *ISO, etc.

So it depends on how the file was described.


-----Original Message-----
From: Justin Dearing [mailto:zippy1981@xxxxxxxxx]
Sent: Friday, October 16, 2015 4:08 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Is there a name for date format used by DB2?

Its not ISO 8601. does it adhere to a published standard, or is it an IBM standard?

Yes, its a bit of pedantry. However, I want to patch the DateTime object in PHP, and possible python, and it would be an easier sell to get my patch accepted into the core dateTime objecct for an OS if I was supporting some ANSI/ISO standard as opposed to "the format the IBM i uses".

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

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