|
Define them as any format you want. It's the INZ that has the problem Neil Wood Programmer Analyst IBM Certified Specialist -----Original Message----- From: David Prowak <prowakd@emi.com> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Date: Thursday, July 23, 1998 3:22 PM Subject: Re: DATFMT >Paul, >Maybe I'm missing the point here, but this from the ILE RPG/400 Reference >Manual: > >3.2.2.7 DATFMT(fmt{separator}) > >The DATFMT keyword specifies the internal date format for date literals and >the default internal format for date fields within the program. You can >specify a different internal date format for a particular field by >specifying the format with the DATFMT keyword on the definition >specification for that field. > >Doesn't this say that I should be able to define a standalone field, with a >date format >other then that of the default format for this module? > >Dave > >---------- >> From: Paul Tuohy <tuohyp@ibm.net> >> To: MIDRANGE-L@midrange.com >> Subject: Re: DATFMT >> Date: Thursday, July 23, 1998 1:56 PM >> >> David, the format for ALL date literals is as per the H Spec, which >defaults to >> *ISO. So, you either put a DATFMT(*ISO) on the H Spec or change the INZ >to >> (D'13/06/1991'). >> >> But it would be a lot neater if it worked as you wished. >> >> HTH >> >> Paul Tuohy >> >> >> David Prowak wrote: >> >> > 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 >> > +--- >> >> >> >> >> +--- >> | 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 >> +--- >+--- >| 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 >+--- >
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.