|
No, the data was not going to the wrong files. But I was think that was only because no records matched. For instance, it fills each divisional PLLINE first, then each divisions PLLINE2. It filled the PLLINE correctly. But when it tried to fill the PLLINE2 the records didn't match because it was using the wrong divisions PLLINE. Maybe it was doing something complex because of the subselect or the concat's and that is when against the wrong path. If it was a logical file issue then we would have to have a join logical in each divisional file that joined their PLLINE file back to the VDLINE file back in the central library. And cross library logicals are everyone's idea of a good time, right? Rob Berendt ================== A smart person learns from their mistakes, but a wise person learns from OTHER peoples mistakes. "Joe Pluta" <joepluta@PlutaBrot To: <midrange-l@midrange.com> hers.com> cc: Sent by: Fax to: midrange-l-admin@mi Subject: RE: SQL vs V5R1 and service woes drange.com 09/11/2001 05:11 PM Please respond to midrange-l > -----Original Message----- > From: rob@dekko.com > > The insert was pretty raw and did no ORDER BY or GROUP BY. How would the > logicals help? I misunderstood. I thought perhaps the data was coming FROM the wrong files. I didn't realize the INSERT was misdirecting the data TO the wrong files. This is particularly nasty, but I can see why it might be done in order to boost performance of the INSERT. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.