|
Thanks for the sanity check Simon. The file uses a traditional iSeries delete scenario, no funny stuff with inserting nulls or flagging of records. I was able to get all the locks away from the file last night and re-organized it. I also see the IBM APAR database is loaded with fixes for this particular message pattern I am seeing on this file. Regards, Mike Shaw -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter Sent: Monday, August 30, 2004 11:46 PM To: Midrange Systems Technical Discussion Subject: Re: iSeries Deleted Record Question On 31/08/2004, at 6:36 AM, Mike wrote: > My question is this: Does a record that is deleted constitute a NULL > value > in the file? The file in question is showing 4 deleted records. I > keep > seeing a CPF5009 message (duplicate record key in member) in job logs > that > touch this file. No, a deleted record is deleted and no longer in any index. Of course if your application doesn't really delete but flags records as deleted by setting some flag field to a magic value then the record still exists and will be in an index and could cause duplicates. The same is true if your application tries to set the fields of deleted records to null either explicitly or via a constraint. The message indicates that an application tried to add a new record with a key that matches an existing record, or tried to update the key fields of an existing record such that they match another existing record. The second level text of the message tells you which records are the culprits so you can determine what the key values are by examining the existing record. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ -------------------------------------------------------------------- -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.