Re: SQL procedure trace -- MIDRANGE-L

Subject: Re: SQL procedure trace
From: Pete Helgren <pete@xxxxxxxxxx>
Date: Wed, 22 May 2013 07:48:36 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Mike,

It's been a while since I used the IBM i ODBC driver but can't you initiate that at the client end? Seems like there were some trace or debug options on the connection properties. Maybe not what you were looking for but it would be one option I can think of.....

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java

On 5/21/2013 8:41 PM, Mike Cunningham wrote:

Is there a way to turn on a trace for a call to a DB2 stored procedure (all SQL - no RPG) coming from an external server running a perl app on a linux server connecting using the IBM iSeries ODBC driver.

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.