× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Y2.1K Compliance
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Wed, 29 Nov 2000 11:19:53 -0800
  • Organization: Pacer International

If you are storing the date as cyymmdd you are not using OS400's native
dates, so it doesn't matter.

Windowing is only used for some date validations.  It should not play a
part at all in 8 digit dates (0001-01-01 is a valid date).  It would definitely
play a role in 6 digit dates (01/01/29.  Is that 1929 or 2029?  Currently, 
it would be 1929.  When the window moves, the OS would interpret it as 2029.
It would not become invalid, just wrong.)

Can this be a problem?  Definitely.  How do we fix this?  Couple of ways.

1. Don't use OS400's date validation programs.
2. Store dates in native OS400 format
3. Store dates in 8 digit form CCYYMMDD

Tell me, though, how are you currently interpreting CYYMMDD yourself?  Are you
using CHECK?  Are you using date functions?  Or are you using all home grown
functions?

Regards,

Jim Langston

Peter Dow wrote:
> 
> Hi Jim,
> 
> Of course, if they do that, anyone who's using cyymmdd to store dates may
> have a problem at that time. If you have a date stored as 0290101 and the
> window moves up, what does that date represent? Currently it would be
> 1929-01-01, but if the window moved, the year is below the window for the
> 20th century. Suddenly the data is invalid?
> 
> Regards,
> Peter Dow
> Dow Software Services, Inc.
> 909 425-0194 voice
> 909 425-0196 fax
> 
> ----- Original Message -----
> From: "Jim Langston" <jimlangston@conexfreight.com>
> To: <RPG400-L@midrange.com>
> Sent: Tuesday, November 28, 2000 10:28 AM
> Subject: Re: Y2.1K Compliance
> 
> > My assumption is that IBM in later versions of the OS will move the window
> > around to reflect the current time period.  So though the window is
> currently
> > 1928 to 2071, around 2040 or so IBM should change it to 1980 to 2110.
> > Programs should not need changing.
> >
> > Although this does mean your current OS version is going to become
> obsolete.
> >
> > I guess we will have to upgrade past V3R7M0 at that point <grin>
> >
> > Regards,
> >
> > Jim Langston
> >
> > Peter Dow wrote:
> > >
> > > Just to add confusion to the issue, AS400 command parameters with type
> *DATE
> > > have the following help text:
> > >
> > > ---
> > > The parameter value is a character string that
> > > represents a date.  When entering the command, the
> > > year may be specified with either 2 digits or 4
> > > digits.
> > >
> > > If a 2-digit year is specified, the date is
> > > assumed to be in the range of January 1, 1940 through December 31, 2039.
> > >
> > > If a 4-digit year is specified,
> > > the date may be in the range of August 24, 1928 through May 9, 2071.
> > >
> > > When it is passed to the command processing program, it is always passed
> in
> > > the format Cyymmdd, where C = century, yy = year, mm = month, and dd =
> day.
> > > The century digit is set to 0 (zero) for years 19xx, and it is set to 1
> > > (one) for years 20xx.
> > >
> > > ---
> > >
> > > Note that even though you can specify a 4-digit year, you may not
> specify a
> > > date past 05/09/2071.
> > >
> > > Looks like commands with *DATE type parameters aren't Y2.1K compliant.
> > >
> > > 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
> > +---
> 
> +---
> | 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.