Re: 30 year mortgage vs Y2K

I suppose that changing those values can result in compatibility problems
for a lot of shops. Maybe submitting a DCR with the suggestion of including
a *DTAARA for the year range would help. That said, maybe the fastest
solution would be creating your own CVTDAT command with the already
mentioned *DTAARA. If present or value <> 40 , run your code. If not, run
the old cmd.

HTH,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Fri, Jun 4, 2010 at 11:08 AM, <rob@xxxxxxxxx> wrote:

Ok, some company tried using the technique below:

From the help on CVTDAT on 7.1

Only valid dates can be converted. If either the from-format or the
to-format use only 2 digits to specify the year (for example, *MDY,
*DMY, *YMD, or *JUL), valid dates are in the range of January 1,
1940, to December 31, 2039. Otherwise, valid dates are in the range
of August 24, 1928, to May 9, 2071. If the year is specified with
only 2 digits, years in the range of 40 to 99 are assumed to be 1940
to 1999; years in the range 00 to 39 are assumed to be 2000 to 2039.
The command works in conjunction with the QLEAPADJ system value.

However, 30 year mortgages are now hitting that wall.

Yes, they should use real date fields.

Any place to set a sliding scale to move that up a bit until they fix it?
Like change the cutoff from 40 to 50 or 60?



Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.