|
It would be nice if at run time the system could recognize *loval equalivence between different date formats and convert accordingly. If I move a *ISO *loval to *MDY field I would expect a *MDY *loval of 01/01/40 from 0001-01-01. joeM ----- Original Message ----- From: "Bob Cozzi" <cozzi@xxxxxxxxx> To: <RPGIV@xxxxxxxxxxxxxxx>; "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx> Sent: Friday, January 28, 2005 11:47 AM Subject: Why RPG IV Sucks > 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. >
As an Amazon Associate we earn from qualifying purchases.
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.