|
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.