JAVA SQLException and SQLWarning

Jim Irwin

JAVA SQLException and SQLWarning
Hey guys........I'm an old mainframe dinosaur trying to adjust to the
new millennium and I need some help. Back in the old days when I saw an
DB2 SQLCODE (or IDMS Error Status) I could go to my handy reference and
eventually figure out what was going on. Now we have a
WebSphere/JAVA/JDBC application accessing DB2 for z/OS that "throws"
exceptions which apparently the application is not "catching". I'm
trying to help diagnose some of the problems but not all of the
exceptions show the SQLCODE/SQLSTATE that caused it.

Can anyone tell me where I might find a document that maps DB2
SQLCODES/SQLSTATES to the JAVA exceptions being thrown by the JDBC
driver or is it not that simple?



***********************************
CONFIDENTIALITY STATEMENT:
This e-mail and any attachments are intended only for those to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure and unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Charles Greer

Re: JAVA SQLException and SQLWarning
(in response to John McKown)
Hello Jim, the good news is that the SQLException passes all information that you need...

if you can have your Java program print a stack trace
then you'll get some more information:

try {
...
} catch (SQLException e) {
e.printStackTrace();
}


With the Type 4 JDBC
driver, the SQLCODE and SQLSTATE
is inserted in the message, in its -XXX notation:

com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 3;ADDRESS.MASTER
at com.ibm.db2.jcc.b.id.d(id.java:1385)
at com.ibm.db2.jcc.c.fb.l(fb.java:366)
at com.ibm.db2.jcc.c.fb.a(fb.java:64)
at com.ibm.db2.jcc.c.s.a(s.java:48)
at com.ibm.db2.jcc.c.xb.c(xb.java:266)
at com.ibm.db2.jcc.b.jd.ab(jd.java:1684)...

As I recall, the Type 3 driver embeds a text message in there as well.

Charles


Charles Greer
Software Systems Analyst
County of Sonoma, Geographic Information Systems
2615 Paulin Drive
Santa Rosa, CA 95403
707-565-3991 FAX 707-565-2187
[login to unmask email]


>>> [login to unmask email] 12/27/05 11:34 AM >>>
Hey guys........I'm an old mainframe dinosaur trying to adjust to the
new millennium and I need some help. Back in the old days when I saw an
DB2 SQLCODE (or IDMS Error Status) I could go to my handy reference and
eventually figure out what was going on. Now we have a
WebSphere/JAVA/JDBC application accessing DB2 for z/OS that "throws"
exceptions which apparently the application is not "catching". I'm
trying to help diagnose some of the problems but not all of the
exceptions show the SQLCODE/SQLSTATE that caused it.

Can anyone tell me where I might find a document that maps DB2
SQLCODES/SQLSTATES to the JAVA exceptions being thrown by the JDBC
driver or is it not that simple?



***********************************
CONFIDENTIALITY STATEMENT:
This e-mail and any attachments are intended only for those to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure and unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

John McKown

Re: JAVA SQLException and SQLWarning
(in response to Jim Irwin)
Perhaps

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DSNJVJ12/2.1.
18

would help?



--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]
On Behalf Of Irwin, Jim
Sent: Tuesday, December 27, 2005 1:35 PM
To: [login to unmask email]
Subject: [DB2-L] JAVA SQLException and SQLWarning



Hey guys........I'm an old mainframe dinosaur trying to adjust
to the new millennium and I need some help. Back in the old days when I
saw an DB2 SQLCODE (or IDMS Error Status) I could go to my handy
reference and eventually figure out what was going on. Now we have a
WebSphere/JAVA/JDBC application accessing DB2 for z/OS that "throws"
exceptions which apparently the application is not "catching". I'm
trying to help diagnose some of the problems but not all of the
exceptions show the SQLCODE/SQLSTATE that caused it.

Can anyone tell me where I might find a document that maps DB2
SQLCODES/SQLSTATES to the JAVA exceptions being thrown by the JDBC
driver or is it not that simple?


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Myron Miller

Re: JAVA SQLException and SQLWarning
(in response to Charles Greer)
Jim,
Somewhere in the Websphere exception log should be the actual
SQLSTATE/SQLCODE being thrown as well. I've never seen a case if the person had
a finally section that captured the SQL exceptions that didn't give the proper
SQL code or state. Your java programmer needs to capture these just like any
other exception.

Myron

--- "Irwin, Jim" <[login to unmask email]> wrote:

