× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I don't think that will be captured by a monitor group ever.

What you could do though is have a *PSSR subrutine in the code that would handle all un-monitored errors. Mine is setup to capture joblogs and a program dump, and then email them to our Operations group.

J

On 4/23/2020 9:43 AM, Martin Neugebauer via RPG400-L wrote:
Sorry, my subscription had to be confirmed.Now i am a proud member of the list.
Please let my request pass.
All the best, Martin


Am Donnerstag, 23. April 2020, 16:08:35 MESZ hat Martin Neugebauer <neugebauer_m@xxxxxxxxx> Folgendes geschrieben:
Hi everybody.
In my RPGLE programs i use a monitor group around my code to handle *PROGRAM type errors, (e.g. divide-by-zero).
I do not want to handle *FILE errors (at this point), so i can not use ON-ERROR *ALL.
Now i discovered that MCH3401 (can not resolve to object) on a dynamic program call can not be trapped by MONITOR .. on-error *program?!
Note that MCH3401 (by the name of it) is a PROGRAM exception.
The errorstatus (which i debugged by use of the %STATUS function) is set to 9999, therefore can not be monitored.
If i code
    ON-ERROR 9999;
it won't compile ("not a valid status code")
This must be a bug, i think.
How can i get MCH3401 handled in my monitor group?


PS. We are on Power8 with V7R3
Thank you all for your advice & best regards, Martin Neugebauer


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.