Help asked for 00D3003B reason code
chris
I wonder if you could assist me with solving the following problem.
The thing is that we are trying to develop a program in Visual Basic that
would select data from DB2 on MVS platform using ODBC connection or OLE DB
connection.
Everything works fine in the sense that we are able to establish connection
from WinXP VB client using DB2 UDB driver and we receive data. But for large
tables, after some time, connection brakes and we receive status code and
DB2 MVS send reason code 00D3003B.
The description of this code is quite clear, in the sense that it refers to
DSNZPARM parameter IDTHTOIN, that relates to IDLE THREAD TIMEOUT value.
According to the manual, the solution to avoid this reason code would be to
set this parameter to a higher value or to disable timeout processing
altogether.
But this is not what we are looking for. We are looking for possibility of
sending SELECT statement from VB client once and receive all the records
from the table as the response. Actually, there are no new requests coming
from client side to DB2 MVS server side, that is making the thread dormant,
but only seemingly. In fact, the client is receiving consecutive records
from DB2 and this is its active state manifestation.
I would be wondering how otherwise we could address the problem of thread
timeout in this scenario? Would it be that we have to somehow artificially
brake the connection with DB2 and throw SELECT statement periodically to DB2
so as not to run a risk of getting 00D3003B reason code and thread
termination?
How this problem is solved in case of some replication data utilities?
Any explanation would be appreciated.
Regards,
Krzysztof Krajewski
Jan Csisko
the Multi-Tier ODBC components provided by OpenLink allow you to
manually set certain time-out variables so that you can specifically
configure your connection to the amnount of data you would expect to
be retrieved.
The components are available at http://www.openlinksw.com. I assume
you can run
a simple test by creating a DataSource with the same name as it is
being implemented within your VB Application.
Hth,
Regards,
Jan
"chris" <chri...@mop.gov.kw> wrote in message news:<bacrdd$4qne$1...@news.boulder.ibm.com>...