Condition handlers

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

Hi all,

  I have a few questions about ILE condition handlers.

   As part of a retail POS (point of sale - cash register) system, we are
receiving oddly formatted data.  Sometimes it's invalid and an EVAL might
generate an overflow condition.  One idea was to use a condition handler
(CH) to trap the error condition.

1)  After a CH fires, can it fix up the data in the field in order to
allow the program to continue properly?  If yes how?  I assume it can be done
via pointers.

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.

   I'm aware of the performance implications of allowing a CH for this, but
if the data is 99.9% clean, then I *think* it will be more costly for all
the testing required for each field.

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?

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