|
View previous topic :: View next topic
|
| Author |
Message |
bryan_lopez
New User
Joined: 01 Aug 2007
Posts: 1
Location: Mumbai
|
|
|
|
Hi all,
I am new to DB2 could you please provide me some abends that we face quite often. I am looking for list of top 20 abends.
Thanks  |
|
| Back to top |
|
 |
raviprasath_kp
Warnings : 1
New User
Joined: 20 Feb 2005
Posts: 65
Location: chennai
|
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
bryan_lopez,
as you are new to DB2- you don't have ABENDs in DB2; SQL failures are reported as negative SQLCODEs
- there is no top twenty. It all depends on how diligent you are with your syntax and attention to detail
The link that raviprasath_kp gave you is a list of all negative SQLCODEs for vsn 5 of DB2 for OS390. Depending upon the vsn of DB2 and the operating system that is running in your shop, you need to either bookmark or download the appropriate Message and Codes manual for your DB2 vsn. This link displays a list of Messages and Codes for all of IBM's products. i.e. DB2, MQS, CICS, etc.... |
|
| Back to top |
|
|
TG Murphy
Active User
Joined: 23 Mar 2007
Posts: 148
Location: Ottawa Canada
|
|
|
|
SQLCODE -911 has to be near the top of the list.
deadlocks, timeouts, techniques used to avoid them could fill a book.
SQLCODE -805 ranks up near the top.
We have a document that deals exclusively with all the different situations that can trigger an SQLCODE -805.
Mastering the issues behind -911 and -805 will take you far more time than all the other nasty SQLCODEs combined.
The only abend I can think of is AD2Z which happens when DB2 attempts to issue an automatic SYNCPOINT ROLLBACK in response to SQLCODE -911 while executing in CICS DPL subset. SYNCPOINT ROLLBACK is not allowed in DPL subset...
If your CICS applications don't not issue LINKs to remote regions then you'll never see AD2Z... |
|
| Back to top |
|
|
md nisar
New User
Joined: 14 Sep 2007
Posts: 2
Location: pune
|
|
|
|
000 for successfull
100 end of Record or not found
-181 invalid date format
-205 column-name is not a column of table
-305 null indicator required
-313 host variable mismatch
-602 too many columns specified in create index
-805 plan or program not found
-811 cursor not declare or too many rows selected
-818 times stamp mismatch in the load module and bind
-905 unsuccessful execution due to resource limit exceeded,
-911 deadlock with timeout with auto rolled back
-913 deadlock with timeout wih manual rooled back |
|
| Back to top |
|
|
|
|
