× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



P6Spy may also help, it's free.

tballen@xxxxxxxxxx wrote:

> The DBMON is not really an option since the job is created only after
> the JDBC connection is made and then the job disappears after it is
> closed.
>
>
> At 04:04 PM 10/7/2005, Franco Biaggi wrote:
>
>> tballen@xxxxxxxxxx wrote:
>>
>> > I really just want to be able to see the actual statement in the
>> > debugger.
>> > In my case I am using WSAD.
>> >
>> > I did not see any variables that showed the SQL statement after the
>> > parameter substitution took place.
>> >
>> > Am I missing something?
>> >
>> > Thanks,
>> > Todd
>> >
>> >
>> > At 06:31 PM 10/6/2005, you wrote:
>> >
>> >> Try running a database monitor (STRDBMON)
>> >>
>> >> -----Original Message-----
>> >> From: java400-l-bounces@xxxxxxxxxxxx
>> >> [mailto:java400-l-bounces@xxxxxxxxxxxx]
>> >> On Behalf Of tballen@xxxxxxxxxx
>> >> Sent: Thursday, October 06, 2005 5:05 PM
>> >> To: Java Programming on and around the iSeries / AS400
>> >> Subject: Display a prepared statement
>> >>
>> >>
>> >> Is there a way to display an SQL prepared statement after the
>> >> parameter placeholders have been replaced with actual values?
>> >> I have not seen anything while debugging.
>> >>
>> >> Thanks.
>> >
>> >
>> >
>> Hi,
>> after starting the DB monitor,
>> you can look the generated statements (and some useful informations)
>> with the iSeries Navigator.
>
>
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.