×
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.
Let's say I have an RPGPGM1 that does the following...
monitor;
RPGPGM2();
on-error;
// check %status();
end-mon.
It is my understanding that if RPGPGM2 pgm fails, then our %status will
only report a 202 and will not give us the details as to why.
Is there anyway in RPGPGM1, to get the exact reason why RPGPGM2 failed,
without adding a msg parm on RPGPGM2 and bubbling the message up?
thanks
Jay
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.
midrange.com
