Re: Catching errors on user screens

Simon,

>Here is the core of such a function. You can add whatever additional 
functions 
>you need (e.g., issue a DUMP, DSPJOB * *PRINT, DSPJOBLOG * *PRINT, page 
someone, 
>send a message, display a friendly error screen, etc.) Use the F-spec 
INFSR 
>keyword to set the *PSSR as the file error handler.

one more question (or two). If I want to catch all file errors, I'll have 
to code
INFSR for each and every file? Or is there a possibility to declare this 
for all 
files?

We have 20+ (sometimes 60-80) files in some programs, and that would be 
lots of work.

Generally, it would be enough for us if we could force a dump on each 
error and send
a message somewhere. There are only very few situations where I can 
continue the crashed
program.

Thanks,

Oliver