Re: Open Explicit -vs- Open Implicit

[Barbara Morris <bmorris@xxxxxxxxxx>]

On 3/22/2012 11:12 AM, Rory Hewitt wrote:
> ...
> But basically, yes, if specified, the INFSR will get control if an implicit
> file open error occurs. Not that you can do much at that point, except
> handle the error 'gracefully'...

The INFSR will get control for an implicit file _close_ but not for an 
implicit file _open_.

This program gets an inquiry message, not a DSPLY from the INFSR.

     Fmyfile    if   f   10        disk    extfile('NOSUCHFILE')
     F                                     infsr(infsr)
      /free
         *inlr = '1';

         begsr infsr;
            dsply 'in the infsr';
         endsr;

So, if there's a possibility of an error during the implicit open, use 
USROPN. If it's a cycle file, check in advance for potential errors in 
the calling program.