setLong() bug in db2 Connect jdbc?

[Rory McQuillan]

Hi. I've been using the personal edition of db2 Connect to access our
mainframe database from java apps for the last 9 months or so. I'm using
prepared statements, and the setLong method has proven unreliable for both
parameters and insert values, not finding search filters or attempting to
insert nulls, etc. This has forced me to use setDouble or setBigDecimal to
get around it, but I'd prefer to use setLong where appropriate. I'm working
with jdk 1.4.2 on a Windows 2000 platform. Any ideas?

[db2start]

Hi Rory,

What version/FixPak of db2connect are you using?

Cheers,

On Dec 9, 2:45 am, "Rory McQuillan" <[e-mail]:

Hi. I've been using the personal edition of db2 Connect to access our
mainframe database from java apps for the last 9 months or so. I'm using
prepared statements, and the setLong method has proven unreliable for both
parameters and insert values, not finding search filters or attempting to
insert nulls, etc. This has forced me to use setDouble or setBigDecimal to
get around it, but I'd prefer to use setLong where appropriate. I'm working
with jdk 1.4.2 on a Windows 2000 platform. Any ideas?

[Rory McQuillan]

I'll have to check at work tomorrow. At first I was running a free trial
edition, but I believe I'm on a licensed copy now.

<db******@gmail.comwrote in message
news:11*********************@79g2000cws.googlegrou ps.com...

Hi Rory,

What version/FixPak of db2connect are you using?

Cheers,

On Dec 9, 2:45 am, "Rory McQuillan" <[e-mail]:

>Hi. I've been using the personal edition of db2 Connect to access our
mainframe database from java apps for the last 9 months or so. I'm using
prepared statements, and the setLong method has proven unreliable for
both
parameters and insert values, not finding search filters or attempting to
insert nulls, etc. This has forced me to use setDouble or setBigDecimal
to
get around it, but I'd prefer to use setLong where appropriate. I'm
working
with jdk 1.4.2 on a Windows 2000 platform. Any ideas?