> Hey guys........I'm an old mainframe dinosaur trying to adjust to the
> new millennium and I need some help. Back in the old days when I saw an
> DB2 SQLCODE (or IDMS Error Status) I could go to my handy reference and
> eventually figure out what was going on. Now we have a
> WebSphere/JAVA/JDBC application accessing DB2 for z/OS that "throws"
> exceptions which apparently the application is not "catching". I'm
> trying to help diagnose some of the problems but not all of the
> exceptions show the SQLCODE/SQLSTATE that caused it.
>
> Can anyone tell me where I might find a document that maps DB2
> SQLCODES/SQLSTATES to the JAVA exceptions being thrown by the JDBC
> driver or is it not that simple?
>
>
>
> ***********************************
> CONFIDENTIALITY STATEMENT:
> This e-mail and any attachments are intended only for those to which it is
> addressed and may contain information which is privileged, confidential and
> prohibited from disclosure and unauthorized use under applicable law. If you
> are not the intended recipient of this e-mail, you are hereby notified that
> any use, dissemination, or copying of this e-mail or the information
> contained in this e-mail is strictly prohibited by the sender. If you have
> received this transmission in error, please return the material received to
> the sender and delete all copies from your system.
>
>
>
>
---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
> "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
> The IDUG List Admins can be reached at [login to unmask email] Find
> out the latest on IDUG conferences at http://conferences.idug.org/index.cfm
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jim Irwin

Re: JAVA SQLException and SQLWarning
(in response to Myron Miller)
Hi Charles, My understanding is that the what you say is true in most
cases but not all. One example would be where the application does a
singleton select but there is more than one row that qualifies. In the
mainframe world you would get back a -811 SQLCODE but all that gets
returned on the JAVA side is an SQLException with no SQLCODE or
SQLSTATE. As I understand it, and I understand very little, the driver
does not pass the SQLCODE and/or SQLSTATE back for all requests.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Charles Greer
Sent: Tuesday, December 27, 2005 1:43 PM
To: [login to unmask email]
Subject: Re: [DB2-L] JAVA SQLException and SQLWarning

Hello Jim, the good news is that the SQLException passes all information
that you need...

if you can have your Java program print a stack trace
then you'll get some more information:

try {
...
} catch (SQLException e) {
e.printStackTrace();
}


With the Type 4 JDBC
driver, the SQLCODE and SQLSTATE
is inserted in the message, in its -XXX notation:

com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -803, SQLSTATE:
23505, SQLERRMC: 3;ADDRESS.MASTER
at com.ibm.db2.jcc.b.id.d(id.java:1385)
at com.ibm.db2.jcc.c.fb.l(fb.java:366)
at com.ibm.db2.jcc.c.fb.a(fb.java:64)
at com.ibm.db2.jcc.c.s.a(s.java:48)
at com.ibm.db2.jcc.c.xb.c(xb.java:266)
at com.ibm.db2.jcc.b.jd.ab(jd.java:1684)...

As I recall, the Type 3 driver embeds a text message in there as well.

Charles


Charles Greer
Software Systems Analyst
County of Sonoma, Geographic Information Systems
2615 Paulin Drive
Santa Rosa, CA 95403
707-565-3991 FAX 707-565-2187
[login to unmask email]


>>> [login to unmask email] 12/27/05 11:34 AM >>>
Hey guys........I'm an old mainframe dinosaur trying to adjust to the
new millennium and I need some help. Back in the old days when I saw an
DB2 SQLCODE (or IDMS Error Status) I could go to my handy reference and
eventually figure out what was going on. Now we have a
WebSphere/JAVA/JDBC application accessing DB2 for z/OS that "throws"
exceptions which apparently the application is not "catching". I'm
trying to help diagnose some of the problems but not all of the
exceptions show the SQLCODE/SQLSTATE that caused it.

Can anyone tell me where I might find a document that maps DB2
SQLCODES/SQLSTATES to the JAVA exceptions being thrown by the JDBC
driver or is it not that simple?



***********************************
CONFIDENTIALITY STATEMENT:
This e-mail and any attachments are intended only for those to which it
is addressed and may contain information which is privileged,
confidential and prohibited from disclosure and unauthorized use under
applicable law. If you are not the intended recipient of this e-mail,
you are hereby notified that any use, dissemination, or copying of this
e-mail or the information contained in this e-mail is strictly
prohibited by the sender. If you have received this transmission in
error, please return the material received to the sender and delete all
copies from your system.



------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm


