Re: VARPG in conjunction with DB2 Constraints

One technique I found to be almost "required" to prevent hard errors on
constraints, is to also put triggers on the files looking for the same
errors the constraint will pick up.  The trigger error gives you a chance to
handle the error "softly" before it gets to the constraint.  All this is at
the database level, of course, and has nothing to do with what language(s)
are being used.


-----Original Message-----
From: flagler@timken.com <flagler@timken.com>
To: CODE400-L@midrange.com <CODE400-L@midrange.com>
Date: Friday, January 21, 2000 4:30 PM
Subject: VARPG in conjunction with DB2 Constraints


>
>
>
>
>
>
>
>FROM: FLAGLER  KEENE     Flagler, Rick: Manager, IT
>
>DATE: JANUARY 21, 2000
>SUBJECT: VARPG in conjunction with DB2 Constraints
>
>
>Has anyone used VARPG to update databases which have Referential
>constraints or Check constraints? I'd like to create my future DB files
>using these new technologies. I have been able to trap the error in my
>VARPG program, but I can't get an english langauge description of which
>REFCST or CHKCST field has triggered the DB add/update failure.
>
>If I use a DFU to do the same adds or updates, DFU catches the failures
>and shows a message with somewhat legible reasons. If I could get at
>these messages in VARPG, perhaps the constraint name at least, then I
>could tell the user what's happening rather than just display a message
>box saying "sorry, something is wrong with your input". If VARPG can't
>get at this from the INFDS File Feedback information area, then maybe
>alternatively I could call a CL to get it from the Job Message Queue some
>how? VARPG will certainly have this ability in a future release if not
>already, right? Any thoughts on this would be appreciated. Thanks. RF
>
>------------------------------
>Rick Flagler
>Manager, IT
>Timken Super Precision (MPB)
>Keene, NH
>
>

+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---