|
Scott, I think that is the answer. Thanks. -----Original Message----- From: Scott Mildenberger [mailto:scottmildenberger@xxxxxxxxx] Sent: Tuesday, March 09, 2004 1:32 PM To: RPG programming on the AS400 / iSeries Subject: Re: whats the difference on this update. Is the key on the logical such that there are records with the same key? I assume the logical on the test file was the only logical existing. The logical on the production file is probably sharing another access path that forces the order of the records to use more fields than the key on the logical being used. The field you are changing is probably one of these additional ordering fields caused by the access path sharing so it is acting like you are actually changing the key fields. I'm not sure that is a clear description above :) but it is saying that the production file is sharing a different access path than the test file which is causing the problem (my guess anyway). Scott Mildenberger --- "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx> wrote: > A coworker has come to me on this and I don't have the answer. Here > is the situation > > a copy of a production physical was created in test library via CPYF. > Logical was built over the copied file. > Program does a read loop on the file updating records in the > test > library. The program updates as desired. > > Same program over the production file when it updates a record, > proceeds to read the same record again. > The field that is being updated is not one of the key fields. > > > I have verified the logical in test and the logical in production are > the same. > > The only real difference i can find in the physical file is that the > production file is journaled. Could this be the cause? > There is only 1 copy of the program. > __________________________________ Do you Yahoo!? Yahoo! Search - Find what you're looking for faster http://search.yahoo.com _______________________________________________ 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.