We are in the midst of implementing an error management piece that uses:
(a) ILE condition handlers are exception handlers that are registered at run time using the Register ILE Condition Handler (CEEHDLR) bindable API. They are used to handle, percolate or promote exceptions.
(b) The exceptions are presented to the condition handlers in the form of an ILE condition. You can register more than one ILE condition handler. ILE condition handlers may be unregistered by calling the Unregister ILE Condition Handler (CEEHDLU) bindable API.
These will allow you to capture and process the error.
We are also using IBM API QtmmSendMail to send mime capable email from this procedure.
Some references:
Who Knew You Could Do That with RPG IV?
A Sorcerer's Guide to System Access and More
Brian R. Smith, Martin Barbeau, Susan Gantner,
Jon Paris, Zdravko Vincetic, Vladimir Zupka
International Technical Support Organization
SG24-5402-00
RPG: Exception and Error Handling
Redpaper
Gary Mullen-Schultz, Susan Gantner,
Jon Paris, Paul Tuohy
REDP-4321-00
WebSphere Development Studio
ILE RPG Language Reference
Version 6, Release 1
SC09-2508-07
IBM i Information Center -
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/index.jsp
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Sent: Thursday, February 25, 2010 8:34 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Uncaught Errors in Interactive Programs and the Users that Ignore the Errors
I am growing tired of this. An error pops up, the user hits 'C' to cancel
the program then tries again. Maybe this time it worked, so they continue on
with their job. The next day, "Why is my data not here?" So now we have to
back out the changes to allow them to reprocess the data so it runs
correctly.
I am sure I am not unique in this situation. No amount of drilling in to
them will get them to call us when there is an error. They are just drones
doing what their job is.
So, I know there are a few methods out there on how to "fix" this problem
(so we know about the problem so we can fix the edge-case bug). I am
thinking I would like to send an email to both developers with the job log
when such errors happen. By the time we get the email, it may be too late,
but at least we have something logged.
How would you handle this?
--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark
midrange.com
