Re: Convert from free to fixed

I've used Cancel Handler (CEERTX/CEEUTX) in some of the programs that must
perform cleanup when it is ended (normally or abnormally). I have never use
conditional handler before. Google for CEEHDLR or CEEHDLU and you should be
able to find some doc on them.

Here is the IBM link:
http://publib.boulder.ibm.com/infocenter/iadthelp/v6r0/index.jsp?topic=/com.ibm.etools.iseries.pgmgd.doc/c0925076251.htm


<vforbes@xxxxxxxxx> wrote in message
news:mailman.3118.1285794011.2702.rpg400-l@xxxxxxxxxxxxxxx

I would like to learn more about the "condition handler". Can you give me
more info about this. {examples, links}

Vincent Forbes

... monitor is your friend

and a condition handler is your BEST friend.

The *PSSR subroutine is archaic and not a good solution when managing
application errors that run on a web server. I
would strongly suggest using condition handlers for this as you have MUCH
more control over how to proceed. Further,
*PSSR is an 'after the event' clean-up routine. Not only has the
exception been thrown but it has percolated to the
control boundary, promoted to a function check (CPF9999) and the
condition manager is now looking for somebody to
shoot.

Condition handlers beat monitor because monitor will handle any exception
thrown within the monitor group. Condition
handlers work even better than MONMSG because you can choose to handle
the exception based on any criteria you wish.
Also, the condition handler is called BEFORE the original *ESCAPE or
*NOTIFY message has reached the control boundary
so the call stack is pristine. You can write code in your condition
handler to pause the process so you can debug the
problem. I have been able to recover from divide by zero, substring
length and array index errors this way. The
process continues from the next line of code as if nothing went wrong.
You can't beat that!

I genuinely believe it is one of the many unsung heros of ILE.

Cheers

Larry Ducie