***********************************
CONFIDENTIALITY STATEMENT:
This e-mail and any attachments are intended only for those to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure and unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jim Irwin

Re: JAVA SQLException and SQLWarning
(in response to Jim Irwin)
Myron, My dilemma here is that this app was built using WAD by people
that didn't necessarily understand what it was doing. There was very
little error handling in the beginning. In fact, I was originally told
that they had no way of knowing what sql the application was sending to
DB2. I know we are doing this backward but if I can find out what the
JAVA exceptions map to in DB2 I can at least point them in the right
direction.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Myron Miller
Sent: Tuesday, December 27, 2005 1:45 PM
To: [login to unmask email]
Subject: Re: [DB2-L] JAVA SQLException and SQLWarning

Jim,
Somewhere in the Websphere exception log should be the actual
SQLSTATE/SQLCODE being thrown as well. I've never seen a case if the
person had
a finally section that captured the SQL exceptions that didn't give the
proper
SQL code or state. Your java programmer needs to capture these just
like any
other exception.

Myron

--- "Irwin, Jim" <[login to unmask email]> wrote:

> Hey guys........I'm an old mainframe dinosaur trying to adjust to the
> new millennium and I need some help. Back in the old days when I saw
an
> DB2 SQLCODE (or IDMS Error Status) I could go to my handy reference
and
> eventually figure out what was going on. Now we have a
> WebSphere/JAVA/JDBC application accessing DB2 for z/OS that "throws"
> exceptions which apparently the application is not "catching". I'm
> trying to help diagnose some of the problems but not all of the
> exceptions show the SQLCODE/SQLSTATE that caused it.
>
> Can anyone tell me where I might find a document that maps DB2
> SQLCODES/SQLSTATES to the JAVA exceptions being thrown by the JDBC
> driver or is it not that simple?
>
>
>
> ***********************************
> CONFIDENTIALITY STATEMENT:
> This e-mail and any attachments are intended only for those to which
it is
> addressed and may contain information which is privileged,
confidential and
> prohibited from disclosure and unauthorized use under applicable law.
If you
> are not the intended recipient of this e-mail, you are hereby notified
that
> any use, dissemination, or copying of this e-mail or the information
> contained in this e-mail is strictly prohibited by the sender. If you
have
> received this transmission in error, please return the material
received to
> the sender and delete all copies from your system.
>
>
>
>
------------------------------------------------------------------------
---------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select
> "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org.
> The IDUG List Admins can be reached at
[login to unmask email] Find
> out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm
>

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm


****************************
CONFIDENTIALITY STATEMENT:
This e-mail and any attachments are intended only for those to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure and unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

John McKown

