|
Joe, Let me sharpen up the sample. I have a file called VDLINE2 in ROBDIVF. Based on which division makes the part, parts from this file will go to one of the following files: ROBAVIF/PLLINE2 ROBKVLF/PLLINE2 ROBRMCF/PLLINE2 ... The insert was pretty raw and did no ORDER BY or GROUP BY. How would the logicals help? C/EXEC SQL C+ insert into plline2 C+ (select * from vdline2 C+ where (vdlpo concat h2item) C+ in (select (pdlpo concat plitem) from plline)) C/END-EXEC 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 03:50 PM Please respond to midrange-l > -----Original Message----- > From: rob@dekko.com > Fails on succeeding rounds. The failure is deemed to be because of how > imbedded SQL, under V5R1, fails to properly handle the new libraries. > Something about QDT and/or ODP. Ouch. Do you have logical files in place that mirror the requirements? If not, maybe you could crwate them. Then perhaps the SQL preprocessor would then select the correct logical rather than using a dynamic ODP that it erroneously thinks is correct. Just a shot in the dark, Rob. This sounds painful. _______________________________________________ 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.