Re: How to debug client server applications?

Buck & Chris,


Chris Bipes wrote:
> 
> Well IF you were writing your own server, you could log the connect reqeust
> to the server with the client IP, Computer Name, User Profile, Date/Time
> Stamp, Job Name/Number/User processing the request.  You can then query the
> file to find the current locked request and work with that job.  Perhaps a
> direct socks application to perform the SQL statement and return the data
> instead of OBDC.  AS far as tracking IBM server for processing OBDC request,
> see if there is an exit point that can trap and log the necessary available
> data.

The QIBM_QZDA* exit points will show you which user is using a
QZDASOINIT job at a particular time.  But depending on which ODBC
request you are processing, the user could be accessing anyone of
seven of these exit points.  

You could fairly easily write one or more exit programs that will
trap the data that comes through this exit point and log the
information to a file for later perusal.  It would then just be a
matter of querting the file by user, or (???) to get information
that you needed.

Or you could just download the free part of PowerLock from
www.400security.com and let it do the logging for you.  PowerLock
logs events realtime, and will track actual ID's and link them to
the requests that are coming through.  The logging part is free,
and we've received positive feednback about it's use as a Client
Server debugging tool (even though it was originally written with
security in mind).

hth,

jte



--
John Earl                               johnearl@400security.com
The PowerTech Group                     206-575-0711
PowerLock Network Security              www.400security.com
--


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---