RE: How to debug client server applications?

But your package sounds like what we may need IF we decide to open our OBDC
servers to non in house programs.  Currently no-one has anything but read
access to all our files.  I saved your original response for future
reference. 

Thanks a bunch.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000


-----Original Message-----
From: John Earl [mailto:johnearl@400security.com]
Sent: Wednesday, May 10, 2000 1:27 PM
To: MIDRANGE-L@midrange.com
Subject: Re: How to debug client server applications?


It is a bit tricky, because different ODBC drivers will use
different IBM servers.  Most use the DRDA server, which only let's
you see the SQL connect statement, not the individual SQL (SELECT,
UPDATE, etc) data manipulation statements.  This is a problem
because the names of the objects being operated on is not readily
available to an exit program.

The IBM ODBC driver generally goes through the Native DataBase
server, though there are some other servers it uses (RTVOBJINF,
SQLSRV, etc.)  It all depends on what information your ODBC
request is asking for (did you just SELECT, or have you asked to
browse a list of files before choosing the file you want to
operate on).  

The problem with trying to map these servers is that they are
organized more for the benefit of the programmers who wrote the
servers as opposed to being written for the benefit of the
programmers who will use the servers.  You really have to spend
some time with them to get a picture of what each server does, and
how it proposes to do it.


jte
+---
| 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
+---