× 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.


  1.  Home
  2. RPG400-L
  3. November 2002

RE: File Exception/Error Subroutine - INFSR

>Carrying this a little further.  Let's say there's
>a chain / read on an update file, and there's a
>record lock condition.  Can I check %status
>right after the chain or read and, if %status =
>1218, process option_to_retry routine;
>otherwise EXSR the file's INFSR?

Sure.  The only thing I use the INFSR for is a post-mortem DUMP and to
signal the caller that this program failed.  It's a catch-all for trapping
those exotic errors that are highly unlikely.  In fact, I rarely have
separate INFSR's - I point them all to the *PSSR.
  --buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.