Re: DATFMT

["Neil Wood" <neil@xxxxxxxx>]

When using INZ:

The constant being specified must be consistent with the type being
initialized. The
constant can be a literal, named constant, figurative constant or built-in
function.

When initializing Date or Time data type fields or named constants with Date
or Time
values, the format of the literal must be consistent with the default format
as derived
from the Control specification, regardless of the actual format of the date
or time field.

The Date field can be initialized to *SYS or *JOB. The Time and Timestamp
field can
be initialized to *SYS.

Workaround:

Hence avoid the INZ in the Data specification unless it coincides with the
default date format you are using.  Looks like MDY for you.  Instead move
the value in during your *INZSR.


                MoveL    '91/164'         SURCH_DATE

Neil Wood
Programmer Analyst
IBM Certified Specialist


-----Original Message-----
From: David Prowak <prowakd@emi.com>
To: midrange list <midrange-l@midrange.com>
Date: Thursday, July 23, 1998 12:41 PM
Subject: DATFMT


>Hi,
>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 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
>+---
>

smime.p7s