RE: *ISO dates, DATFMT, DSPF's, program recompilation required

All dates are *ISO (program and database); *USA is for show only.  I assumed
the WS controller or some piece of under-the-covers code (external to the
application) handled date conversion.  Examples: the timestamp data type
actually only takes 10 bytes but always shows 26 characters; a
variable-length field always shows its full length even if it's empty.

If changing the date data type format is cosmetic, then changing the DSPF
only should have sufficient (but it wasn't).
If changing the date data type format is > cosmetic, it should have signaled
CPF4131 (but it didn't).

-----Original Message-----
From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On
Behalf Of jt
Sent: Thursday, December 20, 2001 1:11 PM
To: midrange-l@midrange.com
Subject: RE: *ISO dates, DATFMT, DSPF's, program recompilation required

Reeve,

I've been wanting to experiment with this myself, but haven't yet.

Just a guess:  is the field named on the display also a DATFMT(*USA) in the
RPG program.  I'm wondering if the RPG field is DATFMT(*ISO), the default.

Just a swag.  I'll be watching this thread...

jt

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.