RE: Error handling between ILE modules

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Loyd,

I would look at either coding a *PSSR routine (what we currently use here), or using a handler (what I'd like us to be using).

CEE4RAGE may not be what you want depending on how you handle the message.  If the program could end but the activation group stay active your exit program won't get called until the activation group is ended.

Monitoring in a CL might do it if you are using a wrapper.

Take a look at the CEEHDLR, CEERTX, and CEEUTX API's.  One of these might be what you are looking for.  I have been experimenting with them in my spare time but haven't come to a definitive decision on how best to use them yet.  I can tell you that CEERTX is called after a message has been answered so if you want to act on an error without user intervention this one isn't the one to use.

As I mentioned previously, our shop is using *PSSR subroutines in our code.  We have a program that is called which prints a current screen shot and sends an e-mail to a table driven list of recipients.  A dump is coded into the subroutine immediately after the call.  The screen capture code was taken from an article by Jon Paris.  I don't remember where but I'm sure a Google search would find the article.

If you haven't already, search the RPG list archives in midrange.com.  This topic has been discussed several times on that list.

HTH,

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Loyd Goodbar
Sent: Wednesday, September 01, 2010 2:42 PM
To: Midrange Systems Technical Discussion
Subject: Error handling between ILE modules

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

Privileged and Confidential.  This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information.  If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail.  You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.