We switched to using this API to send error messages successfully. We decided not to try and fill the subfile, because most users only look at the one being displayed. So, whenever we encounter an error, we loop back to display the screen (and any errors). One thing we had to do was use the overlay keyword on the control record (for a subfile) and the screen format (for just a plain screen) otherwise the error would flash and then dissappear. A simple example of how we use it is this...

Cdow(W$KEY <> f3)
CCALL'SNDPM'WPMSG
CEXFMTSCR01
CevalWPMSID = 'INV0001'
 *other code
Cenddo

the program call to SNDPM displays any error message shown. The WPMSG parameter list includes message id, message data, message file name, and message file library. We created message ID INV0001 as a blank record to clear any messages after they are displayed. Hope this helps.

---

The ERRSFL can only be used ERRMSG, ERRMSGID, SFLMSG, SFLMSGID, and the display file validity checking keywords. If I were you, I would continue to use the Message subfile and QMHSNDPM. It gives your program far better control over error handling. It is a very telling example that message subfiles are what IBM uses for all its displays.

---