|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Buck, I think you are on the right track however I disagree with your methodology. Instead of adding yet another chain, (with it's potential for corrupting the input buffer, unless you prefix, etc), shouldn't we be evaluating the failure on the WRITE? For example, as a community we will be adding lots of stuff to files: - unique logicals, (in this case) - referential constraints - etc What I am saying is that you should just do the write with the E extender, evaluate the error condition and process accordingly. Perhaps this would be a good candidate for the new Monitor function. Anyone care to whip up an example of using it to process write errors? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Buck Calabro <Buck.Calabro@commsoft.net> Sent by: rpg400-l-admin@midrange.com 10/03/2002 12:31 PM Please respond to rpg400-l To: rpg400-l@midrange.com cc: Fax to: Subject: RE: Adding records to a file >Next question: If I change the LF to eliminate >the word UNIQUE, I will need to recompile it >and all the programs that use it, correct? You will need to recompile the LF, but this change will not result in a level check error for existing programs referring to it. I strongly suggest you carefully think about removing the UNIQUE constraint. I would rather add the LF to the program throwing the error, CHAIN to see if the proposed record is a dupe and printing the exception on a report. --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.
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.