× 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.



Oliver

If you have Support Line, have IBM look at the comm trace - that's the
fastest way to do it. Just make it a level 2 or 1 problem, so the good guys
will look at it.

I've looked at various comm traces and am willing to look at yours. Or at
least show you what I'd look for. Contact me offline (507 287-8119 x111)
and we can discuss it.

Regards

Vern

At 07:05 AM 11/13/2002 +0100, you wrote:
Hello,

well, I'm still fighting with this ODBC application. Thanks for the manual
tips, so far.

I've now pinned it down to the following behaviour:

Throughout the whole day, single records are retrieved and updated -
basically this means
writing two stati (start process, end process).

In addition, every 2 minutes a series of select count(*) is run:

        select count(*) from vrosif
        select count(*) from vrosif where sistat='40'
        select count(*) from vrosif where sistat='41'
        select count(*) from vrosif where sistat='43'
        select count(*) from vrosif where sistat='45'

I have PowerLock security auditing installed and this gives me a report of
all ODBC sql
statements received by the AS/400.

This report shows me that the AS/400 does only some of the select count(*)
commands and
then the connection is restarted - I have no idea what is causing this?
It could be a bug in the application, the ODBC driver or the AS/400
returning something
unexpected?

The main problem is, this is a production system and very important for
our daily operations.
So I can't play around with this Win2K PC too much.

I've tried the ODBC trace utility of Client Access - but this is just a
stupid joke. Half an hour
of trace gives about 4 meg of text file with absolutely no timestamp! And
the trace seriously
slows down the ODBC connection.

So, my main questions are:

-  Anybody know a decent ODBC trace utility for a Win2K pc?
-  I can do a communication trace of the problem, but have no idea how to
read it. Would
anybody on the list care to take a look? I'd just want to know who breaks
off the
connection?

thanx,

Oliver



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.