Re: "Date" fields

[rob@xxxxxxxxx]

He wasn't talking about retrofitting.  He was talking about adding new 
fields.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Jim Franz" <franz400@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/09/2005 08:41 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: "Date" fields






I agree, but it does take a huge amount of hours to retrofit a large 
system.
Even one file or one app at a time is difficult. The "if it ain't broke,
don't ..." manager
wins this arguement every time.
All systems I work on that do not have date data types,  after y2k now 
have
ccyymmdd 8.0 S  fields. That is the standard I see. And zero is a valid
value
(unlike date data types). We call common rpgle pgms to do all from/to
conversions
and calcs (and they use date data types as work fields for calcs).
jim

----- Original Message ----- 
From: "Pete Hall" <pbhall@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, May 09, 2005 9:20 PM
Subject: Re: "Date" fields


> I have to agree with Rob. With the power of the newer boxes, these days
> imho, it's foolish to NOT use the date data type. It automagically
> converts itself to whatever format you like, and it's guaranteed to
> contain a valid date.There's never any confusion about what a date is
> supposed to look like, and for display purposes, all I need to do is
> %char(mydate:*USA) or for JDE, %char(mydate:*CYMD0). I can do things
> like mydate = mydate + %days(7). It's a snap. OK, you said please. I'll
> go away now.
>
> Pete Hall
> http://www.pbhall.us/
>
>
>
> Steve Landess wrote:
>
> >Date field question...
> >
> >There may be a few exceptions, but in JDE all date fields are generally
defined as a 6-digit julian format - 105001, for example, indicates
1-January-2005.  099001 indicates 1-January-1999.  (The '1' prefix 
indicates
that the date is in the 21st century, a '0' prefix indicates 20th 
century).
> >
> >Let's say you're defining a date/timestamp field (14,0 Zoned) -or- a 
date
field (8,0 Zoned) in a non-JDE data base (DB2).  Is our industry, is there 
a
standard for populating these types of field?  I have an idea as to how 
they
should be populated, but would like another's opinion.
> >
> >Please do not confuse my question with the "date" data type that is now
available.  I believe that the customer's requirement is to have this 
field
defined as a numeric field...
> >
> >Regards,
> >
> >Steve
> >
> >
> >
> >
> -- 
> 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.