|
Brian: Two thoughts come to mind... First, you might investigate STRDBMON and the info that the database monitor can preserve. While not as real-time as debug, it _should_ show you the actual SQL statement that was executed. Second, you might review the listing of the program that comes out of the preprocessor. Numerous variables are generated that can be discovered in the listing. The calls to the system SQL routines all need parms passed in and variables are created for those parms. It probably won't be the statement itself, but you can find DSs in the listing that bring all the various host variables together in a structure. No reason jumps out why you couldn't see those DSs in debug. Tom Liotta midrange-l-request@xxxxxxxxxxxx wrote: > 3. RE: Returning Passed SQL Statements from Debug (Brian Piotrowski) > >That's what I thought. It's rather unfortunate, really. Ohwell. > >Thanks for the comments, all. > >-----Original Message----- >From: Michael_Schutte > >I've never seen a way to view the way you are asking about it. Here >are >the variables that SQL defines...
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.