|
Thanks for checking on that for me. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com |-----------------------------+-------------------------------------------| | "Paul Tuohy" | | | <tuohyp@xxxxxxxxxxxxx> | | | Sent by: | To| | rpg400-l-bounces@midrange.| "RPG | | com | programm| | | ing on | | 07/19/2004 01:22 PM | the | | | AS400 / | | Please respond to | iSeries"| | RPG programming on the | <rpg400-| | AS400 / iSeries | l@midran| | <rpg400-l@xxxxxxxxxxxx>| ge.com> | | | cc| | | | | | Subject| | | Re: | | | Opinions| | | on | | | determin| | | ing | | | which | | | constrai| | | nt | | | | | | | | | | | | | | | | | | | |-----------------------------+-------------------------------------------| Hi Rob, I wish - butI don't think so :-). The INFDS has the CPF502F message Id in it. The PSDS contains the first level message text (which simply says "Check constraint violation on member xxxxxxxxxx") but the constraint name is in the second level message text. Since the constraint name can be very long, I'm not sure where it would fit in either of the DS's :-) Thanks Paul ----- Original Message ----- From: <rob@xxxxxxxxx> To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> Sent: Monday, July 19, 2004 4:23 PM Subject: Re: Opinions on determining which constraint > Rather tangential, but instead of retrieving messages from the calling > procedure message queue, will not just checking the PSDS or the FINFDS > give you the constraint name? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Paul Tuohy" <tuohyp@xxxxxxxxxxxxx> > Sent by: rpg400-l-bounces+rob=dekko.com@xxxxxxxxxxxx > 07/18/2004 05:45 PM > Please respond to > RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> > > > To > <rpg400-l@xxxxxxxxxxxx> > cc > > Subject > Opinions on determining which constraint > > > > > > > Hi All, > > I am looking for opinions/comments on how people identify which constraint > caused a file exception error. > > For the sake of brevity, let's just deal with check constraints. Here is > what I am currently doing. > > My program traps errors using the (E) extender on writes, updates etc. > > If there is an error with a status of 1022, then a procedure is called > which retrieves messages from the calling procedure message queue until it > gets message CPF502F. > > I then scan the message data looking for the constraint name - I have a > naming convention that all constraint names start with CHECK_ . I am not > ecstatic about using a naming convention to identify constraints. > > I don't want to "hard code" the starting position of the constraint name > in the message data - it may change in the future. > > Does anybody have a different approach? > > TIA > > Paul Tuohy > -- > This is the RPG programming on the AS400 / 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. > > > -- > This is the RPG programming on the AS400 / 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. > -- This is the RPG programming on the AS400 / 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.
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.