Re: EXCEPT & *PSSR

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

One simple approach is simply to designate the PSSR routine as an INFSR for the file(s) in question.


Jon P.

> On Feb 8, 2023, at 4:31 PM, Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:
>
> I retrofit an old program with a *PSSR to serve as a generic error
> handler.  Today, the program encountered a duplicate key error on an EXCEPT
> to a program-described file.  It raised an unhandled exception without
> hitting the *PSSR.
>
> Is there a way to get the *PSSR to handle this?  The program is rife with
> unnamed EXCEPT conditioned on a large number of different indicators, and
> I'd rather not have to trap for exceptions on every EXCEPT.
>
>
> TIA
> -- 
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.