Re: Date Validation

FWiW: That _functional_ effect [i.e. '5/7/2012' recognized as being a valid *USA formatted character date string] was described as an anomaly that should not be depended upon... by Barbara Morris:
http://archive.midrange.com/rpg400-l/201203/msg00323.html

The documentation referenced in my message [above link; quoting Barbara's] has not changed to suggest anything different in the equivalent documentation for v7r1:

IBM i 7.1 Information Center -> Programming -> Programming languages -> RPG -> ILE RPG Language Reference -> Definitions -> Chapter 9. Data Types and Data Formats
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzasd/sc092508283.htm#ddate
"
_i Date Data Type i_

Date fields have a predetermined size and format. They can be defined on the definition specification. Leading and trailing zeros are required for all date data.
...
"

Regards, Chuck

On 30 May 2012 09:45, Scott Mildenberger wrote:

Paul, Your right that it works fine when you have Date_in defined as
10A but the original post had it defined as varying 256A and that
does not work - I even tried %trim on Date_in. So, I get the error
with the following definition

D Date_in S 256A Varying inz('5/7/2012')

Beyond me to explain!
Paul Therrien on Wednesday, May 30, 2012 10:21 AM wrote:

I tried this code and it worked for me with V7R1.
Input parm of '5/7/2012' or '5/07/2012' or '05/07/2012'
CALL PGM(TESTRPG) PARM('5/7/2012')
CALL PGM(TESTRPG) PARM('05/7/2012')
CALL PGM(TESTRPG) PARM('5/07/2012')

dtestrpg PR extpgm('TESTRPG')
D Date_in 10A

dtestrpg PI
D Date_in 10A

D Date_Out S 8 0
D Date_Outc S 25a

Date_out = %uns(%char(%date(Date_in:*usa):*iso0));
Date_outc = %char(%date(Date_in:*usa):*iso0);