常見CICS和DB2錯誤碼

 
CICS ABEND CODES
 
Following are the common ABEND codes related to exceptional conditions.
 
APIA           - ERROR 
AEID                 - EOF
AEIM        - NOTFND   
AEIN           - DUPKEY
AEIP                 - INVREQ
AEIQ         - IOERR
AEIR         - NOSPACE 
AEIS                 - NOTOPEN
AEIT                 - ENDFILE
AEIV         - LENGERR
AEIW        - QZERO  
AEIZ                 - ITEMERR
AE19                 - MAPFAIL  
AEYH          - QIDERR
ABM0             - The map name is misspelled either in the program or in the mapset, or the program specifies the wrong mapset.
ASRA              - Occurs when a program tries to perform an operation that isn’t allowed by the H/W
ABMB   -      Cursor positioning beyond the limit of O/P device
ABM0    -      Specified map isn’t in the mapset
AICA     -      Task exceeded the execution time (task was looping)
APCT    -      Program could not be found
ASRB    -      Operating System abend; CICS able to abend the transaction and                              continue processing
 
DB2 SQLCODES
 
+100       Row not found for FETCH, UPDATE or DELET
 
-117 No of INSERT values is not the same as the columns in the table
 
-119 A Column identified in HAVING clause is not included in the GROUP BY clause                   
-181 The string representation of a datetime value not a valid datetime value.
             
-502 The cursor in OPEN CURSOR is already open.
 
-503      A column cannot be updated because it is not identified in the UPDATE clause of the SELECT statement of the cursor.
 
-601      The name of the object to be created is identical to an already existing object.
 
-811      The result of an embedded SELECT statement is a table of more than one row, or the result of the subquery of a basic predicate is more than one subquery of a basic predicate is more than one value. Use cursor to solve the problem.
 
-818      Precompile TIMESTAMP and bind TIMESTAMP are different. Check whether LEVEL option is there in the PRECOMPILE parameters
 
-904      Unavailable resource
 
-913)    Roll back because of deadlock or timeout.
 
-922)    DB2 connection could not be established.
 
-927)    Check if DB2 is up.
 
-551      No privilege to perform the intended operation. Some of the reasons for this SQL code are as follows:
- Object may not be existing.
- You probably have given an unqualified name, in which case DB2 qualifies with default values.
 
如果遇到了沒在本表中列出的SQLCODE,可以使用如下命令獲取聯機幫助:
       TSO SQLCODE <SQLCODE Value>
 
E.g. TSO SQLCODE -305
發表評論
所有評論
還沒有人評論,想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章