RE: Display Screen problem

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>would PUTOVR/OVRDTA work in the example I am trying 
>to do? If so could you please provide me with an example 
>to resolve this.

I guess I wasn't very clear (not the first time!)

ERRMSG _is_ doing a PUTOVR.  That's what's causing your observed behaviour.
The system sends out only the error message and the attributes to reverse
image/position cursor.  It doesn't send out the rest of the screen.  That's
why your other attribute changes aren't happening.  ERRMSG is specifically
designed to behave this way.

If you want to set other attributes, you'll have to take another approach.
Never tried it myself, but you might consider:
1) detect error
2) set "other" attribute indicators, etc.
3) WRITE (with FRCDTA?) the display format so these attributes get set on
the display
4) set ERRMSG indicator
5) EXFMT to display the error message, lock the keyboard, etc.

Alternately, you could forego ERRMSG altogether and do all the processing it
does yourself.  You'd have to add DSPATR(RI PC) for each field you want to
process in this way, and LOCK on the record format.

Finally, you could change the error processing to use an error message
subfile.

Buck 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---