RE: SQL Error - how to track

["Eyers, Daniel" <daniel.eyers@xxxxxxxxxxxxx>]

cool...  I had to change the catch block to catch a SQLException instead of
an Exception but it works like a champ....

here's the sql that's failing....

SELECT OTPRFG, OTONO, OTLINE, OTNO, OTSDTE, OTSQTY, OTHTMS, OTPN FROM
psddata.fhprvddt WHERE Integer(OTNO) = 29925240

I would guess that there is a row where OTNO is not numeric... I would guess
that it's shown in the joblog somewhere...  Still wondering how to track it
down...

dan


-----Original Message-----
From: Richard Dettinger [mailto:cujo@us.ibm.com]
Sent: Thursday, September 06, 2001 11:02 PM
To: java400-l@midrange.com
Subject: Re: SQL Error - how to track



You can specify "errors=full" on you connection URL.

For example, if you are using the DriverManager to get connections, this
code will provide the second level text in the SQLException message when
errors occur.

     Connection connection = DriverManager.getConnection
("jdbc:db2:system;errors=full");

There is also a DataSource property to accomplish this if you are using
DataSources.

Regards,

Richard D. Dettinger
AS/400 Java Data Access Team

"Biologists have a special word for stability -- dead"

                Larry Wall
                Open Source Developers Journal
                Issue 1, Jan  2000