Re: File Open Error in a Service Program

[Raul A Jager <raul@xxxxxxxxxx>]

You have two nice tools, the (e) extender, and the MONITOR opcode.  They 
will trap the error and your program can do anything you want:  retry, 
send a message, send an e-mail, end, etc.

djobe@xxxxxxxxxxxxxxx wrote:

> We have a situation where a program calls a procedure in a service program.
> This procedure does a usropn on a file for update.  The file was
> exclusively allocated and caused the procedure to end abnormally.  The
> error provided by the calling program was "error occurred in procedure x (C
> S D F)".  In the job log we found the file was allocated.  The only choice
> was to cancel in the middle of processing which was very bad in this
> instance.  In the old RPG program calls another RPG program world, we would
> insert a CL in the middle, which would then give the ability to retry the
> failing call.
>
> I'm looking for solutions on how anyone else has handled this situation.
> Our initial thought was to check for an error and call a procedure to issue
> a message to qsysopr to allow for a retry.  Then the service program could
> retry the open after any file issues have been resolved.
>
> Donnie Jobe
> Retail Team Leader
> O'Reilly Auto Parts
>
>
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>