Re: Y2.1K Compliance

Well, strictly speaking, if the software was upgraded to Y2K compliance 
using a 7 digit date (CYYMMDD) instead of a 8 digit date (YYYYMMDD), then 
it would *NOT* be Y2.1K compliant.... they are, quite possibly, seeking 
assurance that 8 digit dates were indeed used (which, as the original 
poster indicated, was the case).

I would *NOT* take the request lightly ... it most likely came from the 
firms quality assurance organization and could mean the difference between 
doing business or not.

At 06:40 PM 11/27/2000, you wrote:


>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.
>
>
>
>
>"Smith, Nelson" <NSmith@lincare.com> on 28/11/2000 07:52:06
>
>Please respond to RPG400-L@midrange.com
>
>To:   RPG400-L@midrange.com
>cc:    (bcc: STEVEN J RYAN/DIAU)
>
>Subject:  Y2.1K Compliance
>
>
>
>
>Has anyone had a request to make their databases/programs Year 2100
>compliant?   We've got a healthcare company requiring this in a contract and
>I'm not sure how to respond.  We use 8-digit date fields, so I don't see a
>problem, but I'm not sure how to prove it.  Are there any standards being
>set in the legal/contractural community on this?

--
| Internet: david@midrange.com
| WWW: http://www.davids-place.net
|
| On a cellular level, I'm really quite busy.

+---
| 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
+---