Re: Why RPG IV Sucks

I have had the same problem.  I don't see why 0001-01-01 doesn't
translate to 01/01/01 in *MDY format without sqwuaking.  If you use
two digit years to display, you are obviously aware that nobody knows
the first two digits of the year, so 01 might represent 1901, or 2001,
or 9901...

I suppose if you convert a *ISO date to *MDY, then back to *ISO,
somewhere a decision must be made as to the century, but why would you
want ot do that anyways?


On Fri, 28 Jan 2005 11:47:14 -0600, Bob Cozzi <cozzi@xxxxxxxxx> wrote:
> Okay maybe I'm a bit cranky.
> 
> Scenario:
> 
> DSPF DDS contains  a date field with DATFMT(*MDY)
> 
> Compiled RPG IV that uses that display file is called.
> Write to the display file with that date field, BOOM!
> Why?
> Because the RPG IV converts the date from the display file into *ISO within
> the program.
> RPG IV also initializes date fields in *ISO format to D'0001-01-01'
> This date however is NOT valid for *MDY so I end up wth:
> RNQ0114 -  Message . . . . :   The year portion of a Date or Timestamp value
> is not in the correct range (C G D F).
> 
> -Bob
> 
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
> 


-- 
"Enter any 11-digit prime number to continue..."