RE: Error handling between ILE modules

May not be an exact fit, but the CEE4RAGE program may suit your need. Scott
has done some articles that involve this, so a web search should yield nice
fruit.

In a nutshell, CEE4RAGE designates a procedure that will be called when the
activation group ends (your program could specify ACTGRP(*NEW)), no matter
how it ends. So my thought is that the procedure designated by call to
CEE4RAGE could be the one-stop-shop for program exit, sending messages and
so on when appropriate.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Appeasers believe that if you keep on throwing steaks to a tiger, the tiger
will become a vegetarian."
-- Heywood Broun

I have a new ILE program composed of a CLLE driver module and multiple
(SQL)RPGLE modules. It implements a one-way process over data for
first-of-the-month processing; we are automating a manual process. If
an
error should occur in any of the modules, I would like control passed
to a
module to perform cleanup (displaying the job log, send an email, start
ended subsystems) and abort the program.

What is the best way to go about this? Do I need to write an exception
handler and attach to each module?

Thanks,
Loyd
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.