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