RE: Service side ODBC trace

[Mike Cunningham <mike.cunningham@xxxxxxx>]

Thanks Charles. Somehow missed that option.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, April 13, 2010 9:26 AM
To: Midrange Systems Technical Discussion
Subject: Re: Service side ODBC trace

Mike,

STRCMNTRC should handle it...

There's a CMNTRCOPTS(*RMTIPADR) and the RMTIPADR parameter you can use
to limit the trace to packets sent to a specific remote address.

Charles

On Tue, Apr 13, 2010 at 8:06 AM, Mike Cunningham
<mike.cunningham@xxxxxxx> wrote:
> Is there any way to setup a server side trace of ODBC communication and have it trace just requests from a single username? We are having intermittent problems with ODBC requests coming from a linux machine that uses an open source ODBC driver and a unique username for ODBC requests. Other ODBC requests coming from Windows applications that use the Client Access ODBC driver do not have this problem. And we have tons of other traffic coming over the same NIC as the ODBC requests and it does not look like STRCMNTRC can select on username or even type of traffic.  Even if I could trace on single port I could keep the trace data manageable but that does not look like an option either.   Joblogs for QZDASOINIT do not show much of anything.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.