RE: ERRMSGID and screen refreshing

["Christopher J. Jewell (Jewell Consulting)" <jewellcj@xxxxxxxxxxxxxxxxx>]

Chris

I would suggest using a message subfile instead.

This would allow you to rewrite the screen and message together.

In the DDS, you set up the message subfile and then in the program you
simply send the message as an informatonal message to the programs message
queue using a call to a CL which does a SNDPGMMSG of the message (set up as
a Message Description in a message file). You also need to control clearing
the program's message queue by calling your CL with a special value for the
message id of *CLR, lets say, which will do a RMVMSG instead of a SNDPGMMSG.
Obviously you would externalize as much of this as possible to a procedure
in a service program.

Hope this helps

Chris Jewell


> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of
> Chris.Chambers@v2music.com
> Sent: Wednesday, February 10, 1999 4:38 AM
> 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
>
>

Christopher J. Jewell.vcf