Re: Use of Timestamp data field How? Is IBM Y2k Compliant 1940 Onwards?

Hi, Kris:

> Thought I'd be Y2k Compliant and created timestamp field in data file.
>Since I added the field and did a CHGPF based on source did not loose any
>data. However the field was initialized to 0001-01-01-000 etc.

Yes.  INLVAL() could (should?) have been used to initialize this.

> First problem, could not figure out how to define the stamp to be
>displayed. So defined a date type field and Time type filed.

This would be correct.

>Did a MOVE of Timestamp to date type field.
>
> Program fell over.... Date has to be within 1940 to 2039 range. Error
>message was pretty explicit about this..  What goes... Yes timestamp
>will when program is live be in the correct
>range, but it does raise questions about the Move operation?

What questions does it raise, Kris?  This is a documented limitation for a
date field.

Dennis
--
Dennis Lovelady                    Simpsonville, SC
mail: dennis@lovelady.com
URL:  http://lovelady.piedmont.net
ICQ:  5734860
--
"Too bad all the people who know how to run the country are busy driving
taxis and cutting hair."
        - George Burns


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