|
Exactly! Here's the statement I have: C/Exec SQL C+ update ssw85 set kdlotstr=(select min(dskdlf) from sst01 where C+ dsotyp=:ordertyp and dsodno=:ordernum) C+ , kdlotend=(select max(dskdlf) from C+ sst01 where dsotyp=:ordertyp and dsodno=:ordernum and C+ dsspcd=:supp and dssplc=:supploc), asnnum=(select distinct C+ asno from sst02 where C+ asodtp=:ordertyp and asodno=:ordernum C+ and asplcd=:plantcde and asspcd=:supp C+ and assplc=:supploc) where ordertyp=:ordertyp C+ and ordernum=:ordernum and C+ suppcode=:suppcode C/End-Exec I want to run an EVAL on this statement after it executes to see exactly what was passed instead of EVAL DSKDLF, EVAL ORDERTYP, EVAL ORDERNUM, etc... Brian. -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: Tuesday, March 21, 2006 10:00 AM To: Midrange Systems Technical Discussion Subject: RE: Returning Passed SQL Statements from Debug I think I understand now. So, it's not a prepared statement or an executed immediate statement; it's more like a execsql select thisfield, thatfield from myfile where otherfield=:hostvar1 and yaddafield between :this ...; and you want to see what that looks like, right? Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.