By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,279 Members | 1,680 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,279 IT Pros & Developers. It's quick & easy.

handling DB2 warnings

P: n/a

Hi,

This is a very general problem which iam sure application programmers
all over have faced.
How does one handle the warnings that DB2 issues ? Should they be
ignored or treated the same as errors (i.e. as failures).
Is there anything recommended by DB2 itself ?
As you well know it becomes very cumbersome when we start handling
specific warnings.

Appreciate your inputs.

Oct 5 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Vivek wrote:
Hi,

This is a very general problem which iam sure application programmers
all over have faced.
How does one handle the warnings that DB2 issues ? Should they be
ignored or treated the same as errors (i.e. as failures).
Is there anything recommended by DB2 itself ?
As you well know it becomes very cumbersome when we start handling
specific warnings.

Appreciate your inputs.
The most important warning is for +100 which is "row not found" or
"end of cursor on fetch", etc. In most cases, you need to handle
this in your application logic and act accordingly.

There are also warnings for arithmetic overflow, which probably only
need to be handled n certain situations where calculations are done in
the SQL, or when the columns/host variables are different sizes.

Most people ignore all other warnings.

Oct 5 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.