zMan wrote:
On Fri, Aug 13, 2010 at 12:29 PM, Brian Kennelly
wrote, re "days so far in the year" as
a date format:
That is actually a very import format, as well as the full format returned
by the TIME macro: 0cyyddd. (Century, year, days in year.)
Sure, "days this year" can be useful, but d
On Sun, 15 Aug 2010 20:01:49 -0500, Joel C. Ewing wrote:
>
>The point of Shmuel's comment, of course, is that the one most common,
>unavoidable-in-MVS place where dates of the form yyddd were in
>wide-scale use was in SMF accounting records. The format there is
>packed-decimal, so hex digits are o
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:ibm-m...@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.)
> Sent: Monday, August 16, 2010 4:56 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: [Fwd: Re: date formats]
>
> In <1281901
In <1281901727.14657.141.ca...@mckown5.johnmckown.net>, on 08/15/2010
at 02:48 PM, John McKown said:
>Believe it or not, our 20xx dates are encoded x'9A001' for 2000,
Which would imply that you had to track down every program that did
arithmetic on dates.
--
Shmuel (Seymour J.) Metz,
to work with
in the long run than having different bit-twiddling rules for different
digits of the year.
The original question raised of what date formats should be supported by
a conversion routine has a different answer if the object is to support
a single installation rather than for a general pur
On Sun, Aug 15, 2010 at 2:48 PM, John McKown wrote:
>
> Believe it or not, our 20xx dates are encoded x'9A001' for 2000, and so
> on up the alphabet. I wasn't in on this, so I don't know where it
> terminates. But x'9F' is the max - 2015. So the world better end in
> 2012!
>
x'90' 1990
x'9a' 2000
On Sun, 15 Aug 2010 08:23:18 -0400, Shmuel Metz (Seymour J.) wrote:
>In , on 08/13/2010
> at 05:09 PM, Paul Gilmartin said:
>
>>I'll agree enthusiastically except where the change could be made in
>>a compatible manner, altering no sizes, displacements, nor content of
>>existing data bases. One
Forwarded Message
From: John McKown
Subject: Re: date formats
Date: Sun, 15 Aug 2010 13:27:39 -0500
On Sun, 2010-08-15 at 08:23 -0400, Shmuel Metz (Seymour J.) wrote:
> In , on 08/13/2010
>at 05:09 PM, Paul Gilmartin said:
>
> >I'll agree enthusiastica
On Sun, 2010-08-15 at 08:23 -0400, Shmuel Metz (Seymour J.) wrote:
> In , on 08/13/2010
>at 05:09 PM, Paul Gilmartin said:
>
> >I'll agree enthusiastically except where the change could be made in
> >a compatible manner, altering no sizes, displacements, nor content of
> >existing data bases.
In , on 08/13/2010
at 05:09 PM, Paul Gilmartin said:
>I'll agree enthusiastically except where the change could be made in
>a compatible manner, altering no sizes, displacements, nor content of
>existing data bases. One example might be that where Dec. 31, 1999
>is represented as x'99365', Ja
In , on
08/13/2010
at 12:25 PM, zMan said:
>How many different date formats are there?
How many would you like? Are you only concerned with the Gregorian
calendar?
>There's the hardware timestamp,
With your choice of epoch.
>There's some UNIX format that rolls over in 2
What about NETTIME used by NTP (and friends).
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/arch
See below
From: William M Klein [mailto:wmkl...@ix.netcom.com]
Sent: Friday, August 13, 2010 10:25 PM
To: William M. Klein
Subject: Date formats
On 08/13/2010 12:43 PM, zMan wrote:
> On Fri, Aug 13, 2010 at 12:32 PM, McKown, John
> wrote:
>> There are two that I know of w
On Fri, Aug 13, 2010 at 5:09 PM, Paul Gilmartin wrote:
I was more thinking of 1582. Wikipedia (which is always right
> except when it disagrees with you) says:
>
> http://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar
>
> The proleptic Gregorian calendar is produced by extending
> t
On 08/13/2010 12:43 PM, zMan wrote:
> On Fri, Aug 13, 2010 at 12:32 PM, McKown, John
> wrote:
>> There are two that I know of which you did not mention. Lilian and COBOL.
>> COBOL is an integer which is the number of days since 31Dec1600. Lilian is
>> an integer which is the number of days since
On Fri, 13 Aug 2010 21:49:19 +, john gilmore wrote:
>
>| That would be a proleptic Gregorian date?
>
>and the answer to his question is that the dates of all days that occur before
>a calendar's epoch origin are proleptic for that calendar by definition.
>Their day numbers are negative. T
Paul Gilmartin wrote:
| That would be a proleptic Gregorian date?
and the answer to his question is that the dates of all days that occur before
a calendar's epoch origin are proleptic for that calendar by definition. Their
day numbers are negative. The use of a fullword for Gregorian day v
Don Poitras wrote:
SAS uses lots of date formats. ISO 8601 is a good spot to look for a
large list.
http://support.sas.com/documentation/cdl/en/lrdict/63026/HTML/default/a003169814.htm
http://en.wikipedia.org/wiki/ISO_8601
zMan wrote:
How many different date formats are there? There'
Julian astronomical calendar.
Storing multiple date formats is a mug's game. It brings the need for too many conversion routines in train.
The canonical reference for all calendrical calculations, which I have mentioned on IBM-MAIN before, is
Nachum Dershowitz & Edward M. Reingold. Calendr
On Fri, 13 Aug 2010 18:48:55 +, john gilmore wrote:
>
>The obvious epoch origin to use is that for CE and BCE dates, viz.,
>December 31 of the Gregorian calendar. Other epoch origins can then be
>supported simply using a table of displacements.
>
That would be a proleptic Gregorian ca
On Fri, 13 Aug 2010 12:25:01 -0400, zMan wrote:
>How many different date formats are there? There's the hardware
>timestamp, in two forms (original, with the 2046 rollover, and the
>extended one -- what is that, a STCKE instruction?). There's something
ETOD ends at the same po
Julian astronomical calendar.
Storing multiple date formats is a mug's game. It brings the need for too many
conversion routines in train.
The canonical reference for all calendrical calculations, which I have
mentioned on IBM-MAIN before, is
Nachum Dershowitz & Edward M.
>Years ago, Dr Merrill stated that MXG probably processed more different date
>and time formats than any other software package.
MXG had that facilty mainly because SAS could do most of them.
But, once read, they were stored in internal (SAS) format.
Don't get me wrong.
MXG is a great example o
Of
zMan
Sent: Friday, August 13, 2010 9:25 AM
To: IBM-MAIN@bama.ua.edu
Subject: Date formats
How many different date formats are there? There's the hardware
timestamp, in two forms (original, with the 2046 rollover, and the
extended one -- what is that, a STCKE instruction?). There's
>SAS uses lots of date formats. ISO 8601 is a good spot to look for a large
>list.
Now, you have to be careful about that statement!
SAS displays a lot of formats.
But, usually, there is only one internal format.
Days from June 1, 1960, iirc.
-
I'm a SuperHero with neither
SAS uses lots of date formats. ISO 8601 is a good spot to look for a
large list.
http://support.sas.com/documentation/cdl/en/lrdict/63026/HTML/default/a003169814.htm
http://en.wikipedia.org/wiki/ISO_8601
zMan wrote:
>
> How many different date formats are there? There's t
On Fri, Aug 13, 2010 at 10:42, zMan wrote:
> Sure, "days this year" can be useful, but does anyone store dates as
> "days so far in the year"? It's basically the "Julian" date without
> the year.
>
Yes, they do. I worked on a data conversion product a few years ago for a
software vendor, and th
On Fri, Aug 13, 2010 at 12:32 PM, McKown, John
wrote:
> There are two that I know of which you did not mention. Lilian and COBOL.
> COBOL is an integer which is the number of days since 31Dec1600. Lilian is an
> integer which is the number of days since 14Oct1582.
Wow, in 35 years I've never hea
On Fri, Aug 13, 2010 at 12:29 PM, Brian Kennelly
wrote, re "days so far in the year" as
a date format:
> That is actually a very import format, as well as the full format returned
> by the TIME macro: 0cyyddd. (Century, year, days in year.)
Sure, "days this year" can be useful, but does anyone s
ance Company of
> TennesseeSM and The MEGA Life and Health Insurance Company.SM
>
>
>
>> -Original Message-
>> From: IBM Mainframe Discussion List
>> [mailto:ibm-m...@bama.ua.edu] On Behalf Of zMan
>> Sent: Friday, August 13, 2010 11:25 AM
>> To: IBM-
Behalf Of
zMan
Sent: Friday, August 13, 2010 11:25
To: IBM-MAIN@bama.ua.edu
Subject: Date formats
How many different date formats are there? There's the hardware
timestamp, in two forms (original, with the 2046 rollover, and the
extended one -- what is that, a STCKE instruction?). There
The MEGA
Life and Health Insurance Company.SM
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:ibm-m...@bama.ua.edu] On Behalf Of zMan
> Sent: Friday, August 13, 2010 11:25 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Date formats
>
> How many di
On Fri, Aug 13, 2010 at 09:25, zMan wrote:
> Rexx has a few others, but they're conveniences, like the number of
> days this year -- I don't really consider that a date format, though
> it's useful sometimes.
>
>
That is actually a very import format, as well as the full format returned
by the TI
@bama.ua.edu
Subject: Date formats
How many different date formats are there? There's the hardware timestamp, in
two forms (original, with the 2046 rollover, and the extended one -- what is
that, a STCKE instruction?). There's something called an "Oracle format date".
There
How many different date formats are there? There's the hardware
timestamp, in two forms (original, with the 2046 rollover, and the
extended one -- what is that, a STCKE instruction?). There's something
called an "Oracle format date". There's some UNIX format that rolls
35 matches
Mail list logo
