Re: Y2.1K Compliance

>it currently depends on the setting of the QCENTURY system
>value, where 0 = 1928-1999 and 1 = 2000-2053.

I haven't followed this thread closely and, fortunately, I work in a shop that
started using 8-digit dates ten years ago.  But the above quote caught my eye.
 How do you represent May 1, 1925 using CYYMMDD?  May 1, 2054?  Why wouldn't a
century digit of 0 cover all the years 1900-1999?  And so on?

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
Hi Jim,

I think I misspoke on my previous email. As you say, windowing is only with
6-digit dates; I was thinking of what would happen if IBM changed what the
"c" in cyymmdd represents. As I understand it, it currently depends on the
setting of the QCENTURY system value, where 0 = 1928-1999 and 1 = 2000-2053.
If they decided that 0 = 1929-1999, then anyone storing dates in cyymmdd
format might have a problem. However, I don't see that as a likely scenario.

No, I use native dates when possible, or whatever the customer/vendor
software I happen to be working with is using. Still, the cyymmdd date is
what IBM uses to pass from a command to the command processing program when
a parameter is defined as a *DATE parameter. I use CVTDAT to convert such a
date to an 8-digit date, so it's up to IBM to be consistent in how they
convert dates with CVTDAT.

Regards,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---