*DATE data type on a DSPF

We're at V4R2M0 (finally) and have begun putting *DATE's on display
files.  Everything's working fairly well except for a couple of issues
we've encountered.

The first issue is:  If a user enters an invalid date on a screen, data
management issues an error and the user presses the reset key.  So far,
no problem.  If the user corrects the date and presses enter,
everything's fine.  However, if the user simply presses F3 or F12 to
return to previous screen or program, the program dies with an RNX0112
(Date, Time or Timestamp value is not valid.).  Very strange.

The second issue is:  the MAPVAL keyword is not working correctly.  When
the screen comes up, the correct value is displayed, but unless the user
makes any kind of entry on the screen, the MAPPED VALUE does not get
returned to the program.

We're working w/ IBM right now on the first problem but not getting too
far.  Anyone else using the *DATE data types on DSPF's with any similar
problems?

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