Re: Trapping RI constraint errors in RPGLE programs

First the foundations
"RPG: Exception and Error Handling"
http://www.redbooks.ibm.com/abstracts/redp4321.html?Open

Next: a specific method of handling constraint/trigger errors.
"Handling Constraint Violations in RPG"
http://www.itjungle.com/fhg/fhg021710-story01.html

Basically, instead of naming your constraint DETAIL_FK_HEADER, you name it
DETAIL_FK_HEADER_ERR0100

Where ERR0100 is a message ID whose text you can retrieve to provide
specifics about the condition the constraint is checking.

There's a couple other options mentioned in the above article. But the
above method is what the author goes into detail about.

Charles


On Wed, Nov 11, 2015 at 12:32 PM, Gad Miron <gadmiron@xxxxxxxxx> wrote:

Hello everyone

I'd like to test and see for myself the implications of adding
some "modernizing" DB RI constraint .
especially what RPGLE error trapping methods is needed
(like in cases of say, inserting a record into a sales file with
non-existing customer)

can you refer me to relevant publications
and/or to a real-life examples?

TIA

Gad
--
This is the RPG programming on the IBM i (AS/400 and 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.