A date data type is a date data type period. The formatting (*ISO, *USA,
*MDY...) apply only to the mask used to interpret the format of the
input/output to the field. Think of it as having a default edit code. On
your display/printer file you may use an edit code/word on a 8P 0 field, but
do you ever concern yourself about what that edit code is when you are using
it in the calc specs? 
As far as DATFMTs that mask part of the full date format field (*MDY,
*YMD...) you only need to understand that you can only enter dates within
the allowed date window either through the display or programmatically.

In your case I would try this, define the date in the display file as
specified earlier, with an L data type and a DATFMT(*MDY), then in the RPG
define the same field with as standalone with a DATFMT(*ISO). If it compiles
your done. If not change either the standalone field or display field and
move the date appropriately to and from the display.

Duane Christen
 



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.