Re: Condition handlers

["M. Lazarus" <mlazarus@xxxxxxxx>]

Pete,

At 9/19/00 09:25 AM -0500, you wrote:
>You set the 'rc' token  to CEE_HDLR_RESUME rc is passed as the third parm of
>your handler procedure. After setting this and returning from your handler,
>execution continues from the next statement after the statement that raised
>the exception.

  OK, this is good.

> > 2)  How would you identify in the CH which field contains the error?  This
> > is an issue, since the record contains many numeric fields that can
> > potentially have an error.  Also, the idea is to avoid putting all the
> > extra error checking in the mainline program after each calc.
>
>This is down to your code !, But the second parm passed to your handler
>procedure can be a pointer to anything. You could set this up to point to
>the data, where the handler could then examine it.

  Can an operational descriptor be used too?  That would enable some degree 
of flexibility.  How do I determine what the name of the field is, so it 
can be looked up in a rules table and then checked / modified to suit?


> > 3)  Once control is returned to the program, does the CH need to be
> > registered again?  Or is it still active in order to trap the next error?
>
>They remain active until you issue the unregister CEEHDLU API

  Is this scoped to the program or the activation group?

  Thanks!

  -mark

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