FW: errmsgid keyword--unexpected results

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

Thanks to Charlie and Simon.  

Looks like the work around that did it for me was to put a write in the
procedure that sets on the error indicator.  

The other thing I'm curious about is documentation.  I spent a fair amount
of time looking at both the DDS manual and the Display Programming manual.
Is this covered in the parts related to PUTOVR et. al.?  I didn't think to
look there.

-----Original Message-----
From: Charlie_Massoglia@common.org [mailto:Charlie_Massoglia@common.org]
Sent: Wednesday, July 11, 2001 5:39 AM
To: Joel Fritz
Cc: Simon Coulter
Subject: Re: errmsgid keyword--unexpected results




Simon's explanation in a subsequent response that ERRMSG and ERRMSGID use
PUTOVR, OVRATR, and OVRDTA under the covers is correct but there is a very
simple circumvention.  The first time you display the screen do a WRITE of
the
record format before doing an EXFMT, e.g.

C                                          EVAL        ERRMSGIDINDICATOR =
*ON
C                                          IF                FIRSTTIME = 'Y'
C                                          WRITE     SCREEN2
C                                          ENDIF
C                                          EXFMT     SCREEN2

I'm in Singapore right now on my way to Interaction Australasia and could
not
send a response directly to Midrange-L for some reason.  I'd appreciate your
forwarding this response to Midrange-L in case anyone else runs into the
same
problem.

Thanks.

P.S.  Simon, will you be at Interaction Australasia?

----- Original Message -----
From: "Joel Fritz" <JFritz@sharperimage.com>
To: "RPG400-L@midrange. com (E-mail)" <RPG400-L@midrange.com>
Sent: Tuesday, 10 July, 2001 11:57
Subject: errmsgid keyword--unexpected results


> I'm working on a screen where the user will key in one of several possible
> search arguments to bring up a pick list.  To make it simpler, lets call
the
> arguments e-mail and name/zip.  I'm lazy, so I used the errmsgid keyword
on
> the e-mail and name/zip fields.  Each is conditioned by a separate
indicator
> and uses the same indicator as the response indicator.
>
> The logic is pretty simple.  Try to build a pick list.  If no records are
> written to the subfile, build the error message text and turn on the error
> indicator.
>
> The name/zip error checking works fine.  Every time the attempt to build
the
> pick list fails, the message appears on the message line.  The e-mail
> argument only works if the first e-mail argument entered gets no hits.  If
> the error occurs after a successful attempt to build a pick list based on
> the e-mail argument, nothing happens.
>
> I ran it in debug.  The indicator goes on when the error occurs and stays
on
> right up the exfmt.  I put a text literal on the screen that only appears
> when the error indicator is on. That works just fine.
>
> The code for calling the two error messages is (famous last words)
> identical.  The DDS for the screen fields is identical.  I'm going nuts.
I
> can always put the error on the screen a different way, but I really like
> using ERRSFL and system error checking because I've never had to spend
much
> time on it 'til now.
>
> Any ideas?

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