SQLCODE groups

Gregor =?UTF-8?B?S292YcSN?=

Hi!

I was searching through DB2 InfoCenter, but didn't find an answer to my
question:
When I get an SQLCODE from an SQL command (ADMIN_CMD for example) when I
want to know what this code means; is it a warning, error, ....

Best regards,
Kovi

--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

Jul 11 '07 #1

Knut Stolze

Gregor Kova� wrote:

Hi!

I was searching through DB2 InfoCenter, but didn't find an answer to my
question:
When I get an SQLCODE from an SQL command (ADMIN_CMD for example) when I
want to know what this code means; is it a warning, error, ....

With SQLCODEs, you simply remove the sign and prepend "SQL" in front. This
gives you the message id corresponding to this SQLCODE. For example, if
you have SQLCODE = -104, the corresponding message is SQL104 (or SQL0104 if
you want to pad with leading '0's.)

p.s: It may be that there are exceptions to this rule; but so far I haven't
encountered any.
p.p.s: There is work on the way to get such information on a programmatical
way from DB2 itself.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

Jul 11 '07 #2

Serge Rielau

Further: negative numbers are errors, positive numbers are warnings.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Jul 11 '07 #3

Gregor =?UTF-8?B?S292YcSN?=

Hi!

So, what Knut ans Serge are saying...
For example, with IMPORT I get in message file:
SQL3149N "1" rows were processed from the input file. "0" rows were
successfully inserted into the table. "1" rows were rejected.

And since this is code 3149 0, should I consider this is a warning?

Best regards,
Kovi

Gregor Kova� wrote:

Hi!

I was searching through DB2 InfoCenter, but didn't find an answer to my
question:
When I get an SQLCODE from an SQL command (ADMIN_CMD for example) when I
want to know what this code means; is it a warning, error, ....

Best regards,
Kovi

--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

Jul 11 '07 #4

Knut Stolze

Gregor Kova� wrote:

Hi!

So, what Knut ans Serge are saying...
For example, with IMPORT I get in message file:
SQL3149N "1" rows were processed from the input file. "0" rows were
successfully inserted into the table. "1" rows were rejected.

And since this is code 3149 0, should I consider this is a warning?

The message id is SQL3149. To get the SQLCODE for this message (if it has
one), you can simply run:

$ db2 "? sql3149"

This particular message is _not_ associated with a SQLCODE.

However, there is another piece of information encoded in the message id.
The last character of the message id classifies the error like this:

'C' - critical error
'N' - normal error
'W' - warning
'I' - informational message

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

Jul 11 '07 #5

Gregor =?UTF-8?B?S292YcSN?=

Hi!

Great, this is exactly what I wanted to know. :))
Is there a page in DB2 InfoCenter where this is stated?

Best regards,
Kovi

Knut Stolze wrote:

Gregor Kova� wrote:

>Hi!

So, what Knut ans Serge are saying...
For example, with IMPORT I get in message file:
SQL3149N "1" rows were processed from the input file. "0" rows were
successfully inserted into the table. "1" rows were rejected.

And since this is code 3149 0, should I consider this is a warning?

The message id is SQL3149. To get the SQLCODE for this message (if it has
one), you can simply run:

$ db2 "? sql3149"

This particular message is _not_ associated with a SQLCODE.

However, there is another piece of information encoded in the message id.
The last character of the message id classifies the error like this:

'C' - critical error
'N' - normal error
'W' - warning
'I' - informational message

--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

Jul 11 '07 #6

Jeroen van den Broek

On Jul 11, 2:58 pm, Gregor Kova <gregor.ko...@mikropis.siwrote:

Hi!

Great, this is exactly what I wanted to know. :))
Is there a page in DB2 InfoCenter where this is stated?

Best regards,
Kovi

Knut Stolze wrote:

Gregor Kova wrote:

Hi!

So, what Knut ans Serge are saying...
For example, with IMPORT I get in message file:
SQL3149N "1" rows were processed from the input file. "0" rows were
successfully inserted into the table. "1" rows were rejected.

And since this is code 3149 0, should I consider this is a warning?

The message id is SQL3149. To get the SQLCODE for this message (if it has
one), you can simply run:

$ db2 "? sql3149"

This particular message is _not_ associated with a SQLCODE.

However, there is another piece of information encoded in the message id.
The last character of the message id classifies the error like this:

'C' - critical error
'N' - normal error
'W' - warning
'I' - informational message

http://publib.boulder.ibm.com/infoce...c/r0002159.htm

http://publib.boulder.ibm.com/infoce...c/c0mintro.htm

HTH.

--
Jeroen

Jul 11 '07 #7

Serge Rielau

http://publib.boulder.ibm.com/infoce...c/c0mintro.htm

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Jul 11 '07 #8