Re: File Open Error in a Service Program

["Buck" <buck.calabro@xxxxxxxxxxxx>]

> You have two nice tools, the (e) extender, and the MONITOR opcode.

Raul is exactly right.  If you are still using RPG III, put an indicator in
the LO columns to be informed of the error.  Basically, the idea is to do
something like

open(e)   somefile
if        %error
...

I make it a habit to check for errors after every I/O operation.  Not every
error is something like 'record in use' or 'object allocated.'  Sometimes
you encounter actual damage.  You need to check the file and program status
in the feedback areas to be sure of the error you are handling.  The error
handling chapter of the RPG Reference (File and Program Exception/rrors) is
a good place to look for details, and the archives of this list may help as
well.  I'm pretty sure that Simon Coulter posted an example of the file
information feedback structure D-specifications.
  --buck