timeout using SDK 2.81 TC3 - .NET Managed Provider

Discussion:

(too old to reply)

-=Eric=-

2004-09-14 02:55:25 UTC

We have a showstopper issue...after upgrading from SDK 2.7x to 2.81
TC3 (to get the .NET managed provider), we're occasionally running
into timeout errors in .NET applications. Specifically, the.NET code
is throwing this:

Error Message :
ERROR [HYT00] [Informix][Informix ODBC Driver]Timeout expired.
ERROR [HY008] [Informix][Informix ODBC Driver][Informix]Statement
interrupted by user.
Stack Trace= at Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr
hHandle, SQL_HANDLE hType, RETCODE retcode)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior
behavior, String method)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery()
at OurCompany.WWWServices.Methodname(XmlNode inputDoc)
Source=iclit09b.dll

I've been unable to figure out, either in the documentation or on the
'net how to change the default timeout. I think it might be possible
within the code, but this is a major problem - we're not about to go
revamp our entire codebase.

If anyone has seen this or has suggestions, we're all ears. So far,
we've tried inserting various things into the connection string,
setting the CONTIME and CONRETRY environment variables in SetNet32.

Our platform is Informix 9.4O with application servers running Win 2k
and Win2k3 server.

Tsutomu Ogiwara

2004-09-14 07:13:05 UTC

Permalink

Hi Eric.

Make sure SQL_QUERY_TIMEOUT of SetStmtOption in M$ .NET manual.

I am not Windows familiar, sorry I can say the avobe all.
--
Tsutomu Ogiwara from Tokyo Japan.
ICQ#:168106592

Subject: timeout using SDK 2.81 TC3 - .NET Managed Provider
Date: 13 Sep 2004 19:55:25 -0700
We have a showstopper issue...after upgrading from SDK 2.7x to 2.81
TC3 (to get the .NET managed provider), we're occasionally running
into timeout errors in .NET applications. Specifically, the.NET code
ERROR [HYT00] [Informix][Informix ODBC Driver]Timeout expired.
ERROR [HY008] [Informix][Informix ODBC Driver][Informix]Statement
interrupted by user.
Stack Trace= at Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr
hHandle, SQL_HANDLE hType, RETCODE retcode)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior
behavior, String method)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery()
at OurCompany.WWWServices.Methodname(XmlNode inputDoc)
Source=iclit09b.dll
I've been unable to figure out, either in the documentation or on the
'net how to change the default timeout. I think it might be possible
within the code, but this is a major problem - we're not about to go
revamp our entire codebase.
If anyone has seen this or has suggestions, we're all ears. So far,
we've tried inserting various things into the connection string,
setting the CONTIME and CONRETRY environment variables in SetNet32.
Our platform is Informix 9.4O with application servers running Win 2k
and Win2k3 server.

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8.
http://join.msn.com/?page=features/junkmail

sending to informix-list

-=Eric=-

2004-09-16 02:51:48 UTC

Permalink

Apparently, this issue affects the .NET Managed Provider as well as
ODBC. The new driver works correctly, but there's been a change in
the default behavior. Previously, in SDK 2.7, commands did not time
out by default. Now in 2.81 TC3, commands time out after 30 seconds.

The big problem with this is that you must explicitly set the command
timeout in your code. If you have a large installed base of code
already, that's a lot of re-factoring, re-testing, and re-deploying
just to upgrade the driver.

And there appears to be no way to globally change the default timeout
value. If we could set the value to 0 (no timeout), then at least the
new driver's basic behavior would match the old one and save us a lot
of headache.

Post by Tsutomu Ogiwara
Hi Eric.
Make sure SQL_QUERY_TIMEOUT of SetStmtOption in M$ .NET manual.
I am not Windows familiar, sorry I can say the avobe all.
--
Tsutomu Ogiwara from Tokyo Japan.
ICQ#:168106592

Sathyanesh Krishnan

2004-09-15 19:51:48 UTC

Permalink

--0__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791
Content-type: multipart/alternative;
Boundary="1__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791"

--1__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable

Hi Eric,

Most probably this may be due to the CommandTimeoutt value, by default =
it
is 30 sec.
(Microsoft.Data.Odbc.OdbcCommand.CommandTimeout )
A value of 0 indicates no timeout limit, and will wait indefinitely.

By default the .Net application expects a query to be finish with in 30=

second.
In case if an application issue a query that take more than 30
then the application should explicitly set an appropriate time out valu=
e.

Dim myCommand As New OdbcCommand
myCommand.CommandTimeout =3D 0

Regards,
Satyan

Software Engineer
R&D - IBM Data Management Group
11200 Lakeview, Lenexa, KS 66219
Tel: 913 599 8792 (T/L: 337-8792)

=

Abhishek =

Mathur/Lenexa/IBM =

=
To
09/15/2004 12:35 Sathyanesh =

