Re: Specifying dates in DDS

Your choice is settled then.  Use the L date field.  
It solves issue #1. 
It removes the need for issue #3.  
That leaves all of your energy for the 99/99/99 and 00/00/00 problem.

In <199803171117.FAA29848@uucphost.mcs.net>, on 03/17/98 
   at 10:59 AM, neil.williams@pocruises.com said:

>What if;
>     
>     1) The database is accessible stateside and in Europe, and each 
>     location wants the dates displayed as 'native' e.g. MMDDYY stateside

>     and DDMMYY in Europe.
>     
>     2) There are special dates in the RPG part of the application (e.g. 
>     99/99/99 and 00/00/00.
>     
>     3) We want to write 'Date Engines' for all our date 
>     handling/validation, and these must comply with 1) above.
>     

-- 
-----------------------------------------------------------
boothm@ibm.net
-----------------------------------------------------------

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@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
+---