× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: DATFMT
  • From: Paul Tuohy <tuohyp@xxxxxxx>
  • Date: Fri, 24 Jul 1998 00:47:20 +0100

David, Neil just said it. You can specify any DATFMT for the date field, but the
literal in the INZ keyword must conform to the DATFMT on the H Spec ( default
*ISO ).

Ain't it a bummer.

Hans identified the reasoning behind it. But I think it is six of one and half a
dozen of the other ;-).

Paul Tuohy

David Prowak wrote:

> 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
>



+---
| 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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.