PM Krishnan/Lenexa/***@IBMUS =

=
cc
=

Subj=
ect
Fw: timeout using SDK 2.81 TC3 -=

.NET Managed Provider =

=

=

=

=

=

=

Hey Satyan,
Did you have a chance to look at this in the IIUG?

Cheers,
Abhi
--------------------------------------------------------------------
There are 10 kinds of people,,,,,
.... those who understand binary notations, and those who don't.
--------------------------------------------------------------------

----- Forwarded by Abhishek Mathur/Lenexa/IBM on 09/15/2004 12:34 PM --=
---
=

***@fakeisp.net =

(-=3DEric=3D-) =

Sent by: =
To
owner-informix-li informix-***@iiug.org =

***@iiug.org =
cc
informix-***@iiug.org, =

owner-informix-***@iiug.org =

09/13/2004 09:55 Subj=
ect
PM timeout using SDK 2.81 TC3 - .NE=
T
Managed Provider =

=

Please respond to =

***@fakeisp.net =

(-=3DEric=3D-) =

=

=

We have a showstopper issue...after upgrading from SDK 2.7x to 2.81
TC3 (to get the .NET managed provider), we're occasionally running
into timeout errors in .NET applications. Specifically, the.NET code
is throwing this:

Error Message :
ERROR [HYT00] [Informix][Informix ODBC Driver]Timeout expired.
ERROR [HY008] [Informix][Informix ODBC Driver][Informix]Statement
interrupted by user.
Stack Trace=3D at Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr=

hHandle, SQL_HANDLE hType, RETCODE retcode)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior
behavior, String method)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery()
at OurCompany.WWWServices.Methodname(XmlNode inputDoc)
Source=3Diclit09b.dll

I've been unable to figure out, either in the documentation or on the
'net how to change the default timeout. I think it might be possible
within the code, but this is a major problem - we're not about to go
revamp our entire codebase.

If anyone has seen this or has suggestions, we're all ears. So far,
we've tried inserting various things into the connection string,
setting the CONTIME and CONRETRY environment variables in SetNet32.

Our platform is Informix 9.4O with application servers running Win 2k
and Win2k3 server.
=

--1__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
Hi Eric, 
 
Most probably this may be due=
to the CommandTimeoutt value, by default it is 30 sec. 
(Microsoft.Data.Odbc.OdbcComm=
and.CommandTimeout ) 
A value of 0 indicates no tim=
eout limit, and will wait indefinitely. 
 
By default the .Net applicati=
on expects a query to be finish with in 30 second. 
In case if an application iss=
ue a query that take more than 30 
then the application should e=
xplicitly set an appropriate time out value. 
 
Dim myCommand As New OdbcComm=
and 
myCommand.CommandTimeout =3D =
0 
 
 
Regards, 
Satyan 
 
Software Engineer 
R&D - IBM Data Management Group 
11200 Lakeview, Lenexa, KS 66219 
Tel: 913 599 8792 (T/L: 337-8792) 
 
<img src=3D"cid:10__=***@us.ibm.com" width=3D=
"16" height=3D"16" alt=3D"Inactive hide details for Abhishek Mathur/Len=
exa/IBM">Abhishek Mathur/Lenexa/IBM 
 
 

<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td style=3D"background-image:url(cid:20__=3D08BBE58=
***@us.ibm.com); background-repeat: no-repeat; " wid=
th=3D"40%">
<ul>
<ul>
<ul>
<ul>Abhishek Mathur/Lenexa/IBM 
09/15/2004 12:35 PM</ul>
</ul>
</ul>
</ul>
</td><td width=3D"60%">
<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=***@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""> 
<div align=3D"right">To</div></td><td width=3D"=
100%"><img src=3D"cid:30__=***@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
Sathyanesh Krishnan/Lenexa/***@IBMUS</td></tr>

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=***@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""> 
<div align=3D"right">cc</div></td><td width=3D"=
100%"><img src=3D"cid:30__=***@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
</td></tr>

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=***@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""> 
<div align=3D"right">Subject</div></td><td widt=
h=3D"100%"><img src=3D"cid:30__=***@us.ibm.=
com" border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
Fw: timeout using SDK 2.81 TC3 - .NET Managed Provider=
</td></tr>
</table>

<table border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tr valign=3D"top"><td width=3D"58"><img src=3D"cid:30__=3D08BBE583DFFF=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=
=3D""></td><td width=3D"336"><img src=3D"cid:30__=3D08BBE583DFFF67918f9=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=3D""><=
/td></tr>
</table>
</td></tr>
</table>
Hey Satyan, 
Did you have a chance to look at this in the IIUG? 
 
Cheers, 
Abhi 
--------------------------------------------------------------------<br=
There are 10 kinds of people,,,,, 
.... those who understand binary notations, and those who don't. 
--------------------------------------------------------------------<br=
 
----- Forwarded by Abhishek Mathur/L=
enexa/IBM on 09/15/2004 12:34 PM ----- 
 

<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td style=3D"background-image:url(cid:40__=3D08BBE58=
***@us.ibm.com); background-repeat: no-repeat; " wid=
th=3D"40%">
<ul>
<ul>
<ul>
<ul>***@fakeisp.net (-=3DEric=3D-)<font=
size=3D"2"> 
Sent by: owner-informix-***@iiug.org
09/13/2004 09:55 PM
<table border=3D"1">
<tr valign=3D"top"><td width=3D"168" bgcolor=3D"#FFFFFF"><div align=3D"=
center">Please respond to 
***@fakeisp.net (-=3DEric=3D-)</div></td></tr>
</table>
</ul>
</ul>
</ul>
</ul>
</td><td width=3D"60%">
<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td width=3D"1%"><img src=3D"cid:30__=3D08BBE583DFFF=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"58" al=
t=3D""> 
<div align=3D"right">To</div></td><td width=3D"=
100%"><img src=3D"cid:30__=***@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
informix-***@iiug.org</td></tr>

<tr valign=3D"top"><td width=3D"1%"><img src=3D"cid:30__=3D08BBE583DFFF=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"58" al=
t=3D""> 
<div align=3D"right">cc</div></td><td width=3D"=
100%"><img src=3D"cid:30__=***@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
informix-***@iiug.org, owner-informix-***@iiug.org</=
font></td></tr>

<tr valign=3D"top"><td width=3D"1%"><img src=3D"cid:30__=3D08BBE583DFFF=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"58" al=
t=3D""> 
<div align=3D"right">Subject</div></td><td widt=
h=3D"100%"><img src=3D"cid:30__=***@us.ibm.=
com" border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
timeout using SDK 2.81 TC3 - .NET Managed Provider</fo=
nt></td></tr>
</table>

<table border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tr valign=3D"top"><td width=3D"58"><img src=3D"cid:30__=3D08BBE583DFFF=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=
=3D""></td><td width=3D"336"><img src=3D"cid:30__=3D08BBE583DFFF67918f9=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=3D""><=
/td></tr>
</table>
</td></tr>
</table>
 
<tt>We have a showstopper issue...after upgrading from SDK 2.7x to 2.81=
 
TC3 (to get the .NET managed provider), we're occasionally running 
into timeout errors in .NET applications.  Specifically, the.NET c=
ode 
is throwing this: 
 
Error Message : 
ERROR [HYT00] [Informix][Informix ODBC Driver]Timeout expired. 
ERROR [HY008] [Informix][Informix ODBC Driver][Informix]Statement 
interrupted by user. 
Stack Trace=3D at Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr=
 
hHandle, SQL_HANDLE hType, RETCODE retcode) 
at Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior<=
br>
behavior, String method) 
at Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery() 
at OurCompany.WWWServices.Methodname(XmlNode inputDoc) 
Source=3Diclit09b.dll 
 
I've been unable to figure out, either in the documentation or on the<b=
r>
'net how to change the default timeout.  I think it might be possi=
ble 
within the code, but this is a major problem - we're not about to go<br=
revamp our entire codebase. 
 
If anyone has seen this or has suggestions, we're all ears.  So fa=
r, 
we've tried inserting various things into the connection string, 
setting the CONTIME and CONRETRY environment variables in SetNet32. =

 
Our platform is Informix 9.4O with application servers running Win 2k<b=
r>
and Win2k3 server. 
</tt> 
</body></html>=

--1__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791--

--0__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791
Content-type: image/gif;
name="graycol.gif"
Content-Disposition: inline; filename="graycol.gif"
Content-ID: <10__=***@us.ibm.com>
Content-transfer-encoding: base64

R0lGODlhEAAQAKECAMzMzAAAAP///wAAACH5BAEAAAIALAAAAAAQABAAAAIXlI+py+0PopwxUbpu
ZRfKZ2zgSJbmSRYAIf4fT3B0aW1pemVkIGJ5IFVsZWFkIFNtYXJ0U2F2ZXIhAAA7

--0__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791
Content-type: image/gif;
name="pic21091.gif"
Content-Disposition: inline; filename="pic21091.gif"
Content-ID: <20__=***@us.ibm.com>
Content-transfer-encoding: base64

R0lGODlhWwBlANX/AAAAAEhGSenp6jEyNhMUFyMmKfP59/L29PHy8fPihaOIGu7NSsqnH/v36PXq
1O7bvLibe56CZv78+v/+/f79/Ny0kZmTjrWspcq/t9LIwYVhS+ScdfXz8vn08vTv7dB6WdjQzXx5
eP36+cVfQt/Y1m08MLJBKrhMNJFALunk440tHe/p6OXe3WNhYfn39/f19e/u7sDAwP7+/v39/fv7
+/r6+gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADEALAAAAABbAGUAQAb/wJhw
SCwaj8ikkkjpOB6VymY6jT4cnckSCYJULhVIJHJ5mM+YSjoKWW2Tk81pRK9/7vjNh8qv9vF3D0gk
LRoaEYaHYxCMYmIlJYoZb0wfJpeYJiebnCNzdZ91oh8jpHcjGiWhIxVLBiQYEBaMGhcZDTMSNTQ1
vTQ0LzUzSw+eJpAlKpmXm8vOz5knmqEfJEgvKx4eIQHdAS0hFhgcHi8dHBwd6i/kMC8CIQMFBQQD
ARcuMSyndJz+0tCc/etX6g4EEEVgkGBBiMC8hxDltVhBcUUKiykyatTIkIRHEiA8ggCBwVqMDCdQ
oAAYDZM0gP80qCyFMImtDDhz6gSRYeTO/545SVggQLSoUaIBdOJs8caBAgUlFDCYuiCBhwcLsibY
yjWBoCM0MGTAQLasrbJo0V7AYOsCAQBHHTq8KTYnDSHAEHA4wMGFDCIOpjJYMDir1gVXuD5I4EDC
GxEgWgyYDHEegRAP6o4lq7QzTgwehvAMyYJFCtMcGQqgxLq169ewY8s2EoIevbhHWyCYzbt3DBkg
BoRYewFcg8wYhhYtMJmASd/QZRsAccFCiOshwIVgET26CCgRvFw5Y6YClAqho0t4AKiPlChRNrzv
o2eDgy0WDjEKo/8L/AuNiIHCGCm8xsJKA9FhCiAM3kHFByFEUJAe/JTSwREsIDMGIhuOkf9KCRZE
YMEFBryGUkDTcLIMS9H84+IJqoxw3xIKvWDjjS7k6MILOs5ggTzzABnkczJUQIon/rh0iUooIIOM
ClA+448nhkQgnwhFuMCCRS08NNmX8oTggjZklukBDBVRlMJHpX30ggdHeoKkiym+9GIdGnwQgZ4Q
vGDEWiPxxMIFthHVAgYMBRooTguVZppQXb41QEk+5QSCBUeIQAIEKEDp6aefmjDCBoZxNeMRsGym
2VpptYpWBsrhZpQFn4l1wRsVPCXVYIVp5YADXW1lhhI1kFUbc0IW0MJZZF3gbKtj4QTCAzwpJdYL
MywkgAAIIHDAt98isO1fQjhg2LmKNcD/GAWyeYBBdgF82cJn0dZlb20EBFDTETD0FNJHH41UYncE
DwGLBdZlAAO5BTf8BggFWABSTzBYAE4aIcBFFHMW7Obwx0QIYB288jgUJJj03AXyyiy3HEMHGZAn
c3oOi+CAkfW5Jx998jmgBWspwNcIBr8WfQZ86PXWQQV27LGHHzvPJ/UfH3w1SHhehIG1GkhHAQZ/
EXAAmwNLoqBggzx3+DR9eNCxgWNF5NdhIlgH2AjdEbjRGgsspijK36Ms2N4HhgA+6s+iaRDCh4p0
6CEkilzAMCUr9K1kkiraOaXhoKAgqoVHGBBieKSHR/csfsKGQZMB0Ymikpe/NILZVm/h/wK3fdmo
o44xEFpZCyAMQ4QHEiKJiQpOeu6MMpcwL6XfCm6g9xEycABDOTXszuOOGWXDAY80TBcPcw/VY9IK
eoLyjyYoMq+MMp573snZETxHxAwCrNDBj8iiHIII6AigALVBjjPBgAVoatNCRLCP4s0hcxBsBuYS
1LRqHIEDjgqAycgnDyCFoANoSpMINWIRBQIMJByYQQY08MAXufBOeMoTd45QA5JkwCMarIxlIsYC
npAAIxlxVGlOk5GRiGQ0o8HUEDwAAU8lA0qdMkH8OqWSEqiEExtIQAOWcIHRAOWGFgOKohQlLZ68
S4MaO0oIqvWZS1HCKbpixLnQVRVhIf+OCDfJCWfEwkY9lkUpQ0kjbgAQgGaJRYlLgICudtUrxiwm
WMICi1hcRclKugU3liEAraKVkzekQDBU6VUdDxCsxZzKCDVQVQbwVYAQuIpVhvyMdeJ1m3l5xi/b
gsEBDMBLXiIABvkQggcIQ8xS1RFYprpjElJwgXhRJlkOodUkX8UZaykFBFoAiba2JQAYeBMG22LB
aopAgUemS5mtkUAKuiSkktnSM55pQbxaMMMhCAAD/2qUEBPlMZcNQQYryICzIAAgZxm0OgGYhziC
uQWF5NMjLDiAPydK0YZZoFBxAYCYKuqwhCYFVgOQWHJusxx6cjQ63LBhSX51qHtYII3/zAlAgU7a
GwFcIB4bK4og+0cP4dG0N8CxTgvk6Y2iSuSnSE1qpjrQgKLpj10sk8DNeEbVCvgsNhPYFARiJrPy
OIBm3WkAhRxEBfjIx6x/qMCFKDGBDKhhP1cwWnmigIEt+kYEGyjFhPgQn/d0TQoPCsQWZJC1DDjC
qkUjwVzZgAHedCBODOLZ1PrKB0BUAJ1C4MB+uDYG83DVrecJgxgiMDnWTKACzZDiJjQwgj2VTm0Q
oA9gp8CgtRYBA1gDgxgOAZ81IA0Rh6inaT8gv781CG1U2NDa6mMKOkwiboq4W90aIdrdKsJ+jzHG
5uxQkONG9g5j6O7fate7KnlIP3a7/5t5LVAD11Qgdg/knOGOdFwNfE5OI5ipECQAXENAznGko1uE
YOAaDliOGS90kXxFkZJplAKqQ7hAJEpQCAADNxIbwu4bHnBgBEswtfBNcDNK8LnpDYEFFp5bJBhR
V9hUAEEC+TD7XueSl7BPRSioGhIaIFDSOSIRtGpvbDCQEitKKUk0hsaH56ABDS+BBn05gO5yZCMZ
YKAbLaBVCoRcBBL0o3nIUN7rnIeigdxhX0qAQQrcgaPd8e4CHUxWCFInBBEcSUWZaJKTPAUNMteY
Gh+AgNjg8AJgfq/NOnqTNz2QgncBSUj10G8G4uS6ZzjRSZhOHjKqVIHSEoED3nNUCv88kI8ZcGBN
6DjHOXQ3gyufbAD5IrAIIHDnFzEjyX/eRNMYgSWwrAAG+3s1+Sxg6gCuOoC/1IsE4JxlEpyGBS6Y
AQT+hrkUPS+CuqbDnhjB0CJYxAPB6aAzKSMmMpGjgGc6069DyBAhOnvWBLE1nqdxYwXXwbUX6HUR
ZJARD1zUS2AK05uyoY1voskDaXr2Qhb+ERnwLd4urLfm/MHaguRJv0XI1pZ8p0OIhADhIkz4Rk5z
wiOS4C98Q1C1byxxldOhcB8QrhHWBMYdbpB8BGiBs9W0kX0GMVFHVNSthICA2THpdTDR80pGAAEC
K4EFliIBoeSSSVeuiQTScvY+UcP/guQcSiTXROSJIwCqsqugU/CT4gcqYJhTGmGTlUqBcgZwgR6O
EYk2XAh1ImUUffWxJ2I3Ag2kLqCzQ+kECviAKOeoRSTkcSeLChRIqlUpMAoyLgXo4k4Cj4RZP4W3
FRgJHRNQx63YtQia74xm4HnNEMjqKBYwI1uYsoUHKEADT6GKVprKldJz5QgkqaTq/zhJnMTq9Tmv
lxu3oMjc614rWoTk741wT1VV8vqHRD5RJkUvgW6YAYxcPGIMICyvTN8IXcd+q2BZluMvpyjA0yNO
MJ4ECUAAlHP0lTm5cnr0E1+g92B913dTsHYU9LBG8ocovyEuugQu3cJlMkAYz4cu/4zRFVewBOm3
ShCRL8yyfmmhR0KlGfaCEAhAAt30Lb3ES+DEZYGRf1VRFeoiLHCzBAKQAZKBMjtUSGzxgdXEejpR
IP1igrnULQfQLeAUUURwHIdBeqYiAhD2BtnyI18SJOUTAvQigj6oE2vlQwuhEdwkABlhglFlg1NI
GfNghd3ng3VxU8KFRBC1dT00TizjcJKhQ++UhcXhECHgdEQwHT1Rch0BAizgUy5TAykgUAdFSWNB
gPnSMTQoeQAzEhKFVDPQdQiDMLIwC9lxAWBFCTXwS91zAISoVKRYiqbYMlYWL3JRFAOQAZ52iq8R
KSSFGy0gh7DYGgIgFwlFFJe3HIaSc4usYQD1ECgrJQ4PAGdGUQD3AIyU8CPESAKiUxuuFAEkpYy1
yIz4oS/NcgEk0AC10QIVoAHL8SWNhY1KQAK1MQDgoEEBgDAtAFMdRACTaI5IYABet4uYNIU5R49P
xgJCRVTjZg9fokn8SAlCcR1DJU8AWUgF+Ro0IC4gIU5c1pAUuQRBAAA7

--0__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791
Content-type: image/gif;
name="ecblank.gif"
Content-Disposition: inline; filename="ecblank.gif"
Content-ID: <30__=***@us.ibm.com>
Content-transfer-encoding: base64

R0lGODlhEAABAIAAAAAAAP///yH5BAEAAAEALAAAAAAQAAEAAAIEjI8ZBQA7

--0__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791
Content-type: image/gif;
name="pic30514.gif"
Content-Disposition: inline; filename="pic30514.gif"
Content-ID: <40__=***@us.ibm.com>
Content-transfer-encoding: base64

R0lGODlhWABDALP/AAAAAK04Qf79/o+Gm7WuwlNObwoJFCsoSMDAwGFsmIuezf///wAAAAAAAAAA
AAAAACH5BAEAAAgALAAAAABYAEMAQAT/EMlJq704682770RiFMRinqggEUNSHIchG0BCfHhOjAuh
EDeUqTASLCbBhQrhG7xis2j0lssNDopE4jfIJhDaggI8YB1sZeZgLVA9YVCpnGagVjV171aRVrYR
RghXcAGFhoUETwYxcXNyADJ3GlcSKGAwLwllVC1vjIUHBWsFilKQdI8GA5IcpApeJQt8L09lmgkH
LZikoU5wjqcyAMMFrJIDPAKvCFletKSev1HBw8KrxtjZ2tvc3d5VyKtCKW3jfz4uMKmq3xu4N0nK
BVoJQmx2LGVOmrqNjjJf2hHAQo/eDwJGTKhQMcgQEEAnEjFS98+RnW3smGkZU6ncCWav/4wYOnAI
TihRL/4FEwbp28BXMMcoscQCVxlepL4IGDSCyJyVQOu0o7CjmLN50OZlqWmyFy5/6yBBuji0AxFR
M00oQAqNIstqI6qKHUsWRAEAvagsmfUEAImyxgbmUpJk3IklNUtJOUAVLoUr1+wqDGTE4zk+T6FG
uQb3SizBCwatiiUgCBN8vrz+zFjVyQ8FWkOlg4NQiZMB5QS8QO3mpOaKnL0Z2EKvNMSILEThKhCg
zMKPVxYJh23qm9KNW7pArPynMqZDiErsTMqI+LRi3QAgkFUbXpuFKhSYZALd0O5RKa2z9EYKBbpb
qxIKsjUPRgD7I2XYV6wyrOw92ykExP8NW4URhknC5dKGE4v4NENQj2jXjmfNgOZDaXb5glRmXQ33
YEWQYNcZFnrYcIQLNzyTFDQNkXIff0ExVlY4srziQk43inZgL4rwxxINMvpFFAz1KOODHiu+4aEw
NEjFl5B3JIKWKF3k6I9bfUGp5ZZcdunll5IA4cuHvQQJ5gcsoCWOOUwgltIwAKRxJgbIkJAQZEq0
2YliZnpZZ4BH3CnYOXldOUOfQoYDqF1LFHbXCrO8xmRsfoXDXJ6ChjCAH3QlhJcT6VWE6FCkfCco
CgrMFsROrIEX3o2whVjWDjoJccN3LdggSGXLCdLEgHr1lyU3O3QxhgohNKXJCWv8JQr/PDdaqd6w
2rj1inLiGeiCJoDspAoQlYE6QWLSECehcWIYxIQES6zhbn1iImTHEQyqJ4eIxJJoUBc+3CbBuwZE
V5cJPPkIjFDdeEabQbd6WgICTxiiz0f5dBKquXF6k4senwEhYGnKEFJeGrxUZy8dB8gmAXI/sPvH
ESfCwVt5hTgYiqQqtdRNHQIU1PJ33ZqmzgE90OwLaoJcnMop1WiMmgkPHQRIrwgFuNV90A3doNKT
mrKIN07AnGcI9BQjhCBN4RfA1qIZnMqorJCogKfGQnxSCDilTVIA0yl5ciTovgLuBDKFUDE9aQcw
9SA+rjSNf9/M1gxrj6VwDTS0IUSElMzBfsj0NFXR2kwsV1A5IF1grLgLL/r1R40BZEnuBWgmQEyb
jqRwSAt6bqMCOFkvKFN2GPPkUzIm/SCF8z8pVzpbjVnMsy0vOr1hw3SaSRUhpY09v0z0J1FnwzPl
fmh+xl4WtR0zGu24I4KbMQm3lnVu2oNWxI9W/lcyzA+mCKF4DBikxb/+UWtOGRiFP8qEwAayIgIA
Ow==

--0__=08BBE583DFFF67918f9e8a93df938690918c08BBE583DFFF6791--

sending to informix-list

Sathyanesh Krishnan

2004-09-16 05:58:28 UTC

Permalink

--0__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F
Content-type: multipart/alternative;
Boundary="1__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F"

--1__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable

Hi Eric,

Thanks Very Much Eric,

Actually this is an expected behavior than a problem.
Based on the CommandTimeout value the .NET provider informs the underly=
ing
ODBC driver to time out the executing query.
ODBC driver then send an interrupt query to database server.

I guess the problem may be on CSDK 2.70 ODBC driver; it fails to interr=
upt
the query.

Can you please give me some more detail regarding the query that the
application is executing.
How long this query takes to execute.
Also how many second after since it starts the execution the applicatio=
n
throwing error etc.

Really appreciate your help.

Regards,
Satyan

Software Engineer
R&D - IBM Data Management Group
11200 Lakeview, Lenexa, KS 66219
Tel: 913 599 8792 (T/L: 337-8792)

=

-=3DEric=3D- =

Post by Sathyanesh Krishnan
=

To
Sathyanesh =

09/15/2004 08:30 Krishnan/Lenexa/***@IBMUS =

PM =
cc
=

Subj=
ect
Please respond to Re: Fw: timeout using SDK 2.81 T=
C3
eric - .NET Managed Provider =

=

=

=

=

=

=

Satyan:

We have been able to avoid the timeout issue by
changing our code. But no such code was required in
SDK 2.7 - commands did not time out be default. This
change in the default behavior is now causing us to
have to change, test, and redeploy all of our code.

Also - I can say for sure that this timeout is not
related to .NET - otherwise, we would have seen
timeouts using SDK 2.7 (assuming we do not explicitly
set the timeout). But this is not what we are seeing
in our tests.

Additionally, we were able today to replicate the
timeout using the managed provider, so this affects
not only ODBC but the managed wrapper as well...

I sincerely appreciate the response...if this
information prompts you or your team to think of any
additional information, I'm sure many people can
benefit from your insight.

-=3DEric=3D-

Post by Sathyanesh Krishnan
Hi Eric,
Most probably this may be due to the CommandTimeoutt
value, by default it
is 30 sec.
(Microsoft.Data.Odbc.OdbcCommand.CommandTimeout )
A value of 0 indicates no timeout limit, and will
wait indefinitely.
By default the .Net application expects a query to
be finish with in 30
second.
In case if an application issue a query that take
more than 30
then the application should explicitly set an
appropriate time out value.
Dim myCommand As New OdbcCommand
myCommand.CommandTimeout =3D 0
Regards,
Satyan
Software Engineer
R&D - IBM Data Management Group
11200 Lakeview, Lenexa, KS 66219
Tel: 913 599 8792 (T/L: 337-8792)
Abhishek
Mathur/Lenexa/IBM
To
09/15/2004 12:35 Sathyanesh
PM
cc
Subject
Fw: timeout
using SDK 2.81 TC3 -
.NET Managed
Provider
Hey Satyan,
Did you have a chance to look at this in the
IIUG?
Cheers,
Abhi

--------------------------------------------------------------------

Post by Sathyanesh Krishnan
There are 10 kinds of people,,,,,
.... those who understand binary notations, and
those who don't.

--------------------------------------------------------------------

Post by Sathyanesh Krishnan
----- Forwarded by Abhishek Mathur/Lenexa/IBM on
09/15/2004 12:34 PM -----
(-=3DEric=3D-)
To
owner-informix-li
cc
09/13/2004 09:55
Subject
PM timeout using
SDK 2.81 TC3 - .NET
Managed
Provider
Please respond to
(-=3DEric=3D-)
We have a showstopper issue...after upgrading from
SDK 2.7x to 2.81
TC3 (to get the .NET managed provider), we're
occasionally running
into timeout errors in .NET applications.
Specifically, the.NET code
ERROR [HYT00] [Informix][Informix ODBC
Driver]Timeout expired.
ERROR [HY008] [Informix][Informix ODBC
Driver][Informix]Statement
interrupted by user.
Stack Trace=3D at

Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr

Post by Sathyanesh Krishnan
hHandle, SQL_HANDLE hType, RETCODE retcode)
at

Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior

Post by Sathyanesh Krishnan
behavior, String method)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery()
at OurCompany.WWWServices.Methodname(XmlNode
inputDoc)
Source=3Diclit09b.dll
I've been unable to figure out, either in the
documentation or on the
'net how to change the default timeout. I think it
might be possible
within the code, but this is a major problem - we're
not about to go
revamp our entire codebase.
If anyone has seen this or has suggestions, we're
all ears. So far,
we've tried inserting various things into the
connection string,
setting the CONTIME and CONRETRY environment
variables in SetNet32.
Our platform is Informix 9.4O with application
servers running Win 2k
and Win2k3 server.

=

--1__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
Hi Eric, 
 
Thanks Very Much Eric, 
 
Actually this is an expected behavior than a problem. 
Based on the CommandTimeout value the .NET provider informs the underly=
ing ODBC driver to time out the executing query. 
ODBC driver then send an interrupt query to database server. 
 
I guess the problem may be on CSDK 2.70 ODBC driver; it fails to interr=
upt the query. 
 
Can you please give me some more detail regarding the query that the ap=
plication is executing. 
How long this query takes to execute. 
Also how many second after since it starts the execution the applicatio=
n throwing error etc. 
 
Really appreciate your help. 
 
 
Regards, 
Satyan 
 
Software Engineer 
R&D - IBM Data Management Group 
11200 Lakeview, Lenexa, KS 66219 
Tel: 913 599 8792 (T/L: 337-8792) 
 
<img src=3D"cid:10__=***@us.ibm.com" width=3D=
"16" height=3D"16" alt=3D"Inactive hide details for -=3DEric=3D- <er=
***@fakeisp.net>">-=3DEric=3D- <***@fakeisp.net> 
 
 

<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td style=3D"background-image:url(cid:20__=3D08BBE58=

Post by Sathyanesh Krishnan

09/15/2004 08:30 PM
<table border=3D"1">
<tr valign=3D"top"><td width=3D"168" bgcolor=3D"#FFFFFF"><div align=3D"=
center">Please respond to 
eric</div></td></tr>
</table>
</ul>
</ul>
</ul>
</ul>
</td><td width=3D"60%">
<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=***@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""> 
<div align=3D"right">To</div></td><td width=3D"=
100%"><img src=3D"cid:30__=***@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
Sathyanesh Krishnan/Lenexa/***@IBMUS</td></tr>

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=***@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""> 
<div align=3D"right">cc</div></td><td width=3D"=
100%"><img src=3D"cid:30__=***@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
</td></tr>

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=***@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""> 
<div align=3D"right">Subject</div></td><td widt=
h=3D"100%"><img src=3D"cid:30__=***@us.ibm.=
com" border=3D"0" height=3D"1" width=3D"1" alt=3D""> 
Re: Fw: timeout using SDK 2.81 TC3 - .NET Managed Prov=
ider</td></tr>
</table>

<table border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tr valign=3D"top"><td width=3D"58"><img src=3D"cid:30__=3D08BBE582DFB3=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=
=3D""></td><td width=3D"336"><img src=3D"cid:30__=3D08BBE582DFB3F38F8f9=
***@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=3D""><=
/td></tr>
</table>
</td></tr>
</table>
 
<tt>Satyan: 
</tt> 
<tt>We have been able to avoid the timeout issue by 
changing our code.  But no such code was required in 
SDK 2.7 - commands did not time out be default.  This 
change in the default behavior is now causing us to 
have to change, test, and redeploy all of our code. 
</tt> 
<tt>Also - I can say for sure that this timeout is not 
related to .NET - otherwise, we would have seen 
timeouts using SDK 2.7 (assuming we do not explicitly 
set the timeout).  But this is not what we are seeing 
in our tests. 
</tt> 
<tt>Additionally, we were able today to replicate the 
timeout using the managed provider, so this affects 
not only ODBC but the managed wrapper as well... 
</tt> 
<tt>I sincerely appreciate the response...if this 
information prompts you or your team to think of any 
additional information, I'm sure many people can 
benefit from your insight. 
</tt> 
<tt>-=3DEric=3D- 
--- Sathyanesh Krishnan <***@us.ibm.com> wrote: </tt> <tt>> 
> 
> 
> 
> 
> Hi Eric, 
> 
> Most probably this may be due to the CommandTimeoutt 
> value, by default it 
> is 30 sec. 
> (Microsoft.Data.Odbc.OdbcCommand.CommandTimeout ) 
> A value of 0 indicates no timeout limit, and will 
> wait indefinitely. 
> 
> By default the .Net application expects a query to 
> be finish with in 30 
> second. 
> In case if an application issue a query that take 
> more than 30 
> then the application should explicitly set an 
> appropriate time out value. 
> 
> Dim myCommand As New OdbcCommand 
> myCommand.CommandTimeout =3D 0 
> 
> 
> Regards, 
> Satyan 
> 
> Software Engineer 
> R&D - IBM Data Management Group 
> 11200 Lakeview, Lenexa, KS 66219 
> Tel: 913 599 8792 (T/L: 337-8792) 
> 
> 
> 
> 
> 
>              Abhishek 
> 
>              Mathur/Lenexa/IBM<=
br>
> 
> 
>                   &nb=
sp;To 
>              09/15/2004 12:35 &=
nbsp;        Sathyanesh 
> 
>              PM 
> Krishnan/Lenexa/***@IBMUS 
> 
>                   &nb=
sp;cc 
> 
> 
> 
>               Subject 
>                   &nb=
sp;                   &nbs=
p;Fw: timeout 
> using SDK 2.81 TC3 - 
>                   &nb=
sp;                   &nbs=
p;.NET Managed 
> Provider 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Hey Satyan, 
>       Did you have a chance to look at this in the<=
br>
> IIUG? 
> 
> Cheers, 
> Abhi 
> 
--------------------------------------------------------------------<br=
> There are 10 kinds of people,,,,, 
> .... those who understand binary notations, and 
> those who don't. 
> 
--------------------------------------------------------------------<br=
> 
> ----- Forwarded by Abhishek Mathur/Lenexa/IBM on 
> 09/15/2004 12:34 PM ----- 
> 
> 
>              ***@fakeisp.net<b=
r>
> 
>              (-=3DEric=3D-) =

> 
>              Sent by: 
>                   &nb=
sp;To 
>              owner-informix-li<=
br>
> informix-***@iiug.org 
>              ***@iiug.org 
>                   &nb=
sp;cc 
> 
> informix-***@iiug.org, 
> 
> owner-informix-***@iiug.org 
>              09/13/2004 09:55<b=
r>
>               Subject 
>              PM     &=
nbsp;                  tim=
eout using 
> SDK 2.81 TC3 - .NET 
>                   &nb=
sp;                   &nbs=
p;Managed 
> Provider 
> 
> 
>              Please respond to<=
br>
> 
>              ***@fakeisp.net<b=
r>
> 
>                 (-=3DEric=3D=
-) 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> We have a showstopper issue...after upgrading from 
> SDK 2.7x to 2.81 
> TC3 (to get the .NET managed provider), we're 
> occasionally running 
> into timeout errors in .NET applications. 
> Specifically, the.NET code 
> is throwing this: 
> 
> Error Message : 
> ERROR [HYT00] [Informix][Informix ODBC 
> Driver]Timeout expired. 
> ERROR [HY008] [Informix][Informix ODBC 
> Driver][Informix]Statement 
> interrupted by user. 
> Stack Trace=3D at 
> 
Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr 
> hHandle, SQL_HANDLE hType, RETCODE retcode) 
> at 
> 
Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior =

> behavior, String method) 
> at Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery() 
> at OurCompany.WWWServices.Methodname(XmlNode 
> inputDoc) 
> Source=3Diclit09b.dll 
> 
> I've been unable to figure out, either in the 
> documentation or on the 
> 'net how to change the default timeout.  I think it 
> might be possible 
> within the code, but this is a major problem - we're 
> not about to go 
> revamp our entire codebase. 
> 
> If anyone has seen this or has suggestions, we're 
> all ears.  So far, 
> we've tried inserting various things into the 
> connection string, 
> setting the CONTIME and CONRETRY environment 
> variables in SetNet32. 
> 
> Our platform is Informix 9.4O with application 
> servers running Win 2k 
> and Win2k3 server. 
></tt> 
 
</body></html>=

--1__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F--

--0__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F
Content-type: image/gif;
name="graycol.gif"
Content-Disposition: inline; filename="graycol.gif"
Content-ID: <10__=***@us.ibm.com>
Content-transfer-encoding: base64

R0lGODlhEAAQAKECAMzMzAAAAP///wAAACH5BAEAAAIALAAAAAAQABAAAAIXlI+py+0PopwxUbpu
ZRfKZ2zgSJbmSRYAIf4fT3B0aW1pemVkIGJ5IFVsZWFkIFNtYXJ0U2F2ZXIhAAA7

--0__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F
Content-type: image/gif;
name="pic21961.gif"
Content-Disposition: inline; filename="pic21961.gif"
Content-ID: <20__=***@us.ibm.com>
Content-transfer-encoding: base64

R0lGODlhWABDALP/AAAAAK04Qf79/o+Gm7WuwlNObwoJFCsoSMDAwGFsmIuezf///wAAAAAAAAAA
AAAAACH5BAEAAAgALAAAAABYAEMAQAT/EMlJq704682770RiFMRinqggEUNSHIchG0BCfHhOjAuh
EDeUqTASLCbBhQrhG7xis2j0lssNDopE4jfIJhDaggI8YB1sZeZgLVA9YVCpnGagVjV171aRVrYR
RghXcAGFhoUETwYxcXNyADJ3GlcSKGAwLwllVC1vjIUHBWsFilKQdI8GA5IcpApeJQt8L09lmgkH
LZikoU5wjqcyAMMFrJIDPAKvCFletKSev1HBw8KrxtjZ2tvc3d5VyKtCKW3jfz4uMKmq3xu4N0nK
BVoJQmx2LGVOmrqNjjJf2hHAQo/eDwJGTKhQMcgQEEAnEjFS98+RnW3smGkZU6ncCWav/4wYOnAI
TihRL/4FEwbp28BXMMcoscQCVxlepL4IGDSCyJyVQOu0o7CjmLN50OZlqWmyFy5/6yBBuji0AxFR
M00oQAqNIstqI6qKHUsWRAEAvagsmfUEAImyxgbmUpJk3IklNUtJOUAVLoUr1+wqDGTE4zk+T6FG
uQb3SizBCwatiiUgCBN8vrz+zFjVyQ8FWkOlg4NQiZMB5QS8QO3mpOaKnL0Z2EKvNMSILEThKhCg
zMKPVxYJh23qm9KNW7pArPynMqZDiErsTMqI+LRi3QAgkFUbXpuFKhSYZALd0O5RKa2z9EYKBbpb
qxIKsjUPRgD7I2XYV6wyrOw92ykExP8NW4URhknC5dKGE4v4NENQj2jXjmfNgOZDaXb5glRmXQ33
YEWQYNcZFnrYcIQLNzyTFDQNkXIff0ExVlY4srziQk43inZgL4rwxxINMvpFFAz1KOODHiu+4aEw
NEjFl5B3JIKWKF3k6I9bfUGp5ZZcdunll5IA4cuHvQQJ5gcsoCWOOUwgltIwAKRxJgbIkJAQZEq0
2YliZnpZZ4BH3CnYOXldOUOfQoYDqF1LFHbXCrO8xmRsfoXDXJ6ChjCAH3QlhJcT6VWE6FCkfCco
CgrMFsROrIEX3o2whVjWDjoJccN3LdggSGXLCdLEgHr1lyU3O3QxhgohNKXJCWv8JQr/PDdaqd6w
2rj1inLiGeiCJoDspAoQlYE6QWLSECehcWIYxIQES6zhbn1iImTHEQyqJ4eIxJJoUBc+3CbBuwZE
V5cJPPkIjFDdeEabQbd6WgICTxiiz0f5dBKquXF6k4senwEhYGnKEFJeGrxUZy8dB8gmAXI/sPvH
ESfCwVt5hTgYiqQqtdRNHQIU1PJ33ZqmzgE90OwLaoJcnMop1WiMmgkPHQRIrwgFuNV90A3doNKT
mrKIN07AnGcI9BQjhCBN4RfA1qIZnMqorJCogKfGQnxSCDilTVIA0yl5ciTovgLuBDKFUDE9aQcw
9SA+rjSNf9/M1gxrj6VwDTS0IUSElMzBfsj0NFXR2kwsV1A5IF1grLgLL/r1R40BZEnuBWgmQEyb
jqRwSAt6bqMCOFkvKFN2GPPkUzIm/SCF8z8pVzpbjVnMsy0vOr1hw3SaSRUhpY09v0z0J1FnwzPl
fmh+xl4WtR0zGu24I4KbMQm3lnVu2oNWxI9W/lcyzA+mCKF4DBikxb/+UWtOGRiFP8qEwAayIgIA
Ow==

--0__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F
Content-type: image/gif;
name="ecblank.gif"
Content-Disposition: inline; filename="ecblank.gif"
Content-ID: <30__=***@us.ibm.com>
Content-transfer-encoding: base64

R0lGODlhEAABAIAAAAAAAP///yH5BAEAAAEALAAAAAAQAAEAAAIEjI8ZBQA7

--0__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F--

sending to informix-list