×
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.
Peter.Colpaert@xxxxxxxxx wrote:
...
Taking into account that INFSR is not supported in *NOMAIN modules and
procedures, I have the following question.
Is this keyword useful in this day and age, or can we simply remove it
where not supported, and move on?
I think that the most useful feature of the INFSR is that it prevents an
inquiry message being issued for an unhandled exception due to an
unexpected error on a file op that didn't have (E) or error-indicator or
MONITOR.
But inquiry messages are only issued for RPG main procedures. For
subprocedures, unhandled exceptions just cause the procedure to be taken
off the program stack, and the exception to be percolated.
If your INFSR code just does ENDSR *CANCL, you can probably just remove
them without any worries. If they have anything more complicated, you
might need to move some of the code into a procedure that you call from
your ON-ERROR handling in your subprocs.
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
