On Wed, Sep 2, 2015 at 4:13 PM, James Rich <james@xxxxxxxxxxx> wrote:
Thankfully we are on V5R4, so I will look at STRWCH.

I guess you could be thankful that you're not on V5R2 or something,
but most of the folks on this list would not be thankful to be on
V5R4. ;)

On Wed, Sep 2, 2015 at 4:16 PM, James Rich <james@xxxxxxxxxxx> wrote:
On Wed, 2 Sep 2015, Buck Calabro wrote:

A possible alternative is to MONMSG (ie trap the error), in the DO()
send the email and then re-throw the exception.

I thought about this but couldn't come up with a satisfactory way to do it.
Many programs are called during the execution of the daily close and I'd
want execution to stop at the original point of execution of the error.

Gary gives some example code for using the approach Buck describes,
applied to all CPF and MCH errors anywhere in the CLP.

Others have mentioned using system APIs if you are up for rolling your
own monitoring program. This is the approach we took. You don't even
have to be good at coding API calls because there are ready-made
examples on the Web that you can simply tweak to suit your needs. Ours
is adapted from

http://www.code400.com/forum/showthread.php/1123-Use-the-QUSLJOB-API-to-whip-thru-WRKACTJOB

We set ours up to run periodically throughout the day.

John Y.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].