×
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've stumbled across the CALL(E) opcode in a couple of very old programs.
If I were to use CALL(E) instead of a MONITOR group then I would check
%error() and %status() afterwards, but in these particular two programs
there is no such check. (No %error/%status, monitor group, or *PSSR
routines anywhere in the call stack.)
Basically, the program is inhibiting all errors from the called program.
I am still confused though. A user is telling me their screen is
unexpectedly returning to the menu for no reason. I check the joblog and
there are no escape messages listed. Would the CALL(E) prevent the called
program's error messages even appearing in the joblog?
-Paul.
As an Amazon Associate we earn from qualifying purchases.
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
