Re: L-date field again

Booth:

The L date field is very picky.  You need to move the correct date into it.   
For
example if the L date is *ISO then you need to move 19971226 into it.  If it is
*USA, then you move 12261997 or *DATE into it.  If you are using RPG/400, then
you need to use CVTOPT(*DATETIME) on CRTRPGPGM and then the dates will be pulled
into your program as character fields.  This means you need to insert the 
editing
symbols like -,/ etc.  However, if you use ILE/RPG, then all the work is done 
for
you.  The only thing is to move the correct type into the date field.  The nice
thing is if you are moving a L date into another L date field, the system will
correctly transform the dates.  HTH


boothm@ibm.net wrote:

> OK, so I like the L-date field idea.  I tried it out in a few places.  Its
> nice.  I decided to put it in all new files as part of the time-date
> stamp.
>
> Now, one of these new files will have records updated in an existing RPG
> program.  I tried    C      MOVE UDATE     DATEL
>
> It compiles with a warning message about the LDATE field being ignored.
>
> Have I missed something simple and basic?  How can I access this field,
> update it, etc.?
>
> ----------------------------------------------------
> Booth Martin
> ---------------------------------------------------
>
> +---
> | 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
> +---



--
Thank You.

Regards

Dave Mahadevan.. mailto:mahadevan@fuse.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
+---