Re: Y2.1K Compliance -- RPG400-L

I beg to differ.  Our current system is only good until 2079.  We are using
a 1980 to 2079 window (company founded in 1981).  Any system that uses 
windowing will have difficulties unless the window is adjusted periodically.

Since we are not planning on using our current home grown system for even anther
year, it becomes a pretty mute point to us.  But not to others.

I think we have seen that we can not count on programs not being used for a 
certain length of time.  How many managers/analysts/administrators didn't worry
about the Y2K problem (which any decent programmer knew about from day 1) 
because
they felt their system wasn't going to be used for that long anyway, so why 
bother
to code it in.  

I had pointed it out to my boss back in 1990 that there was a Y2K problem, and 
asked him what he was going to do about it.  Being a programmer he was totally 
aware of it and knew that it would cause problems, but justified it, to himself
anyway, that it would force his customers to upgrade when he did fix it (one of
the reasons I stopped working for this employer).

If you used windowing, you will have a problem.  If you use native OS/400 dates,
you shouldn't have a problem.

Regards,

Jim Langston

STEVEN.J.RYAN@denso.com.au 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?
> 
> Nelson Smith
> DBA Team
> (727) 530-7700 ext. 243
> (800) 284-2006
> 
> 
>************************************************************************************************************************************************************************************************************
> 
> This message originates from Lincare Holdings Inc. It contains information 
>which
> maybe confidential or privileged and is intended only for the individual or
> entity named above.
> It is prohibited for anyone else to disclose, copy, distribute or use the
> contents of this message.
> All personal messages express views solely of the sender, which are not to be
> attributed to Lincare Holdings Inc., and may not be copied or distributed
> without this disclaimer.
> If you received this message in error, please notify us immediately at
> MailAdmin@lincare.com or (800) 284-2006.
> 
>************************************************************************************************************************************************************************************************************
> 
> +---
> | 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
> +---
+---
| 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
+---