RE: Constraint Violations

Its an ILE SQL RPG program. All it is, is a wrapper around the message
handling APIs. I enhanced it to handle the SQL0530, SQL0545 and SQL0532
differently. Made it into a service program and all the other programs just
use the procedures. But I am sure you can modify the code to handle for a
different message Id.


-----Original Message-----
From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
Sent: Wednesday, October 03, 2001 12:40 PM
To: rpg400-l@midrange.com
Subject: RE: Constraint Violations


>But if you are using SQL, I can send you our standard message
>handler that
>does this. It looks for 3 sql error messages - REf. Cst, Chk.
>Cst and the
>trigger error. IF any of these exist, it retrieves the column
>descriptions
>and sends a message to the stack level that you request.

I should have been more specific.  In native I/O, put an indicator on the
WRITE or UPDATE in the error column. Or use %error in RPG IV.  You then have
trapped the I/O error that occurs.  Then it's up to you to deal with it
however your program sees fit.

Is the "standard message handler" mentioned here an RPG program or CL?  Does
it only check for 3 messages, or is that just a subset of it's capabilities?
  --buck
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.