Connection TIMEDOUT error with ODBC connection -- MIDRANGE-L

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

> I have an ODBC connected application that I occasionally get a "Connection
> TIMEDOUT" error (TCP/IP 10060 error).  I am trying to determine where the
> problem lies. It is either a network congestion problem (the iSeries is
> about 20 miles away over a WAN connection) or a QSERVER subsystem
> performance issue.  I just don't know how to go about diagnosing the
> problem.
> 
> I searched through the archives and found a few references to ODBC and
> performance but nothing that indicates what is optimal on the iSeries.
> This is a model 800 with 2GB memory, 140GB storage (at 16%) running
> V5R2M0.  CPU currently shows 1% utilization (middle of the day, all users
> actively logged in).  The QZDASOINIT job shows a priority of 20 and a
> timeslice of 3000.  This guy looks plenty robust enough to handle the load
> of two or three ODBC connections and the job run priorities look plenty
> generous.  I suspect network congestion but the network guys say they are
> only peaking at 800-1000 kbps on a 1.5 kbps T1.
> 
> Any suggestions?
> 
> Pete Helgren
> Timpanogos Technologies, Inc
> 
>

This mailing list archive is Copyright 1997-2025 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.