Re: DATFMT

Dave wrote
>I keep getting this compile error:
>
> D  SURCH_DATE     S               D   DATFMT(*JUL) INZ(D'91/164')
>                                                        a
> 5 20 a      000140  The value D'91/164' is not a valid *ISO- Date literal.
>
>This will compile if I use a control spec to change the default date format
>for the entire module, but I shouldn't have to do that.  I thought that I
>could define the date format for a field specifically, regardless of the
>default date format.
>I'm on V3R2, QDATFMT = MDY.

Dave:  This is working as designed.

The format of all date literals within the program is
based on the DATFMT keyword you specify on the H-Spec,
not on the DATFMT keyword on the D-Spec.  If the DATFMT
keyword is not specified on the H-Spec, the default
format for date literals is *ISO-.

Just code your date literal in *ISO- format and it
should work fine.

Why was it designed this way?  This forces all date
literals within a program to be coded with a
consistent format.  This way, you don't have to worry
about the format when assigning a value to a date
field.

BTW, why aren't you using a 4 digit year?

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---