Re: File Exception/Error Subroutine - INFSR

[Barbara Morris <bmorris@xxxxxxxxxx>]

Dan wrote:
>
> I guess the bigger question was whether you can explicitly call the
> file's INFSR subroutine and expect the same behavior as if RPG itself
> called it.  I.e.:
>

Dan, it depends.  If you code a factor 2 on the ENDSR of your INFSR, or
if you send an escape message from your INFSR, then it will behave the
same for EXSR as it does for an exception. Otherwise, EXSR behaves like
an ordinary EXSR and ENDSR returns to the next instruction after EXSR,
but going to the INFSR from an exceptions causes an RPG inquiry message.

I think it's best to use (E) where an exception is expected, and use an
INFSR with '*CANCL' on its ENDSR for unexpected errors.  (Even if you
send an escape message from your INFSR, coding '*CANCL' is an extra
belt-and-suspenders ensuring that the program won't continue after the
INFSR runs.)

By the way, to use the *PSSR for both program and file errors, just code
INFSR(*PSSR) on your F specs.