Re: ERRMSGID and screen refreshing

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Chris,

That's the way ERRMSG, ERRMSGID, SFLMSG, and SFLMSGID were designed.  They use 
the PUTOVR and OVRATR options 
under the covers and just send the new data for the error msg and attribute 
byte to the screen.  No other 
screen data will change.

They only work if there has been no intervening WRITE to a different record 
format.

Your suggestion of writing once to update the data and writing again with the 
error indicators on will work 
but you could try coding PUTOVR at the format level and OVRDTA on the fields 
you want updated.  Condition them 
with the same error indicator (or a generic one which is set whenever an error 
indicator is set).

Caveat: I didn't check the DDS Reference for keyword dependencies.

I usually find ERRMSG, ERRMSGID, SFLMSG, and SFLMSGID keywords to be a royal 
pain for many reasons 
(requirement of same format on screen, separate indicator for each error 
message, etc, etc, etc) and use a 
message subfile and the QMHSNDPM API or SNDPGMMSG from a CL utility program.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
//--- forwarded letter -------------------------------------------------------
> Date: Wed, 10 Feb 99 12:37:44 +0000
> From: Chris.Chambers@v2music.com
> To: midrange-l@midrange.com
> Reply-To: MIDRANGE-L@midrange.com
> Subject: ERRMSGID and screen refreshing

> I am developing an application using the ERRMSGID keyword on screens
> accessing message files with the ERRSFL keyword for each screen file.
> 
> However on error processing whenever an indicator is set to flag an errror
> and written back to the user none of the output fields already changed by
> the controlling program (COBOL) are shown - (only when all fields are
> without error is the true state of the screen file redisplayed).
> 
> SO. . . . .is there a DDS keyword which will ensure that all of the screen
> along with the error message is displayed OR
> do I really have to write the screen twice - once with no errors set (to
> refresh) and then once with the error switches on (assuming this would
> work).
> 
> Any advice, as always, gratefully received.
> 
> Chris

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