Re: JAVA SQLException and SQLWarning
(in response to Jim Irwin)
> -----Original Message-----
> From: DB2 Data Base Discussion List
> [mailto:[login to unmask email] On Behalf Of Irwin, Jim
> Sent: Tuesday, December 27, 2005 3:07 PM
> To: [login to unmask email]
> Subject: Re: [DB2-L] JAVA SQLException and SQLWarning
>
>
> Myron, My dilemma here is that this app was built using WAD by people
> that didn't necessarily understand what it was doing. There was very
> little error handling in the beginning. In fact, I was
> originally told
> that they had no way of knowing what sql the application was
> sending to
> DB2. I know we are doing this backward but if I can find out what the
> JAVA exceptions map to in DB2 I can at least point them in the right
> direction.

Are you allowed to modify the application? If so, then you should be
able to use the Java code at:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DSNJVJ12/2.1.
18

and wrap it around their code to "catch" the JDBC errors. Or modify
their code to print the DB2 stuff as shown in the example code.

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Myron Miller

Re: JAVA SQLException and SQLWarning
(in response to John McKown)
Jim,
The problem is that 99% of the java exceptions don't relate to anything in
DB2. So you're facing an impossible task. You really need to modify the
application such as John McKown suggested and put in the finally section to
trap and write either the exception trace or the SQLCA data. Without one or
the other, you will be basically shooting in the dark unless you happen to have
a monitor on the mainframe that can trap all SQL and SQL exceptions and relate
it back to the requestor.

You are going to have to bit the bullet and get your developers to add some
error checking code into their programs. That's the long and short of it.

Myron

--- "Irwin, Jim" <[login to unmask email]> wrote:

> Myron, My dilemma here is that this app was built using WAD by people
> that didn't necessarily understand what it was doing. There was very
> little error handling in the beginning. In fact, I was originally told
> that they had no way of knowing what sql the application was sending to
> DB2. I know we are doing this backward but if I can find out what the
> JAVA exceptions map to in DB2 I can at least point them in the right
> direction.
>
> -----Original Message-----
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
> Behalf Of Myron Miller
> Sent: Tuesday, December 27, 2005 1:45 PM
> To: [login to unmask email]
> Subject: Re: [DB2-L] JAVA SQLException and SQLWarning
>
> Jim,
> Somewhere in the Websphere exception log should be the actual
> SQLSTATE/SQLCODE being thrown as well. I've never seen a case if the
> person had
> a finally section that captured the SQL exceptions that didn't give the
> proper
> SQL code or state. Your java programmer needs to capture these just
> like any
> other exception.
>
> Myron
>
> --- "Irwin, Jim" <[login to unmask email]> wrote:
>
> > Hey guys........I'm an old mainframe dinosaur trying to adjust to the
> > new millennium and I need some help. Back in the old days when I saw
> an
> > DB2 SQLCODE (or IDMS Error Status) I could go to my handy reference
> and
> > eventually figure out what was going on. Now we have a
> > WebSphere/JAVA/JDBC application accessing DB2 for z/OS that "throws"
> > exceptions which apparently the application is not "catching". I'm
> > trying to help diagnose some of the problems but not all of the
> > exceptions show the SQLCODE/SQLSTATE that caused it.
> >
> > Can anyone tell me where I might find a document that maps DB2
> > SQLCODES/SQLSTATES to the JAVA exceptions being thrown by the JDBC
> > driver or is it not that simple?
> >
> >
> >
> > ***********************************
> > CONFIDENTIALITY STATEMENT:
> > This e-mail and any attachments are intended only for those to which
> it is
> > addressed and may contain information which is privileged,
> confidential and
> > prohibited from disclosure and unauthorized use under applicable law.
> If you
> > are not the intended recipient of this e-mail, you are hereby notified
> that
> > any use, dissemination, or copying of this e-mail or the information
> > contained in this e-mail is strictly prohibited by the sender. If you
> have
> > received this transmission in error, please return the material
> received to
> > the sender and delete all copies from your system.
> >
> >
> >
> >
> ------------------------------------------------------------------------
> ---------
> > Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home
> > page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select
> > "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org.
> > The IDUG List Admins can be reached at
> [login to unmask email] Find
> > out the latest on IDUG conferences at
> http://conferences.idug.org/index.cfm
> >
>
> ------------------------------------------------------------------------
> ---------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
> page select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm
>
>
> ****************************
> CONFIDENTIALITY STATEMENT:
> This e-mail and any attachments are intended only for those to which it is
> addressed and may contain information which is privileged, confidential and
> prohibited from disclosure and unauthorized use under applicable law. If you
> are not the intended recipient of this e-mail, you are hereby notified that
> any use, dissemination, or copying of this e-mail or the information
> contained in this e-mail is strictly prohibited by the sender. If you have
> received this transmission in error, please return the material received to
> the sender and delete all copies from your system.
>
>
---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
> "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
> The IDUG List Admins can be reached at [login to unmask email] Find
> out the latest on IDUG conferences at http://conferences.idug.org/index.cfm
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jim Irwin

Re: JAVA SQLException and SQLWarning
(in response to Myron Miller)
Thanks to everyone for their input. I know that the application needs to
handle these errors but I have no control over the application
developers....I'm just trying to do what I can from our side to help the
project out.

On the plus side I'm getting a crash course in WebSphere/JAVA/DB2
interaction. Thanks again.


***********************************
CONFIDENTIALITY STATEMENT:
This e-mail and any attachments are intended only for those to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure and unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system.



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

John McKown

Re: JAVA SQLException and SQLWarning
(in response to Jim Irwin)
> -----Original Message-----
> From: DB2 Data Base Discussion List
> [mailto:[login to unmask email] On Behalf Of Irwin, Jim
> Sent: Wednesday, December 28, 2005 8:28 AM
> To: [login to unmask email]
> Subject: Re: [DB2-L] JAVA SQLException and SQLWarning
>
>
> Thanks to everyone for their input. I know that the
> application needs to
> handle these errors but I have no control over the application
> developers....I'm just trying to do what I can from our side
> to help the
> project out.
>
> On the plus side I'm getting a crash course in WebSphere/JAVA/DB2
> interaction. Thanks again.

Ah! Been there. "Please debug our problem for us. Don't ask us to do
anything to our code to help generate debugging output." Psychic
debugging our speciality!

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm