Re: Custom MONTITOR handling

I'd think you might have at least three design choices here. 
 
One would be to offer up the error message within the the piece that finds
the error.
 
Another would be to generate a universal error subprocedure for your shop
that can be used everywhere to handle all errors.
 
 A third way might be to design and error data structure and pass that data
structure up and down the stack, filling and emptying it as is appropriate.
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Thursday, April 17, 2003 15:33:39
To: rpg400-l@xxxxxxxxxxxx
Subject: Custom MONTITOR handling
 
Is it possible to "throw" custom messages from a subprocedure?
 
That is, I have a program called ShowCust. It has a bit of code which looks
like this:
 
/Free
openBalance = getOpenBalance( myCustNo );
monitor:
on-error ????;
// handle customer not found
on-error;
// handle other errors
end-mon;
/End-Free
 
getOpenBalance() is another procedure that accesses a file via SQL, and
calculates the current open balance. I'd like it if it could throw an
exception message if the customer isn't found, the customer number is
invalid,
etc.
 
Any ideas?
 
Thanks
 
-Doc