RE: Y2.1K Compliance

2060 will be the big one.  I predict WAY worse than 2000.

Brad

> -----Original Message-----
> From: Joel Fritz [mailto:JFritz@sharperimage.com]
> Sent: Monday, November 27, 2000 6:40 PM
> To: 'RPG400-L@midrange.com'
> Subject: RE: Y2.1K Compliance
> 
> 
> It depends on how you handled two digit years.  For data that 
> doesn't need
> to last more than a year or two, a common work around was an exception
> subroutine for the year 2000 and keeping the files with the 
> two digit years.
> If all your dates have four digit years or are stored as true 
> dates, 2100
> isn't an issue.  I can hardly wait til 2098 or so. <g>   
> 
> > -----Original Message-----
> > From: STEVEN.J.RYAN@denso.com.au [mailto:STEVEN.J.RYAN@denso.com.au]
> > Sent: Monday, November 27, 2000 4:40 PM
> > To: RPG400-L@midrange.com
> > Subject: Re: Y2.1K Compliance
> > 
> > 
> > 
> > 
> > The ONLY thing I can think of here, apart from a typo in 
> > their request for '2100
> > compliance', is the fact that 2100 is NOT a leap year, 
> while 2000 was.
> > 
> > Unless there is something in some of the standard AS/400 date
> > formatting/conversion that has a limit in its range (eg 
> 1920 to 2060).
> > 
> > Apart from that, anything that handled 2000 ok should be 
> > alright in 2100.
> > 
> > 
> > 
> +---
> | 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
> +---
> 
+---
| 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
+---