Re: Date Comparison yyyymm

From a disk space point of view a date takes 4 bytes, a time takes 3 bytes,

and a timestamp can be from 7 to 13 bytes depending on the precision of the
second that is desired.

On Wed, Oct 11, 2017 at 11:04 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

I just don't see how it would be any less disruptive to move from 5 digit
dates to 7 digit dates than it would have been to go to a DATE field.
Unless you were still doing a lot of RPGII or some such thing (which may
have been more likely 18 years ago).
There's the usual concerns about double meanings. For example a date of
all 9's means something special. Then again a DATE of 1666-01-01 could
mean the same thing.
And as far as disk space goes, one has to remember that DSPPFM does not
tell you really how many bytes a date field takes. That was customized,
along with RPG buffers and everything else, so that older versions of RPG
could process it as a string. I think you'd have to either find the
documentation, or delve down into DMPOBJ or some such thing.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: John Yeung <gallium.arsenide@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/11/2017 11:41 AM
Subject: Re: Date Comparison yyyymm
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On Wed, Oct 11, 2017 at 8:19 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

I remember hearing a panel lecture from a companies experience when they
did their Y2K project. They went to seven digit dates. When it came

time

for questions I asked them if they are going to convert again when users
try to query that data?
Dead silence.

At my first job, which was at a software vendor, all their dates were
5-digit Julian anyway. It was a closed system, with no user visibility
to naked PFs or tables. So the move to 7-digit Julian was the least
disruptive both to them and to their users.

John Y.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD